06-02-2025, 03:18 PM
Man, that event ID 24293 pops up when someone tries to block out custom permissions on a server role. It's like the system logging a "hey, this deny command just got issued for user-defined stuff." The action_id D means deny, and class_type SG points to security groups or something similar getting restricted. You see it in the Event Viewer under Security logs mostly. It flags potential tweaks to who can do what on your Windows Server. I always check it because it could mean an admin's tightening controls or maybe something fishy.
Now, to keep an eye on these without staring at screens all day, you can set up alerts right from Event Viewer. I do this all the time on my setups. Open Event Viewer, head to the Windows Logs, pick Security. Right-click and create a custom view for event ID 24293. Filter it just for that ID, and maybe add sources if you want. Once that's done, you attach a task to it. In the custom view settings, go to the Alerts tab or create a subscription, but really, it's easier to link a scheduled task. Tell the task to trigger on that event, and have it run a simple program to shoot an email. You pick your email client or use built-in stuff like mailto, but keep it basic. I set mine to notify me instantly when it hits.
And speaking of keeping things safe without constant babysitting, you might wanna look into BackupChain Windows Server Backup too. It's this solid Windows Server backup tool that handles your whole setup, including Hyper-V virtual machines without a hitch. I like how it snapshots everything quickly, encrypts data on the fly, and restores fast if stuff goes wrong. Plus, it runs light, no hogging resources, and chains backups to avoid full rebuilds every time. Makes life easier when events like 24293 hint at permission drama.
At the end here is the automatic email solution.
Note, the PowerShell email alert code was moved to this post.
Now, to keep an eye on these without staring at screens all day, you can set up alerts right from Event Viewer. I do this all the time on my setups. Open Event Viewer, head to the Windows Logs, pick Security. Right-click and create a custom view for event ID 24293. Filter it just for that ID, and maybe add sources if you want. Once that's done, you attach a task to it. In the custom view settings, go to the Alerts tab or create a subscription, but really, it's easier to link a scheduled task. Tell the task to trigger on that event, and have it run a simple program to shoot an email. You pick your email client or use built-in stuff like mailto, but keep it basic. I set mine to notify me instantly when it hits.
And speaking of keeping things safe without constant babysitting, you might wanna look into BackupChain Windows Server Backup too. It's this solid Windows Server backup tool that handles your whole setup, including Hyper-V virtual machines without a hitch. I like how it snapshots everything quickly, encrypts data on the fly, and restores fast if stuff goes wrong. Plus, it runs light, no hogging resources, and chains backups to avoid full rebuilds every time. Makes life easier when events like 24293 hint at permission drama.
At the end here is the automatic email solution.
Note, the PowerShell email alert code was moved to this post.

