My guess is that it’s not receiving it’s “Wake On Lan” command, or in this case the shut down command. What kind of hardware is between your server and the computer? There are some routers and switches that do not pass the WOL packets. Try running wireshark to see of the magic packet is sent from the sever by placing wireshark in line with the server, best to port mirror. Then run it again at the Host. Somewhere along the line the command is being misplaced, packets are lost, or your computer is not configured to receive the commands.

Have you ever used WOL in your environment? Has it ever been successful? There are some free tools out there to test your WOL capabilities and I would start there!

Try a few different ones, just go thru the list, keep track of what they say, I’m sure Chad will be able to sort it out XD.

I know that the problem is stemming from the Image and the OS selected.

Well thanks, I’m suppose to be getting some new equipment this summer to set up and I WILL be imaging with FOG, so I’ll remember this in case I run into issues!

Try to set it to “vista” someone else had an issue pushing windows 7 images but resolved it by selecting “Vista” under OS type.

Quick question, when you registered the computer as a host, did you specify the OS?

If you did a quick registration you need to specify the image and OS associated with that Host on the Host Management of the FOG web GUI. If you did a Full registration did you specify which image is associated with the host? If not, you can set it in the Host Management.

I don’t have these problems, when I upload a Windows 7 or 8 image to my FOG server I choose OS as Windows 7 and have NO problems deploying. This is peculiar, glad you got it sorted!

There’s no need to re-install the OS it won’t solve anything except after first running the installer it will start the service again, then after you reboot it will happen again.

IT IS A KNOWN ISSUE with 12.04, if you’re going to nuke and start all over, use an older version like 10.04, I’ve done so and it has eliminated the problem you are facing right now.

It is also not THAT big of a deal, a quick simple command will start the service again you just have to remember to run it each time you reboot, and that command is [B]sudo service tftpd-hpa restart[/B]

If after re-installation and checking the TFTP boot and you are still having issues we can help you to get it pointing to where it needs to and also help with DHCP issue;, but first, try to restart the service, or use and older linux revision, 10.04 and fog 0.32 work very nicely together!

