@sudburr I believe that solved it! On my first attempt I inserted a 5 second delay after every command in my SetupComplete.cmd; that did not help. Then I added an additional 60 second delay at the start of the SetupComplete.cmd and my first test after was successful.

Thank you all; you have answered my questions! I have about five images I use most of the time. I do believe your suggestion to deploy from FOG and then capture using CZ would be my best option! And thank you for helping me understand the fundamental differences between FOG and CZ!

@Scott-B Understand that link is for BIOS based computers. I might expect the UEFI mode computers will need a bit different boot kernel. Looking at that error message again, why is it asking about bootmgr.exe that is a “MS Windows” thing. The Rescue CD of the link appears to be booting a linux (variant) kernel.

You can see the code in this link: https://github.com/FOGProject/fogproject/commit/501e2e947abe55f61fec434751e51e517dcba4d4

Hi again. Today I need to install some HP Prodesk 400 G4 :D And the problem come back in both mod (uefi and legacy) I try to check for a Bios update, and I done it but the problem steal here. I already try with a old no managed dumb switch. In my case I make a upgrade from 1.4.4 to 1.5.5 it was working like a charm with the 1.4.4. Now I have this problem with the 1.5.5. Any idea ?

@Almeida Free disk size? df -h? Anything you see in the apache error logs (see my signature)?

@Tom-Elliott said in Check in Failed There are 0 Before Me (In line for XX:XX): @Ginto what about max clients for the storage node itself? It is set to 10. I was able to bypass this error just now by going to my active tasks and force starting it. I would still like to fix this.

I don’t have a second computer right now but i plugged the SSD (SN520) into a computer Dell and it’s OK. I plugged the SSD of the Dell (Toshiba) on the HP-705-G4 and it’s OK. On the 705-G4 with the SSD SN520, it’s OK with a boot winpe. Thanks

Here are a couple of ideas. Make sure the geometry of file.png matches (exactly) the geometry and color depth of bg.png. Also if I remember correctly size does matter. There is a maximum total byte count of this background image. Secondly some uefi firmware can’t / doesn’t display background images. There is nothing you can do it make it work, its flaky uefi firmware. As for the uefi boot manager. Yes I’ve seen that myself. I think one of the developers was going to look into that issue. I don’t know if the fix will be in 1.5.6 or 1.5.7 if they can work it out. One of the issues we’ve seen is some people want windows to be the first boot option after imaging and other want to keep what ever boot order they currently have and not have FOG change the boot order.

@Valer i know that some bios let the „windows boot manager“ always go on position 1 if found afaik this can be turned off to keep your current order: https://superuser.com/questions/1043451/asus-bios-keeps-resetting-boot-priority-to-windows-boot-manager-before-uefi Regards X23

@Sebastian-Roth Caro colega muito obrigado pela ajuda, consegui resolver o problema com a sua ajuda. Agradeço também o esforço do @george1421 na contribuição do conhecimento. Se vocês residissem no Brasil eu pagaria uma cerveja bem gelada. Obrigado de coração.

@ylber you can get the code from from working_dev branch in git repository.

@emryz @ragnurenson From my point of view it’s all working fine. See the screenshot below. You are right that the power management task is not in the scheduledTasks table. I was on the wrong track with that when I had a brief look at this last time. As mentioned by @emryz the power management tasks show up in the same view where you schedule those for the host. See my screenshot below. @emryz I can imagine that some kind of AdBlock add-on in the browser could make this view disappear. We had a very strange case where one single text field was missing just because of an AdBlock add-on. Please disable these and see if it works for you. Note: I corrected my other post so when people come along and find this, they don’t get confused.

@UWPVIOLATOR said in Dell Precision 5530 Compatibility: It does have Legacy Boot BUT NOT for Internal HD. Thus you must deploy a UEFI image to this model. One additional comment on this point. It is possible with FOG to PXE boot in bios mode and with FOG deploy a UEFI image with a computer running in BIOS mode (I do this on systems where pxe booting in UEFI mode is broken, but pxe booting in BIOS mode works OK). Just be aware that you can not boot a UEFI image on a computer running in BIOS mode.

