Thanks all. That is an easy solution! 😃

@FlareImp Possibly the older iPXE version used in FOG 1.2.0 did not send DHCP option 97?!

http://ipxe.org/cfg/uuid (especially the last section ‘Notes’ is interesting I guess)

@elishasmantle said:

Is it possible, If I have all the images created and stored on a server to have it find a specific image to use for imaging that particular system?

I have written scripts that take advantage of the fog postinstall function that will use the OS utility dmidecode to pick up the model number of the target system and then deploy (push) the correct drivers to a known folder on the target computer. For this to work correctly you need to update your reference image before you sysprep to have windows look in this known folder (c:\Drivers) before it looks at the inf folder for the drivers. I have one image that supports 15 different models using this method (i.e. they are all Dell computers).

The only other caveat I have to say is you need to ensure that you have all required F6 boot drivers install on your reference image before you sysprep it. These drivers are required to boot the system, so there is no chance to pick them up from the disk since the drivers are required to connect to the disk.

here is what I use to pick up the Dell model number

machine=`dmidecode -s system-product-name | tr -cd '\60-\176'`;

And here is what I use to pick up the Intel NUC and Lenovo model numbers

machine=`dmidecode -s baseboard-product-name`;

I would recommend non-resizable as well, but if you can afford to, manually shrink the partitions.

As a part of the unattend file (I’m just guessing you’re using one) you can have the unattend set to expand the disk as needed. That would be another method though I don’t know how simple it is to do.

Good to hear!

Thanks for the help Sebastian. Yeah, I meant AHCI 🙂

I followed what some others suggested on the spiceworks forums and upgrading to the Trunk version. I made sure to factory reset my bios settings so it was uniform with my source computer (where I didn’t mess with anything) and it booted up! Everything works great and the windows key applied all by itself like it should. I’m a happy 🙂

Thanks!

@mrayzies said:

you must first have a KMS host running in your deployment

They are actually not too hard to setup. But the steps are easy to forget. I’ve only done it once.

@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