Hi I want to be able to use Win2K GPO to map a network drive for all users who log onto a domain. I have written a template adm file like this: CATEGORY "Drive Mappings" CATEGORY "Drive Z: (The main directory)" KeyName "Network\Z" POLICY "Enable static drive mappings (Reconnect at Login)" ACTIONLISTON VALUENAME ConnectionType VALUE NUMERIC 1 VALUENAME ProviderName VALUE "Microsoft Windows Network" VALUENAME ProviderType VALUE NUMERIC 131072 VALUENAME UserName VALUE "" END ACTIONLISTON PART "Drive Z:" EditText VALUENAME RemotePath END PART PART "Enter the UNC path. This supports Microsoft Windows Networks," TEXT END PART PART "only. Ensure that this drive is not in use as a home drive." TEXT END PART END POLICY END CATEGORY END CATEGORY I can add this as a template to a User Group Policy OK, but when I click on "Drive Z:" no policy dialog appears. It seems to be something to do with the KeyName command, but I am sure this is right - it worked on NT4. Anybody any ideas? Thanks Rick

If this is their home directory, just put it in each user's profile. :)

Thanks Jennifer That's OK for one mapping. But if I also want to map Y: to something else, what then? I know I could use a logon script with NET USE commands, but according to Microsoft, we should all be using Group Policy with our Win2K servers. I feel there must be a way to do this.

How about different users in different OU's with seperate logon scripts called from different GPO's?

Hi Thanks for the post. It doesn't need to be that complicated. What I need basically is for every user in the domain to have his Z: drive mapped to \\win2kServer\someshare and his Y: drive mapped to \\win2kserver\users\%username% I know I can do this from a logon script, but it does mean that users have to have the capability to run the NET.exe program. If I did this via a straight GPO, then no extra capability would be needed. Have you any idea why my .adm file doesn't work?