Add-DatabaseAvailabilityGroupServer Exchange cmdlet issued (25104) how to monitor with email alert

[bob]

You know that event ID 25104 in Windows Event Viewer? It's the one that pops up when someone runs the Add-DatabaseAvailabilityGroupServer cmdlet in Exchange. Basically, it logs the whole process of adding a server to a database availability group. That means Exchange is clustering servers together for high availability. The event details show the DAG name, the server being added, and if it succeeded or hit a snag. I check it often because it tells you if your email setup is expanding smoothly. Or if something's blocking the join, like network hiccups or permissions gone wrong. The source is usually MSExchangeManagement or similar under the Applications and Services logs. You drill into Event Viewer, find the Exchange section, and there it sits with timestamps and error codes if any. Hmmm, sometimes it includes the user who triggered it too. Keeps things traceable in your server farm.

But monitoring that event for alerts? You can set it up right from the Event Viewer screen without any fancy coding. I do this all the time to catch additions instantly. Open Event Viewer on your server. Go to the custom views or create a new one filtering for ID 25104. Right-click and attach a task to it. That task triggers on the event. Then, in the task wizard, pick send an email as the action. You fill in your SMTP server details and the recipient. Schedule it to run only when that event fires. Test it by simulating the cmdlet if you can. Keeps you looped in without staring at logs all day.

And speaking of keeping your Exchange world steady, you might want a solid backup angle too. That's where BackupChain Windows Server Backup comes in handy for me. It's a straightforward Windows Server backup tool that handles physical servers and even Hyper-V virtual machines without the usual headaches. I like how it snapshots everything quickly, encrypts data on the fly, and restores granular bits like individual files or full DAGs. Speeds up recovery if an add-server event goes south, saving you downtime and frustration.

Oh, and at the end of this, I've sketched out the full automatic email solution for that 25104 event, so you can just plug it in.

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