none
Howto migrate Work Folders server?

    Question

  • Hi,

    I have some servers running 2012 R2 with active Work Folders feature. They will be replaced by 2016 machines. Is there some howto regarding the migration of Work Folders feature?

    The sync shares are created with file access only for the users itself. Work folders URL is distributed by GPO to the clients and setup is enforced. Clients are Windows 10 1709 and 1803. 

    Before Windows 10 1803 the clients had all the data and changing the sync share was easy. Clients were just resynchronizing their files to the new, empty share. Now with the new features, most files stay on the sync share server and only a few files are offline available. 

    So how do I handle this? 

    Thanks, Ingo

    Friday, July 13, 2018 1:48 PM

All replies

  • Hi,

    You could follow the guide to migrate Work Folders server

    https://social.technet.microsoft.com/wiki/contents/articles/32900.migrating-work-folders-server-configuration.aspx

    And please also follow the guide to move a user to different sync shares

    https://blogs.technet.microsoft.com/filecab/2014/07/18/moving-users-to-different-sync-shares/

    Best Regards,

    Mary


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, July 16, 2018 2:39 AM
    Moderator
  • Hi, 

    both documents are older than Windows 10 1803 and I think they are not reflecting the current status.

    When I assign the user to a new security group, he will be rejected at the old sync share and directed to the new one. That is okay. But what about his data that is stored on the old sync share? How does this data get to the new sync share if it is not locally stored on the client?

    Monday, July 16, 2018 7:35 AM
  • Hi,

    For now I still couldn't find official documents to describe this with more details about Windows 10 1803

    Maybe you could also contact the Work Folders team mentioned in the thread.

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/01269b82-4f70-43ea-8a60-b12df030830a/issues-with-work-folders-after-1803-upgrade?forum=winserverfiles

    Best Regards,

    Mary


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, July 17, 2018 2:34 AM
    Moderator
  • Hi,

    If you have the updates, please feel free to contact us.

    Best Regards,

    Mary


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, July 20, 2018 7:15 AM
    Moderator
  • Hi, 

    I have contacted the Work Folders team, but haven't got any answer. Looks like it's holiday time. I'll wait a little more. It's not an absolutely time critical task for now.

    Best regards, 

    Friday, July 20, 2018 7:29 AM
  • Hi,

    Thanks for your feedback.

    It also is appreciate you sharing the information if you get the updates.

    Best Regards,

    Mary


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, July 23, 2018 1:24 AM
    Moderator
  • There are two migration options:

    Option #1 – Work Folders client migrates the data to the new server

    Pros:

    • No file conflicts

    Cons:

    • Increased network traffic
    • On-demand file access feature must be disabled. The Work Folders client will download the entire dataset locally and then upload the entire dataset to the new server.

    High-level steps

    • Disable the on-demand file access feature via group policy (if enabled)
    • Wait a week to ensure the client has downloaded the entire dataset
    • Give the user access to the sync share on the new server (see moving users to a different sync share blog)
    • Remove access to the sync share on the old server
    • The Work Folders client will discover the new sync share and upload the data to the new server
    • Enable the on-demand file access feature via group policy

     

    Option #2 – Copy the data to the new server using Backup\Restore, Robocopy or another tool

    Pros:

    • Less network traffic than option #1
    • On-demand file access feature can remain enabled and the client doesn’t need to download the entire dataset locally

    Cons:

    • Can cause conflicts if the file(s) on the client and server are different. See reconciliation section below

    High-level steps

    • Use Backup\Restore, Robocopy or another tool to move the user data to the new server (see disaster recovery planning blog for more info)
    • Give the user access to the sync share on the new server (see moving users to a different sync share blog)
    • Remove access to the sync share on the old server
    • The Work Folders client will discover the new sync share and reconcile the data between the client and server (see reconciliation section below for more info)

    Reconciliation

    If content exists on both the client and server when creating a sync partnership, sync will enter a stage called reconciliation. Any file that is in an identical path, same size, same last modified time, will be seen as the ‘same’ and not re-downloaded or uploaded.  Any file which has a different path and/or size and/or last modified time will be seen as different and downloaded/uploaded. If the file that is downloaded/uploaded is in the same path as an existing file with the same name, a conflict will occur. Work Folders uses a simple conflict-resolution strategy: The most recently written change keeps the original file name. The older file has the "source" machine and the conflict number appended to the name.

    Tuesday, July 24, 2018 5:16 PM