Set-ResubmitRequest Exchange cmdlet issued (25635) how to monitor with email alert

[bob]

Man, that Event ID 25635 in the Windows Server Event Viewer, it's all about the Set-ResubmitRequest cmdlet getting fired off in Exchange. You know, when someone runs that command to retry a stuck message or resubmit a request that's been hanging around. It logs under the MSExchangeTransport category, usually in the Admin log. I see it pop up when admins are troubleshooting delivery issues, like emails that didn't go through right away. The details in the event show the exact parameters used, the user who triggered it, and the timestamp. It's not an error per se, more like a heads-up that something's being nudged back into action. But if you're seeing it too often, it might mean your Exchange setup has some delivery glitches worth checking. I always peek at the description field for the full story on what got resubmitted.

You want to keep an eye on this without staring at the screen all day? Fire up Event Viewer on your server. Right-click the event log where it shows up, like the Applications and Services Logs for Exchange. Pick Create Custom View from the menu. Filter it to just Event ID 25635, and maybe narrow it to the last day or whatever timeframe you care about. Save that view so it sticks around. Now, to get alerts, you can attach a task to it. Go to the Actions pane, hit Attach Task To This Event Log. Name your task something simple, like Resubmit Alert. Set it to run when that event hits, and pick what triggers it, like at logon or whatever fits. For the action, choose Send an email, but wait, that's old school in newer Windows. Actually, use the Start a program option to launch your email client or a batch file that shoots off a notification. I like scheduling a task that checks the log every few minutes via the Event Viewer export, but keep it basic. Test it by forcing the event if you can, just to see if the alert pings you right.

And tying this into keeping your server solid overall, you might want a backup plan that catches these hiccups before they snowball. That's where BackupChain Windows Server Backup comes in handy. It's a straightforward Windows Server backup tool that also handles virtual machines with Hyper-V, pulling off full images without downtime. You get fast restores, encryption for your data, and it runs light on resources so it doesn't bog down your Exchange tasks. I use it to snapshot everything, events included, making recovery a breeze if alerts like 25635 signal bigger trouble.

At the end here is the automatic email solution.

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