@marted Just want to keep this topic up as it might be very helpful for others. Not sure if you have time and access to systems right now though.

@sebastian-roth It’s beautiful!
Thanks for figuring that out!

bonsoir george, stp excuse moi de venir ce soir te poser ce problème,

je veux déployer mon image sur une machine physique mais cela ne fonctionne pas. voici l’erreur que je reçois.20210404_012630.jpg 20210404_012700.jpg

la marque de mon ordinateur c’est un dell latitude et en passant, mon serveur est sur une machine virtuel et j’ai connecté ma machine cible directement sur la machine physique qui abrite mon serveur fog sur virtual box. par quelle moyen savoir que ma machine physique est bien connecté à mon serveur virtuel???

No idea ?

@hugothebas This article applies to 1.2.0 and below: https://wiki.fogproject.org/wiki/index.php?title=Advanced_Boot_Menu_Configuration_options

@Tune389 said:

@ch3i okay thanks for the info. I try now to downgrade my fog version back to 1.2 …

That’s not supported nor advised…
To “downgrade” requires either restoring a previous snapshot (via a virtual machine) or rebuilding your FOG server from scratch…

Good to know. So it seams to only cause problems with a distinct combination of curl and openssl version(s). Possibly the newer curl version works around an openssl bug or the other way round… 😄

Again, anything to report?

@gwhitfield said in FOG service on 0.10.6 not restarting after reboot:

demon ninja gremlins

We are certified demon ninja gremlin dispatchers.

@Tom-Elliott

The group settings change in the update fixed the problem!

Thanks!

Perhaps I should expand.

This is what I did up to v1607.

My sysprep answer file sets autologon of Administrator for 99 times. It enables the Administrator account and has the password included (hashed by sysprep). It also includes a FirstLogonCommands to run a cleanup script.

That cleanup script performs the first part to remove security, rewrites the RunOnce registry value, then restarts the computer. Because the RunOnce registry value was recreated, the auto logon of Administrator launches that script again to perform further functions. After 3 more restarts the script turns off autologon, does not rewrite the RunOnce, re-enables security, then shuts the system down.

With v1709 I changed how I harvest driver files and have been able to install all drivers without the need to dumb down the security. I now install all general drivers from setupcomplete.cmd .

@aksl Are keen to get your hands dirty and dive into “compiling and debugging iPXE”?? If yes is your answer, there is a way I could lead you.

@Alex78 What do we need to do to gain access to the images? When clicking any of the links, I get “Not Found”.

@Sebastian-Roth that’s good news! I can test it out once it’s wrapped in. I tried what John did, but didn’t have any luck. Also tried following the wiki post on HTTPs/custom certificates that you shared in the other thread, but was still getting the overlength error. I decided to just use the certificate that FOG creates on install instead of my custom one for now.

@austinjt01 Ok that is a great starting point. I’ll again refer you to my tutorial: https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed

Look at the fog.custominstall script. Start with that script and then in this section add your code:

echo "Done" debugPause . ${postdownpath}fog.copydrivers # . ${postdownpath}fog.updateunattend umount /ntfs

Remove the call to the fog.copydrivers and fog.updateunattended and insert your code. At this point in the code /ntfs has been mounted onto the windows (C: drive) partition, wherever it may be. The script takes into account nvme vs sata as well as partitions being in different order or locations.

@Tom-Elliott Thank you! I can confirm this fixed the issue. Snap-ins are deploying successfully and the tasks are clearing.

@george1421 A Merry Christmas and a Happy new year to you guys.

@Sebastian-Roth as well as all the others ( @developers @moderators @testers )

Would we want anything besides kernel information? I had some ideas:

Number of hosts
Number of images
Number of each type of image
Number of systems imaged in the last 7 days
Number of storage nodes
Number of storage groups
Other things?

It’s been said before, but will say it again. This is all anonymous data. There is no way to correlate this data back to any system.

It just provides us insight (and possibly bragging rights). imagine us being able to say “FOG imaged a bazillion systems last week, we’re proud of that” or maybe “FOG assists with managing a quadrillion million computer systems every day”. I’m being funny with the imaginary figures here, but you get the idea. It’d be nice to make statements like that on the home page fogproject.org