Comments on: Wondering when AD CMDLETS 1.2.2 will ship? http://www.bobbobel.com/wondering-when-ad-cmdlets-122-will-ship/ "Anyone can hold the helm when the sea is calm." - Syrus Publilius Sat, 10 Sep 2011 16:57:32 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: rbobel http://www.bobbobel.com/wondering-when-ad-cmdlets-122-will-ship/comment-page-1/#comment-185 rbobel Wed, 17 Jun 2009 14:51:02 +0000 http://www.bobbobel.com/?p=321#comment-185 Should be (!(userAccountControl:1.2.840.113556.1.4.803:=2)) Should be (!(userAccountControl:1.2.840.113556.1.4.803:=2))

]]> By: Rick Sheikh http://www.bobbobel.com/wondering-when-ad-cmdlets-122-will-ship/comment-page-1/#comment-170 Rick Sheikh Thu, 11 Jun 2009 13:50:43 +0000 http://www.bobbobel.com/?p=321#comment-170 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. 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.

]]>