techies123
asked on
Problem when moving roaming profiles and user data to new server hardware.
Hi guys,
I'd appreciate any help here, as this particular problem has got me tearing my hair out!
(there's 500 points up for grabs on this one)
One of our servers (lets call it serverA) is due for retirement, its replacement - a new server with a different name (serverB) is now in place on the network and has assumed most of the roles previously held by the old machine - The old server has been demoted from DC to a member server.
The old server held all of our corporate data, and all the users roaming profiles (as well as the redirected My Docs and Desktop folders). Ive migrated all of the data to the new machine, being careful to retain all NTFS permissions, and recreated the shares on the new machine. The user login script has been updated to reflect the moved shares:
\\serverA\share becomes \\serverB\share, etc.
The AD properties for the user accounts have been updated to reflect the new path to the roaming profile and home drive locations, and the GPO for the My Docs/Desktop redirect has been updated to point to the new server location.
All client PCs have been purged of locally cached user profiles, and the offline files store has been cleared out on each machine.
*It doesnt work*
When logging on to the domain, users will see their desktop as expected, but then up pops an offline files synchronisation dialogue box stating it is making files on serverA available offline. As these files have been moved to serverB the synchronisation fails and the workstation acts as if the server is not available. At this point all of the users desktop icons disappear!
Im at a loss as to what is causing this, my colleagues and I are completely stumped.
Please help!
I'd appreciate any help here, as this particular problem has got me tearing my hair out!
(there's 500 points up for grabs on this one)
One of our servers (lets call it serverA) is due for retirement, its replacement - a new server with a different name (serverB) is now in place on the network and has assumed most of the roles previously held by the old machine - The old server has been demoted from DC to a member server.
The old server held all of our corporate data, and all the users roaming profiles (as well as the redirected My Docs and Desktop folders). Ive migrated all of the data to the new machine, being careful to retain all NTFS permissions, and recreated the shares on the new machine. The user login script has been updated to reflect the moved shares:
\\serverA\share becomes \\serverB\share, etc.
The AD properties for the user accounts have been updated to reflect the new path to the roaming profile and home drive locations, and the GPO for the My Docs/Desktop redirect has been updated to point to the new server location.
All client PCs have been purged of locally cached user profiles, and the offline files store has been cleared out on each machine.
*It doesnt work*
When logging on to the domain, users will see their desktop as expected, but then up pops an offline files synchronisation dialogue box stating it is making files on serverA available offline. As these files have been moved to serverB the synchronisation fails and the workstation acts as if the server is not available. At this point all of the users desktop icons disappear!
Im at a loss as to what is causing this, my colleagues and I are completely stumped.
Please help!
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS 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.
johnb6767
Actually, does a new user account synch properly? I would expect it to, since there is no previous offline files....
ASKER
Hi johnb6767, thanks for your suggestions. I'll read up on the csccmd.exe tool you've identified.
You are quite correct, a newly created test user account does behave as it should. The profile is created in the roaming profiles location on the new server, and the GPO steps in to redirect my docs and the desktop.
Are you of the opinion that the problem lies with the client machines? I know Windows XP caches things left right and centre, but thought that by deleting the locally cached copies of user profiles and clearing out the CSC store would force it to pull everything down from the new location...
You are quite correct, a newly created test user account does behave as it should. The profile is created in the roaming profiles location on the new server, and the GPO steps in to redirect my docs and the desktop.
Are you of the opinion that the problem lies with the client machines? I know Windows XP caches things left right and centre, but thought that by deleting the locally cached copies of user profiles and clearing out the CSC store would force it to pull everything down from the new location...
There are somwe keys in the registry that still hold old server locations, both user created, and GPO created (2 different locations) though, that need to be removed manually. That, in combination with the removal of Non primary user profiles, seems to work best in unison with each other, for a complete solution.....
If you look in the Offline Files folder, and sort by the synch column, as long as there are no files marked other than "File is synchronized", then you wont even need the csccmd.exe tool. I only offered that to mkae sure you dont lose any data... Does come in handy....
ASKER
Thanks again John - most helpful.
I'll test your theories and research the offline files thing further. I'll come back to this thread in a day or two to let you know if your solution worked, or ask further questions as needed.
Cheers.
I'll test your theories and research the offline files thing further. I'll come back to this thread in a day or two to let you know if your solution worked, or ask further questions as needed.
Cheers.
ASKER
Thanks for your help - I'm sorry it took me so long to close the question and assign the points!
ASKER
For anybody who is interested, here are the steps I took to resolve this issue:
1. Copy csccmd.exe file to Netlogon share (%systemroot%\sysvol\domai
2. Create a batch file and copy it to netlogon share
a. Open the notepad
b. Type the below command
\\domainname\netlogon\cscc
c. Save the file as filename.bat
3. Create a start up script and add the the batch file.
4. Apply the policy at domain level
5. Restart the clients
6. Once the issue is resolved on all the clients, remove the policy
1. Copy csccmd.exe file to Netlogon share (%systemroot%\sysvol\domai
2. Create a batch file and copy it to netlogon share
a. Open the notepad
b. Type the below command
\\domainname\netlogon\cscc
c. Save the file as filename.bat
3. Create a start up script and add the the batch file.
4. Apply the policy at domain level
5. Restart the clients
6. Once the issue is resolved on all the clients, remove the policy
Windows Server 2003
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
