DexterPOSH's Blog

I had posted a while back about the dreaded Checkbox of Doom which is a real pain in the Migration Scenarios where few AD Users might be marked as protected (Admincount = 1) but we don't really know which Group membership (marked as protected) might be causing this.  Shout out to MVP Ace Fekay for providing his insights on the topic :) It becomes a pain when the Groups are nested multiple levels and to determine which Portected Groups membership the User have which might be causing the Inheritance disabled (checkbox of doom). [Update]  Fellow friend and MVP Guido Oliveira highlighted that he had come across an issue where the AdminCount was once set to 1 when the User was part of a Protected Group. Once he was removed from the Group as per the Wiki Link shared at the end the AdminCount and the Inheritance will still be disabled so this Function can hunt those accounts too. Function is up for download @Technet : Click Here Read below on how to use the Script and...

Many of the Exchange Admins might already be familiar with the dreaded checkbox of doom , which causes issues with move request and Mobile devices. Post by MVP Tony Redmond here  explains this in detail. Scenario & the Problem at hand : When a User connects to the Exchange Server using his Mobile device, then after the authentication the Exchange Trusted Subsystem creates  msExchActiveSyncDevices Objects for the User. This will be evident from the below screenshot for one of the User in ADSI edit. Now what if the Exchange Trusted Subsystem doesn't have permissions on the AD User to create those Objects , all hell is let loose. This was the case I was tackling recently and searching each User in the Directory which had this checkbox of doom unchecked manually is not feasible (am lazy).