@Sebastian-Roth FYI, i am using 1.5.4 with a ad join password starting with % (percent sign) in production.

Hi,

why not use cross transfering @Tom-Elliott ? Maybe some of us moderates can receive the money and transfer it through paypal to the fog project?

Regards X23

This post is just a destroying message, i can understand that you are frustrated but there are a lot of people out there successfully using fog. Why not starting to tell us your issues to may solve them?

Posts like this are helpful for no one.

@Wayne-Workman whoops did not read your post, its pretty the same to mine, sorry :D

Regards X23

Hi,

i tried to activate a VL Image with an OEM key and this doesn’t work!
But with a single VL Key you can activate up to 250 machines (my last information) maybe its lower today until it counts out. You can see the activation count in the VLC.

Doing this more then once is okay if the target machine has an oem key in its bios. Remember the reference image needs to be build based on the VL Media!

Thats all about the trick purchasing one VL copy of for example Windows 10 Pro to gain the reimaging rights.
Also the activation count can be resetted, i don’t know anymore if this happens after x days or can be done another way.

In the past i gave a s*** on that part in the eula, at least when everbody is onboarded to the cloud microsoft isn’t interested anymore in doing sam checks, so i was used to activate my computers by reading the key from bios and activating it by a snapin that was doing nothing more then slmgr.vbs /ipk key followed by a slmgr.vbs /ato ;)

P.S. my company is on a strict way up to the ms clouds, i have to deal with intune (autopilot) i hate it, FOG rules! that said!

Regards X23

@Aaron-McLaughlin try to not remove the image definition, just copy it and delte the image files and let the image definition alive, if you now copy the files back it should work.

Fog doesbt know that the image was still captured if you copy image files back and simply recreate the image definition.

Not sure but if you want the backup and restore images you also have to backup the sql part of the image, that should cover all the image settings and maybe also file sizes.

Regards X23

Hey Tom :)

nice to hear from you, all the best…

It’s not time to make a change
Just relax, take it easy
You’re still young, that’s your fault
There’s so much you have to know
Look at me
I am old, but I’m happy

I was once like you are now
And I know that it’s not easy
To be calm when you’ve found
Something going on
But take your time, think a lot
Why, think of everything you’ve got
For you will still be here tomorrow
But your dreams may not

Regards Cat ;)

@Pere-Pozo-Miro you can setup as much storage nodes as needed and if you create the image you decide on which storage node it will be stored. There is a replication between storage nodes but that can be configured.

Regards X23

Of course, if you don‘t use an answer file (unattend.xml) you will have the full oobe (out of the box experience).

Here you can create an answer file:
http://www.windowsafg.com

@YG2018 no need for a snapin pack if your snapin only consists on a batch file, just create a normal snapin from bat (cmd), if your below post is a paste of the contents of your bat file then your are missing a space " " ;)

@YG2018 said in Install snapin packs with elevated command prompt.:

Bat file (uninstall.bat) —> MsiExec.exe /X{A1E58BXX-ECXX-XX19-XXEA-B85CA4F1A2XX} /qn /norestart

It should look like:

msiexec.exe /x {A1E58BXX-ECXX-XX19-XXEA-B85CA4F1A2XX} /qn /norestart

Regards X23

I am wondering, the snapin should be run under system privilegues and therefore it should have admin rights.

Could it be possible that you just habe a path problem, how does your batch look like, can you paste it?

You can use a bat to exe coverter and set the admin manifest, system should it let be run then under admin rights.