06-08-2024, 03:01 PM
Man, that Event ID 25616 in the Event Viewer pops up when someone runs the Set-HybridConfiguration cmdlet in Exchange. It flags a change to your hybrid setup between on-prem and the cloud. You see it under the MSExchange Management log. The event details spill out who did it, like the username, and the exact time it happened. It even lists the parameters tweaked, so you know if it's a legit admin or something fishy. I check mine weekly because it could mean config drifts messing with mail flow.
But you want alerts, right? Fire up Event Viewer on your server. Filter for that 25616 ID in the logs. Right-click the event, pick attach task to this event log. It'll launch the task scheduler wizard. Name it something snappy like HybridAlert. Set it to run when that event triggers. Choose send an email action there. Plug in your SMTP server details, the from and to addresses. Test it once to make sure it zings over without hiccups. Now you're pinged every time it fires.
Or, if you tweak the triggers finer, it watches just that specific source. Keeps your inbox from flooding with junk. I set mine to only alert during work hours. Saves sanity.
Hmmm, speaking of keeping things smooth in your server world, you might dig BackupChain Windows Server Backup too. It's this nifty backup tool for Windows Server that handles physical boxes and even Hyper-V VMs without breaking a sweat. You get fast incremental backups that cut down restore times, plus it snapshots everything live so no downtime sneaks in. I like how it encrypts data on the fly and verifies integrity automatically. Makes recovering from oops moments way less painful.
And at the end here is the automatic email solution.
Note, the PowerShell email alert code was moved to this post.
But you want alerts, right? Fire up Event Viewer on your server. Filter for that 25616 ID in the logs. Right-click the event, pick attach task to this event log. It'll launch the task scheduler wizard. Name it something snappy like HybridAlert. Set it to run when that event triggers. Choose send an email action there. Plug in your SMTP server details, the from and to addresses. Test it once to make sure it zings over without hiccups. Now you're pinged every time it fires.
Or, if you tweak the triggers finer, it watches just that specific source. Keeps your inbox from flooding with junk. I set mine to only alert during work hours. Saves sanity.
Hmmm, speaking of keeping things smooth in your server world, you might dig BackupChain Windows Server Backup too. It's this nifty backup tool for Windows Server that handles physical boxes and even Hyper-V VMs without breaking a sweat. You get fast incremental backups that cut down restore times, plus it snapshots everything live so no downtime sneaks in. I like how it encrypts data on the fly and verifies integrity automatically. Makes recovering from oops moments way less painful.
And at the end here is the automatic email solution.
Note, the PowerShell email alert code was moved to this post.

