@george1421

Thanks! I managed to get a script made to run in powershell that will install the fog service correctly. I ended up having to download the original file from the server and using that. The MSI file that I created was bombing for some reason. Either way I’m glad I got it working!

Now my next question is does anyone have any good wiki’s on how to run a powershell script in GPO on a group basis not a login script? I’m new to this stuff so any ideas are helpful! Thanks!

Cheers!

Joe

Hi,

i hardly recommend PDQ Deploy for easy deployments if you hate GPO’s 😉
Also the way with ORCA is possible but for what you have a switches for cli.

alt text

I have it licensed to pro mode but simple deployments can also be done in free mode.
PDQ Deploy is very powerful, take a look 🙂

PDQ has AD integration and can also suck hosts from Spiceworks.

Regards X23

Does the USB Dongle work on other models?

Also, 1.3.5 isn’t released yet, it’s still in RC. I’d advise you to update FOG again because RC 11 was just released yesterday.

@Junkhacker

I just checked on the server and it is…

Running Version 1.3.4
SVN Revision: 6066

I used SVN to update my server… What was posted was from one of the FOG clients FOG.log files.

Ryan’s link worked! This can be marked as solved 🙂 Thanks gents!

And my last final thoughts on this. You may want to review these two threads to see if they give you any additional guidance with your task.

https://forums.fogproject.org/topic/9394/trying-to-sysprep-windows-10-to-upload-to-fog-please-help

https://forums.fogproject.org/topic/697/windows-7-and-setupcomplete-cmd

Great! that worked! thanks for the quick response.

@Jaymes-Driver Well Yeah FOG is going to be my go to for OS X and Ubuntu builds. But I will have to stick with MDT and WDS deployment seeing we have a ton of different configuration I push out.

@thisisryanswift You can surely image home edition. You would create your reference image just as you would for pro. You can preload application, and set some custom configurations, then sysprep the image.

The issue you run into is more of a legal / licensing issue than a physical one. Home and OEM licenses (of all flavors) doesn’t support (hint: allow) reimaging rights. You can only install from OEM media unmodified. AFAIK Home version doesn’t have a VLK key to allow reimaging like Pro does. Just be aware of this restriction.

From a physical standpoint OEM images will not run the setupcomplete.cmd file at the end of OOBE. You might get around this by modifying the first run section of the unattend.xml file.

@Tom-Elliott
Resolved. Perfect. That did it. Much thanks.

Now on to sysprep testing.

Here is the file I used.

0_1486506949560_SetupComplete.cmd

Place your SetupComplete.cmd in %windir%\Setup\Scripts
(you will nedd to create the scripts folder.)

Copy your unattend.xml to %windir%\system32\sysprep\

hit windows key and S, type service, click on services, find FOG and right click and select propereties, select disable click apply.

hit the Windows key and R to open the run box, type in sysprep.
double click the sysprep icon.

Hope it works for you.

@Joe-Schmitt
It work fine now, thanks.

@Scott-Adams Thanks, Scott. Checking it out…

I reconfigured Windows 7 to use ACHI by following the instructions in this article.

http://www.ithinkdiff.com/how-to-enable-ahci-in-windows-8-after-installation/

Worked like a charm!

@x23piracy While this isn’t FOG related, imaging rights are important to follow. If you want to survive an audit you should understand what you are allowed to do and can’t do.

Chris (from Microsoft) has posted 2 clear documents on what you can do with system imaging (from a MS perspective). This question comes up on Spiceworks almost daily.

https://community.spiceworks.com/how_to/124056-reimaging-rights-for-windows-10-licensing-how-to

https://community.spiceworks.com/how_to/69219-reimaging-rights-how-they-apply-to-your-licensing

Take these documents as a clear explanation of the MS EULA.

It is true if you have a single VLK key, you can deploy any number of systems as long as the OEM key is licensed for the same OS as the VLK key. For example if you have a single VLK key for Windows 10 Pro. You may reimage any number of computers that came from the manufacturer with Windows 10 Pro already installed. You may not use the VLK key for Win 10 Pro to deploy Win 10 Pro to a computer that had Win 8.1 previously installed. That is a different license (version upgrade).

@Tom-Elliott The resize worked correctly. Thank you for quickly finding the solution!

I have managed to resolve this now, i needed to reinstall Windows on the server and choose New to create the partitions on the installation instead of just next for some reason.

I have now been able to image server 2012r2 and server 2016 without issues.

@boynty77 Most often this is the best thing to do.

Change the boot file you’re using (assuming this is booting via UEFI) to ipxe7156.efi

@MarkusK This depends entirely on your snapin, it simply accepts the exit code it gets from the program it is told to run.

If this is not the desired behavior, you need to alter your setup.