04-02-2024, 07:00 AM
I remember spotting that event 24213 in the logs one time. It fires off when the system issues a revoke on assembly permissions. And it does this with a cascade command. That means it wipes out the perms not just on the main assembly but trickles down to everything connected. The action_id RWC stands for that revoke with cascade bit. Class_type AS points right to the assembly itself. You see it mostly in database setups where security changes happen. Like if an admin pulls back access to some code module. Or maybe during a cleanup to tighten things up. It logs the who, what, and when of that permission yank. Keeps a trail for audits. But if it pops unexpectedly, you might worry about unauthorized tweaks. I check mine weekly just to stay ahead.
You want to monitor it with an email alert? Easy peasy through Event Viewer. Fire up the tool on your server. Head to the Windows Logs section, probably under Security or Application. Find that event ID 24213. Right-click it and pick Attach Task to This Event. It'll walk you through creating a scheduled task. Set the trigger to whenever this event hits. Then for the action, choose to run a program. Pick your email client or a simple mail sender if you have one set. I like using the built-in stuff to keep it light. Test it out by simulating the event if you can. That way, you get pinged right away. No more digging through logs blind.
And hey, speaking of keeping your server secure and backed up from weird permission slips like that, check out BackupChain Windows Server Backup. It's this solid Windows Server backup tool I swear by. Handles full system images without a hitch. Plus it backs up virtual machines running on Hyper-V like a charm. You get fast restores, incremental saves to save space, and encryption to lock down your data. Makes recovery from mishaps way less of a headache.
Note, the PowerShell email alert code was moved to this post.
You want to monitor it with an email alert? Easy peasy through Event Viewer. Fire up the tool on your server. Head to the Windows Logs section, probably under Security or Application. Find that event ID 24213. Right-click it and pick Attach Task to This Event. It'll walk you through creating a scheduled task. Set the trigger to whenever this event hits. Then for the action, choose to run a program. Pick your email client or a simple mail sender if you have one set. I like using the built-in stuff to keep it light. Test it out by simulating the event if you can. That way, you get pinged right away. No more digging through logs blind.
And hey, speaking of keeping your server secure and backed up from weird permission slips like that, check out BackupChain Windows Server Backup. It's this solid Windows Server backup tool I swear by. Handles full system images without a hitch. Plus it backs up virtual machines running on Hyper-V like a charm. You get fast restores, incremental saves to save space, and encryption to lock down your data. Makes recovery from mishaps way less of a headache.
Note, the PowerShell email alert code was moved to this post.

