@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

6 weeks? I threw together my golden image in 2 days… Yours was definitely more well documented and probably supported more computer models though as mine only had to work on about 5 different models ^^

See https://forums.fogproject.org/topic/5243/kernel-panic-with-svn-3553-and-virtual-esxi-image

ok thanks a lot

Fixed in v0.9.1.

Yes. Nothing has changed except the upgrade of fog. Now I’m currently using the Domain Admin account to ensure that it has permissions needed.

@Wayne-Workman

Thank you for the response! They are the same models and same image all over unicast. It works on some of them. For example, we have a lab with 20 PCs it works on 18/20 of them but on two of them it goes into the Error Recovery loop. So, it is working on MOST of the 4000s but some it is not.

We are upgrading our current inferstructure so we will look into upgrading the fog server as well. I assume it is pretty simple and straightforward? I haven’t researched it at all but will do so when I get some time today!

Thank you for your assistance!

@Wayne-Workman said:

@nengelhardt

I don’t sysprep… However, on that same note… my co-worker was messing around with Windows Deployment Services which requires sys-prep.

I remember him getting aggravated about the 3 reboot limit thing… I told him, ok build the image over again… and we will just upload it to FOG for safe keeping. If you need to restart, we can restore it (THEN) in 15 minutes.

And now, we’ve ditched WDS in favor of FOG, and because of the awesome compression and upload / download times in FOG Trunk, we often find ourselves doing a pre-upload of images lol… Uploading what we have before we do something risky that you can’t come back from cleanly.

Once we verify that what we did works, we delete the early image of course. But, we have reverted to early images a few times.

Yeah, I found the speed difference in snapshot vs. upload is well worth building it in a VM, but I suppose if that’s your style then go ahead.

@flat4 said:

Im Having the same problem, i can deploy an windows 8.1 image but for some reason i cannot upload it. I get the same screen as the OP. Any progress on this?

Edit i fix my issue with a little google, someone else posted to use Part Magic and try to open the drive in the file viewer. When this happens it will tell you to run a command to remove the hibernated file. I did and boom fog is now uploading the image.

“Removing hibernate file and page file” feature is available since FOG 0.12

@Wayne-Workman said:

@Tom-Elliott said:

Ultimately, unless your planning to have dog manage the joining of domain, snapins, printers

lololol I was the dog at my old job. Dark days!

Wayne-Workman the FOG 2.0 Client lol

@Deastrom That’s amazing, thank you!

Yes, Wayne; I guess so…
We spent a couple of days recreating a new image from scratch and it’s working: we’ll use that.

Thanks everybody for the support.

Oh, my fault, read to fast…
I’ll try this today, thanks