oh ok thanks 🙂

Thank you so much, with the new / old inits the capture process ran successfully. Am trying to deploy now and see if everythin works out.

Thanks for your help
Sébastien

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!

Hi again.

Today I need to install some HP Prodesk 400 G4 😄
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.

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.

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

Capturar.PNG

Se vocês residissem no Brasil eu pagaria uma cerveja bem gelada.

Obrigado de coração.

@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

@RobTitian16

I realize this is a few month’s old. But you might want to check out and or contribute to the fog module I have in git and published in the powershellgallery, there’s a forum post with more info here https://forums.fogproject.org/post/120746
Also did you have a chance to try the code I posted back in september and see if that worked? Because it works for me.
And looking again at your code I would ask what the value of $useAD is, is it 1 it should be 1. And I would also try piping the object into convertto-json, I’ve had better luck with that, I think it parses it different i.e. $CreateHostJson = $HostJson | ConvertTo-Json I would also encapsulate everything in quotes on the splat.
The only other thing that might be an issue is the ADPass. When you get the password via the api it is returned in plain text (because you already authenticated with api keys, so it’s not like just anyone can grab it). When you input the password in the gui you put it in plaintext and it encrypts when you hit save, I don’t think the same thing happens if you set it through the api. My solution has been to always enable the default AD settings when adding a host via the gui or the pxe menu. But it sounds like you’re adding the host through the api. The “useAD”=“1” in the json should be causing the checkbox for the ‘join domain after deploy’ to be checked. Sadly when you check it from the api it doesn’t pull the default domain settings. You might try creating the host without the AD settings and then sending just the AD settings in an update/put command. If you copy paste the already encrypted password from a working host in the gui, that might do the trick as it seems to pass whatever you put in that field to be in plaintext.

So point is, try adding the domain stuff with an update api command after creating. And use the code I have in the example to help if needed.

Thanks Sebastian,

The fog server ia a quad core 3.4GHZ with 32GB ram and uses a 4 TB sata drive to store these images on. It’s normal images are stored on a SSD array, its just because these aren’t used that often that they’re stored on a sata.

The clients are all 32GB 4/6 Cores @3.4 GHZ, single SSD disk with a dedicated 1 GB network.

The machines are usually used for just their PC’s image in the training room.

Any suggestions?

Thanks

@Gamienator I am not sure if the Location Plugin will exactly match your needs. I was asking about this because it’s definitely worth looking into this for your kind of setup and on the other hand it might make a difference when we talk about adding ${storage-ip}.

I have not had the time to think this all through and work on the code though. I will try to do so over the weekend but won’t promise anything.

@Tom-Elliott Thanks again, I am by no means a Linux expert, I wouldn’t even be considered a novice.

Michael

@Sebastian-Roth That makes sense, to be honest, just didn’t think it would make a big difference. I actually followed those exact instructions to get UEFI working. All machines were able to boot to UEFI before. But now it’s just the one. The only thing that I changed was I reverted the changes I made for the driver injection that george1421 made. Now as I said only one machine that can boot with UEFI. It’s weird though, I can image the other machines with a UEFI format through the legacy Onboard NIC.

@george1421, @Sebastian-Roth

Thank you both VERY much! I just went and updated to 1.55 instead of doing the kernel update manually, figured it would probably be better in the long run. Now it appears to be working normally. Sorry I didn’t notice earlier the kernel wasn’t what I thought it was!

Solution my problem:

tips of Sebastian Roth: mkdir /home/fogbackup/ chown fogbackup:fogbackup /home/fogbackup/ change config file /etc/vsftpd/vsftpd.conf vsftpd_log_file=/var/log/vsftpd.log log_ftp_protocol=YES allow_writeable_chroot=YES chroot_local_user=YES chroot_list_enable=YES chroot_list_file=/etc/vsftpd.chroot_list rsa_cert_file=/etc/ssl/private/vsftpd.pem rsa_private_key_file=/etc/ssl/private/vsftpd.pem ssl_enable=YES force_local_data_ssl=NO force_local_logins_ssl=NO

@apollo40 Or you can use a postinit script to set the password: https://forums.fogproject.org/post/88286