Recommendations to others considering GroupID:
I highly recommend using Active Directory's (Exchange created but unused by Microsoft) "Extension Attributes." The first 15 are called extensionAttribute1 - extensionAttribute15 plus another 30 under msExchExtensionAttribute16 -msExchExtensionAttribute45) keeping it automatically updated from your HR system that will help you 'slice and dice' your users into various groups. We use extension attribute items like GL Org, GL Department, GL Division, GL Program (i.e. sub-division), Job Code, Work Location Code, Health Coverage Plan, Retirement Plan, Sworn vs Civilian, Employee Type (Full, Part, Temporary), Bargaining Unit, Office 365 license type, FLSA Exempt vs FLSA Non Exempt, 457 plan participants, CDL drivers, Gender.) Imanami is such a powerful tool to standardize both your security groups and email distribution groups - with the ability to easily see who is in the group - and not have to use Powershell limited only for email distribution groups. Review collected by and hosted on G2.com.
What problems is GroupID solving and how is that benefiting you?
With Microsoft's original Query Based Distribution Group (QBDG) and then Dynamic Distribution Group (DDG) they were both only limited to email distribution groups - never tackling security groups :( With Imanami, we now are moving our (even existing) manually maintained security groups into Imanami's method of dynamically maintaining these security groups so that we don't have to change our NTFS permissions on our millions of files on our various file servers! We are also successfully using it for Office 365 SharePoint security reasons. Review collected by and hosted on G2.com.