@mpatel as others have mentioned here - speed is the key; we’re in an identical situation, all sites connect to HQ via VPN but then all sites have Gig Internet so imaging machines at the remote sites has never been an issue, you just talk the end user over the phone to his F12 and that’s that (FOG job must be submitted ahead of time of course).

@buddyaderholt I don’t see how this is directly related. Please remove the link you posted or we will do so unless you can explain the context of how this fits into the picture.

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.

@mpatel For CentOS use the following:

dodhcp='Y' bldhcp='1' dhcpd='dhcpd' packages='bc curl dhcp ...'

Then re-run the installer and see it do the work.

@mpatel Disabled SELinux and Firewall???

it did finish. but took long time. Thank you guys. please resolve this.

i was able to locate instruction. https://wiki.fogproject.org/wiki/index.php?title=Migrate_images_manually#Image_Definitions

please mark this question as answered.appreciate your quick response.

@mpatel said in Imaging over WAN:

now how do i go about transferring my exiting fog setup to new box including images that i have.

May I ask you to open a fresh topic on this question just so don’t mix things up too much and people can find things more easily in the forums. Take a look at export/import the image definitions and we’ll give you more of the details in the other topic.

Marking this as solved.

Good evening, I’m configuring the FOG Project on several remote networks and so far it’s been a success.
I did the FOG Master in a DMZ network and in the other distinct networks I did the FOG Storage doing the replication of all the images of machines inside the FOG Storage.
The boot checks the FOG Master the PXE and after that it does the entire cloning process inside the network itself, thus avoiding bandwidth consumption and competition with other services.

Please resolved this post. we went virtual machine route to capture image and it worked.

Thank you for support.

I will try it out and post update here.
All our disks have 2 partitions. which are created by windows when it was installed. system reserved 100MB & rest is 😄 drive. here are pictures i took from FOG…could you help me select correct options. it’s bit confusing for me. our FOG version is 1.5.4

1_1535473437005_3.PNG 0_1535473437004_2.PNG

Dumb switch solved the issue. Please resolved this thread.

Thank you for your assistance.

Tom, Thank you so much for help on this. it did work. i noticed on Fog dashboard. disk space shows 190gb.

@mpatel the second question doesn’t do anything anymore. It is from before the fos system was able to grab dns from dhcp.

The first question is only needed if you’re using fog for dhcp, so no is the correct answer.

@mpatel If you look towards the bottom of the thread the drivers on the fog server go into /images/drivers (you will need to create the drivers directory because its not fog standard.) Below is the basic structure of the directories needed.

/images ├─/drivers ├─Optiplex7040 ├─win7 └─x86 └─x64 ├─win10 └─x64 ├─Optiplex7050 ...

@mpatel said in Fog setup question:

Do i need to set mysql root password ?

No.

is this correct way for setting it up for private network ?

If that’s what you need, yes.

@mpatel It’ll work, but the capture will be really slow since it’s copying from & to the same physical disk. You’ll want to setup FOG with DHCP and you’ll want to use Bridged-mode for the NIC on both VMs. FOG requires internet connection to be installed. After installation, it does not need internet connection.