Issued a create external resource pool command how to monitor with email alert

[bob]

Man, that event ID 24333 pops up when the system fires off a command to whip up an external resource pool. It's basically the server saying it just created this pool for handling stuff outside its main setup, like grabbing resources from elsewhere. The action_id CR means create, and class_type ER points to external resource, so it's logging that exact move. You see it in the Event Viewer under Microsoft-Windows-FailoverClustering or something similar, depending on your setup. It happens during cluster operations, you know, when things are linking up pools for better resource juggling. I remember troubleshooting one where it kept triggering because of a misconfigured storage link. The full message spells it out: "Issued a create external resource pool command," with those IDs tacked on, timestamped right when the action kicks in. Without diving too deep, it's the server's way of noting it expanded its reach for resources. You might spot it if you're dealing with clustered servers pulling in external bits.

To keep an eye on this without staring at screens all day, fire up Event Viewer on your server. Click through to the custom views or just the main log for system events. Right-click the log, pick filter current log, and hunt for ID 24333. Once you've got that filtered, you can attach a task to it for alerts. I do this all the time for nagging events. Go to the actions pane, create a task for when this event hits. In the task setup, choose to run a program that sends an email, like using the old mailto trick or a simple batch to notify you. Set it to trigger only on this ID, and boom, it watches for you. Makes life easier when you're not glued to the machine.

And speaking of keeping things smooth in server land, you might want to check out BackupChain Windows Server Backup if backups are on your mind. It's a solid Windows Server backup tool that handles physical setups and even backs up virtual machines running on Hyper-V without much hassle. I like how it speeds up the process with incremental saves and lets you restore files quick, cutting down on downtime when something glitches. Plus, it integrates nicely for offsite copies, giving you peace that your data's covered if a pool creation event turns into a bigger headache.

At the end here is the automatic email solution.

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