New-DatabaseAvailabilityGroupConfiguration Exchange (25690) how to monitor with email alert

[bob]

You ever notice how Windows Server logs all these little happenings in Event Viewer? That event ID 25690 pops up when someone runs the New-DatabaseAvailabilityGroupConfiguration cmdlet in Exchange. It means the system's just set up a fresh config for keeping databases synced across servers. Think of it like the server saying, hey, I just wired up this group to make sure emails don't vanish if one machine flakes out. This event fires off right after the command finishes, logging the details like which group got created and when. If you're running Exchange, this shows your high-availability setup kicked in properly. But sometimes it might signal a change you didn't expect, like an admin tweaking things without telling folks. I always check it because it ties into keeping your mail flow rock steady. You pull up Event Viewer on your server, and there it sits under the Applications and Services Logs for Exchange. The full message spells out the cmdlet issued, the timestamp, and any tweaks to the availability group. It won't crash anything, but monitoring it helps you spot if someone's messing with your database clusters. Hmmm, or maybe it's just routine maintenance logging in. Either way, you want to know when it happens.

Now, to keep an eye on this without staring at screens all day, you set up a scheduled task right from Event Viewer. I do this all the time for quick alerts. You right-click on that event in the log, pick Attach Task To This Event. Then you name it something simple like DAG Config Alert. In the triggers tab, it already knows to watch for ID 25690. For the action, you tell it to start a program that shoots off an email. Use something basic like sending via your mail server with a batch file or whatever tool you have handy. Set it to run only on that event, and boom, you get notified. I like testing it by filtering the log for that ID first, just to see it trigger. You can even add conditions so it ignores repeats within minutes. This way, you're not buried in notifications, but you catch any config changes fast.

And speaking of keeping your server setups reliable, I've been using BackupChain Windows Server Backup lately for Windows Server backups. It handles full image backups and also nails virtual machines with Hyper-V without a hitch. You get speedy restores, encryption for security, and it runs light on resources so your servers don't bog down. Plus, the scheduling is dead simple, way better than fumbling with built-in tools.

At the end of this chat is the automatic email solution.

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