@george1421 @Sebastian-Roth Hello guys! I’m here to say that I had no problems loading tasks, neither capture or deploy, since I’ve updated the init files. I’m using bzImage at latest version, did extensive tests on Legacy BIOS systems that were presenting the “rcu_sched” warnings and so far I’ve never saw them again or any other hanging issues. If I can help with any othe kind of tests, please let me know. Thanks everyone, awesome work!

@j_d As well I may ask you to validate the certificate is matching the CA: openssl verify -CAfile /var/www/html/fog/management/other/ca.cert.pem /var/www/html/fog/management/other/ssl/srvpublic.crt Should tell you OK. From the client log you posted it clearly states to be a certificate/CA issue: Middleware::Authentication ERROR: Certificate is not from FOG CA

@george1421 yes it was. I also had to create the Scripts folder, it was not there by default. After adding that folder and the setupcomplete.cmd, I ran sysprep again with the unattend.xml file after adding the firstlogoncommand section to the file, deployed to my other test machine and everything worked according to plan.

@maouu Here is how we deploy with PDQ Deploy (sorry I don’t use snapins but the install function is similar: @Echo Off start /wait dfmirage-setup-2.0.301.exe /verysilent /norestart REM Hack to determine arch of this system IF EXIST C:\Windows\SysWOW64\diskpart.exe GOTO :x64 :x86 msiexec /i tightvnc-2.7.10-setup-32bit.msi /qn /norestart ADDLOCAL="Server" SERVER_REGISTER_AS_SERVICE=1 SERVER_ADD_FIREWALL_EXCEPTION=1 SERVER_ALLOW_SAS=1 SET_USEVNCAUTHENTICATION=1 VALUE_OF_USEVNCAUTHENTICATION=1 SET_PASSWORD=1 VALUE_OF_PASSWORD=<SetMe!!> SET_USECONTROLAUTHENTICATION=1 VALUE_OF_USECONTROLAUTHENTICATION=1 SET_CONTROLPASSWORD=1 VALUE_OF_CONTROLPASSWORD=<SetMe2!!> SET_IPACCESSCONTROL=1 VALUE_OF_IPACCESSCONTROL="192.168.0.0-192.168.255.255:2,0.0.0.0-192.167.255.255:1,192.169.0.0-255.255.255.255:1" SET_REMOVEWALLPAPER=1 VALUE_OF_REMOVEWALLPAPER=1 :x64 msiexec /i tightvnc-2.7.10-setup-64bit.msi /qn /norestart ADDLOCAL="Server" SERVER_REGISTER_AS_SERVICE=1 SERVER_ADD_FIREWALL_EXCEPTION=1 SERVER_ALLOW_SAS=1 SET_USEVNCAUTHENTICATION=1 VALUE_OF_USEVNCAUTHENTICATION=1 SET_PASSWORD=1 VALUE_OF_PASSWORD=<SetMe!!> SET_USECONTROLAUTHENTICATION=1 VALUE_OF_USECONTROLAUTHENTICATION=1 SET_CONTROLPASSWORD=1 VALUE_OF_CONTROLPASSWORD=<SetMe2!!> SET_IPACCESSCONTROL=1 VALUE_OF_IPACCESSCONTROL="192.168.0.0-192.168.255.255:2,0.0.0.0-192.167.255.255:1,192.169.0.0-255.255.255.255:1" SET_REMOVEWALLPAPER=1 VALUE_OF_REMOVEWALLPAPER=1 :Exit REM Install done, errors generated by msi will be reported to installer net stop "TightVNC Server" net start "TightVNC Server" rmdir /s /q "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\TightVNC\" I’m pretty sure if you reinstall with the new parameters they will overwrite what is in the registry. I know this ISN’T what you are looking for, but it works for us.

@ragnurenson so, I’ve just tested after applying the commited changes and everything works fine! Thank you for pointing out the github commit and thanks @Fernando-Gietz for the awesome work! If I can make a suggestion, I’d say it would be nice to have that search filter implemented in “List All Hosts” screen on Active Tasks!