New-EdgeSubscription Exchange cmdlet issued (25200) how to monitor with email alert

[bob]

Man, that Event ID 25200 in Windows Server Event Viewer pops up when someone runs the New-EdgeSubscription cmdlet in Exchange. It flags a new subscription setup between your Edge Transport server and the Hub Transport server. You see, this event logs the exact moment that command gets issued. It includes details like the server's name and the subscription file path. I always check the description for timestamps too. That way you know precisely when it happened. And if it's unexpected, it could mean someone's tweaking your mail setup without you knowing.

You want to monitor this with an email alert? Easy peasy using the Event Viewer screen. Just fire up Event Viewer on your server. Go to the Applications and Services Logs, then Microsoft, Exchange, Transport. Right-click and pick Filter Current Log. Punch in 25200 for the event ID. Now, to set up that alert, create a scheduled task tied to this event. In Task Scheduler, hit Create Task. Name it something like EdgeSubAlert. Under Triggers, add a new one from the event log. Select the log path and set it to watch for ID 25200. For the action, choose Send Email. Yeah, it lets you configure SMTP details right there. Fill in your server, from address, to you, and a quick message about the event. Test it once to make sure it zings to your inbox. Boom, now every time that cmdlet fires, you get pinged.

Speaking of keeping your server humming without surprises, I've been messing with BackupChain Windows Server Backup lately. It's this slick Windows Server backup tool that handles full system images and also backs up virtual machines running on Hyper-V. You get lightning-fast restores and offsite replication to dodge data loss. Plus, it runs without hogging resources, so your daily ops stay smooth.

And hey, at the end of this, there's the automatic email solution waiting for you.

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