ADMT v3.1 and Folder Redirection

I have performed interforest migration using ADMT v3.1 from WIn2k3 to Win2k8. All groups/users/computers have transferred successfully to target forest while retaining their respective user profile. i rendered SID filtering enabled on two-way forest trust.

Now, when the users were in source domain, i was hosting roaming profiles/folderredirection on the member server joined to sourced domain.I have successfully moved member server to target forest.
Roaming profiles are working fine( i had to manually enter the FQDN of member server transferred to target forest on each user profile tab properties because on profile tab it showing old UNC)

NOw, folder redirection works fine when i login the user in target forest. But when i logg off the user it performs SYNCHRONIZATION and still references the old UNC path to member server when it was joined to source domain. Moreover, it also lists the new UNC path which is fine. What i am doing is that i manually uncheck the old UNC path from Synchronization Settins tab and i get no error when logging off. there is no reference of old UNC in GP which i created in target forest for folder redirection.
Is there any way to automate this such that all old references to old UNC path get removed from Synchronization Settings tab

__________________
A.Rajesh Khanna

Hi,

This issue may be caused by old information left on clients. You can try the following options to clear old information.

1. Create GPO and use "User Configuration/Administrative Templates/Network/Offline Files/Administratively assigned files" setting to follow clients to the new file servers. Applying the policy to user accounts should redirect them to the new servers.

2. Stop the Folder Redirection to clear old date and enable it to create new date on clients. You may refer to the following article to disable Folder Redirection.

How to stop Folder Redirection in Windows Server 2003 and in Windows 2000 Server
How to stop Folder Redirection in Windows Server 2003 and in Windows 2000 Server

3. You can also use the following script to clear client Registry.

Hi,

when i tried to run the script using group policy startup script, noting happen at client..they were still referring to old UNC path.

when i tried to run at client computer(windows xp x86 sp2) using command line i got the error as shown in screenshot.


I says,

Error: Too many command-line parameters

further, i didnt tried your first recommendation and will let you know when i turns out to be successfull.

Attached Images

Error1.JPG (130.7 KB, 1 views)

__________________
A.Rajesh Khanna