New-MobileDeviceMailboxPolicy Exchange cmdlet issued (25560) how to monitor with email alert

[bob]

You ever notice how Windows Server logs all these little happenings in Event Viewer? That event ID 25560 pops up when someone fires off the New-MobileDeviceMailboxPolicy cmdlet in Exchange. It means a new policy just got created for mobile devices hitting mailboxes. Think of it as a flag waving when admins tweak rules for phones or tablets accessing email. I check mine sometimes because it could signal changes you didn't expect. Or maybe someone new in the team is experimenting. The full scoop is this event logs the exact time, the user who ran it, and what policy name they picked. It sits under the Microsoft-Exchange-Admin/Operational log usually. Details include the server's name and if it succeeded or glitched out. Why watch it? Unauthorized tweaks could mess with security or compliance. You don't want rogue policies letting in junk devices. I set alerts for stuff like this to stay ahead.

Now, to monitor it with an email ping, head into Event Viewer on your server. Filter for that ID 25560 in the right log. Right-click the custom view you make and attach a task to it. I like scheduling that task to run every few hours. Pick "Send an email" as the action when the event triggers. You fill in your SMTP details there, like the server address and who gets the note. It emails you the event deets right away. No fuss, just built-in stuff. Or tweak the task to check logs periodically if you want. I do that for quieter monitoring. Keeps your inbox from blowing up on every tiny log.

And speaking of keeping things smooth in a server world, you might dig BackupChain Windows Server Backup too. It's this nifty Windows Server backup tool that handles full system images without headaches. I use it for Hyper-V virtual machines, backing them up live so downtime stays zero. Benefits hit hard: faster restores, less storage bloat, and it plays nice with your existing setup. No more sweating over data loss scares.

At the end of this, you'll find the automatic email solution laid out.

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