@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?

@SirAdams said:

How to get product key from fog server and use in script?

Maybe a script running under Windows 7 x64 something like:
$key=http://x.x.x.x/fog/…?mac=xx:xx:xx:xx:xx:xx
cscript //b c:\windows\system32\slmgr.vbs /ipk $key
cscript //b C:\windows\system32\slmgr.vbs -ato

P.S. I have install fog 1.2 on QNAP NAS TS-212 without multicast.

I like it.

I’m solving this thread since the OP has not returned and there is good info here for future readers.

@TRex good job on getting it working, I think you’ll like FOG Trunk and FOG 1.3.0 even more as there are even more good features to make life easy. 🙂

@Tom-Elliott said:

I uploaded, just a moment ago, to FOG 1.2.0, and Windows 10 with OS set to Windows 7. I Uploaded, then downloaded and all worked 100% flawlessly.

Great, thanks for the info. Weird how it never worked for me first time round with windows 7 template.

Oh well. Working now too 🙂

@sudburr We had a issue with licensing when I first started deploying machines at my job about two years ago.

Most Microsoft product licensing requires a minimum number of unique requests before it allows product activation. So we simply generated a bunch of fake requests and then all was fine. We’ve used this method at four different locations, on probably about 3,000 windows systems - over and over again. And being a school district that has as diverse of software requirements are there are educational areas, we’ve never had a problem.

But again, whatever floats you boat! 🙂

All I can tell you is that there are several methods to serve an ISO via FOG.

I can tell you also that no one method will work with all ISOs.

Please search our forum thoroughly for “ISO” and also our WiKi. Also keep an eye on this thread because someone may help you here, too.

@Bruno-Nogueira I’ve recently updated this: https://wiki.fogproject.org/wiki/index.php/Windows_8_UEFI_Imaging_Tips#Windows_8_and_8.1_Imaging_Problems

Please look it over. Although it’s written for Win 8 / 8.1, I think it would probably apply to Win 7 as well.

@fredlwal said:

when I ran fog, I see it is asking for please boot windows fsck.

I’m familiar with this error.

It’s caused by one of two things.

The dirty bit is set on the OS partition. This means there are updates pending or you improperly shutdown the system. Either way, you need to fix those things. If you can’t do them by installing updates and shutting down properly, then you’ll need to run a chkdsk /F on the OS.

Hibernation is enabled, and a hibernation file exists on the HDD. You’ll need to disable hibernation and remove the hibernation file.

Here’s a WiKi article section to help you with those things:
https://wiki.fogproject.org/wiki/index.php/Windows_8_UEFI_Imaging_Tips#Windows_8_and_8.1_Imaging_Problems