@george1421 I found that my previous image which I used on Elitebook g5s is having diffrent ethernet driver, its issue with image. I test it on diffrent computer its installed correct. Please disregard my question.

@george1421 You were right, it was a problem with DHCP, our System team solved it by comparing it with another site, I don’t know the details, but it’s working now, Thank you for your help!

@george1421 You were right, it was a problem with DHCP, our System team solved it by comparing it with another site, I don’t know the details, but it’s working now, Thank you for your help!

@george1421 I did sent you dropbox link to wireshark logs, let me know if you find something

@george1421 We was doing the test with tcpdump and wireshark, unfortunately no luck, between 2 vlans we have it fog server and vlan we do images, there is no Firewall, so its suppose not block anything

what can we check next? We have FOGs in a few locations, in every place, but the network configuration is the same, and only this new one with 1.5.9 is having this kind of problem…

Hi,
new fog installation here
ver. 1.5.9
ubuntu 20.4 LTS graphic interface (root wasnt activated at start)
we have domain DHCP option 67 and 66 configured with correct IP and ipxe.efi
all HP machines
bios configured - (secure boot off, fast boot off, uefi only machines)

I dont know If I forgot to setup something after we install fog yesterday, all we done is listed above. I updated kernel to newest from WebUi but didnt help. I think I might try change refind, but I am not sure is correct step now? Give me some hints please

We are only seeing this, no errors, after a minute its movind to windows, cant access fog ui from boot

Sorry for no response till now, I tested with antivirus disabled, created new snapin, and add new file again. Old end up with hash error.
This machine have build in wifi and lan, now its error on both. In snapin history all task end with return code -1 after around 1 min time. What else I can check?

Hello,
fog version 1.59 - RC
linux centos 7

I am recently strugling with WPKG installation on wireless computers, ended up with Idea to run script via fog snapins, but I met with a problem

------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 25.02.2022 10:46:19 Client-Info Client Version: 0.12.0
 25.02.2022 10:46:19 Client-Info Client OS:      Windows
 25.02.2022 10:46:19 Client-Info Server Version: 1.5.9-RC2
 25.02.2022 10:46:19 Middleware::Response Success
 25.02.2022 10:46:19 SnapinClient Running snapin run_wpkg
 25.02.2022 10:46:19 Middleware::Communication Download: http://10.180.8.90//fog/service/snapins.file.php?mac=F4:39:09:07:E3:D8|D2:37:45:4E:D9:E3|D0:37:45:4E:D9:E3|D0:37:45:4E:D9:E3&taskid=454
 25.02.2022 10:46:19 SnapinClient C:\Program Files (x86)\FOG\tmp\run_wpkg.bat
 25.02.2022 10:46:19 SnapinClient ERROR: Hash does not match
 25.02.2022 10:46:19 SnapinClient ERROR: --> Ideal: A38A276FC3F8F3BA03094495668B7459C56ED1B5DCBD77774BBA22A3CDCF0B9CE3B33C612C824220E0C2156864332C1F9E0A3C18A190A6BA6F17D9C239122626
 25.02.2022 10:46:19 SnapinClient ERROR: --> Actual: 94C85322BD7EC5FE201F52064A78C58BFA99C10AC316EC557BE010FF88D3AD5F3F3BF220FFCB07CAF77F89A9E0F4A44CE1CF9343DBFD0C7E582C5DC0C7AF42B5
 25.02.2022 10:46:19 Middleware::Communication URL: https://10.180.8.90/fog/service/snapins.checkin.php?taskid=454&exitcode=-1&mac=F4:39:09:07:E3:D8|D2:37:45:4E:D9:E3|D0:37:45:4E:D9:E3|D0:37:45:4E:D9:E3&newService&json
------------------------------------------------------------------------------

this is showing only once I trying to run the snapin on wireless. Snapin on the same machine on wired network goes through nicely (well beside script failing to work).
So I want to ask, if snaping will always fail when I switch network card and mac address? Can I have it work on both? If laptops only work on wireless should I try to image them via wireless too?
Please give some hints, explanations how to solve it

thank you in advance!

@quazz Thank you so much, it was wrong date, I am ashamed I didnt check that, case solved.

Hello,
specification
fog: 1.5.9-RC2
linux: centos 7
dhcp seeting ipxe.efi
computer: HP Elitedesk 705 g5 sff with Amd processor

problem with only one machine after trying to deploy new image, we got this error on every boot:

What I did was: setting bios back to defaults and set it for uefi again, secure boot disabled
delete machine from fog completely in webui.

What else I can do?

Hi, so I did change to version refind version 0.10.4 worked with my HP models, and capture new image, on only UEFI bios, and its working. @EduardoTSeoane made me think that I have only legacy compatible images so I tried to fix that. Thank you guys for help!

@sebastian-roth Yes I am testing it every time too, always end with chainloading failed, and reboot in 10 seconds.
Edit: I found more options to exit boot:
a) IPXE General Configuration> boot Exit settings> exit to hard drive type (EFI)
b) Fog settings> Fog boot settings> EFI boot exit type

are they different, and what with “boot exit type” its also there which is to change here?

I also notice that “key sequence which is set to f12” is not recognized, and its always “ESC” instead, maybe its not sending settings to machine after changing to ipxe.efi?

Maybe I am missing something as I need in the new Image for this? I am open for suggestions