You can point computers to different kernels. In the general tab of the host properties add the Kernel location in ‘Host Kernel:’ for example:- Host Kernel: fog/kernel/backup/bzimage2012
This will solve the problem while you find a kernel that will work on both sets of computers.

Like kevin mentioned. If your IP phones are on a seperate VLAN they can point to different boot server than the PCs because they would be on a seperate DHCP scope…

There is no reason why this would conflict. The PC’s are using pxe and the mac’s are using neboot and both can share the same windows DHCP server. We have a setup of both Deploystudio and FOG. If you are using cisco network equipment you may need to add an IP Helper address for netboot server and enter details for options 66 & 67 on your windows DHCP server for FOG.

I think I replied to your other thread, you have asked this question in 2 places.

Make sure you have a computer name in the xml file. Doesn’t matter what you use as fog will rename it later. My guess is that you have left this blank.

[CODE]<ComputerName>FOG-TEMP</ComputerName>[/CODE]

I recommend you continue using DeployStudio for the macs and FOG for Windows/Linux. Also continue using your existing Microsoft DHCP sever, you need to setup options 66 & 67 on DHCP server for FOG.

I dont quite understand what you mean. You don’t need access to the web console to restore an image. You can generate a restore task individually on each computer by using the pxe menu option quick image. I recommend you use the product deepfreeze to keep your images clean on each boot.

Fog backups each partition to a seperate file, just delete the other partition files on storage node after upload. If it can’t find them it can’t restore them.

You will not be able to mount the image and restore individual files.

You can stop it creating the extra admin account by tricking it to create an administrator account called Administrator which it can’t do as it already exist by default. For example:-

<UserAccounts>
            <AdministratorPassword>
                <Value>Password</Value>
                <PlainText>true</PlainText>
            </AdministratorPassword>
            <LocalAccounts>
                <LocalAccount wcm:action="add">
                    <Password>
                        <Value>Password</Value>
                        <PlainText>true</PlainText>
                    </Password>
  <Description>Local Administrator</Description>
                    <DisplayName>Administrator</DisplayName>
                    <Group>Administrators</Group>
                    <Name>Administrator</Name>
                </LocalAccount>
            </LocalAccounts>
        </UserAccounts>

If you are using cisco switches see [url]http://www.fogproject.org/wiki/index.php?title=Cisco_Multi_Cast[/url] for sample config

Check that the pxelinux.0 file exists on the server, its stored in /tftpboot and logon to the webconsole and check the tftp server section in fog settings.

Try upgrading the kernel. This can be done easily from fog settings in web console.

As Kirksec said your IP phones should ideally be on a different VLAN. If you’re just testing FOG on a couple of computers, you could create dhcp reservations for these hosts and point there options 66&67 to another server.

Matt,

You won’t be the first educational establishment using this product, there are hundreds using it. We are a large University in the UK and have been using FOG for about 3 years to deploy Windows XP/7 to a large mixture of hardware (roughly 3500 computers). We have our main fog server (web,database,pxe server) on the central site and several storage nodes on remote sites. The storage nodes keep the bulk of the traffic at remote sites. Large corporations are also using FOG, I was at Cisco’s head office in a UK a few months ago and noticed that they were using FOG to deploy operating systems in their training labs.

I can remember people having some issues with using FOG on some dell computers in the past. My advice to you would be to setup a server, and test the product on your computers, if it works, make the switch. Why waste money on Ghost.

You could use the script file c:\windows\setup\scripts\setupcomplete.cmd to call the windows diskpart.exe utility to extend the volume.