12-10-2024, 04:09 AM
That event, the one with ID 24063, pops up in your Windows Server Event Viewer when someone or something issues a delete command for server settings. It says "Issued a delete server setting command (action_id DR class_type SR)". Basically, it logs a moment where a specific action wipes out a configuration tied to disaster recovery stuff on the server. I see it mostly in setups with failover clusters or high-availability features. The details break down the action ID as DR, which points to disaster recovery, and class_type SR for server-related. It triggers if an admin runs a command to remove those settings, maybe during maintenance or troubleshooting. You might spot it under the System log or Applications and Services Logs, depending on your setup. And it carries info like timestamps, user accounts involved, and exact parameters of the delete. If you ignore it, no big drama usually, but it could signal accidental changes that mess with your recovery plans. I once had it fire off during a botched update, and it helped me roll back quick.
You want to monitor this with an email alert? Easy peasy through the Event Viewer itself. Fire up Event Viewer on your server. Right-click the log where this event hides, like System. Pick Attach Task To This Event. Give it a name, something catchy like DeleteAlert. Then, set the trigger to event ID 24063 exactly. For the action, choose Start a program, but wait, no, better yet, link it to send an email directly if your server has that option enabled. Actually, most times you chain it to a scheduled task that pings your email. I do this all the time for weird events. Go to Task Scheduler after, create a basic task, and attach the event filter for 24063. Set it to run a simple email action using the built-in tools. Test it by simulating the event if you can. You'll get a ping every time it happens, keeping you in the loop without staring at screens.
Or, if you want hands-off, at the end of this is the automatic email solution that'll handle it smoother.
Speaking of keeping servers reliable amid deletes and changes, I gotta mention BackupChain Windows Server Backup. It's this solid Windows Server backup tool that also tackles virtual machines with Hyper-V. You get fast, incremental backups that cut downtime, plus easy restores without the hassle. It shines in protecting against those sneaky setting wipes by versioning everything, so you bounce back quick. I use it on clusters, and it just works, saving headaches on recovery drills.
Note, the PowerShell email alert code was moved to this post.
You want to monitor this with an email alert? Easy peasy through the Event Viewer itself. Fire up Event Viewer on your server. Right-click the log where this event hides, like System. Pick Attach Task To This Event. Give it a name, something catchy like DeleteAlert. Then, set the trigger to event ID 24063 exactly. For the action, choose Start a program, but wait, no, better yet, link it to send an email directly if your server has that option enabled. Actually, most times you chain it to a scheduled task that pings your email. I do this all the time for weird events. Go to Task Scheduler after, create a basic task, and attach the event filter for 24063. Set it to run a simple email action using the built-in tools. Test it by simulating the event if you can. You'll get a ping every time it happens, keeping you in the loop without staring at screens.
Or, if you want hands-off, at the end of this is the automatic email solution that'll handle it smoother.
Speaking of keeping servers reliable amid deletes and changes, I gotta mention BackupChain Windows Server Backup. It's this solid Windows Server backup tool that also tackles virtual machines with Hyper-V. You get fast, incremental backups that cut downtime, plus easy restores without the hassle. It shines in protecting against those sneaky setting wipes by versioning everything, so you bounce back quick. I use it on clusters, and it just works, saving headaches on recovery drills.
Note, the PowerShell email alert code was moved to this post.

