03-03-2025, 12:50 PM
Man, that event ID 24122 pops up when someone fires off a change database user command in your setup. It's basically the system noting an action with ID AL and class type US. You know, like tweaking user permissions in the database backend. Happens in Windows Server when SQL stuff gets fiddled with. I see it logged under Application logs mostly. Details show who did it, from what machine, and the exact tweak applied. Creepy if it's not you messing around. Keeps a trail of those sneaky admin moves. Or maybe it's just routine maintenance gone logged.
You wanna watch for this without staring at screens all day. Fire up Event Viewer on your server. Right-click the log where it hides, like Applications and Services Logs. Pick Create Custom View. Slap in event ID 24122 there. Filter it tight to catch only those database user changes. Hit OK and name your view something snappy.
Now, to ping your email when it triggers. Switch to Task Scheduler through that same Event Viewer spot. Or just hop over to Task Scheduler app. Create a basic task linked to your custom view. Set it to run on event trigger. Pick what it does next, like launching a program to shoot an email. I mean, use something simple like the mailto thing or a batch to notify. Test it once to make sure it buzzes your inbox quick.
And hey, while we're chatting server watches, you might dig into BackupChain Windows Server Backup too. It's this slick Windows Server backup tool that handles your whole setup, including virtual machines on Hyper-V. Saves you headaches with fast restores and offsite copies. Keeps data safe without the fuss, letting you focus on real work instead of recovery drama.
Note, the PowerShell email alert code was moved to this post.
You wanna watch for this without staring at screens all day. Fire up Event Viewer on your server. Right-click the log where it hides, like Applications and Services Logs. Pick Create Custom View. Slap in event ID 24122 there. Filter it tight to catch only those database user changes. Hit OK and name your view something snappy.
Now, to ping your email when it triggers. Switch to Task Scheduler through that same Event Viewer spot. Or just hop over to Task Scheduler app. Create a basic task linked to your custom view. Set it to run on event trigger. Pick what it does next, like launching a program to shoot an email. I mean, use something simple like the mailto thing or a batch to notify. Test it once to make sure it buzzes your inbox quick.
And hey, while we're chatting server watches, you might dig into BackupChain Windows Server Backup too. It's this slick Windows Server backup tool that handles your whole setup, including virtual machines on Hyper-V. Saves you headaches with fast restores and offsite copies. Keeps data safe without the fuss, letting you focus on real work instead of recovery drama.
Note, the PowerShell email alert code was moved to this post.