[FONT=sans-serif][COLOR=#000000]Did you reboot your server? There is a known issue with Ubuntu revisions of 12.04 and higher, the service does not start at the right time and thus causes problems. First check to make sure your TFTP service is running by running a few commands.[/COLOR][/FONT]
[FONT=sans-serif][COLOR=#000000] [/COLOR][/FONT]
[FONT=sans-serif][COLOR=#000000]From your FOG server test out tftp[/COLOR][/FONT]
[COLOR=#000000][FONT=monospace]tftp -v X.X.X.X -c get pxelinux.0
[/FONT][/COLOR]
[FONT=sans-serif][COLOR=#000000]From a Windows PC run at the cmd prompt:[/COLOR][/FONT]
[COLOR=#000000][FONT=monospace]tftp x.x.x.x get pxelinux.0
[/FONT][/COLOR]
[FONT=sans-serif][COLOR=#000000]If tftp & xinetd are running your should get:[/COLOR][/FONT]
[COLOR=#000000][FONT=monospace]Received XXXX bytes in X.X seconds…[/FONT][/COLOR]

This is very peculiar, I would say you are on the right track, I was just making sure we are understanding each other correctly.

I know that when you join the PC to the domain, you get a copy of the local security policy, pushed from the domain, it could be possible that the domain is disabling the account.

You can try [url]http://www.pogostick.net/~pnh/ntpasswd/[/url] to re-enable the account I know other have had success with it.

Did you install the fog client? Did you update the host in your host management to reflect the change?

With the FOG client installed I ran into some renaming issues and Novell, the client kept changing the host back to the name in the host management system causing log in issues until I updated the host name in the Host management system.

I wish I could help I hope someone who does understand Capone and uses it steps in, good luck!

From my little understanding your problem is coming from the fact that you don’t want to use the mac address to image with.

FOG creates a file based on the mac address of the unit. The unit boots, it looks on the server for it’s file if it finds it then it goes on about it’s business with FOG, if not then it proceeds to boot from the next specified device.

Take a look at this below from: [url]http://www.fogproject.org/wiki/index.php?title=FOGUserGuide[/url] abotu half way down the page, I hope this clears up some questions you were asking, sorry I can’t be of more service to you, we do not use Capone and I am not familiar with it

[SIZE=4][B][FONT=sans-serif][SIZE=17px][COLOR=#000000]Tips[/COLOR][/SIZE][/FONT][/B][/SIZE]

[LIST=1]
[]FOG requires that all hosts be entered in the FOG Database for imaging. [B]The most important part is getting the MAC address of the host right[/B]. [B]FOG uses the MAC for targeting image installs and acquires[/B]. [B]Using the wrong MAC could result in unpredictable results, including the complete erasure of the wrong pc[/B]! The IP address isn’t that important, and the ‘name’ field is more for the user. Mac address format is 00:12:3F:C4:57:0C . Using dashes, spaces, or no items at all will result in the GUI not accepting the host.
[]After hosts are entered, it is wise to group them together by function, hardware, or common image. The image will be shared among all members of a particular group. This occurs within the ‘hosts’ screen, and NOT on the groups screen. This is a little confusing, so it helps to think of the ‘groups’ screen as a task generator, rather than controlling group memberships.
[]For importing hosts in a .csv file follow the format below: 1 line per host:
[FONT=monospace]“00:c0:4f:18:62:63”,“Hostname”,“1.1.1.1”,“Your description”,“XP/Vista”,“Image filename to use”[/FONT]
[]Hosts are then configured to boot via PXE boot by going into the BIOS. Make sure PXE boot is the FIRST option, NOT the hard disk, or things won’t work.
[*]Configure your ‘master’ pc for the first image. Probably a good idea to run ‘[URL=‘http://support.microsoft.com/kb/302577’][COLOR=#3366bb]sysprep[/COLOR][/URL]’ prior to imaging, but not necessary. Sysprep will make your imaging life easier, if hardware is different, etc. See Microsoft.com for more details on using sysprep.
[/LIST]

but then further down the page I see

[SIZE=5][B][FONT=sans-serif][SIZE=19px][COLOR=#000000]FOG Plugins[/COLOR][/SIZE][/FONT][/B][/SIZE]

[FONT=sans-serif][COLOR=#000000]Plugins enhance FOG’s functionality.[/COLOR][/FONT]
[LIST]
[*]The Capone plugin allows FOG to recognize similar hardware platforms and push your specified image to them with minimal (or no) interaction.
[/LIST]
[FONT=sans-serif][COLOR=#000000]See [URL=‘http://www.fogproject.org/wiki/index.php/Plugins’][COLOR=#5a3696]Plugins[/COLOR][/URL] to activate and manage plugins.[/COLOR][/FONT]
[FONT=sans-serif][COLOR=#000000] [/COLOR][/FONT]
[FONT=sans-serif][COLOR=#000000]so I have no clue :)[/COLOR][/FONT]

First make sure your image is set up for MULTIPLE PARTITIONS aka the WHOLE disk.

Then take a look here: [url]http://fogproject.org/forum/threads/problem-uploading-ext3-ubuntu-image.459/[/url]

I found this from the link above. Others have had success, try this below:

Update: I finally tried manually using PartImage to pull the image with the plan to then copy it manually in to the server. In doing so, I saw that PartImage was erroring out (which FOG was hiding). Googling around found that running an fsck prior to uploading the image fixes the problem. I may dig in to the FOG code to see if I can make it automatically run an fsck prior to pulling any Linux image. For now, though, I just boot my source PC in to a live CD and fsck, then I upload the image. Works a treat.

What Version of Linux are you running and what version of FOG?

Have you updated to the latest FOG kernel? there is a 3.8.8.8 update out now and you can update from the Fog Web Management.

Try changing your partition on Image Management to a “Multiple Partition Image - All Disks (Not Re-sizable)”

So you have not been successful in backing up the image yet, but you have registered it as a host?

I take it you have set up an image in Image management and selected the proper storage and image type. Have you assigned the image to the host? Did you also select it’s OS type?

Does your VAIO have more than one partition on the hard drive? If so, make sure you set up the host image properly so that FOG will do the disk and not partitions.

You may need to go into the images directory on the fog server and delete any reference to the image, then re-run the upload.

no I mean manually do it, when it’s giving you fits like this, can you get past it by bringing up the boot menu selecting your network device and let it pull pxe boot, will it?

Did you run the commands?

What was the outcome?

Have you tried using F11 or F12 to bring up your boot options and manually selecting the network boot option?

I have a few win 7 pcs when I reboot them and then load fog menu, they feel the need to “repair” but I can normally get around this by manually selecting the boot device and selecting Network.

Windows 8 is really particularly bad about this, but I’ve not even tried to image it yet

Yes from my experience it is best to have the DHCP and the TFTPBoot server on the same machine it helps things to resolve best. The things is with your using a router and simple network setup there’s no place to tell it where the “next-server” is for the PXE boot nor what file to pull to the client, but being on the same switch and having the DHCP service enabled, you should at least see an error.

I’d try setting up your server again from scratch and I’d install the DHCP service with FOG to see if I could get it to boot.

Also I’d be making sure I can see the server and I can pull the file from TFTP protocol.

If you can pull your pxelinux.0 using the commands we know that the TFTP function of your server is functioning correctly, if not we can begin troubleshooting here.

If your file pulls, it would be a good idea to set up a machine in the network with wireshark to see if the client is talking to the server and looking for the file or if it is just blowing over it because there is no “next-server” or “file” set for it to pull, these are options 066 and 067 respectively and need to be set to point to your server and pxelinux.0 file.

[FONT=sans-serif][COLOR=#000000]From your FOG server test out tftp[/COLOR][/FONT]
[COLOR=#000000][FONT=monospace][code]tftp -v X.X.X.X -c get pxelinux.0[/code][/FONT][/COLOR]

[FONT=sans-serif][COLOR=#000000]From a Windows PC run at the cmd prompt:[/COLOR][/FONT]
[COLOR=#000000][FONT=monospace][code]tftp x.x.x.x get pxelinux.0[/code][/FONT][/COLOR]

[FONT=sans-serif][COLOR=#000000]If tftp & xinetd are running your should get:[/COLOR][/FONT]
[COLOR=#000000][FONT=monospace][code]Received XXXX bytes in X.X seconds…[/code][/FONT][/COLOR]

This page tells how to configure proxy DHCP -> [url]http://www.fogproject.org/wiki/index.php?title=Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server[/url]