Server 2012 Folder Redirection / Windows 7 - modifying existing....

[mikkydoos]

Hi all,

 

Looking for an answer plz....

 

 

Recently VM'd new DC (AD,DNS,DHCP etc).

 

Server 2012, Win 7 SP1 clients.

 

I have a physical file server I want to change the IP address of - Have a problem with Folder Redirection.

 

 

The file server hosts Folder redirects, Profiles etc.

 

I have changed the server name successfully - The name resolves fine for batch scripts for mapped drives etc, but need to change the ip address to conform to my new structure.

 

DNS works fine.

 

When I change my Folder Redirection GPO from...

 

\\192.xxx.xxx.xxx\share\user\

 

to...

 

\\Servername\share\user

 

 

the user logs on.... 'Please wait' for ages.... New share overwritten over the old data in the same location.

The client redirects the new path ok, but recreates the users share and deletes all their data - (lots of data hence 'Please Wait' for ages).

 

Wanted to change the path from IP to Name so DNS resolved the address - then I can change the IP as much as I like.

 

 

Any solutions to why the change from specifying a Name rather than an IP address should make the client see it as a different path and overwrite ???

 

 

Drivin' me nuts

 

 

 

Cheers all : )

Edited September 9, 2013 by mikkydoos

[Michael]

It does look like a DNS issue to me. The IP address works fine, but the servername doesn't as it resolves to something else. What about if you use the FQDN?

 

I'm speculating you've either changed the IPs around with another server or VM, or you've re-used the same servername?

[mikkydoos]

I thought DNS too but the servername does work ok. It redirects as I'd expect. - Thing is... I'm redirecting to the same location as before, just using the name instead of the ip, nothing else, but it overwrites with a new folder (same folder name, hence old one deleted - along with all the data in it).

 

Server name is unique. Havent tried FQDN yet though.

Edited September 9, 2013 by mikkydoos

[DMcCoy]

I'm afraid this is working as expected, moving between server name and server FQDN will also have the same effect when used with the move option. There is a policy option "Verify old and new Folder Redirection targets point to the same share before redirecting" but this *may* break redirection although not delete the files.

 

You need to disable move files on the folder redirection.

Edited September 9, 2013 by DMcCoy

[Michael]

2008, 2008 R2 and 2012 do favour the FQDN. You'd be surprised how much of a difference it makes.

[ADMaster]

As said above it is trying to move the files to the same location.

 

I think now is a good time for you to implement DFS name spaces. Then when you change servers you do not need to update the GPO.

 

I moved all of the user data files to a new server this summer and just updated the DFS target, it worked well.

[mikkydoos]

Cheers guys.

 

I'll give the above a try and post back later.

 

 

Thanks for your help (s) ; )

[bart21]

As said above it is trying to move the files to the same location.

 

I think now is a good time for you to implement DFS name spaces. Then when you change servers you do not need to update the GPO.

 

I moved all of the user data files to a new server this summer and just updated the DFS target, it worked well.

 

Agreed the best method for you would be a Dfs name space then in future you just change the name space backend and the client doesn't notice any change.