This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Local Group Change History

Is there a report, or can one be created, that can view the change history on local groups of servers, such as Administrators, Power Users, etc?

 

Ideally we would like to be able to get the list of all changes for all servers in a particular OU.

 

Any help would be appreciated!

 

Brandon

Parents
  • Yeah, this is the report I was working with, but you have to specifically add each server separately by their group (so servername\Administrators, servername\Power Users, etc), which can get tedious and servers can be missed since it's a manual process.

    We were hoping to be able to add an OU (which all our servers belong to) and then specify the groups we want to track changes for and then if a new server gets added to the OU it would automatically show in the next report, nothing manual needs to be done.

    We got around this by getting creative with wildcards, since most of our servers have a naming convention and start with the same 3 characters, so we could use this format: 3char*\Administrators, which would get all devices with the name that starts with those 3 characters' administrators group. It's not ideal, since we have to make sure we stick to the naming standards that we use, or we have to update the report if we do stray from it.
Reply
  • Yeah, this is the report I was working with, but you have to specifically add each server separately by their group (so servername\Administrators, servername\Power Users, etc), which can get tedious and servers can be missed since it's a manual process.

    We were hoping to be able to add an OU (which all our servers belong to) and then specify the groups we want to track changes for and then if a new server gets added to the OU it would automatically show in the next report, nothing manual needs to be done.

    We got around this by getting creative with wildcards, since most of our servers have a naming convention and start with the same 3 characters, so we could use this format: 3char*\Administrators, which would get all devices with the name that starts with those 3 characters' administrators group. It's not ideal, since we have to make sure we stick to the naming standards that we use, or we have to update the report if we do stray from it.
Children
No Data