• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

help

Scheduled Pinned Locked Moved
General
2
2
304
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M
    mpatel
    last edited by Jul 22, 2019, 11:36 PM

    We are looking for some help figuring out how to migrate users data when we deploy windows 10 thru fog server.

    we will be sending fog server to our remote offices and locally image each of the user’s computer with windows 10. how do we migrate their user’s data to windows 10 without involving external drives like Flash drive,passport drivers or file servers.

    ideally we like to automate this process so after deploying windows 10 user’s profile and data is there.

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by Jul 23, 2019, 1:17 AM

      Well the answer isn’t clean no matter which route you take. You have to remember that FOG doesn’t really care about user data or host OS. FOG (FOS Linux) is linux based so it really can’t step into the MS Windows world other than copying files to and from a MS Windows mounted disk. FOG (FOS) has no concept of user’s profile data.

      With that said I can think of 2 routes. One involves FOG and the other is strictly a Windows activity.

      For the MS Windows only solution use USMT (MS Windows User State Migration Tool). You run this from inside windows as an admin to backup and restore user profiles to a network file share. It works well for both same system user migration such as when the same computer is upgraded from Win 7 to Win10, as well as a different system migration between two computers. You can use USMT interactively of deploy the USMT Save State and USMT Load state functions via a FOG snapin or any other package deployment tool like PDQ Deploy.

      Now for a FOG only solution. This task would be done with one of FOG postinit scripts. Where the script would mount the windows 😄 drive and rsync the c:/users directory to a remote NFS file share before the image is deployed to the target computer. Then after the image has been pushed use a FOG postinstall script to rsync the files back to the c:/users directory. This is not a very clean solution because ms windows won’t have the connection between the windows user account and their home directory.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

      1 Reply Last reply Reply Quote 1
      • 1 / 1
      1 / 1
      • First post
        1/2
        Last post

      271

      Online

      12.0k

      Users

      17.3k

      Topics

      155.2k

      Posts
      Copyright © 2012-2024 FOG Project