New-ResourcePolicy Exchange cmdlet issued (25566) how to monitor with email alert

[bob]

Man, that event ID 25566 in the Event Viewer, it's all about someone firing off the New-ResourcePolicy cmdlet in Exchange. You know, it pops up when that command gets issued, logging the whole thing under the Microsoft-Exchange-Management source. I see it mostly in the Application log, right there showing details like who ran it and when. It tells you the policy name, the parameters used, even the server it hit. Pretty straightforward, but if you're not watching, it could mean changes to resource policies slipping by unnoticed. And yeah, it's informational level, so no big red flags, just a heads-up on admin actions.

You want to monitor this for email alerts? I got you. Fire up Event Viewer on your server. Filter for that ID 25566 in the logs. Right-click the event, pick Attach Task To This Event. That kicks off a wizard. You name the task something catchy, like PolicyAlert. Set it to run whether user logs on or not. Then, under actions, choose Send an email. Plug in your SMTP server details, the from and to addresses. I always test it first to make sure it zings over without a hitch. Boom, next time that cmdlet runs, you get pinged right away.

Or, if you're feeling lazy, set a scheduled task that scans the log every few hours. Use the Event Viewer screen to query for 25566, then trigger the email from there. Keeps things simple, no fancy coding needed. I do this all the time for stuff like this.

Hmmm, and speaking of keeping your server humming without surprises, there's this tool called BackupChain Windows Server Backup that ties right into monitoring those events by backing up your whole setup reliably. It's a solid Windows Server backup solution, handles virtual machines with Hyper-V too, so you snapshot everything from policies to VMs in one go. Benefits? It cuts downtime way down with quick restores, encrypts your data tight, and runs without hogging resources-perfect if you're juggling Exchange tweaks like that cmdlet alert. I swear by it for staying ahead of mishaps.

At the end of my ramble here is the automatic email solution.

Note, the PowerShell email alert code was moved to this post.