As I remember, I used to just do a net user *%username% */domain | find "*groupname*"
and checking for the errorlevel. Pretty crude but always seemed to work. Doubtless the list bods will have some more elegant ways of doing it :-) Group Policy client extension is available as an update via WSUS now, if that helps you. 2009/12/14 RM <[email protected]> > We haven't rolled out the GP Prefs client. It would take a while to get > it out there. We'll need a solution rather soon. > > How do you leverage NET USER to check group memberships? Did you mean NET > GROUP, and if so, do you leverage the FIND command followed by checking the > errorlevel? > > Thanks for your help! > RM > > > > On Mon, 14 Dec 2009 15:35 +0000, "James Rankin" <[email protected]> > wrote: > > Bin your logon scripts, and use Group Policy Preferences. Vastly easier. > > You can use net user rather than ifmember if you want to use native Windows > commands in logon scripts. I'd still go the Group Policy Preferences route > though > > 2009/12/14 RM <[email protected]> > > My boss wants to add some intellegence to our logon scripts with > IFMEMBER. I had planned to use Group Policy user logon scripts. > > Is IFMEMBER still kosher on modern Windows networks? I know it's pretty > old technology... > > Thx, > RM > > > > > > > > > > > -- > "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into > the machine wrong figures, will the right answers come out?' I am not able > rightly to apprehend the kind of confusion of ideas that could provoke such > a question." > > > > > > > > > > > > -- "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into the machine wrong figures, will the right answers come out?' I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question." ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
