http://blogs.technet.com/b/jhoward/archive/2005/05/26/405400.aspxI received an email overnight asking about greyed out settings in the local security policy on a newly installed Windows Server 2003 machine. In my group policy session on Tuesday, I was talking around this whole area, and the reason for it is relateden-GBTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.technet.com/b/jhoward/archive/2005/05/26/405400.aspx#409331Wed, 17 Aug 2005 12:11:02 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:409331Mohammadi also have the same problem with the member servers in windows 2003 domain it alwasys effect the local security policy for the members, there is any way to isolate the policy from the domain?<div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=409331" width="1" height="1">http://blogs.technet.com/b/jhoward/archive/2005/05/26/405400.aspx#407929Wed, 20 Jul 2005 05:14:46 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:407929DKWindows 2003 server - I have edited the Default Domain Policy - password complexity and password age - I see it is affecting machines in the domain that log on locally. Is there a way to stop this policy from affecting local accounts on local machines?<div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=407929" width="1" height="1">