|
server
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Refresh/Reload Domain Sec Policy changesI just installed 2003 server and built AD, i went into Deflaut Domain
Security Policy MMC and changed the password requirements and complexity related settings to Not Defined so that i can use simple passwords. In the Deflaut Domain Controller Security Policy MMC all those settings are already set to Not Defined. I ran gpupdate and also tried right clicking on the server within the MMC and selecting Reload, I've even rebooted and when I go to add a user to AD, i get the message that it could not create the user due to possword restrictions and complexity requirements. event logs do not have anything that seem to relate.......any ideas? hey ill give this one a shot to (i am a noobie)........ maybe a gpupdate
/force command. i bet you just have to be patient if this does not work. Show quoteHide quote "Mark AMJ" wrote: > I just installed 2003 server and built AD, i went into Deflaut Domain > Security Policy MMC and changed the password requirements and complexity > related settings to Not Defined so that i can use simple passwords. In the > Deflaut Domain Controller Security Policy MMC all those settings are already > set to Not Defined. > > I ran gpupdate and also tried right clicking on the server within the MMC > and selecting Reload, I've even rebooted and when I go to add a user to AD, i > get the message that it could not create the user due to possword > restrictions and complexity requirements. > > event logs do not have anything that seem to relate.......any ideas? You need to disable this - not set it to "not defined". You can only set
these settings on GPOs linked to the domain. If you're interested in the why to the above, this article explains it: -- http://www.msresource.net/content/view/59/46/ -- Paul Williams Microsoft MVP - Windows Server - Directory Services http://www.msresource.net | http://forums.msresource.net I follow both of your suggestions! I disabled all the settings and then i ran
a gpupdate /force and it worked! thanks! Show quoteHide quote "Paul Williams [MVP]" wrote: > You need to disable this - not set it to "not defined". You can only set > these settings on GPOs linked to the domain. > > If you're interested in the why to the above, this article explains it: > -- http://www.msresource.net/content/view/59/46/ > > -- > Paul Williams > Microsoft MVP - Windows Server - Directory Services > http://www.msresource.net | http://forums.msresource.net > > > No problem!
-- Paul Williams Microsoft MVP - Windows Server - Directory Services http://www.msresource.net | http://forums.msresource.net |
|||||||||||||||||||||||