I’ve been thinking on this for a bit, and have thought of some far more complex ways to do it. I think that George’s below post is the best out of all the things I’ve thought of.

Basically have the post-install scripts write a .bat file on the local hdd with the needed arguments. Then make a snapin that runs a .bat file - and that just execute the local .bat file.

It is indeed possible to OEM activate a non-OEM image.

How you do it depends on exactly what kind of OEM license it is, whether it’s OEM:SLP, OEM:NON-SLP or OEM:COA. Read this to see the differences.

‘Activation Backup & Restore 1.7 BETA 1’ can be used to extract OEM:SLP Licensing key and certificate which is tied to the manufacturer, the BIOS, the key, the cert and the OS from an original OEM image.

backup-cert.xrm-ms backup-key.txt

You can then use the same program to restore the OEM:SLP key and cert to a non-OEM image (like GVLK aka KMS).

There are other tools and methods but you’ll have to do some careful digging.

@Wayne-Workman That looks like a very handy script to have. I think it will do the trick to clean up some issues in district. Thanks!!

@Wayne-Workman said in Word - temp environmental variable:

@John-Johnson What is it that you did? I’m asking for future readers.

I kept it offline until I could get Administrator activated. Once logged into Administrator my user account was safe from Microsoft’s unwanted pushed apps.

Thanks! That was helpful!

fixparts /dev/sda worked for me.
thanks

The GUI can also be used to add “filtered MAC’s” this is simply a comma separated list (e.g. mac1,mac2,mac3,etc…)

The GUI accessible portion to add the filtered mac is:
FOG Configuration Page ->
FOG Settings ->
FOG Client - Host Register ->
FOG_QUICKREG_PENDING_MAC_FILTER

@MRCUR said in Recommended guide for Windows 10 image creation (from scratch) ?:

@x23piracy Are you keeping all 3 of the “store” apps? “ConnectivityStore”, “StorePurchasesApp” & “WindowsStore”?

I can’t find a clear answer on what of those three (besides “WindowsStore”) is required to make the store functional if we decide to enable it in the future. I’ve also seen it noted that “DesktopAppInstaller” may be needed for some apps to be installed through the store.

Since i use WILDCARDstoreWILDCARD i think yes because all of that apps cover the word “store”

Or possibly virtual network/adapter issues preventing the fog server from from communicating with the host OS, because in the first picture I see you’re using Virtual Box. But I tend to still think you’re not putting in the fog server’s IP address during client install.

@anthony.delarosa The legacy pass field is in no way, shape, or form used by the new client. Probably ticking the “Join Domain” checkbox and saving caused the machine to Join the Domain.

@Joe-Schmitt said in Snapin Pack:

the one thing I’m seeing from those screenshots is that you have a sub-directory in your zip file.

I knew this would be confusing for folks, and there’s no way around it, people just need to understand the pathing. It took me months of here-and-there moments to wrap my head around it. So nobody would have to go through that, In the SnapinPacks wiki article, I explained this at very great length.
https://wiki.fogproject.org/wiki/index.php?title=SnapinPacks

@sapeurorca highly recommend updating to the RC builds. You may not want to but I’m confident it will improve your chances of success.

@Wayne-Workman Alright, I will have to test it out. Thanks!

Thanks for the tip @george1421 I’m not sure it works for the scenario I am working on, but none the less, good idea for future items too, more than just name changes.

@coldenburg Did you try a mini-switch yet?

Depending on your hardware, you may need the right driver.

Or if you’re in a VM, you need to select the right device to emulate.

Read through this, ask if you still have issues.
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

@DEMONTECH
You need to run the Fogcrypt command passing all the path where fogcrypt file is, or add the location to path variable.
eg. “C:\Test\FogCrypt.exe” …

an advice:
when you hear: “legacy client”, run in the opposite direction as fast as possible … save your life … 🙂

@Wayne-Workman said in FOG Client Service Updater:

If you go the PDQ route, be sure to include some way to first remove the legacy client. If it’s still there, the new client will not install.

Following Wayne’s instructions then you should create a batch script and deploy that with PDQ Deploy.

In that batch script you will issue the FOG client uninstall command

@echo off msiexe /X <guid of fog client> REM then install the new FOG client with msiexec /i fogclient.msi <what ever option switches>

Thanks George and Wayne for your advise.