Jump to content

Recommended Posts

Posted

Hi all,

 

We migrated our file server from Windows 2003 to Windows 8 R2 with a new server server name. We updated permissions and home folders in AD - all good and well.

 

On the clients Windows 7 mapped the drive to the new server which connects no problems but the document library does not. It is still pointing to the old server. We use offline files as all students have laptops that they take home. However, students are saving to the Document folder in which the path is invalid but still caches the files. The Document Library is showing the old server UNC path. GPO doesn't have any settings for this either.

 

Anyone get any suggestions?

 

Thanks in Advance.

 

Mark

Posted

Not my strong point, but until someone else wakes up, did you also migrate client OS. We had problems with migration from XP to Win7 due to use of roaming profiles.

Redirected folders caused a problem, and it was best to clear out old profile and restart. Also, from a really old issue, there was a way to force cached files to delete, some weird key combo, maybe that would help...

Posted

Hi,

 

Thanks for reply. The problem is caused by cached looking for the old server UNC path which it is no longer available. Because in GPO under Documents folder redirection the "Move folders...." option is ticked the new path will not update. Looking at creating a C-Name with for the old server then updating this.

 

Thanks for your help.

 

Mark

  • 8 months later...
Posted

Hi There,

 

I am having the exact same problem after migrating my users to a new server, did you find a solution for this?

 

Thankfully only used offline files on my staff laptops and not every computer, but i only have 2 more working days before the staff come back after xmas!

 

Cheers!

Posted

Thanks.

 

I think it caused by the fact we demoted the old server first before GPO / User Log On session had a chance to update the path to the new server. If the old server path no longer exists Windows will not update the libraries. This is what we figured.

 

We just updated everyone profile manually. Harsh but lesson learnt. We didn't our changes properly.

 

Cheers,

Mark

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...