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
- Microsoft Azure addes PowerShell Management
- TEC 2010 ActiveRoles User Group
- Quest AD PowerShell CMDLET BETA
- New IE View for Firefox posted
- Funny Google search
- Quick Connect for SAP Solutions – Tech Preview
- ActiveRoles Server added to 115 UK schools!
- Quick Connect and Quest Password Manager
- Quick Connect for Exchange Resource Forests
- Quick Connect 4.5 GA!
- Old School threats still persist
- SUN Identity Manager Customers SOL?
- Windows IT Pro Editor’s Choice: ActiveRoles
- Quick Connect 4.5 Goes Gold!
- How you can personally help Haiti




2 Responses
Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.
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))