Used below method to apply win XP templates to Windows
2000 GPO using mmc.
Still have a problem. The MMC does not allow you to
browse for Group Policy Objects, it allows you to browse
for computers.
I'm wondering if there is a fix for this problem in
Windows XP?
Thanks,
Jim
****************************************************
Got from Newsgroup:
The following is a list of items you must complete in
order to get Window XP to
work with Mandatory profiles, Group Policies, and home
drive mapping
A: Update Policies for XP: 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:
1. Click Start , click Run , type mmc , and then click
OK .
2. On the File menu, click Add/Remove Snap-in .
3. In the Add/Remove Snap-in dialog box, click Add .
4. In the Add Standalone Snap-in dialog box, click Group
Policy , and then click Add .
5. 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.
6. On each policy, highlight the User, Administrative
Templates. Right click and ADD new templates.
7. Replace the four templates listed (admin, inet, conf,
sys) by clicking add and selecting the same name from the
local Windows XP station (NOTE: Replace the templates
EVEN if the XP template date is older than the one on the
server)
8. You can now set XP policies correctly (such as forcing
Classic Desktop)
9. Click OK .
Going forward, you should only edit group policies from
an XP machine, not a 2000 desktop or server. You can now
adjust the policy settings in this Policy object by using
the Group Policy console from the Windows XP-based
client.
Notes
The GPO is actually updated with the new administrative
template (.adm) files when you click or expand Computer
Configuration or User Configuration under the title of
the Policy object. You can upgrade a single Policy object
at a time by using this method.
The Windows XP Group Policy snap-in works only in Windows
XP Professional.
The Windows XP Group Policy snap-in implements a new
feature that displays the operating system version that
is required by an Administrative Template policy setting
in the side pane in Extended view. The Windows 2000 Group
Policy snap-in cannot display this version information,
but can be used to modify the administrative template
settings after being upgraded.
New Security settings are also supported in Windows XP.
These are available by using the Windows XP Group Policy
snap-in; they are not displayed by using the Windows 2000
Group Policy snap-in whether or not they are configured.
Editing Security settings by using the Windows 2000 snap-
in preserves the Windows XP-specific security settings.
B: Update the general policy to RUN login scripts
synchronosly.
The option is under administrative templates, login. Once
you set this, the entire login
script will execute, THEN the mandatory profile loads
C: Make sure your login script (or kickstart) uses the
correct syntax
If you are using home drives (through DFS shares) make
sure the login
script uses the %username% variable (ie net use h:
\\server\groupshare\%username%
NOTE: If you are going to use this variable, you MUST
create the share using
the DFS option on the 2000 server. Create a standalone
(not Active Directory)
share (ie groupshare)
