@Anil-Patil Again, we need more information on what exactly goes wrong. What do you mean by “But when I boot for the machine through iPXE network boot, there is no option available there to boot it.”? No option available? Please take a picture and upload it here.

By the way, FOG 1.2.0 won’t work with UEFI BIOS out of the box!

@Anil-Patil said:

… but get error and not completing the process.

Please tell us about what error (the exact message, best if you can take a picture or video!) you see and we might be able to help. Without knowing exactly what went wrong we cannot give you any advice.

For future readers - this problem was most likely caused by the image being deployed to a HDD that was too small to hold the image. This is a common error with non-resizable type images and is normally resolved by using resizable type images or by deploying to HDDs that are large enough to receive the image. Further documentation can be found in the WiKi here:
https://wiki.fogproject.org/wiki/index.php/Troubleshoot_Downloading_-_Unicast

@Wayne-Workman Thanks for the help, ill let you know after the update.
0_1447707617587_Server 2008 DHCP BIOS and UEFI Co-existence.zip

@Scott-B

Printer Issue seems resolved in the most recent SVN. Thank you!

So glad I set up a WSUS server on our domain. Its allowed me to dodge a number of bullets like this now. Its my common practice now to sit on all Microsoft patches for a week before rolling them out. Let the consumers and small businesses find the bugs. Enterprise aint got time for dat.

I take it back, after more testing I was able to see the notification from a regular user. What version are you on?

@sudburr he’s running 0.32 so x86 is the only usable kernel for him.

He must use the x86 otherwise everything will break.

That said I’d actually recommend using the 3.0.1 32 bit kernel. I say this as Windows 8/Windows 10 configs off of vm seem to break kernel loading. 3.0.1 apparently just works.

@groinksan said:

… should I continue to use the multiple partition/single drive resizable option?

Either that or you could try deploying the image once to a 1TB disk using ghost. Then pull an image from that using FOG (non-resizeable setting) and deploy it to your other hosts (if they all have 1TB disks). Should work with 1.2.0 as well.

I will take a look at this once I get it settled in the environment. The way I got around it for now was to create the SetupComplete.CMD file and put what I needed in there so it would start the FOG service once imaging was complete and it is working good now.

I’m not a coder so it all looks like Greek to me but I know I can figure out what I am looking at. And thank you for the suggestion.

@Tom-Elliott said:

This is fixed in current. Thanks for reporting.

Excellent thanks Tom!

Ok so imaged the PC with the Bios set to ATA. this time no errors. Already purchased new License for windows. Thanks Tom

@Tom-Elliott Ok, well after upgrading to svn 2096, I am still unable to deploy a vista image to this laptop. I reuploaded the image just to make sure and still no go

It does work, thanks Tom! Also, the normal default printers returned without having to set them all one by one.

That is sooooo nice. Testing it out on my computer with a handful of my printers.

Two huge factors I’ve found for startup hangs like you’ve described have been bad/old drivers and startup programs that are having issues or are just terribly slow.

Same here; except my computer names start with lab-xxxxx

<ComputerName>lab-*</ComputerName>

Works like a charm!

@aruhuno said:

@Wayne-Workman I can’t because I’ve already create master without reserved partition, sorry!

Not sure that remove the reserved partition is the good solution. 😉

@Wayne-Workman Yep, the sky’s the limit as far as drivers go 🙂 Customize your little heart out lol…

@Exig3nci Can you get a screen shot of it?