Mass Profile Problem / Redirections

[jamwatn]

Hi,

 

We've had to change our file server to a new name (don't ask..it's done now) but users redirections are sticking to the old names on their devices, despite the fact they are seemingly receiving group policies properly. I think the devices are still using their offline file cache for the old server.

All users use local profiles.

 

The only way I can think to resolve this is a mass profile reset of all devices, but I don't want to use Delprof2 and lose possible local data on the devices that are incorrectly storing the data.

 

Has anyone got any advice or ideas?

 

Thanks

[bezzoh]

Easiest solution for me is you add the Alias of your old server name to your new server. You will need to make sure your old Server is completely removed from the domain to do this however (including removing DNS records entirely for it) or you will just get errors when trying. Again, delete the old DNS records and make sure that has replicated around your DC's before doing this. Just changing the IP to your new server name won't necessarily work. When you go through this process you'll end up with a dynamic DNS entry for the new IP anyway.. at that point if you feel it necessary to make it static again you can do.

 

Anyway, this will mean you can then connect to profile paths (and any other path so long as they have the same share names) on your new server, using the old server name. No issues. I do this every time I create a new file server so I don't have to faff around.

 

A quick google brought me to this, looks like a reasonable guide to follow.. its how I do it. https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/using-computer-name-aliases-in-place-of-dns-cname-records/ba-p/259064

[Neil83]

Have you tried deleting a users local profile from a machine and asking them to log in again (forcing it to pull down a fresh copy)?

[bezzoh]

Its all 'shell folders' in the registry hive which will be both local and on the file server. Changing group policy doesn't update these (or not all of them) once they are generated, so you can completely wipe the profile... try and script changing these registry keys (which would actually be a bit of a ridiculous thing to do, but I did once actually try that,) or just go for giving your file server multiple names. 5 mins... everyone's fixed.

[mavhc]

Whatever you do, fix it properly by setting up DFS so next time it's not an issue

[DavR]

If adding an alias is not an option, I would look into the user shell folders in registry, and force any changes you need through using group policy preferences.

[DavR]

The registry keys you need are in:

 

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders

 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders