@george1421 yes

@sebastian-roth about the live system, i need to find the time today, i have the book until next friday.

@Tom-Elliott said in Certificate expired FOG Website:

I’ve modified the cron to run every 5 days so this should no longer happen.

with letsencrypt i let the cron job run every 2 months (certs are valid for 90 days).
i would leave the cert server contacts as small as possible, for what should 5 days good for? 🙂
Sure, the best way in my mind would be 24 hours before it expires…

Regards X23

Look for setupact.log and setuperr.log files under the following paths:

C:\Windows\Panther
C:\Windows\Panther\UnattendGC
C:\Windows\System32\sysprep\Panther

Additional log from this post: https://forums.fogproject.org/post/96860

But now, i know all sysprep logs … :

cbs.log
setup.etl
session.xml
setupact.log in Windows folder
setupact.log in Windows\Panther folder
setupact.log in Windows\Panther\unattendGC folder
setupapt.dev in Windows\inf
setupapt.offline in Windows\inf
setuperr in Windows\Panther …

@chris6862 FWIW: Between image captures I’ve used the FOG post install scripts to “patch” the target image as FOG deploys it to the target machine.

In our process we rebuild our reference image once a quarter. We have to go through and validate that the reference image works on all 12 models in our fleet before we can release it in fog for deployment. If we discover a gotcha after its been approved and released (as in needing to add something to the unattend.xml file or setupcomplete.cmd) We will have a post install script run to slide in the correction once imaging is done, and before the system reboots into windows setup. I’m not saying that this process will solve your issue here, but it IS a workable option if you need it.

@x23piracy Mark as solved is only available for moderators and developers and such, to prevent people from solving too early and what not.

@george1421 Windows was telling me after the second boot (inaccessible boot device) this was after the bootloader.

Regards X23

@Wayne-Workman not tested yet, but i will try this but don’t expect it in the next hours 🙂

Thanks all good!

@lebrun78 I don’t use the FOG Client so I can’t really speak to its activation of the target computer. But I believe if its enabled in the fog management web ui and you have entered either a OEM key or VLK key in the host configuration for that computer the FOG Client will try to activate it. I believe this is outside of any sysprep process.

I can tell you how I use MDT, sysprep and FOG.

I do use MDT to build my golden image each time using the lite touch process. At the end of imaging I run through a quick quality check to ensure everything is setup as it should be then I run a batch file that MDT drops in a certain directory that calls sysprep and points to a custom unattend.xml file. Sysprep then powers off the computer. I capture it with FOG. Then deploy it. I have a post install script update the unattend.xml file on the target computer with the computer’s name, target OU, timezone, KMS Key, and a few other things. When the computer boots and runs WinSetup/OOBE the target computer connects itself to AD and in the proper OU from the unattend.xml file. At the end of OOBE WinSetup calls the setupcomplete.cmd and runs a command cscript c:\Windows\System32\slmgr.vbs /ato that activates windows.

@x23piracy unfortunately a standard Active Directory contains usually just: hostname, and sid, along with a few other details such as OS version. FOG 2.0 doesn’t rely on MAC addresses as a primary identifier anymore, but still requires some additional information that’s not stored in AD to perform proper host matching. So long story short; no we will not support AD importing for the foreseeable future due to some technical limitations.

@goempie said in Read Windows Keys from Registry and BIOS (OEM Key) (FOG Client):

Hello
I’m trying to get your script working, but can’t get it to work.

Does the bat to exe converter also pack in the oemkey.exe or do i have to copy the oemkey.exe to a directory in my image?

Thanks

setkey.exe in the bin directory is the finished product. oemkey.exe is packed into setkey.exe while the script itself is also in oemkey.exe but executed from setkey.exe itself.

All you need is setkey.exe to be executed as admin (snapin) nothing i just uploaded everything together because people may leery when can’t see the source of it.

Regards X23

One might think FOG is pretty close to what you want today. If you go into the quick image menu FOG today displays a list of all images, but the default image assigned to that workstation is selected by default. So FOG knows the defined image for that computer, the trick (solution) is to not have fog show all the other images. After the menu timeout the defined image is started if no one touches the keyboard.

While I’m sure it not as easy as this, but if you could find the sql commands used to display that menu, one might be able to tweak it to only show the assigned image.

This was just an idea, without any basis of fact in the code.

to solve this in future i will add a “net time…” command to my first logged on user.

@x23piracy said in [SOLVED] Network Boot does not work anymore (no FOG Problem!):

It a shame i must say i dont know the differences between the different boot files 😞

https://wiki.fogproject.org/wiki/index.php?title=Filename_Information

@Joe-Schmitt no interaction with fog client then triggering the snapin.

@x23piracy If it’s system wide, it shouldn’t matter, but that doesn’t mean much. System wide still is not “system wide” in the case of curl/wget/apt/yum unless you make sure the default configuration files with the same information.

Moved to “FOG Problems”.