If you are a system admin who is still sticking to Clonezilla, you must probably look out to try FOG – a very fast and easy to deploy cloning solution. Compared to Clonezilla, Fog imaging process usually takes less than few minutes. With the current release, fog includes the ability and support for Linux and multiboot resizable imaging too. However,FOG can be used to image Windows XP, Vista, Windows 7 and Window 8 PCs using PXE, PartClone, and a Web GUI to tie it together.
I had one of my friend who runs cyber cafe business and keen on deploying the similar configuration on all the 50 Windows machine. I visited his cyber cafe in the inauguration day where I came up with the idea of cloning and rescue suite. I decided to help him out with the implementation of Fog – really a great tool.
- Installing Ubuntu 12.04.1
As a pre-requisite, install Ubuntu 12.04.1 on the physical machine.
Ensure Ubuntu Desktop packages are selected to be installed.
- Installing Fog Cloning Solution
- Open Firefox
2. Go tohttp://www.fogproject.org and download FOG.
3. Open Terminal Applications->Accessories->Terminal
4. cd Desktop (Remember Linux is case sensitive)
5. tar -xvzf fog*
6. cd fog*
7. cd bin
8. sudo ./installfog.sh
9. Select opt 2 Enter
10. N Enter
11. Default IP Enter
12. You dont need to set up a router IP but I will in case I ever use the server for DHCP.
13. Set up a DNS IP, just accept the default.
14. No do not change the default network interface.(you may not get this prompt if you have 1 nic)
15. I will not be using FOG for DHCP. (will require changing my current DHCP server.)
16. Note your IP settings and continue.
17. Enter to Acknowledge.
18. (I like to notify the FOG group, they have made a great product and deserve my feedback, choice is yours here)
19. gksu gedit /var/www/fog/commons/config.php and put your mysql password you typed during install in “MYSQL_PASSWORD”, “<passwordhere>” save and close. It has been noted that you also should change the MYSQL password here while you are at it /opt/fog/service/etc/config.php.
20. Browse to http://localhost/fog/management
21. Click install!
22. Click to log in. You can now reach this webpage from anywhere on the network where your server is installed by using it’s ip address. eg http://192.168.0.100/fog/managementI would reccomend putting an A record in your DNS called FOGSERVER this will make things easier to remember.
default: fog/password
Creating an Image in FOG
The following instructions walk administrators through the process of configuring a computer for image creation in FOG.
Create Image in FOG
Log into the FOG management console
- FOG management console URL or address is:
http://ip address/fog/management
- Click the Image Management icon
- Click New Image button in the left section of screen
- Enter the following Information
- Image Name: Use clear concise name
- Consider keeping name short and model or OS specific
- Image Description: Enter clear concise description
- Storage Group: Default
- Image File: Will automatically be entered. You may edit if you want
- Image Type
- Windows XP = Single Partition (NTFS Only, Resizable)
- Windows Vista/7 = Multiple Partition Image – Single Disk (Not Resizable)
- Click Add
Inventory Machine
- Boot host machine to FOG pxe boot menu
- Select Perform Full Host Registration and Inventory
- Enter the computer Host Name and press enter
- Leave IP Address field blank and press enter
- Press the ? and press enter to get the list of Image ID’s
- Enter the Image ID number
- Press the ? and press enter to get the list of Operating System ID’s
- Enter the Operating System ID number
- Choose Y or N to add to Active Directory
- NOTE: XP choose Y, Vista/7 choose N
- Leave Primary User field blank and press enter
- Leave both Asset #’s blank unless you utilize
- Select N as you do not want to Image this machine and press enter
- Enter “fog” and press enter
- Load machine with all software and drivers you need.
- Windows XP you need an image for each model
- Windows Vista & Windows 7 you can use the same image for any model but hard drive size can cause issues.
**DO NOT Activate Windows in Vista or 7**
Optional
It is a good idea to change the default boot order to enable the network boot to be your first boot item. It is not required, however. All brands have a slightly different way of doing this. Check your manufacturer’s manual for assistance figuring out how to boot into the BIOS to make this change.
- Ensure all Windows Updates are Current
- Make sure all service packs are current
- Make sure current with .NET framework
- Install the FOG Client
- Enter the IP address of your FOG server
- Leave all other options checked
- Windows XP continue to STEP 13
- Windows Vista & Windows 7 continue to STEP 25
Windows XP
- Install the Windows XP Service Pack 2 Support Tools
- http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=49ae8576-9bb9-4126-9761-ba8011fabf38
- Download Windows XP Service Pack 3 Deployment Tools
- http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=673a1019-8e3e-4be0-ac31-70dd21b5afa7
- Open the deploy.cab file
- Select all files within
- Right Click and select Extract
- Select the following destination
- C:\Windows\System32\Sysprep
- NOTE: If the Sysprep folder doesn’t exist you need to create it
- Double Click the setupmgr.exe file in the C:\Windows\System32\Sysprep folder
- Click Next
- Select Modify Existing
- Click Browse Button
- Go to the C:\Windows\System32\Sysprep folder if not already there
- Click the drop down menu in the “Files of type” field
- Select Sysprep Inf Files (*.inf)
- Select the sysprep.inf file
- Click Open
- Click Next
- Make sure “Sysprep setup” is selected
- Click Next
- Select “Windows XP Professional”
- Click Next
- Select “Yes, fully automate the installation” if you use the same product key for all machines. If not select “No, do not fully automate the installation”
- Click Next
- Change the following settings:
- Name and Organization
- Time Zone
iii. Product Key
- Computer name
- Set to Automatically generate computer names (FOG will rename for you)
- Administrator Password
- Click File
- Click Save
- The save location should be C:\Windows\System32\Sysprep
- Click OK
- Close the Setup Manager program
- Run Disk Cleanup
- Select all items
- Click the More Options Tab
- Under the “System Restore and Shadow Copies” section click the Clean Up button
- Click OK
- Click the Delete Files button
- Run Disk Defragment Tool
- Run the defragmenting tool and ensure there is not more than 5%-10% fragmentation
- 1%-2% is ideal
- When ready to Sysprep the machine ensure you have installed all programs you want on the machine and removed everything you do not.
NOTE: You cannot turn the machine back on after SYSPREP’ing until after you have taken the image.
- When ready to sysprep the machine proceed to step 12.
- Navigate to C:\Windows\System32\Sysprep
- Double Click the Sysprep.exe file
- When the Sysprep program appears choose the following settings
- Options section
- Check “Use Mini-Setup”
- Shutdown Mode: “Shut down”
- Click Reseal button
- The machine will sysprep and then shut down
- Continue to STEP 37
**Leave the machine OFF until instructed otherwise**
Windows Vista & Windows 7
Windows Vista & Windows 7 do not have the Support Tools XP does. These instructions will cover this difference along with different SYSPREP steps.
Retrieving NETDOM.exe Instructions
You will need to perform STEP 6 in the Windows XP instructions on a Windows XP machine. You only need to do this one time.
Once installed navigate to C:\Program Files\Support Tools
Locate the NETDOM.exe file and copy
On a flash drive or network share you manage create a folder called “Support Tools”
Paste the NETDOM.exe file into the new Support Tools folder
- Copy the “Support Tools” folder (see “Retrieving NETDOM.exe Instructions”)
- Navigate to C:\Program Files
- Paste Support Tools folder into Program Files folder
- Path will be C:\Program Files\Support Tools
- NETDOM.exe will be inside the Support Tools folder
- Run Disc Cleanup Utility
- Check all items
- Click More Options tab
- In the System Restore and Shadow Copies section click Clean Up
- Click Delete button
- Click OK
- Click Delete Files button
- Run Disc Defragmenter Utility
- You can choose to simply Analyze the disc first. Your disc must be less than 15% fragmented. If it is higher then defragment it.
- I recommend defraging it anyway to get it as low as possible
**Ensure you are prepared to SYSPREP this machine as you will have to repeat the following steps if you have to boot the machine after SYSPREP’ing**
Optional
Past versions of FOG required Vista and 7 images to have the following three commands run immediately before continuing to STEP 23
Run CMD.exe as Administrator
bcdedit /set {bootmgr} device boot
bcdedit /set {default} device boot
bcdedit /set {default} osdevice boot
**It is not required to run these commands**
- Copy the unattend.xml file to the following location:
- c:\windows\system32\sysprep
- Run CMD.exe as Administrator
- Run the following command:
- cd c:\windows\system32\sysprep
- Now run the following command to sysprep the drive:
- sysprep /generalize /oobe /shutdown /unattend:c:\windows\system32\sysprep\unattend.xml
- SYSPREP will take a few moments to run
- The machine will shut down when done
- Continue to STEP 37
**Leave the machine OFF until instructed otherwise**
Uploading the Image
Choosing shutdown after task completion ensures you don’t begin unpacking your sysprep’ed machine by booting to Windows should the image upload fails.
- Log into the FOG Management Console
- Click the Task Management icon
- Click List All Hosts
- Locate the host you Inventoried in the Inventory Machine section of these instructions
- Click the Upload arrow for the indicated host
- Add a check to the following option
- Shutdown after task completion?
- Click Upload Image
- Ensure the host machine PXE boots and not to the hard drive
**NOTE: If the machine begins to boot to Windows for any amount of time you will need to SYSPREP again if your image has not been uploaded successfully
Test Image
- When the image has been uploaded test it on a different machine
- Ensure you use the same make and model if using a Windows XP machine
- Vista and Windows 7 machines are not model or brand specific but you may run into driver issues. You will need to address those issues either prior to upload or after.
46. Test as many possible scenarios prior to implementing your image to production
Comments are closed.