Anyone experienced Microsoft Sync Center Issues after move from a NAS to an EMC isilon based NAS (in the process changing Server Name & IP Address) resulting impact on Network shares UNC path name? We have certain users still having their home drive path referencing the old path ie (
\\server\oldshare instead of
\\server\newshare still being referenced). We ensured the old UNC to new UNC was properly defined and effected via GPO for Folder redirection. This policy has been enforced thoroughly on clients and tested after several updates and restarts.
Manually deleting the old references on client by IT support still results into conflicts and eventually rolls back after a while to referencing the old path. Our conclusion was this doesn't work properly on Windows 10.
The Client has no control over this since option has also been greyed out due to a global policy restriction making it impossible to effect this change on the client side of things. Is there any way this can be resolved via group policy via a global reg update setting? Do we have to re initiate offline caching on clients or via GPO? I also noticed that this has affected most clients migrating from windows 7 -> 10, most clients working offline or remotely via WiFi/VPN outside the corporate network or haven't been online for several days due to business travel.
We have also adhered to all best practices here.
I am thinking of possible scenarios via global policies - Reg Update of Offline cache paths from 7 -> 10 via GPO or manually via Clients?
Trigger manual offline sync cache process a step before or during the Migration process so Files are where they supposed to be when migration is done.
We have also found a script here which can trigger this cache manually but will require system privilege which the user doesn't have and we want to avoid having the user do this. We might probably include that in our migration process.
Is the information in this article relevant?