@Tom-Elliott said in Ubuntu is FOG's enemy: apt-get -y remove unattended-upgrades This saved my bacon, thank you very much, first command failed but second one worked, i have also run the unattended-upgrades command, once again thank you.

Sebastian : I do this in the day Thanks

I figured it out, login to the MySQL database and run: DELETE FROM tasks WHERE taskStateID IN (“1”,“2”,“3”);

@Daniel-Miller Thanks for such a quick reply! Yes, there is a proxy on both server and client. Fixed this one now! Script is trying to set environmental variables using [Environment]::SetEnvironmentVariable Method for “Process”, “User” and “Machines”. I see, so there is no way I can set it at the machine using snapins? Script is using New-ItemProperty method in powershell. I forgot to mention that it succeeds in setting values in HKLM:\SYSTEM (but not HKLM:\SOFTWARE). I am mainly using powershell scripts and some batch scripts that trigger other powershell scripts. It is run on Windows 10.

@george1421 Did another test of the surface go with the surface usb-c adapter on the new kernel. It did technically finish the image but at the very end of imaging this db error stuff happened The image got to 100% complete and thus far everything looks like it’s working, the only thing I can see thus far that didn’t work was writing the image history to the host. Could be unrelated to the kernel and such but this didn’t happen on the other 2 surfaces I imaged today with the lenovo usb-c adapter and a usb 2.0 ethernet adapter.

@sudburr your commands fixed the issue. we also found article on Microsoft website that covered your commands. https://support.microsoft.com/en-us/help/4056823/performance-issue-with-custom-default-user-profile Thank you so much

@Daniel-Miller Thanks Daniel. They use puppet. I’ll shoot them an email. Thanks again everyone for all the help.

@Tom-Elliott Great comments, Tom! Thanks! Just pushed new commits and answered as well.

Thanks, everyone for the help. Our new laptops arrived today and I plan on a rollout after the holiday break (January 6th). I hope I gave myself enough time. Mark

@Tom-Elliott said in Backing up database Failed on install: git checkout dev-branch @Rogsninja As Tom said, you need to use the latest dev-branch version as there were issues due to the CentOS 8 release that came out after we had published 1.5.7 (latest official FOG version). About install errors in general: The installer creates logs. Please take a look at /root/fogproject/bin/error_logs/fog_error_1.5.7.log and post the full content or a least the last 10 lines of that file here in the forums.

@Foglalt Yes new thread please. We like to keep one issue per thread so not to confuse future readers.

It took some doing, but group module status’s will now be reflected in the group if all hosts in the group have the module associated, otherwise it will display as unchecked as we don’t know which hosts do/don’t have the modules applied.

@Tom-Elliott Removed the postinit Replaced the inits with artifacts. Linux is working with capturing, still need to test deployment with Linux. Still needing to test deployment & capture with Mac after the above changes. -Edit 1- Linux deployment works. Mac deployment works, still needing to test capture. Want to write the master image before rewriting the golden image on Mac.

@LittleTux How i can pass this post on Solved ? Done. Glad it worked

okay thanks for the reply

@tomhtil Thanks for bringing this up. As Tom said, the fog-client maintains a strict security trust relationship to the server. This design has the obvious drawback of not being able to maintain two trust relationships for one MAC address at the same time. Probably something Joe left out when he initially created the fog-client. But I can see why people want to use it this way and I will look into this. Be aware, this will probably take some major changes in the code and won’t be fixed in a matter of a few days. There might be some kind of quick fix (copy token from one OS to the other) but I have not looked into this. Will do so.

@Daniel-Miller Thanks for reporting! Obviously hasn’t been noticed in a while. I just pushed a fix to working-1.6. Moving this to section bug reports and marking as solved.

Waiting for them to produce an Amazon Machine Image: https://wiki.centos.org/Cloud/AWS

Typically a post install script relies on the image being on the computer because the post install script would interact with the image once its downloaded to the disk. With that said I can give you some tips to make debugging a bit easier. Schedule your deployment task, but before you hit the submit button tick the debug checkbox. PXE boot the target computer. After a few screens of text that needs to be cleared with the enter key you will be dropped to a linux command prompt. These next to steps are optional Get the IP address of the target computer using ip addr show Set root’s password with passwd give it a simple password like hello. Don’t worry it will be reset the system is rebooted. Now use putty and connect to the target computer using the information from steps 3 and 4. Using putty you will be able to cut/copy/paste a bit easier than using the FOS Linux console. But these 3 steps are up to you The rest of the steps work both from the putty shell as well as the console shell. Start the deployment process from the command prompt by keying in fog. You will now single step through the imaging process pressing enter at the each debugPause command. You can insert the debugPause command into your post install script to stop the deployment at critical points. Pressing enter will continue the script until the next debugPause breakpoint. Hints: Add liberal echo commands to indicate the start, execution of critical points and exit of your post install script. If something goes wrong, pressing ctrl-c will exit out of the deployment script at the point where you hit ctrl-c. If you are linux savvy you can navigate to where the postinstall script is and rerun just that script after you fix what needs fixing. (I don’t know the path off the top of my head, sorry) You can start the deployment process over again without needing to reboot by just keying in fog again at the command prompt. If you are interacting with windows, I have some post install scripts with examplesin the tutorial forum. While they are windows focused they should show you some trick you could implement in your scripts.