Make sure to enclose your usernames in quotes if there are any spaces in them (not that many people do, but I've seen it done)
2009/3/4 John Hornbuckle <[email protected]> > I don’t know—that looks pretty simple. Easier than Michael’s method, I > think! > > > > (Er… No offense, Michael.) > > > > > > > > *From:* James Rankin [mailto:[email protected]] > *Sent:* Wednesday, March 04, 2009 7:51 AM > *To:* NT System Admin Issues > *Subject:* Re: Changing Account Settings en Masse > > > > They should be %a rather than %%a (doh) > > 2009/3/4 James Rankin <[email protected]> > > Try *for /f %%a in ('global "Domain Users" domainname^|find /v "$"') do > net user %%a /domain /passwordchg:yes > * > You will need a copy of global.exe from the old ResKit for this > > There are probably much better ways to do it tho :-) > > 2009/3/3 John Hornbuckle <[email protected]> > > We’ve previously not allowed users to change their own passwords; we’ve > handled that for them, and in Active Directory have their accounts > configured to prevent them from doing it. > > > > We’re implementing some new policies now, and in the near future users will > need to be able to change their own passwords. > > > > I feel sure there’s a way for me to enable this capability without having > to launch ADUC and bring up each user’s account individually. > > > > Could one of you command line commandos give me a point in the right > direction? > > > > > > > > John Hornbuckle > > MIS Department > > Taylor County School District > > www.taylor.k12.fl.us > > > > > > > > > > > > > > > > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
