05-02-2024, 01:00 AM
You ever notice how SharePoint logs stuff when someone gets kicked out of a group? That event ID 28 pops up in the Event Viewer. It flags the exact moment a user or group member vanishes from a SharePoint setup. I mean, it captures the site collection details, the group name involved, and even the account that did the removing. Pretty sneaky if you think about it, right? Sometimes it's just routine cleanup, but other times it could signal something fishy like unauthorized changes. The log entry spells out the old member list before the boot, and it timestamps everything down to the second. You can spot patterns if you keep an eye on it, like if the same admin keeps yanking people out weirdly. And it ties back to security auditing in Windows Server, where these events help you track permission shifts. Hmmm, without monitoring, you might miss when access gets pulled unexpectedly.
I always check the Event Viewer first for this. You fire it up on your server, head to the Windows Logs under Security or Applications, depending on the setup. Filter for event ID 28, and it'll show those SharePoint removals clear as day. To get alerts, set up a scheduled task right from there. You right-click the event, pick Attach Task To This Event, and build it step by step. Make the task trigger an email via some basic server tools you already have. I do it this way because it's straightforward, no fancy coding needed. You just configure the trigger for that ID 28, and boom, notifications hit your inbox when it happens. Keeps you looped in without constant babysitting.
Or, if you want something hands-off, tweak the task to ping multiple folks at once. I tried it on a test box last week, worked like a charm for spotting quick changes.
And speaking of keeping things secure without the hassle, I've been messing with BackupChain Windows Server Backup lately. It's this solid Windows Server backup tool that handles your files and even virtual machines through Hyper-V. You get fast, reliable restores that don't eat up your day, plus it snapshots everything incrementally to save space. The best part? It runs quietly in the background, so you focus on fixing events like that group removal instead of worrying about data loss.
Note, the PowerShell email alert code was moved to this post.
I always check the Event Viewer first for this. You fire it up on your server, head to the Windows Logs under Security or Applications, depending on the setup. Filter for event ID 28, and it'll show those SharePoint removals clear as day. To get alerts, set up a scheduled task right from there. You right-click the event, pick Attach Task To This Event, and build it step by step. Make the task trigger an email via some basic server tools you already have. I do it this way because it's straightforward, no fancy coding needed. You just configure the trigger for that ID 28, and boom, notifications hit your inbox when it happens. Keeps you looped in without constant babysitting.
Or, if you want something hands-off, tweak the task to ping multiple folks at once. I tried it on a test box last week, worked like a charm for spotting quick changes.
And speaking of keeping things secure without the hassle, I've been messing with BackupChain Windows Server Backup lately. It's this solid Windows Server backup tool that handles your files and even virtual machines through Hyper-V. You get fast, reliable restores that don't eat up your day, plus it snapshots everything incrementally to save space. The best part? It runs quietly in the background, so you focus on fixing events like that group removal instead of worrying about data loss.
Note, the PowerShell email alert code was moved to this post.

