We are getting very-very close to shipping version 1.2.2 of the Active Directory CMDLETS. This release will improve compatiblity with Quest’s PowerGUI graphical interface for PowerShell. Check back between now and friday for an announcment about our release.
Recent Posts
- Automatically Provisoning and Deprovison Postini
- Visual Studio Lightswitch
- PING Identity’s Cloud Identity Conference
- Apple Bumper – they are kidding right?
- Use PowerShell to easly find Obsolete Accounts
- AD CMDLETS 1.4 now live!
- Microsoft KIN – RIP
- ActiveRoles User’s Groups Denmark & Sweeden
- Google Apps goes mutli-domain
- Review, Droid HTC Incredible, My First Week
- Death of the Incandescent bulb
- Droid Incredible, Verizon 3 Week Backorder
- AD CMDLETS Version 1.4 (Early look)
- Federation Service 2.0, now Shipping
- Just-in-Time Access Provisioning




I have noticed that with newest version of QAD cmdlets (1.2.1), whereas the -enabled swtich allows you to search for enabled users only, I no longer seem to be able to use the simple old-school ldap switches i.e (-ldap “(!userAccountControl:1.2.840.113556.1.4.803:=2)), is there any reason that core functionality was not left there ?
Same is the case for finding disabled/enable computer accounts using the get-qadcomputer.
Should be (!(userAccountControl:1.2.840.113556.1.4.803:=2))