@Baessens Maybe i need to change the UID of my FOG installation? ?
Edit: changed the UDPCAST INTERFACE to eth0, still same problem.

Also, Is this wrong?

ict@fogserver:/images$ ls dev postdownloadscripts Priminfowin10pro lost+found postinitscripts priminfowin10pronewofficekey ict@fogserver:/images$ cd dev ict@fogserver:/images/dev$ ls dev postdownloadscripts

EDIT: re-running the installer seemed to fix the issue.

Hi @NT_Tech ,
The access control Plugin works, but is possible that you need to do some changes manually in the code.

I need to know to help you some things about your server.

Do you use LDAP plugin to validate your students?

@george1421 DUDE it worked after adding imgFormat=0 (for gzip). Thank you again!

For anyone having the same issue I ended up with this GRUB menu item:

set myfogip=10.100.71.8 set myimage=/boot/bzImage set myinits=/boot/init.xz set myloglevel=4 set timeout=-1 set fogimage=2018-07-17Win10-1803UEFI set imageid=9 insmod all_video menuentry "1. FOG Quick Image Deploy $fogimage" { echo loading the kernel linux $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=$myfogip/fog/ storage=$myfogip:/images/ storageip=$myfogip boottype=usb consoleblank=0 rootfstype=ext4 imgPartitionType=all chkdsk=0 capone=1 type=down imgid=$imageid img=$fogimage imgFormat=0 imgType=n osid=9 echo loading the virtual hard drive initrd $myinits echo booting kernel... }

Changing the interface to enp2s0 solved the problem - many thanks George, really appreciate your support.

@lxrsd Now on this part. Its giving you a bitlocker screen when you boot the iso image?

This may show ignorance on my part with bitlocker, but isn’t bitlocker dependent on uefi mode?

@george1421 I didn’t know that storage nodes were deploy only. Thank for the info.

@george1421

That is indeed sad news 😞

I will have a look at the link.

Thanks you very much.

@noob It’s not a problem, it’s a default. Whether to change the partitioning or reinstall is up to you. You’d learn a lot going the longer road.

yes that’s it, thank you, I had not seen.
it was two lines to enter
thank you

set username "login" set password "password" params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param sessionJoin 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme

thanks!
It’s more clear.
I always have 0.11.16 version, not need to upgrade 🙂
Regards.

Hi @cmyron . I had the same issue until i upgraded the kernel version to 4.5.0
Maybe you can try it as well?

@Beber55 Looking at your screenshot and the wording, the reason for the RJ45 needing to be plugged is that you’ve got it set to DHCP instead of static IP.

For static IP, follow this guide: https://askubuntu.com/questions/766131/set-static-ip-ubuntu

The other option is, if Virtual Box supports it, set the interface as NAT’d so that you get another DHCP locally on your PC. I’ve not used Virtual Box in ages so I can’t confirm this.

@george1421 Hahaha, it’s all good. Thank you! Merry Christmas!

@fogger1 The links that are provided are the init’s in the most current state we have. The good thing is now that the init’s are separated from the main elements of FOG, and changes aren’t quite as frequent as the main elements, the init’s being provided should work with any 1.5.x version of FOG and even the 1.6 as the backend “functional” pieces aren’t being modified at the same scale between the two versions. So they’re not provided for 1.5.4, they’re whatever the most current version is. The init’s are not labelled in the same fashion as our normal releases which is why it’s important for the distinction here. The init’s in the links are what are provided for 1.5.5 and 1.5.5.2 (which is the most current dev-branch version).

@Junkhacker Thanks for your assistance

@mary-montesanto said in ERROR #16 IRQPOLL:

@george1421

advice to update the Lenovo Bios? What is the client PC?

Sorry I don’t understand the question. What I’m suggesting is to update the pc bios on the lenovo computers, or at least check the installed version vs what is current from the Lenovo web site.

I know this is an old topic, just wanted to reiterate that this fixed my problem. The weird thing is that this wasn’t a problem until today. Been using Fog with the same laptops, same basic install of Windows 10 for around 1.5 years now, and today was the first time I saw this error. Went and turned off fast boot and it works great. Yay for forum search functions. 😉

Philip

@BSZAdmin hello, I have the same issue, can you please help me? How did you fix it?

@chanstag A proper dhcp/pxe boot process should be this.

PXE client - Discover DHCP Server - Offer PXE client - Request DHCP Server - ACK.

That second pcap is discover, offer 1, offer 2, discover. Meaning that the pxe client didn’t get what it needed to even get an IP address.

So a couple things I’ve gleaned from looking at the pcap.

If your dhcp server is running on your router, its not responding to the dhcp discover from the pxe booting computer. You have a non-fog created dhcp server running on the fog server. Its responding with an IP address but its not sending the boot file or next server information. The FOG created dhcp server will send the proper boot information. You have dnsmasq installed on the FOG server, and it IS responding correctly. But because there is a dhcp server also running at the same IP address the target computer is getting confused and taking the dhcp offer and not the proxy dhcp offer. Your target pxe booting computer is a uefi type BC (00007). Not really important, but dnsmasq should be sending ipxe.efi to the target computer so it can boot.