Discussion Locked

2000 policy not working on xp client

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We currently have a native windows 2000 server setup. We have win2000pro and winxp-pro clients. The Active Directory group policies work fine on the 2000 clients, but not on any of the xp clients. i.e. disable showing display control panel item, xp client users can open display properties and make changes to their desktops etc. Any ideas?

4 replies

by hailes103z

MS 307900
"Windows XP Professional supports a superset of the Group Policy features supported by Windows 2000. The new features are implemented through updated client-side extensions, .adm files, and an updated Group Policy snap-in.
This article describes how to upgrade a Windows 2000 Active Directory Group Policy object (GPO) to support the new features in Windows XP, and how to manage such objects.
If you upgrade an Active Directory GPO to support the new Windows XP policy settings, Windows 2000-based clients ignore any Windows XP-specific settings. This behavior occurs on a per-setting level; if a policy object contains a policy setting that is unsupported, all other supported policy settings from that policy object are applied.

To upgrade a Windows 2000 GPO, follow these steps on a Windows XP-based domain member:
Click Start, click Run, type mmc, and then click OK.
On the File menu, click Add/Remove Snap-in.
In the Add/Remove Snap-in dialog box, click Add.
In the Add Standalone Snap-in dialog box, click Group Policy, and then click Add.
In the Select Group Policy Object dialog box, Local Computer appears as the target object. Click Browse, select the GPO that you want to upgrade, and then click OK. Note that when you click Browse, a delay might occur while Windows searches for the policy objects in the domain.
Click Close.
Click OK."

But you should read the whole article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;307900&Product=winxp

by hailes103z

In short, remove the Software Restriction policies in both Computer and User Configuration/Windows Settings/Security Settings/Software Restriction. Your problem is in there.

by sysnetmgr

I have created the XP policy and have left Active Directory time to replicate etc. However, some of the policy seems to have taken effect and some of it hasn't. Is there something in the local policies on the XP client I need to change. Under the new policy, I cannot open MSAccess files, Publisher fails with not enough memory, I can still see the run command, start a dos prompt, C: drive is visible in my computer,the desktop has items I don't want to see, MSWORKS won't run - gets and error it wants to send to Microsoft. When I logon as local Administrator all the programs run ok. WHAT HAVE I MISSED?!

This discussion is closed to new replies.