The known good systems were extremely slow as well just like the new one using 3.12

Any other scripts I an run or ideas to get some usable info towards troubleshooting?

Well Congratz lol!

@sebastian-roth Hi sorry, I couldn’t answer any sooner. “Nevertheless we ought to try out using the SNP binary (debug enabled - DEBUG=snp:3,nii:3 to start with). So find 01_snp.efi here. Just give it a try and post pictures or video. Make sure when you take those to place the camera or phone on a stack of books in front of the screen so we have a good picture.” Here you go, not much to say from my side but here goes: video Thanks!

Thanks, Wayne!

@Sebastian-Roth Sadly I am out of surface go’s to test at this time. Gotta get the ones we have in production.

@lebrun78 Just be aware there is no way back to the 1.5.x version of FOG if you switched to working-1.6 now other than very messy manual manipulations in the database. We are working towards 1.6 and hope to have most users upgrade at some point. So I am not saying you shouldn’t. Just want to make sure you understand the consequences.

That did work!! Hallelujah! Thanks vinyard and Tom!! I ran the following commands and now its uploading that first image: systemctl status nfs-server systemctl enable nfs-server systemctl start nfs-server Thanks guys, success at last!

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

No idea ?

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

@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…

Again, anything to report?

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…

@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.

@gwhitfield said in FOG service on 0.10.6 not restarting after reboot: demon ninja gremlins We are certified demon ninja gremlin dispatchers.

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 .

@Tom-Elliott The group settings change in the update fixed the problem! Thanks!

@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.

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