NoDrives Policy not working after server upgrade to 2003

[gbl]

I have had a modified group policy created at the organizational unit level within our domain that hid certain server drives for users in that OU, that worked fine in Windows 2000 server. We have upgraded to Windows Server 2003 and this no longer seems to work.
The relevant part excluding the elements in the Strings section reads as follows:
POLICY !!NoDrives
EXPLAIN !!NoDrives_Help
PART !!NoDrivesDropdown DROPDOWNLIST NOSORT REQUIRED
VALUENAME "NoDrives"
ITEMLIST
NAME !!ABOnly VALUE NUMERIC 3
NAME !!COnly VALUE NUMERIC 4
NAME !!DOnly VALUE NUMERIC 8
NAME !!ABConly VALUE NUMERIC 7
NAME !!ABCDOnly VALUE NUMERIC 15
NAME !!WOnly VALUE NUMERIC 4194304
NAME !!CDWOnly VALUE NUMERIC 4194316
NAME !!ALLDrives VALUE NUMERIC 67108863 DEFAULT
; low 26 bits on (1 bit per drive)
NAME !!RestNoDrives VALUE NUMERIC 0
END ITEMLIST
END PART
END POLICY

But I am confused: Has the location also changed in the system.adm file for Windows Server 2003?

I have also noticed in another system.adm on the server these three lines after the header line for this Policy:
#if version >= 4
SUPPORTED !!SUPPORTED_Win2k
#endif
and they are not explained anywhere!

Will I have to just recreate my system.adm to create the customizations I had before, only this time using one found on server 2003?
Thanks for any help

 

[markdmac]

The location for ADM files has not changed. They are still stored in the INF folder in your Windows directory.

These are just the templates of course. Your actual policies and copies of the ADM files get stored in the SYSVOL.

The code you are seeing:
#if version >= 4
SUPPORTED !!SUPPORTED_Win2k
#endif
is used to check that the client is at least Windows 2000.

If you have created your own custom ADM file for the hide drives policy, then all you need to do is create a new GPO and import that policy template.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark