FOG Project - User contributions [en]

Building a Custom Kernel

2013-02-07T19:04:12Z

Itismike: per this post, bzImage isn't necessary: http://fogproject.org/forum/threads/vmware-hard-disk-clone-part-2.141/#post-1619

=== Building a Custom Kernel ===

== Overview ==

In FOG the kernel and the boot file system are separate and interchangeable, this makes it easier to upgrade a kernel without modifying the boot file system. This also means that all drivers in the kernel are build into the kernel instead of being compiled as modules. In our example we will be compiling the kernel on Fedora 9.

== Build Process ==

# Install the required packages to build the kernel with:
#* RHEL/Fedora/CentOS/.rpm other: (need confirmation that this is all the packages required?!?, may also need qt-devel and a few others)
#: <code>yum groupinstall "Development Tools"</code>
#* Ubuntu/Debian/.deb other:
#: <code>sudo apt-get install qt3-dev-tools libqt3-mt-dev</code>
# Download the latest kernel source (which in this case is version 2.6.35.3):
#: <code>cd /usr/src</code>
#: <code>wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.35.3.tar.gz</code>
# Extract the tar file:
#: <code>tar -zxvf linux-2.6.35.3.tar.gz</code>
# Copy the .config file from the fog release package which is located in the Fog Setup ./kernel directory:
#: <code>cp /opt/fog-setup/fog_0.29/kernel/kitchensink.config /usr/src/linux-2.6.35.3/.config</code>
# Start configuring the kernel:
#* RedHat forks:
#: <code>make menuconfig</code>
#* Ubuntu/Debian, etc:
#: <code>make xconfig</code>
#* This will run the kernel configuration tool, you will need to navigate around it a little to get a feel for it as there are many options. Placing a check mark in a box will include it in the kernel, and unchecking an item will remove it from the kernel.
#* To add or remove drivers from the kernel you will need to go to '''Device Drivers''', and network drivers are in '''Network Device Support.'''
#* '''Important:''' All settings required by fog are already in the kernel, when you are done making changes click '''save''' and close the application.
# Now you need to build the kernel:
#: <code>make bzImage</code>
#* or possibly just:
#: <code>make</code>
#* ''This could take 10 minutes, depending on the speed of your machine and how many options you checked.''
# Backup your FOG kernel, and copy the new kernel image to your TFTP kernel folder, probably under /tftpboot:
#: <code>sudo cp /tftpboot/fog/kernel/bzImage /tftpboot/fog/kernel/backup/bzImage_</code>'''YYYYMMDDHHMMSS'''
#:* ''Of course, you can name your backup anything you want, that is simply the name convention used by FOG
#: <code>sudo cp /usr/src/linux-2.6.35.3/arch/x86/boot/bzImage /tftpboot/fog/kernel/bzImage</code>
# And, you're done! Try booting a client with your new kernel to test it. Repeat steps 5-7 above if you need to make any changes. If you are happy with your configuration, you can save the configuration by backing up the .config file located in the boot of the kernel source directory.

== Note ==

When building on x86_64 systems you may need to specify that you are building for an x86 target architecture.

<code>make ARCH=i386 menuconfig</code>

<code>make ARCH=i386 bzImage</code>

Client Setup

2013-01-22T16:20:42Z

Itismike: Clarified pre-installation steps including BIOS settings, partition deletion, etc.

== Absolute Basics ==
When using FOG all clients should be setup to have PXE boot as the [[Booting into FOG and Uploading your first Image#Set_client_to_PXE_boot_in_BIOS|first boot device]]. This allows imaging tasks to be deployed without visiting the client computer, while only slowing down the boot process by a few seconds. 
If you are following this guide straight through, it is a good idea to test an upload on a spare computer rather than testing it on your master image after doing all the steps below, just in case of complications.

=== Deciding on an Image Strategy ===
FOG's strength is the flexibility to adapt to your environment needs.
As an example lets say you have 20 of one computer model and 20 of another.
You need to support both groups of machines and wish to use FOG to host images for both the machines.

There are two ways to do this.

* Create an image for a specific computer (useful if you have 10+ more of the same model computer)
* Create a hardware independent image (useful if you have many different models of computers in your environment)

''' Example: '''
Your environment has 20 Dell Optiplex 760 Machines.
Your environment also has 20 Lenovo ThinkCentre M91p Machines.

Since FOG allows you to group your host and apply the same image to all host in that group, it might be better for you to create a standard ''Dell'' Image and a seperate ''Lenovo'' Image.
However if you have 5+ machines with different models, it might be time to create a ''Master Image'' that covers the hardware for ALL your machines. These are known as ''Hardware Independant'' Images or ''Master'' Images. They are also known as ''Golden Images''. Regardless of the name used, they all mean the same thing. An image that works on any machine/hardware.

== Common Steps for Any OS Installation ==
=== Always Start with a Clean Hard Drive ===
Even if your drive is brand new from the Factory, it is recommended to wipe the drive before you install an OS on it.
This is considered a '''best practice''' and has several reasons for doing so.

=== Reasons for Wiping a Hard Drive ===
==== Brand New Hard Drives ====
Even if the drive is brand new from the factory in an unopened box, you should wipe it.
In 2007 [http://www.zdnet.com/blog/hardware/malware-found-on-new-hard-drives/928 an incident was reported] where 1800 brand new hard drives were shipped from the manufacturer with a virus already on the drive. While the likelihood of hard drives being infected from the manufacturer is extremely small, wiping a drive with a single pass only takes a few minutes and can save you much heart aches in the future. It is also a good way to test the drive to make sure it's not a bad drive from the factory. Most hard drives that have a factory defect will die within the first few months of use. If the drive fails during the wipe, you normally can return it to the store in a timely manner and get a new one.

==== Used Drives ====
Deleting partitions or doing a ''soft'' format isn't enough. Some virus and malware components can survive a full disk format. They place themselves in un-used disk areas (eg: [http://www.eset.com/resources/white-papers/Rooting-about-in-TDSS.pdf counting backwards] from the last logical block of the drive geometry.) Even though they cannot execute themselves until specifically called, a re-infection could allow them to access previously-saved information, such as keylogger data or other personal information.

=== Wiping a Drive ===
''Wipeing a Hard drive can take a long time depending on the size of the drive!''
On average a 160gb SATA hard drive can take an hour to wipe.
Writing a single pass of data (random or not) is plenty sufficient to remove all traces of a program or malware. In fact, the [http://en.wikipedia.org/wiki/Gutmann_method Gutmann method] has been called useless by the creator of the method [http://en.wikipedia.org/wiki/Gutmann_method#Criticism] as his paper was misinterpreted. Thirty Five passes are not needed in modern drives.

==== Windows 7 ====
Open a Command Line as Administrator
Type: <tt>format /p:1 '''<Drive Letter>'''</tt>
Replace '''<Drive Letter>''' with E:\ or which ever drive you wish to format.
This will zero-out all bits on a disk.

==== UNIX/Linux ====
Open a Shell prompt as ''root'' or a user with ''sudo'' rights on Ubuntu/Debian based machines

===== Simple Wipe =====
Fedora: <tt>dd if=/dev/zero of=/dev/sd'''X'''</tt>

Ubuntu/Debian Based <tt>dd if=/dev/zero of=/dev/sd'''X'''</tt>

''Replace '''sdX''' with the driver leter you wish to wipe''
This will zero-out all bits on the disk

===== Random Wipe =====
Fedora: <tt>dd if=/dev/random of=/dev/sd''X''</tt>

Ubuntu/Debian Based <tt>dd if=/dev/random of=/dev/sd''X''</tt>

''Replace '''sdX''' with the driver leter you wish to wipe''
This will zero-out all bits on the disk

==== FOG ====
FOG has a built-in utility that can do this as well. Be sure to use '''Normal Wipe''' as Fast Wipe only zeros out the first few sectors of a disk (Master Boot Record and Partition Table). A Full Wipe is not necessary to remove data from a disk. It is reserved for the [http://www.root777.com/security/the-great-zero-challenge/ most extreme] cases.

==== DBAN ====
[http://www.dban.org/ DBAN] is another tool you could use to wipe a drive. It is available as a bootable ISO (or put on a USB drive if you wish[http://www.pendrivelinux.com/]) and can wipe many drives at the same time. It supports all types of wipes. Either Zero, Random, 7 Pass, or even 35 Pass.

== Single Image Machines ==

=== Install Windows ===
* Set the BIOS to your preferred SATA mode. Legacy and AHCI work very well. Intel (fake) RAID has caused problems.
* After wiping your hard drive, install Windows as normal on the machine you wish to make the image for.
** During installation, select Custom(Advanced) to open the disk partitioner and delete any existing partitions.
** Click Next to continue with Unallocated space. Do not manually create partitions unless absolutely necessary. Doing so may break FOG's ability to manage Windows.

=== Install Updates ===
Be sure to perform all updates. Windows often requires multiple reboots and visits to update.microsoft.com until everything reports as up-to-date.
''Note that Windows may attempt to push additional software through the update channel such as Windows Live and Silverlight. Decide what you want on your platform before accepting additional software.''
It is recommended you at least explore the ''custom'' updates section as many times there are updated drivers for your hardware.

=== Install Software ===
Any software that are constantly updated such as Adobe Products (reader/flash), Java or anything that has the possiblity of being out-of-date. Should be installed using other means ''AFTER'' the image is made. This will save space as well as keep security risk to a minimum. Execptions should be made for large applications or time-consuming software such as Microsoft Office Suite.

* Install any software that is necessary for client management.
:: For example, install the FOG Service. Don't forget to place your customized version of hostnamechange.dll in the FOG programs folder.
* Install other enterprise tools you need such as SCCM or Atriris services.

=== Setup a Default Profile ===
In order to have the same settings for all new profiles on the machine such as desktop shortcuts you should setup a default profile.
''Note:'' The default profile is different from the all users profile. All Users are only for profiles already created. Any new profile will be generated by using the default profile.

==== Windows XP ====
<ol>
<li>Create a new profile</li>
<li>Setup the profile as you wish - Shortcuts/Desktop Image</li>
<li>Log out of this profile and log in to the administrator profile.</li>
<li>Copy the profile: Right-click My Computer > Properties > Advanced > User Profiles. Select the profile you edited and choose to Copy it to the Default Profile folder under Documents and Settings.</li>
<li>Ensure permissions are correct: Under Permitted to use, click Change, click Everyone, and then click OK.</li>
</ol>
You may wish to see [http://support.microsoft.com/kb/168475 MS KB 168475] and [http://support.microsoft.com/kb/959753 MS KB 959753] for details.

==== Windows 7 ====
This is handled by Sysprep. You can use the '''<CopyProfile>true</CopyProfile>''' in your unattend.xml file.

=== Remove Unnecessary Software/Files ===
It is recommended you remove any software that is not used.
You can use a cleaner program such as [http://www.piriform.com/ccleaner ccleaner] to remove unnecessary files. Other things you can remove to save image size space are:
::* shrinking/turning off system restore.
::* removing hotfix uninstaller folders

=== Before Running Sysprep ===
==== Make a Pre-Sysprep an Image ====
It is recommended that you make a system image using FOG ''BEFORE YOU SYSPREP''!
Sysprep does alot of changes, and takes a long time. It is useful to make an image of the drive the way it is now incase something happens during the sysprep process.
It is also nice to have a pre-sysprep image available when it comes time to update the systems image. You can deploy the pre-sysprep image to the computer and then update windows or install new software etc. without having to redo this entire process!

==== Before Running Sysprep ====
Other steps to consider are:
* Run Chkdsk /f /p prior to imaging
* Defrag the drive
* Make sure 2gb of disk space is free or the NTFSresize will fail
* Make sure the FOG service is installed and properly configured
* Update your [http://www.fogproject.org/wiki/index.php?title=Managing_FOG#Securing_Active_Directory_Integration hostnamechange.dll] file
* For *Windows 7 ONLY*: FOG Prep
** (Both of the above are available from your FOG server: FOG_Server_IP_or_Hostname/fog/client/)
*pasted from notes: (Some of these are best handled at the enterprise-level (Group Policy) rather than maintaining them on the image.)
<pre>
Enable Admin account
Set admin PW
Disable UAC
Disable Sidebar objects?
My Computer, IE, Recycle Bin, Documents on Desktop
Change Home page
Delete Start Menu Items
Run Media Player
Disable System Restore
Disable Hybernation - delete Hyberfile.sys
disable Virtual Memory - delete pagefile.sys
Disable Firewall
Disable Windows Defender
Disable automatic updates
Security Center - Warnings
Disable Windows Welcome Screen
Don't show this message - IT Information Bar
Power Options
HAL Drivers set correctly within Device Manager (Advanced Configuration and Power Interface (ACPI)
Show "Run" and "Printers" in Start menu
Windows Updates up-to-date
Enable Remote Desktop
Enable Remote Assistance
Show Hidden Files Disable Hidden Files
Remove/Delete other Windows Accounts
Delete Recent Items
Empty Recycle Bin
Copy Creation Profile to Default profile
Defrag
Disk Clean up
Chkdsk OS partition
bcdedit /set {bootmgr} device boot
bcdedit /set {default} device boot
bcdedit /set {default} osdevice boot</pre>

*Set up "creation" profile exactly how user profiles will be.
*Select option to copy profile to Default profile during Sysprep
*Rather than enabling Admin account as described above, disable built-in Administrator account - create custom named Administrator account and Set password

Windows 7: Add NetDOM*
*As of FOG 0.28 this is no longer riquired. 
Both: Download Sysprep - don't use included version

==== Run Sysprep ====
===== Windows XP =====
<content needed>
===== Windows 7 =====
<content needed>

== Dual boot Images ==

This part is referred to the installation of the master PC to be cloned, in the following working environment:

* Fog 0.32 - http://www.fogproject.org/
* The installation of the server has been accomplished using the official wiki infos
* The installation will be performed on Dell Optiplex 960
* The desired system is a dual boot
** Windows 7
** Ubuntu (12.04 alpha at the moment, final installation will be done on Ubuntu 12.04 LTS)

=== PC configuration ===

The needed partitions are:
# Windows 7 (about 100M)
# Windows 7 (the all system)
# linux swap
# linux home

The disk is partitioned in 4 primary partitions, the installation sequence is:
* Windows installation (Seven will setup 2 partition)
* Manual disk resizing/partitioning to add a swap and the linux partition (formatted as ext3)
* Ubuntu installation

NOTE: FOG use partimage, so the selected partition type must be compatible with partimage

=== Windows Seven ===

No particular modifications (i.e. see the relevant part on installing a standalone Windows 7)

=== Linux Ubuntu ===

The installation is a standard Linux installation, but the default grub is not supported
(see also http://www.ehu.es/es/web/instalaciones/fogehu/-/wiki/main/conocimiento#Despliegue_de_im%C3%A1genes_con_Ubuntu_11.04), so we downgrade to grub-legacy:

apt-get install -y grub
cp NEWmenu.lst /boot/grub/menu.lst
cp ${DATA_DIR}/wallpaper-asid-640x480.xpm.gz /boot/grub/wallpaper-asid-640x480.xpm.gz
grub-install /dev/sda

where the NEWmenu-lst is:

timeout 10

# Pretty colours
color cyan/blue white/blue

#splashimage
splashimage=(hd0,3)/boot/grub/wallpaper.xpm.gz

title GNU/Linux Ubuntu
root (hd0,3)
kernel /boot/vmlinuz-3.2.0-14-generic-pae root=/dev/sda4 ro quiet splash
initrd /boot/initrd.img-3.2.0-14-generic-pae

title Windows 7
rootnoverify (hd0,0)
chainloader (hd0,0)+1

quiet
savedefault
boot

The partition naming and kernel filenames are related to a particular installation: you need to check them.
Here we setup a custom grub wallpaper: it is an XPM image, 640x480, 14 colors.

=== Image Upload ===

The image upload need to be setted as:

* Single disk, multiple partitions
* OStype Linux

The option Single disk, multiple partition will manage to upload/deploy all the partition of the disk.
The OStype setted to Linux will copy a 32256 bytes MBR.

NOTE: setting a Windows 7 OStype, will clone a 512 bytes MBR: at the boot the system will show the string GRUB and then will hang!

With this configuration, after the image upload, in the directory '''/images''' of the fog server there should be a directory with the name selected for the image containing:

* d1.mbr (the MBR: should be 32256 bytes)
* d1p1.img
* d1p2.img
* d1p4.img

there are 1 file for partition, with the exception of the swap partition.

== Hardware-Independent Images ==
Making a Hardware Independent Image, is very similar to making a Single Machine Image with a few very important differences.

=== Understanding HAL ===
HAL (Hardware Abstraction Layer) is very similar to the Kernel in *nix systems.
====Windows XP and HAL====

Not using the correct HAL will lead to a BSOD on your computers or give you a huge performance hit.
Luckly you can tell Windows XP (via sysprep) to update the HAL on the fly.

'''Windows XP typically uses one of 3 HAL types.'''

*Advanced Configuration and Power Interface (ACPI)
*ACPI Uniprocessor PC
*ACPI Multiprocessor

'''Updating HAL with Sysprep.inf'''

You can update the HAL dynamically by adding this to your Sysprep.inf under the [unattended] section

''
UpdateUPHAL = “ACPIAPIC_UP,%WINDIR%\Inf\Hal.inf”
UpdateUPHAL = “ACPIPIC_UP,%WINDIR%\Inf\Hal.inf”
UpdateUPHAL = “MPS_UP,%WINDIR%\Inf\Hal.inf”
''

''As a General rule it is best to create your image using a machine (or virtual machine) using a single processor (ACPI Uniprocessor PC). Using a Muti-core processor might yield unexpected results even when using the UpdateUPHAL lines in the sysprep.inf file.''

====Windows Vista,7 and Beyond====

As of Windows Vista you '''don't need to worry about HAL's''' due to the /generalize switch.
When you use this switch with sysprep Windows will automatically take care of updating the HAL during the sysprep process!

=== Install Wipe / Install / Setup ===
At this point you should:
For help with these steps refer to the Single Image Directions above.
*Wipe The Hard Drive
*Install Windows
*Install Large Software Packages
*Install other Enterprise software (such as FOG Client)
*Install Windows Updates
*Setup Default Profile
*Remove Unnecessary Software/Files

=== Changing the IDE Controller to Standard ===
''Windows XP Only''
If using Windows 7 you can skip this step.
To help make the image more compliant to other hardware, you should change the IDE controller to the standard driver included with Windows XP.
To do this:
*Open Computer Management (right click '''My Computer''' Select Manage)
*Locate the IDE ATA/ATAPI Controllers
::*Expand
*Right Click on the IDE Controller
*Select Update Driver
*If asked to search online select No, not this time.
*Select install from a list or specific location (advanced)
*Select Don't Search, I will choose the driver to install
*Make sure "Show Compatible Hardware" is checked
*Select the Standard Dual Channel PCI IDE CONTROLLER
*Next
*Finish
*Reboot

This will allow Windows to boot on the target machines, then the new hardware wizard will take over and detect the correct controller card for that machine.

=== Loading Drivers ===

==== Mass Storage Drivers ====
To make a truly hardware independent image it is recommended you load all the mass storage drivers in your image.
To include every mass storage driver needed for '''any''' machine you could use [http://driverpacks.net/ driver packs].

==== Other Drivers ====
You should also include all other drivers for all your other machines. These drivers should include VGA Drivers, Network Drivers, Sound Drivers and any other drivers you might need for those systems.

=== Before You Sysprep ===
==== Make a Pre-Sysprep an Image ====
It is recommended that you make a system image using FOG ''BEFORE YOU SYSPREP''!
Sysprep does alot of changes, and takes a long time. It is useful to make an image of the drive the way it is now incase something happens during the sysprep process.
It is also nice to have a pre-sysprep image available when it comes time to update the systems image. You can deploy the pre-sysprep image to the computer and then update windows or install new software etc. without having to redo this entire process!

==== Run Sysprep ====

===== Windows XP Sysprep Guides=====
[http://www.vernalex.com/guides/sysprep/ Vernalex Sysprep Guides] offer some great advice on this subject. You should pay particular attention to the [http://www.vernalex.com/guides/sysprep/mass.shtml mass storage devices] part of the guide as this is crucial to makeing the image work with your hardware. It is recommended to build the mass storage section before running sysprep.

You should also read [http://support.microsoft.com/kb/302577 Microsoft KB Article 302577] on sysprep

===== Windows XP =====
Run Sysprep.exe and tick mini-setup and detect plug and play hardware.
Click Reseal.

===== Windows 7 =====
<content needed>

=== Take a Post-Sysprep Image ===
'''TEST THIS IMAGE''' Before use in a production environment. Your first try might not work, you might be missing drivers that you will have to add. This is why it is recommended to make a Pre-Sysprep Image. It might take a few trys before all the drivers needed are loaded.
When all is done right, it's worth the time as you will have an image that works on ANY HARDWARE!

If the image works fine on one type of computer, try others to make sure its truely hardware independant. If it works well, this is the image you should use when deploying to your target machines.

Talk:Password Central

2011-12-06T20:09:13Z

Itismike: /* MySQL Root Account */

== Scratch Area ==
See the Discussions tab at the top for templates and known password locations. 
And please, feel free to make adjustments and add content!

= Template =

====Fog's user account on main FOG server====
This is a standard user account on the server. It is named 'fog' 
Common errors associated with this mismatched password:
<ul>
<li>FOG can't do anything</li>
<li>Unexpected, strange errors</li>
<li>...</li>
</ul>
How to modify this password:
:The location varies per operating system.
:To reset it, type this at the command line on the Main FOG server:
<pre>sudo passwd fog</pre>
'''(Click EDIT to copy the source code of this template)'''

= Known Passwords =
===Passwords on the Main FOG Server===
====TFTP Credentials====
"Other Information" > "FOG System Settings" > "TFTP Server"
<pre>FOG_TFTP_FTP_USERNAME
FOG_TFTP_FTP_PASSWORD</pre>

====MySQL Root Account====
<tt>/opt/fog/service/etc/config.php</tt>
<pre>define( "MYSQL_HOST", "localhost" );
define( "MYSQL_DATABASE", "fog" );
define( "MYSQL_USERNAME", "root" );
define( "MYSQL_PASSWORD", "SQLpassword" );
</pre>

<tt>/var/www/fog/commons/config.php</tt>
<pre>define( "MYSQL_DATABASE", "fog" );
define( "MYSQL_USERNAME", "root" );
define( "MYSQL_PASSWORD", "SQLpassword" );</pre>

NOTE: SQLpassword is usually blank if following the FOG installation instructions.

====PXE Boot Menu passwords====
See [https://sourceforge.net/projects/freeghost/forums/forum/716419/topic/3669158 this forum post]

===Passwords on Storage Nodes===
==== The storage node's management password ====
"All Current Storage Nodes" > "Edit Storage Node Definition"
<pre>Management Username:
Management Password:</pre>

To match what was in "Other Information" > "FOG System Settings" > "TFTP Server"
<pre>FOG_TFTP_FTP_USERNAME:
FOG_TFTP_FTP_PASSWORD:</pre>

Storage > Select Storage Node > Edit Storage Node Definition
<pre>Management Username: fog
Management Password: [pw of user 'fog' on the storage node]</pre>
How to reset:
From the command-line of the Storage Node:<pre>sudo passwd fog</pre>
 
<pre>/var/www/fog/commons/config.php
define( "TFTP_FTP_USERNAME", "fog" );
define( "TFTP_FTP_PASSWORD", "****" );</pre>

<pre>define( "STORAGE_FTP_USERNAME", "fog" );
define( "STORAGE_FTP_PASSWORD", "3b4f2a" );</pre>

<pre>define( "MYSQL_DATABASE", "fog" );
define( "MYSQL_USERNAME", "root" );
define( "MYSQL_PASSWORD", "" );</pre>

How to change:
On the node:<pre>sudo vi /var/www/fog/commons/config.php</pre>

Talk:Create a windows 7 image for many different hardware

2011-10-11T14:02:48Z

Itismike:

FOGprep.exe and bcdedit are not necessary when using sysprep and the /generalize command:
https://sourceforge.net/projects/freeghost/forums/forum/716419/topic/4502277
[[User:Itismike|Itismike]] 07:02, 11 October 2011 (MST)

Troubleshooting an image upload

2011-08-09T16:42:54Z

Itismike:

=== Troubleshooting an image upload ===

To make this process easier, we are going to use an Windows XP image. '''Note that this process has not been tested on Windows 7.''' Please also note that this process will change your partitions on the client computer. This tutorial assumes that your disk is /dev/sda1.

<ol>
<li>In the management portal, start a debug task for the client computer in question. Allow the client to boot and at the bash prompt type the following commands.</li>
<li>mkdir /images</li>
<li>mount -o nolock x.x.x.x:/images/dev /images (where x.x.x.x is the server ip)</li>
<li>cd /images</li>
<li>dd if=/dev/sda of=/mbr.backup count=1 bs=512</li>
<li>/usr/local/sbin/ntfsresize -f -i -P /dev/sda1 Look for ''You might resize'' you will need this number, so write it down. We will call this number ''NTFSSize''.</li>
<li>Take NTFSSize and divide it by 1000</li>
<li>Now add 300000 to that number and write down as '''N'''</li>
<li>Now take NTFSSize again and multiply it by 1.1 and then round that to the nearest whole number and write it down as '''F'''</li>
<li>/usr/local/sbin/ntfsresize -f -n -s '''N'''k /dev/sda1 (where N is the value calculated above with a k after it.</li>
<li>If the test above ends successfully then run: /usr/local/sbin/ntfsresize -f -s '''N'''k /dev/sda1</li>
<li>fdisk /dev/sda</li>
<li>Press "d", then Enter</li>
<li>Press "w", then Enter</li>
<li>fdisk /dev/sda</li>
<li>Press "n", then Enter</li>
<li>Press "p", then Enter</li>
<li>Press "1", then Enter</li>
<li>Press "1", then Enter</li>
<li>Press "+'''F'''K", then Enter (where F is the value calculated above; K must be capital)</li>
<li>Press "t", then Enter</li>
<li>Press "7", then Enter</li>
<li>Press "a", then Enter</li>
<li>Press "1", then Enter</li>
<li>Press "w", then Enter</li>
<li>partprobe</li>
<li>/usr/local/sbin/partimage save /dev/sda1 /images/dev/[somefile] --volume=9900000000 -z1 -o -d -f3 -b</li>
<li>dd if=/mbr.backup of=/dev/sda</li>
<li>Press "w", then Enter</li>
<li>partprobe</li>
<li>/usr/local/sbin/ntfsresize /dev/sda1 -f -b -P</li>
<li>mv /images/dev/[somefile] /images/[somefile]
</ol>

Troubleshooting an image push to a client

2011-07-25T19:21:34Z

Itismike:

=== Troubleshooting an image push to a client ===

This process will '''wipe out''' whatever is currently present on the client computer. 
This tutorial is for FOG .30 pushing Windows XP and assumes that your primary disk is /dev/sda. '''Note that this process has not been tested on Windows 7.'''

<ol>
<li>In the management portal, start a debug task for the client computer in question. Allow the client to boot and at the bash prompt.</li>(Everything below is done within the bash prompt '''on the client's console'''.)
<li>From your client, mount the remote /images folder on your FOG server onto a local /images folder using nfs:<ul><li><tt>mkdir /images</tt> (type this on the client's keyboard, as explained above)</li>
<li><tt>mount -o nolock x.x.x.x:/images /images</tt> (where x.x.x.x is the server ip) you may try also <tt>mount -t nfs -o nolock x.x.x.x:/images /images</tt></li></ul>
<li>Copy the master boot record to the first 512 bytes of the local disk. Take a look into <tt>/usr/local/fog/mbr/</tt> to determine the correct MBR for your system. This example uses XP:
<ul><li><tt>cd /images</tt></li>
<li><tt>dd if=/usr/share/fog/mbr/xp.mbr of=/dev/sda1 bs=512 count=1</tt></li>(For previous versions, find the <tt>fog</tt> directory under:/usr/local/)</ul>
<li>Start fdisk and remove all previous partitions:<ul><li><tt>fdisk /dev/sda</tt> (Note there is no <tt>1</tt> at the end of the device name)</li>
<li>Press "d", then "Enter" - select a partition if prompted and repeat pressing "d"</li>
<li>Press "w", then "Enter" to save and exit fdisk</li></ul>
<li>Create a new partition:<ul><li>fdisk /dev/sda</li>
<li>Press "n", then "Enter"</li>
<li>Press "p", then "Enter"</li>
<li>Press "1", then "Enter"</li>
<li>Press "1", then "Enter" or just "Enter" to accept the default starting sector</li>
Note: Windows 7 users may want to create a 100M partition, then repeat these steps to create the system partition and assign the rest of the disk to the OS.
<li>Press "Enter" to accept the default ending sector</li>
<li>Press "t", then "Enter" to change the partition type</li>
<li>Press "7", then "Enter" for NTFS</li>
<li>Press "a", then "Enter" to toggle the bootable flag</li>
<li>Press "1", then "Enter"</li>
<li>Press "w", then "Enter" to save and exit fdisk</li></ul>
<li>Update the partition info:<ul><li><tt>partprobe</tt></li></ul>
<li>Use partimage to copy image from FOG server to local partition:<ul><li><tt>/usr/sbin/partimage restore /dev/sda1 /images/[imagename] '''-f3 -b'''</tt></li></ul>
<li>Use ntfsresize to expand partition:<ul><li><tt>/usr/sbin/ntfsresize /dev/sda1 '''-f -b -P'''</tt></li>(For previous versions, find sbin under: /usr/local/)</ul>
</ol>

An alternate way to do partimage (which gives more feedback) is to load the gui version of partimage with: <tt>/usr/sbin/partimage</tt>, then manually fill in the fields/choose options.

Troubleshooting a multicast

2011-06-27T12:28:54Z

Itismike: Created page with 'Taken from [https://sourceforge.net/projects/freeghost/forums/forum/716419/topic/4583604/index/page/1 this forum thread]. ---- * On your server open up terminal and kill any ru…'

Taken from [https://sourceforge.net/projects/freeghost/forums/forum/716419/topic/4583604/index/page/1 this forum thread].

----

* On your server open up terminal and kill any running udpcasts by typing
sudo killall udp-sender
* now run this command
udp-sender --file /opt/fog/log/multicast.log --ttl 1
* you should see <tt>broadcasting control to:</tt> and it should be the highest address of the subnet your fogserver is on
* the line before that should say your fogserver ipaddress and the interface
* Now boot up 1 client go to your pxe menu and select debug mode. Do this on the same subnet if possible. Type in:
udp-receiver --mcast-rdv-address yourfogserver
* On your server you should see that 1 client connected and then you can press any key to start the transfer
* On your client you should see the contents of your multicast log file scrolling by the screen. You can press ctrl-C to stop it.
 
Hopefully that worked. Now we need to test 2 clients.
* Run the command on your server again but this time change the <tt>--ttl 1</tt> to <tt>--ttl 32</tt>
* You will see that this time your broadcast control is 224.0.0.1 this is the multicast address
* Boot both clients in debug mode and run the client command on each. Once you see that both clients have connected to the server press any key and see if the log file transfers again to both machines this time. If it does not then chances are something is not setup properly in your router possibly routing tables or multicast settings.
 If it does work then good lets try one more step
* On your server run this:
gunzip -c "/images/anyimagename" | /usr/local/sbin/udp-sender --min-receivers 2 --portbase 9000 --interface yourInterface --half-duplex --ttl 32
* Now boot up 2 clients in debug mode and enter
udp-receiver --portbase 9000 --mcast-rdv-address fogserverIP | partimage -f3 -b restore /dev/sda stdin
you might need to change /dev/sda to your correct harddrive if it's different use fdisk -l to find out
* If the clients start imaging then it seems that all of your multicast settings are correct and the problem may lie within fog configuration if it doesn't work then you need to check your router settings

Talk:Troubleshooting an image push to a client

2011-05-25T14:29:41Z

Itismike:

This page needs help. What are we actually troubleshooting?
[[User:Itismike|Itismike]] 15:25, 12 February 2011 (UTC)

I made a first-approach at making this page more readable. Still a little vague on the fdisk commands.--[[User:Itismike|Itismike]] 14:29, 25 May 2011 (UTC)

File:E5.jpg

2011-05-14T14:34:16Z

Itismike: Select Image

Select Image

File:E4.jpg

2011-05-14T14:34:10Z

Itismike: Select School

Select School

File:E3.jpg

2011-05-14T14:34:02Z

Itismike: Boot Menu

Boot Menu

Capone

2011-04-15T18:24:50Z

Itismike:

:Please ensure you read about [[PXE]] before attempting to understand Capone if this is the first time.
:Also, be sure to visit this page to [[Plugins:_Capone|ENABLE CAPONE]]

Capone is a plugin used for automated deployment of images to a large number of PCs, but taking into account the fact that different machine models have different drivers and so an image for a machine of one make / model is not good for a machine of another make / model.

Capone solves this problem by keeping an association of crucial hardware information of the model of a machine with the appropriate image stored on the FOG server that has drivers for that model.

This crucial hardware information is formally known as [http://en.wikipedia.org/wiki/Desktop_Management_Interface DMI] or "Desktop Management Interface".

The native Linux program [[dmidecode]] is used by the Capone plugin's shell script component to get all the hardware information from the computer on which it is run.

== How it works ==

What Capone does is that it uses dmidecode present in the init.gz to be uncompressed and loaded into the client via [[PXE]] boot, and the capone shell script selects the needed information like SKU number (Stock Keeping Unit) to identify the model of the client and send it to the FOG server in real-time.

In the Capone web interface, the user is expected to enter DMI SKU code association with a particular image for a particular model. For example, all machines that have an SKU code of "ABCD-1234-X/PQR" will be for PCs from ABCD corp, 1234 series, PQR variant sub-model.

Now in the past, at least once, the standard image for this machine has been made and stored in the FOG server's /images directory. This image is known to the FOG web management console via the Images screen.

This image is now associated with the SKU code of "ABCD-1234-X/PQR" via the DMI/RegEx field in the Capone web interface screen.

This tells Capone that if the machine model has a SKU code of "ABCD-1234-X/PQR", it must be loaded with the particular image named "ABCD1234X" (or any comfortable name for your IT staff / operators to remember)

This being known, the image corresponding to the SKU is the one sent to the client.

Thus automated model recognition is achieved and there is no need for manual intervention as far as selection of the appropriate image goes.

Note that this is possible only because of the very useful dmidecode program and a custom script named fog.capone in the init.gz.

The way Fog uses init.gz and PXE to achieve a variety of tasks is as follows: 
Let us assume that we have a HP desktop whose system needs to be imaged or wiped and reinstalled. 
Then the setup would be as shown below:
<pre>
HP client ---(PXE request)---> Fog Server
.......

HP client <---(TFTP response init.gz)---- Fog Server
.......

HP client loads `init`, linux kernel and runs selected Fog option (PXE menu)
.......

HP client ---(TFTP upload/download request)---> Fog Server
.......

HP client ---(NFS upload)---> Fog Server
OR
HP client <---(NFS download)--- Fog Server
</pre>

For all this to happen, several settings need to be right:
* PXE setup of client is correct
* IP addresses for DHCP for signals before TFTP stage.
* TFTP/NFS/DHCP configured and running properly
* Web interface and Fog server processes running properly
* init.gz must be right for the specific client

The init.gz is a gzipped version of the initial part of Linux kernel which is loaded first.

The init image is binary and is not a gzip stream. It is mounted using a special utility script located at /utils/Boot Image Editor/FOGMountBootImage.sh

All you have to do is to go to that path and run the script:
<pre>
user@computer:~$ cd /utils/Boot\ Image\ Editor/

user@computer:~$ pwd
/utils/Boot Image Editor/

user@computer:~$ ./FOGMountBootImage.sh
</pre>

This does many things - it uncompresses the init.gz and mounts the resulting init to a temporary directory /tmp/tmpMnt 
In that mounted file system (within your ordinary Fog server file system) is a bunch of binary programs that might be useful to run on the client after being transferred over TFTP from Fog server to client as shown above. Also included are the following scripts:
<pre>
fog fog.man.reg fog.statusreporter fog.wipe
fog.auto.reg fog.chntpw fog.photorec fog.surfacetest
fog.av fog.chpass fog.quickimage fog.testdisk
fog.capone fog.debug
</pre>
Depending on what you chose in the PXE menu, one of these is run. 
Let us see a few interesting lines in the fog.capone script:
<pre>
dmivalue=`dmidecode -t 1 | grep SKU | cut -d' ' -f3`
echo "";
echo " * Using Key Value: ${dmivalue}";
echo "";
sleep 1;
</pre>
What this does is explained below.
<pre>
user@computer:~$ sudo dmidecode -t 1

# dmidecode 2.9
SMBIOS 2.3 present.

Handle 0x0001, DMI type 1, 25 bytes
System Information
Manufacturer: MICRO-STAR INTERNATIONAL CO., LTD
Product Name: MS-7104
Version: 3.0
Serial Number:
UUID: 00000000-0000-0000-0000-001D92092567
Wake-up Type: Power Switch
</pre>
"-t 1" is the Type of DMI info - "1" stands for System Information. 
Note this phrase in the output: "Handle 0x0001, DMI type 1, 25 bytes". 
("Product" is used instead of "SKU" because not all systems not have SKU Numbers, and to illustrate how to modify the command to your setup) 
This text is sent to grep, looking for "Product". 
The output of that command is a single line:
<pre>
user@computer:~$ sudo dmidecode -t 1 | grep Product

Product Name: MS-7104
</pre>

Now that output is "cut" using "cut -d' ' -f3". 
The command means this: take input, split by delimiting using single space as delimiter(-d' ') and return field number 3.
<pre>
user@computer:~$ sudo dmidecode -t 1 | grep Product | cut -d' ' -f3

MS-7104
</pre>
This is your product identification string. 
If you want to catch a different field than SKU number or Product Number, you simply have to change that parameter to something that you know is the crucial identification parameter from the DMI information of your systems.

Now to the really smart part - this '''DMI value is sent over HTTP to the Fog server''' via the following lines, to check and see whether such a record exists in the Capone DMI association tables in the MySQL database.
<pre>
dmi64=`echo $dmivalue | base64`
echo -n " * Looking for images..........................";
img="";
while [ "$img" = "" ]; do
img=`wget -O - "http://${web}service/capone.php?action=imagelookup&key=${dmi64}" 2>/dev/null`
sleep 2;
done
echo "Done";
</pre>
<pre>
dmi64=`echo $dmivalue | base64`
</pre>
dmi64 just holds the same dmi value in base64 encoding. This is ensure that there are no special characters in the transmitted data that might cause something in the web appliaction part to fail or behave unexpectedly.
If an image matching this DMI value exists, then download of that image begins soon. This is how automated imaging based on DMI information is achieved. 
Now if you '''generalise the situation to allow for any DMI field to be used''' to identify dmi values, you also need to supply the dmi field name you are looking for. This is the DMIField value in the web screen for Capone plugin where you are asked to associate '''DMIField''' (SKU Number / Product Number / UUID / Product Serial / Model / etc ... ) with the desired '''DMIRegex'''. 
The code that would be executed then would be:
<pre>
dmivalue=`dmidecode -t 1 | grep ${dmifield} | cut -d' ' -f3`
</pre>

The fog.* scripts are very informative if you have nominal understanding of Linux bash shell scripting. 
It also shows the wide range of tasks that can be performed by editing the desired one among the fog.* scripts in the init image.

Vista Image says 0xc000000e \windows\system32\winload.exe can not be loaded

2011-03-01T04:17:55Z

Itismike:

[[Image:Vista winload.png]]

This is typically caused when the following commands are not run on the client computer right before it is shutdown, and then rebooted for an image upload:

bcdedit /set {bootmgr} device boot
bcdedit /set {default} device boot
bcdedit /set {default} osdevice boot

However if you've already done this and received this message, you do not need to recreate your image. All you need to do is insert your Vista Install DVD, and use it to repair your previous installation. The machine will reboot, preform a checkdisk, and reboot again.

----

If it still isn't working, try [http://social.technet.microsoft.com/forums/en-US/itprovistadeployment/thread/096ec0c8-8f41-4824-873a-781315fc914e this]:

<blockquote>"Before you sysprep, open RegEdit and export the Mounted Devices key (<tt>HKLM/SYSTEM/MountedDevices</tt>). '''Do not close RegEdit.''' Open a command prompt and run sysprep:</blockquote>
<pre>c:\windows\system32\sysprep>sysprep -oobe -generalize -quit</pre>

<blockquote>Go back to the RegEdit window and import the Mounted Devices key that you exported earlier."</blockquote>
Now shutdown the PC and capture the image.

Talk:Knowledge Base

2011-02-18T07:26:37Z

Itismike: /* Talk section on the Wiki */ new section

How to image windows xp OS and restore windows xp OS?
Why I can not boot from pxe,show error receive from TFTP server!(Can DHCP IP from Fog)

== Installation of additional packages ==

Once a PC has been cloned and used for distribution, I would like to add additional programs on an adhoc basis. So PC1 will have only the base image. PC2 will have the base image and 1 additional package. Can these additional packages be deployed using FOG or must I use some other solution like Altiris or MS Deployment Manager?

Yes, you just need to install the FOG client service on the computer. The plugin you would use for this is called the snapin module.

== Host Name Changer Error Padding is invalid ==

I am getting a host name changer error padding is invalid and cannot be removed. Any ideas what may be causing this?

Got it! User error. I had to replace the hostnamechange.dll file.

== Problems Uploading Image ==

First let me say "Great Job on this software" I also work for a K-12 school system and while testing on an older HP/Compaq model HPD51c when I try to upload I get an error "Cannot open font file latarcyrheb-sun16 sh-3.1#" and the machine freezes up. Any ideas what I'VE done wrong.

Thanks
Keith Miller
Network Administrator
Overton County Schools
kmiller1@k12tn.net

I had the same problem. I did a quick format of the hard drive (did this from the advanced tasks in FOG) and this corrected the problem for me.

I get a similar error after running the disk surface test. '''sh: dircolors: command not found Cannot open font file latarcyrheb-sun16'''. I have fog running on Debian Lenny perhaps that is the issue.--[[User:Hillie|Hillie]] 11:26, 22 September 2010 (UTC)

== Upload error with new install ==

I have installed the server piece on an Ubuntu 8.04 VM on Xenserver. The install went well, the management console works great, but I cannot create an image from a workstation. When I initiate the upload the task says waiting for host to check in....and just sits there. What am I doing wrong?

Dick Wright
rhwright99@gmail.com

== Installation stops at GCC package ==

I am installing Fog on a Dell PE 700 and the install stops at Installing Package:GCC. firewall, Selinux and iptables are off and has a active internet connection using Fedora 10. help...

Eddie Gonzales egonzales@buckeyeusd.org

== move a image from one Fog server to another Fog server ==

Does anyone know how to do this?

== Internationalization Issue ==
Hi!

I'm trying FOG on my school, and it's great. However we use a Danish version of Windows XP which install program files in ''C:\Programmer\'' and not ''C:\Program Files\'' as in the english version. This

=== Preparing the Master Client host - Danish Windows XP ===
*Abstract:
**With FOX Service Installer (FOX Tray version 0.1) The installer installs in C:\Program files\FOX but looks for the FoxServiceConfig.exe in C:\programmer\FOX in the danish version of XP.

Install [http://www.microsoft.com/downloads/details.aspx?FamilyId=49AE8576-9BB9-4126-9761-BA8011FABF38&displaylang=en Windows XP service Pack 2 support tools] and if using the '''danish'' edition of Windows XP edit ''C:\Program files\FOG\etc\config.ini'' line with the path to netdom.exe from ''C:\Program files\Support tools\netdom.exe'' to ''C:\Programmer\Support tools\netdom.exe''

*[http://mars.tekkom.dk/mediawiki/index.php/FOG_installation_on_CentOS5#Preparing_the_Master_Client_host My WIKI about FOG]
Regards
[[User:Heth|Heth]] 00:48, 20 June 2009 (MST)

== Importing images ==

Does anybody know how i can import my images from my old fog server database into my new fog server database?

== Add DCHP to existing Fog Server that was setup without it. ==

We initially setup our fog server without DCHP, and used the PXE boot options on our windows DHCP server.
We now want to isolate it to it's own LAN, as it seems to drag down our network speed while uploading images.
Thus I want to FOG server to take over the DHCP function on that isolated network.
It's a debian system, and I did apt-get install dhcp3, but I'm unsure how to configure it.

How do I add DCHP to existing Fog Server that was setup without it?

== Using FOG to create automated images of client for backup purposes ==

Is it possible to use FOG to create automated images (snapshots) of clients for backup purposes?

I'd like to have FOG create an image of all clients each weekend and save the image a default path automatically. This way if a client hard drive crashes, I can send down the latest image and get them back up and running without having to reinstall all the applications independently.

Thanks.

== Talk section on the Wiki ==

Hey guys, what do you say we move discussions about using and troubleshooting FOG to the [https://sourceforge.net/projects/freeghost/forums Sourceforge] forums, and use the talk pages for discussing and/or previewing changes on the Wiki??

Uninstall FOG

2011-02-17T21:37:08Z

Itismike:

==Rerun the Installer==
If you simply want to run the <tt>foginstaller.sh</tt> to update your FOG server settings, rename the hidden <tt>.fogsettings</tt> file located under <tt>/opt/fog/</tt>:<pre>sudo mv /opt/fog/.fogsettings /opt/fog/fogsettings-firstInstall</pre>
==Remove FOG Completely==
If you want to remove all services, blank the database, delete all files/folders associated with FOG and remove the <tt>fog</tt> user account:<pre>
#Uninstall FOG

#remove service
sudo rm /etc/init.d/FOGImageReplicator
sudo rm /etc/init.d/FOGMulticastManager
sudo rm /etc/init.d/FOGScheduler

#delete fog database
sudo mysql
#(or 'sudo mysql -p' if you set a root password for mysql)
drop database fog;
quit

#Remove files
sudo rm -rf /var/www/fog
sudo rm -rf /opt/fog
sudo rm -rf /tftpboot
sudo rm -rf /images

#delete fog system user
sudo userdel fog
</pre>

Separate TFTP and DHCP Server

2011-02-11T05:30:04Z

Itismike: Created page with '=== Separate TFTP and DHCP Server === In this setup, the TFTP server and the DHCP server are hosted on a separate server. The TFTP server holds the PXE boot files including the…'

=== Separate TFTP and DHCP Server ===

In this setup, the TFTP server and the DHCP server are hosted on a separate server. The TFTP server holds the PXE boot files including the Linux Kernel, boot file system image, and pxe config files. The DHCP server is the server that assigns the clients with IP addresses and network connection information.

In this setup we will have two servers:

<ul>
<li>'''Server A''': This is the 'Master' server which will host Apache, MySql, NFS and HTTP</li>
<li>'''Server B''': This server will host TFTP and DHCP</li>
</ul>

In our example, both of these servers need to have a fresh install of Fedora. They will both need static IP addresses, in our example we will use:

<ul>
<li>'''Server A''': 192.168.1.50</li>
<li>'''Server B''': 192.168.1.51</li>
</ul>

On both nodes, download the FOG installation package from:

http://sourceforge.net/project/showfiles.php?group_id=201099

On Server A install FOG, when you are prompted with:

Would you like to use the FOG server for dhcp service? [Y/n]

Select "n" to not start DHCP on that server.

After installation is complete navigate to:

http://localhost/fog

and install the FOG schema.

On server A go to:

System -> Administration -> Services

Uncheck and Stop the following Services:

<ul>
<li>dhcpd (should already be stopped.)</li>
<li>xinetd</li>
<li>vsftpd</li>
</ul>

On Server B install FOG, but this time install the dhcp service.

On server B go to:

System -> Administration -> Services

Uncheck and Stop the following Services:

<ul>
<li>FOGMulticastManager</li>
<li>httpd</li>
<li>mysqld</li>
</ul>

On server B open:

/var/www/html/fog/commons/config.php

Copy the value from '''TFTP_FTP_PASSWORD'''

Then open

/tftpboot/pxelinux.cfg/default

Replace all instances of web=x.x.x.x/fog/ with the the ip address of Server A.

Now on Server A, open:

/var/www/html/fog/commons/config.php

Replaced the value from '''TFTP_FTP_PASSWORD''' on Server B.

To test your configuration, navigate to

http://192.168.1.50/fog

login as:

Username: fog
Password: password

Create a host and then attempt to create a task, if everything works correctly you should see a file created on Server B in the directory /tftpboot/pxeconfig.pxe/ name with the mac address of the host.

Plugins: Capone

2011-02-11T05:18:17Z

Itismike: Created page with '=== Capone === ==== FOG Version ==== Applies to version 0.29 or higher. ==== Overview ==== Capone is a plugin for FOG that allows you to image a computer based on DMI/Hardwa…'

=== Capone ===

==== FOG Version ====

Applies to version 0.29 or higher.

==== Overview ====

Capone is a plugin for FOG that allows you to image a computer based on DMI/Hardware information without having to register it with the FOG server. This module was originally written for a HP computer warranty service center in the UK. They wanted to be able to restore a computer's image just by plugging it into the network and PXE booting the machine, without any user intervention. This module is great for repair shops and places where you don't need FOG to manage the computer after it is imaged. This is our attempt at pushing FOG into the service/repair sector.

===== Enabling Capone =====

#You should now have a new icon in the menu bar for plugins near the right hand side that looks like a puzzle piece, click on it (you already [[Plugins|enabled Plugins]], right?)
#Click on '''Activate Plugin'''
#Select '''Capone'''
#Active '''Capone'''

You are now set to use the Capone plugin.

==== Using Capone ====

We need to determine what DMI field we want to use for Capone. Currently Capone only supports a single DMI field globally. To do this boot up a client computer and from the PXE boot menu select the option '''Client System Information'''. When prompted with a menu, select option '''7''' to show DMI information. Press the enter key to scroll through the fields and pick a field that can uniquely identify the computer type you are working with. Common fields are:

*bios-version
*system-product-name
*system-serial-number

Once you have determined the field you would like to use, perform the following:

#In the plugins section, select '''Installed Plugin''', then select '''Capone'''
#In the '''Settings''' section set your selected DMI field. This settings is global.
#Now we can create associations for return values from that DMI field and an Image. In '''Add Image to DMI Associations''' select an image you would like to link to a DMI field response.
#Select the operating system for the image
#Then enter the matching value for the DMI field in the text field. This string can be treated as a 'starts with' query. So if you use the field '''system-serial-number''' and you have a group of computers that all start with '''112233''' then you can enter that into the text field and it would match a client with the system-serial-number of '''1122334455'''.

We now have our first association added to Capone. Now what we need to do is to add the Capone menu item to the PXE boot menu.

#Scroll to the bottom of the capone plugin page and copy all the text in the '''PXE Configuration''' area.
#Now go to '''Other Information'''
#Select '''PXE Boot Menu'''
#Click '''Advanced Configuration Options'''
#Paste the text that you copied from the previous page.

Please note that this will not password protect this entry item. If you would like to password protect this item you will need to use the md5pass utility that is in the /opt/fog/utils directory.

It is possible to have multiple matching entries per DMI result. So for example you could have to associations for response '''112233'''. In this case, at the console on the client computer you will be prompted for which image you would like to use.

Capone does not use additional storage nodes other then the master within a storage group.

Plugins

2011-02-11T05:13:49Z

Itismike:

== Plugins ==
Plugins add more functionality to FOG.
===== Enabling Plugins =====
Plugins are not enabled on the FOG server by default, so this is the first thing we will need to do.

#Log in to the FOG Web UI.
#Go to the '''About''' Icon
#Scroll Down and locate the section '''Plugin System''' and change '''FOG_PLUGINSYS_ENABLED''' from '''0''' to '''1''' and select Save Changes.

== Capone ==
Capone is a plugin for FOG that allows you to image a computer based on DMI/Hardware information without having to register it with the FOG server. This module was originally written for a HP computer warranty service center in the UK. They wanted to be able to restore a computer's image just by plugging it into the network and PXE booting the machine, without any user intervention. This module is great for repair shops and places where you don't need FOG to manage the computer after it is imaged. This is our attempt at pushing FOG into the service/repair sector.

[[Plugins: Capone]]

File:Bg2.png

2011-02-10T16:29:33Z

Itismike: Transparent logo in Black

Transparent logo in Black

File:Bg1.png

2011-02-10T16:28:51Z

Itismike: White background with FOG logo at bottom

White background with FOG logo at bottom

Bottleneck

2011-02-10T04:37:29Z

Itismike: Created page with '=== Bottleneck === To determine why a server is not performing as well as expected a program called atop if very useful. On Ubuntu apt-get install atop, this program will give y…'

=== Bottleneck ===

To determine why a server is not performing as well as expected a program called atop if very useful. On Ubuntu apt-get install atop, this program will give you CPU, net card and disk information. Generally FOG does not require much CPU but requires great amount of disk and net card resources whilst imaging machines.

Troubleshooting Driver Issues

2011-02-10T04:34:30Z

Itismike: Created page with '=== Troubleshooting Driver Issues === ==== Method 1 ==== The first step to troubleshooting driver related issues with FOG clients is to download a live CD such as Fedora, or Ub…'

=== Troubleshooting Driver Issues ===

==== Method 1 ====

The first step to troubleshooting driver related issues with FOG clients is to download a live CD such as Fedora, or Ubuntu. Boot up the CD and see if the device that wasn't functional under FOG is working with the live CD.

If it is we just need to know the kernel driver name. This can be listed by issuing the following command:

lspci -k

The output will look something like this:

...
03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5754 Gigabit Ethernet PCI Express (rev 02)
Kernel driver in use: tg3
Kernel modules: tg3
...

In this case we know the driver required in the '''tg3''' driver for network. You can either submit a request to the forum/feature requests section of sourceforge for this driver to be included, or see the section on building a kernel.

==== Method 2 ====

[http://freeghost.sourceforge.net/videotutorials/kernel.swf.html Video Tutorial]

The first step to troubleshooting driver related issues with FOG clients is to download a live CD such as Fedora, or Ubuntu. Boot up the CD and see if the device that wasn't functional under FOG is working with the live CD. If it is then:

<ol>
<li>Go to http://cateee.net/sources/lkddb/</li>
<li>Download the latest version of lkddb.list.bz2</li>
<li>Go to http://cateee.net/sources/autokernconf/</li>
<li>Download the latest version of autokernconf</li>
<li>Copy both files to a directory and extract them</li>
<li>Copy lkddb.list, kdetect.sh, and autokernconf.sh to a common directory</li>
<li>cd to the common directory where the three files listed above are located.</li>
<li>run ./kdetect.sh</li>
<li>run ./autokernconf.sh</li>
<li>Then post the contents of the auto.config to the [http://sourceforge.net/forum/?group_id=201099 FOG Forum], along with the model of computer or the device you are having issues with. It would also be helpful to post a link to the manufactures spec page for that device.</li>
<li>If a driver exists for this device we will attempt to post an updated kernel to the '''kernel updates''' section of the FOG Management portal.</li>
</ol>

Restoring FOG from Backup

2011-02-10T03:53:46Z

Itismike: Created page with '== Restoring FOG == Restoring a FOG installation requires essentially the opposite actions as taken above. This section assumes you backed your installation up manually. This …'

== Restoring FOG ==

Restoring a FOG installation requires essentially the opposite actions as taken above. This section assumes you backed your installation up manually. This section will assume that your backup is in /opt/fog_backup. Also, you may need to be root for some of these actions.

First, go to your backup directory:
# cd /opt/fog_backup
# ls
fogopt fog.sql web
As you can see, I have named my /opt/fog into fogopt, and my /var/www/fog into web. I chose not to backup my /images directory due to some issues copying such large files.

=== Web Directory ===

Restoring your web directory will take two steps. First, remove the current one, if it exists, then copy the backup over to the appropriate location.
# rm -rf /var/www/fog
# cp -a /opt/fog_backup/web /var/www/fog

=== OPT Directory ===

Restoring the /opt directory is just about the same as the web directory above.
# rm -rf /opt/fog
# cp -a /opt/fog_backup/fogopt /opt/fog

=== MySQL Databse ===

In order to restore the database, you should first drop the current one (if it exists), then create a blank fog database, then import your backup.
# mysql -u root -p
Enter password:
mysql> DROP DATABASE fog;
mysql> CREATE DATABASE fog;
mysql> exit
# mysql -D fog -u root -p < fog.sql

That should do it!

Thank you, sending notification

2011-02-06T03:11:55Z

Itismike: Created page with 'Hopefully this bug will be fixed before anyone else experiences it, but just in case I'm creating this page so it may come up in searches. When installing FOG server the …'

Hopefully this bug will be fixed before anyone else experiences it, but just in case I'm creating this page so it may come up in searches. 
When installing FOG server the option to notify the developers is presented:
<pre> Would you like to notify the FOG group about this installation?
* This information is only used to help the FOG group determine
if FOG is being used. This information helps to let us know
if we should keep improving this product.

Send notification? (Y/N)y
* Thank you, sending notification.....</pre>
Since the developers coded this feature in, we might assume they appreciate knowing how many people are using FOG. In one person's experience, this step freezes more often than not. If you choose Yes and it takes longer than a few seconds, it is likely frozen. If the script never finishes, the completion message is never printed. Final configurations may or may not have been completed.

=== Solution ===
<ol><li>Log into another terminal to the same server: 
:Either open a second SSH connection, or press [http://linux.about.com/od/linux101/l/blnewbie5_1.htm CTRL-ALT-F1] to open a new terminal on the local machine. 
::NOTE: Pressing CTRL-ALT-'''F7''' will take you back to the graphical screen. You might want to write that down.</li>
<li>Use <tt>ps</tt> to list all processes that are currently using the <tt>wget</tt> command (this is how the notification is sent)<pre>$ ps -ef | grep wget
root 21794 11185 0 20:16 pts/0 00:00:00 wget -q -O - http://freeghost.no-ip.org/notify/index.php?version=0.29
myuser 22005 21962 0 21:01 pts/1 00:00:00 grep --color=auto wget
</pre></li>
<li>Kill the hung thread: (substitute the process ID from your <tt>ps</tt> result)<pre>$ sudo kill 21794</pre></li>
<li>Return to the original terminal to see the installation process complete:
<pre>
Send notification? (Y/N)y
* Thank you, sending notification...../lib/common/functions.sh: line 250: 21794 Terminated wget -q -O - "http://freeghost.no-ip.org/notify/index.php?version=$version" > /dev/null 2>&1
Done

Setup complete!

You still need to install/update your database schema.
This can be done by opening a web browser and going to:

http://192.168.1.1/fog/management

Default User:
Username: fog
Password: password

$</pre></li>