How can I forward a folder in MSN email?

Folder redirection issue after Changing the IP Range.?

• Hi, I would appreciate if you can help me, in fact i am facing a serious problem with my network. I have change my IP range in my organization. Everything went well except the folder redirection. I am having a Domain Controller with windows server 2003 where i applied 2 policies, one is to redirect the my documents of the users to the file server ( note that file server is having windows sever 2008) and the other is to redirect the desktop also to the file server. Before i used the to synchronize , i had no issue at all, but since I changed the IP range i am facing two issues. 1st: The users having normal PC's are still showing the old path on their documents, if i right click on any file on their desktop or my documents and select properties i see \\olderserver\filesrevername\mydocuments… I tired to move the users to a new OU in the DC server, also i removed the opld policies of folder redirection and i created a new new, and i restarted the clients several times, but still the problem same. Also note that i stop the synchronization of folders...but always with the same problem. Now the 2nd big problem is with my users having thin Clients. I am having an application server running windows server 2008 R2, with hyper-v having an RD-Host for thin clients to use remote applications. Now the thin client is facing a serious problem , when i boot the thin client and i login with the domain admin, the client boots normally, but when i login with the user it takes like 5 to 10 minutes to show the desktop and to boot, it keeps stuck on the taskbar for a while. Also desktop and my documents are not showing nor redirected for the thin clients users. I wish someone can help me with this serious problem. Please send me an email to [email protected] with the solution. I really need some help. Best Regards.

• Answer:

  Your clients are failing to find the domain aware local DNS at login. You probably have them hard coded to look for your old DNS server. Check to make sure that DNS is running on the new segment and that the clients are pointing to it.