asked on
Moving users files to new server
Hi Experts, hope you can help me with this.
I am in the process of moving users folders from an old 2003 server to a new Win 2012 server, both of which are currently domain controllers although as soon as the transfers are complete the old one will be retired.
The users folders are currently set in the users AD account under profile - home folder - connect and is set as U \\servername\users\usernam
When I change the servername to the new servername everything initially seems ok in that the U: drive now maps to the new server and the My Documents (or library) also points to the new server.
However I have 2 issues:-
1. The offline files are still trying to sync to the old server and while I can setup a new sync manually on the client PC there seems to be no way of deleting the old one. These always set themselves up automatically when I setup a new computer so have never had to do anything manually before. Should they not change with the moving of the path in the user profile? There seems to be nothing set in the GPO for offline files.
2. The recent documents links on the users computer are now broken as they point to a UNC path of the old serve instead of the mapped drive. Anyone no of an easy way to update these to the new path.
If anything is no clear please let me know and I will try to clarify.
Thanks in advance
Colin
I am in the process of moving users folders from an old 2003 server to a new Win 2012 server, both of which are currently domain controllers although as soon as the transfers are complete the old one will be retired.
The users folders are currently set in the users AD account under profile - home folder - connect and is set as U \\servername\users\usernam
When I change the servername to the new servername everything initially seems ok in that the U: drive now maps to the new server and the My Documents (or library) also points to the new server.
However I have 2 issues:-
1. The offline files are still trying to sync to the old server and while I can setup a new sync manually on the client PC there seems to be no way of deleting the old one. These always set themselves up automatically when I setup a new computer so have never had to do anything manually before. Should they not change with the moving of the path in the user profile? There seems to be nothing set in the GPO for offline files.
2. The recent documents links on the users computer are now broken as they point to a UNC path of the old serve instead of the mapped drive. Anyone no of an easy way to update these to the new path.
If anything is no clear please let me know and I will try to clarify.
Thanks in advance
Colin
Microsoft Legacy OSMicrosoft Server OSWindows Server 2012
Last Comment
itslnet
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
You can also utilize a Microsoft tool called the "Client-Side Caching Command-Line Options" Or CSCCMD. CSCCMD.exe is available in the Windows Server 2003 Resource Kit which is on the 2003 installation disc also.
Once downloaded, run the RStools.exe to install it on the PC on which you wich to change the offline files path. Now you can utilize the tool to change the offline files path. Type:
csccmd /moveshare:\\oldpath\oldsh
You can also make a batch file by putting the executable up on a share and calling it using logon script.
Once downloaded, run the RStools.exe to install it on the PC on which you wich to change the offline files path. Now you can utilize the tool to change the offline files path. Type:
csccmd /moveshare:\\oldpath\oldsh
You can also make a batch file by putting the executable up on a share and calling it using logon script.
ASKER
Hi Jimpen
I have only moved a couple of users so far so would this work for the rest if I created the Cname record now before moving any more. The recent files all show an actual unc path.
I have only moved a couple of users so far so would this work for the rest if I created the Cname record now before moving any more. The recent files all show an actual unc path.
You would have to get the users to create a new shortcut "now" to do it. Or change the mapping of drives. But at my last company we had any number of AppServer and FileServers done up as CName records. We would come in on a weekend and do a app moves/upgrades and the end user never realized they had been moved. Or they saw an upgrade script run on Monday morning.
But if you do it by FS groups you can migrate the five HR people on Tuesday and the ten accountant types on Wednesday, and eat a late dinner at home as opposed to sucking down a whole weekend moving everybody.
No matter, DNS can be your friend if used properly. :-D
But if you do it by FS groups you can migrate the five HR people on Tuesday and the ten accountant types on Wednesday, and eat a late dinner at home as opposed to sucking down a whole weekend moving everybody.
No matter, DNS can be your friend if used properly. :-D
ASKER
Sorry it's been so long, still working through it. I have found I had to put in both of the reg entries below on Windows 7 otherwise the original entry didn't delete. Takes a while to login the first time but seems to have fixed it.
REG.EXE ADD "HKLM\SOFTWARE\Microsoft\W
reg add HKEY_LOCAL_MACHINE\SYSTEM\
Didn't bother in the end with the recent docs, doesn't seem to have caused to many issues.
REG.EXE ADD "HKLM\SOFTWARE\Microsoft\W
reg add HKEY_LOCAL_MACHINE\SYSTEM\
Didn't bother in the end with the recent docs, doesn't seem to have caused to many issues.
I'm not sure of the answer to #1.
The fix for #2 should have been implemented at the beginning of the process and works for SQL Servers as well. If you have control/access to the DNS server you create a CName record that points at the actual servers A record. So you create a CName record that is called MainFS that points as FileServer2003. Then when you move the files to to FileServer2012 you change CName record to point at the new server. Depending on how large your organization is you can also do something like MainFSHR, MainFSAcct, or MainFSOps. That way you can move groups at a time and they don't realize it.
And how it works for SQL Server is that you have a DB/App CName record for each DB. Then if you move a DB from SQLServer1 to SQLServer2, you just change the CName pointer.
Essentially the CName record allows you to make the servers "virtual" as in they are pointing at a generic server name and a move is "invisible" to the end user.