I am a network manager working in a large regional high school. I have had a number of years experience setting up Win95-ME workstations to log on and download set policies and logon scripts from NT4 severs, and have battled through the usual hassles with installing group policy support (grouppol.dll's)before the stupid things will recognise your group settings etc etc.. So I guess I shouldn't be surprised that now we are testing a Win2000 Domain Controller, the single user policies are applied OK from the NETLOGON\config.pol but guess what?? No amount of coaxing, reinstalling group policies on the ME machine,or editing the registry, will entice it to apply any group policy settings!!!!
Does Win2000 Server now not support this feature, even though I can browse the global groups and select them in my config.pol?? Or is there a new Grouppol.dll that fixes the problem?? Any answers would be great, thanks.

There are a few terms that could be confusing things. Group Policies in Windows 2000 are usually referred to as GPOs (Group Policy Objects). GPOs for Windows 2000 are set in the Activie Directory Users and Computers and only affect Windows 2000 clients.

If you are using Policy Editor and creating a config.pol file, then you put that policy file in the NETLOGON share on the W2k DC(s). The confusing thing here is that I think you want to use the config.pol file to apply the setttings to a group of user in a w2k domain but not actually use w2k GPOs. Is that right.

Thanks for your reply Glen, I'll try and clarify. I'm aware that win2k Server GPO's only apply to 2000 clients. So you're right in thinking I create a config.pol on ME and transfer it to my Win 2000 AD server.

I pinched another working ME machine today that was happily downloading a global group setting from a config.pol on our current NT 4 DC. Guess what?? when logged
in to the 2000 server, it wouldn't apply the group settings either!! Although it was happy to apply single user settings if I added them to the config.pol.
I'm sure this is a quirk of AD or Win 2000 DC's it just won't do it!!! Help!!!

Glen and others,

David again. Problem solved!!
Having read Minasi's Win2000 sever book, I wasn't hopeful, because he suggests clients (NT4) other than 2000 won't download security group settings from the config.pol because of a security setting/s in AD.

I originally copied the Administrator account on the 2000 DC and made a test user account. This account was member of a number of groups. One in particular "Domain Group Policy Managers" or similar (I don't have it in front of me), was one of those groups.
REMOVE IT!! Group settings in the config.pol WON'T apply while the user is a member of this group!!
Make a seperate Domain Security group (Testers or whatever you like)and add the user to it. Add this group to your config.pol and hey presto!! It works!!