Group Policy

[Guest]

I have a Windows 2000 network with 2000 Pro and XP Pro Clients and a 2000
Server. When assigning a policy through Group Policy it does not effect any
XP Pro Clients. How can I fix this? Thank you.

 

[Richard G. Harper]

Check the event logs on both the server(s) and the client(s) to see why
group policy is not being applied to the XP clients.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[Ron Lowe]

I have a Windows 2000 network with 2000 Pro and XP Pro Clients and a 2000
Server. When assigning a policy through Group Policy it does not effect
any
XP Pro Clients. How can I fix this? Thank you.

As Richand says, check the event viewer as to why
group policy processing is being aborted.

If it's common to the XP clients, bot not the 2k clients,
then I suspect you have a DNS misconfiguration issue.

This will manifest itself as an inability to find the domain controller.
Does anything in the Event Viewer suggest that it can't find a
Domain Controller for your domain?

All the clients ( 2k and XP ) should be pointing to the
domain's internal DNS server, not an external ISP one.

 

[Guest]

I checked the event viewer and it had a 1202 event. "Security policies were
propagated with warning. 0x57 : The parameter is incorrect." I went through
the Microsoft Troubleshooting Event 1202's and found the following error.
"Configure Security Policy...
Configure password information.
Error 87: The parameter is incorrect.
Error configuring account lockout information."

I checked the lockout information and they are the same in Group Policy and
this log. Any suggestions? Thank you.