Link to home
Start Free TrialLog in
Avatar of Milkybar-kid
Milkybar-kid

asked on

Change location of redirected My Documents folder after Domain change

I have migrated an SBS2003 server to SBS2008 but had to change the AD Domain name.
In order to migrate the users profile I removed the computers from the SBS2003 network. Attached them to the SBS2008 network and then ran Profwiz form ForensIT
This seems to have worked ok except that the "My Documents" is still set to the old server and it is greyed out as if still controlled by group policy.
I have checked the group policy on the SBS2008 server and that is configured correctly.
I have ran gpupdate /force on the clients. This makes no difference.
When I run RSOP.MSC on the clients it only shows settings for Desktop redirection and a yellow exclamation mark against "User Configuration"
There is nothing there for "My Documents"
Curiously this hasn't occured on all clients but as far as I can tell they are not different (they must be!). All are running XP SP3 and are up to date with patches.
Avatar of Ross-C
Ross-C
Flag of United Kingdom of Great Britain and Northern Ireland image

have you tried restarting the problematic clients
Avatar of Rob Williams
This issue has come up fairly often. As I recall you have to manually delete the existing offline folder cache (link below) on each PC, reboot, login so GP is applied, log off and back on.  Make sure you have a copy of the redirected my doc files first.
http://support.microsoft.com/kb/230738
Avatar of Milkybar-kid
Milkybar-kid

ASKER

I'm not sure that is the issue.
The redirected "My Documents" is not accessible so there is no local cache.
When I try and open "My Documents I get asked to aurthenticate against the old server. It is still trying to open the files at the old location not holding a local cache.
The desktop is now in the migrated profile. To make it worse I have discovered one of the users has been saving all of their files to the Desktop!
And yes I have rebooted!
As I understand it clearing the cache resets the offline files function allowing it to establish a new connection with the new server. It's not so much an issue of clearing the cache contents, as reseting offline files.
Though I don't recommend manually changing the registry, and if you do make sure you back up the key first, you may be able to manually change under the following key:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
newer O/S's
"HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders

I have no concern editing the registry but I'm happy to follow your first recommendation if you think that is the best route. My biggest concern now that I have found all of the files stored on the desktop is ensuring that the profile and data are backed up first. Can you recommend thebest way to do that? I'm currently copying the desktop files from the local cache to the server but I want to ensure I preserve all settings.
If they are in the local profile there is no worry. If they are in the cache you will have to be logged in as that user to access. Copying the csc folder will not allow you to access.
If stuck you can extract the files using:
csccmd /extract /target:C:\Restore /recurse
ASKER CERTIFIED SOLUTION
Avatar of Milkybar-kid
Milkybar-kid

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I'm not sure how I get to award you some points here. You certainly assisted in getting me to the right place even though your answers weren't quite right. Do you know how I can accept my answer to make the question right but get you the points?
Did that work? Thought that only applied if the same server.
Did you try deleting the cache? That should have allowed it to connect to the new source automatically.
Regardless I am not worried about the points, just apply to your answer http://#33814523 after you have verified it resolved your problem.
--Rob
Yes - that was the answer.

I messed around with several settings on one of the clients. There were others exhibiting the same behaviour.
To prove it was that setting that worked I ran gpupdate /force on another PC wothout messing with any other settings. That seemed to fix it. Just to be sure I rebooted and now it's fine.

Thanks for taking the time to help out.