Hello, I'm looking for a fresh perspective on this. I'm migrating a few hundred users over to a new file server. The paths will be different. It's not just the server name that's changing. I have run into several problems. 1. Although I'm a domain admin, I don't have access to most of the folders. In the worst case scenario I need to take ownership to gain access. 2. Inheritance is disabled on some of the sub folders. 3. Permissions are sometimes configured on the fifth or even tenth sub folder. 4. There are drive paths distributed using group policy but 99% of the paths are mapped directly on the PC. 5. Five minutes of down time causes untold problems. 6. The tool that is used to replicate the files isn't replicating the permissions in all cases. It is also having the same problem that I'm encountering in terms of access to some files and folders. 7. Permissions aren't given to groups. Each person is added to the folder directly. 8. There are often eight different drive maps. Some of these are even pointing to duplicate locations. Here's what I've tried. 1. Section shares will be mapped to S. However, the policy is set to update. IT isn't changing locally mapped drives. This is ok. It allows users to come to support if they can't access their files. The benefit of this is support are noting down what S was previously mapped to. 2. I'm using powershell to level the permissions on all sub directories. 3. I'm talking to section heads to determine the permissions that each person needs. 4. I'm adding these people to groups based on the section and directory name and applying access to the group. 5. I'm marking the old files as hidden. Mainly so that if someone continues using the old path they will think the drive is empty. That will result in a call to support where they can tell the user to use the new drive and then also delete the old map. There are far too many manual steps in this. There's also too many remaining drive maps that aren't needed. I'm thinking of doing something like the following: Write a script that will be run at log in. 1. Remove all drive maps 2. Check the groups that the user is a member of. 3. Map drives based on those groups. That way I don't need to touch the old file server. The problem is that if I move Drive Q that is used by ApplicationX to the letter Y, all the users who used the old letter will probably have problems opening files. I'm a bit stressed. I don't know how I can do this without down time or causing problems for some users. Thanks Darragh