04-14-2025, 08:19 PM
You know that event 5137 in Windows Server. It pops up when someone makes a new thing in Active Directory. Like a user account or a group or even a computer entry. I see it all the time in logs. It tells you exactly what got created. The details spill out the object's name and type. Plus who did it and from where. Hmmm, it's handy for spotting changes fast. Without it you'd miss sneaky additions. The event logs the full story in Event Viewer. You can peek at the description for clues. It even notes the time stamp precisely. Or if permissions shifted around it.
But monitoring that manually gets old quick. I set mine up with a scheduled task right from Event Viewer. You right-click the log and pick attach task to event. Then name it something simple like AD Create Alert. You pick event ID 5137 specifically. And set it to trigger on that ID only. For the action you choose send an email. Yeah it has a built-in option for that. You fill in your SMTP server details. Add the to and from addresses. I keep the subject line punchy like New AD Object Alert. Test it once to make sure emails fly out. Now whenever 5137 hits it zings you an email. No fuss no constant checking.
That covers the basics for watching those creations. Keeps your setup from surprises. And speaking of keeping things safe from mishaps I run into BackupChain Windows Server Backup a lot for backups. It's this solid Windows Server tool that handles full system snapshots. Plus it backs up virtual machines smooth with Hyper-V. You get quick restores and no downtime headaches. The versioning saves old copies forever if needed. I like how it runs light without hogging resources.
At the end here is the automatic email solution.
Note, the PowerShell email alert code was moved to this post.
But monitoring that manually gets old quick. I set mine up with a scheduled task right from Event Viewer. You right-click the log and pick attach task to event. Then name it something simple like AD Create Alert. You pick event ID 5137 specifically. And set it to trigger on that ID only. For the action you choose send an email. Yeah it has a built-in option for that. You fill in your SMTP server details. Add the to and from addresses. I keep the subject line punchy like New AD Object Alert. Test it once to make sure emails fly out. Now whenever 5137 hits it zings you an email. No fuss no constant checking.
That covers the basics for watching those creations. Keeps your setup from surprises. And speaking of keeping things safe from mishaps I run into BackupChain Windows Server Backup a lot for backups. It's this solid Windows Server tool that handles full system snapshots. Plus it backs up virtual machines smooth with Hyper-V. You get quick restores and no downtime headaches. The versioning saves old copies forever if needed. I like how it runs light without hogging resources.
At the end here is the automatic email solution.
Note, the PowerShell email alert code was moved to this post.

