Posts made by WillingMost7

@george1421 it is on the same subnet. It was working a while ago when I did a test and now it’s not working, I don’t know if I just forgot a step I did or something else went wrong somewhere else (that maybe related to other division, but I don’t know what else to look for). Anyhow I am checking all possible leads.

What should I change in the first lines you marked? Sorry, I didn’t quite understand.

Edit: legacy PCs still able to boot perfectly, which shouldn’t be possible due to the change of the boot file in the config

@george1421

# Don't function as a DNS server:
port=0

# Log lots of extra information about DHCP transactions.
log-dhcp

# Dnsmasq can also function as a TFTP server. You may uninstall
# tftpd-hpa if you like, and uncomment the next line:
# enable-tftp

# Set the root directory for files available via FTP.
tftp-root=/tftpboot

# The boot filename, Server name, Server Ip Address
dhcp-boot=ipxe.efi,,X.X.X.X
# dhcp-boot=undionly.kpxe,,X.X.X.X

# rootpath option, for NFS
#dhcp-option=17,/images

# kill multicast
#dhcp-option=vendor:PXEClient,6,2b

# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override

# inspect the vendor class string and match the text to set the tag
dhcp-vendorclass=BIOS,PXEClient:Arch:00000
dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
dhcp-vendorclass=UEFI,PXEClient:Arch:00007
dhcp-vendorclass=UEFI64,PXEClient:Arch:00009

# Set the boot file name based on the matching tag from the vendor class (above)
dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,X.X.X.X
dhcp-boot=net:UEFI,ipxe.efi,,X.X.X.X
dhcp-boot=net:UEFI64,ipxe.efi,,X.X.X.X

# PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
pxe-prompt="Press F8 for boot menu", 3

# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot from network", undionly
pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi
pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi

# A boot service type of 0 is special, and will abort the
# net boot procedure and continue booting from local media.
#pxe-service=X86PC, "Boot from local hard disk", 0

# If an integer boot service type, rather than a basename is given, then the
# PXE client will search for a suitable boot service for that type on the
# network. This search may be done by multicast or broadcast, or direct to a
# server if its IP address is provided.
# pxe-service=x86PC, "Install windows from RIS server", 1

# This range(s) is for the public interface, where dnsmasq functions
# as a proxy DHCP server providing boot information but no IP leases.
# Any ip in the subnet will do, so you may just put your server NIC ip here.
# Since dnsmasq is not providing true DHCP services, you do not want it
# handing out IP addresses.  Just put your servers IP address for the interface
# that is connected to the network on which the FOG clients exist.
# If this setting is incorrect, the dnsmasq may not start, rendering
# your proxyDHCP ineffective.
 dhcp-range=X.X.X.X,proxy
# dhcp-range=X.X.X.X,proxy

# This range(s) is for the private network on 2-NIC servers,
# where dnsmasq functions as a normal DHCP server, providing IP leases.
# dhcp-range=192.168.0.20,192.168.0.250,8h

# For static client IPs, and only for the private subnets,
# you may put entries like this:
# dhcp-host=00:20:e0:3b:13:af,10.160.31.111,client111,infinite

X.X.X.X stands for my FOG’s server IP

@george1421 some lines were indeed missing but I don’t think this is the cause, as I had changed a year ago the boot file for better compatibility and the change applied.

I tried adding them but it didn’t help. Thanks for helping!

I have a Lenovo Neo 50T gen3 set to UEFI. On boot it detects the FOG server though after NBP download is completed it skips the FOG menu and jumps into Windows11 (secure boot is off).

Fog version is 1.5.9 with kernel Version: 5.10.50
I have a dnsmasq so options 66,67 is the DHCP server doesn’t affect PCs. I tried ipxe.efi and snponly.efi (I had to make a symbolic link to undionly.0 cause for some reason if I change it only in the ltsp.conf it seems to not affect).

Thanks in advance!

@peterl Ton of thanks to you. I have the exact same model here and I have had this problem.

Now downgraded to rEFInd of fogproject-1.5.5 it is not stuck anymore on “rEFInd-Initializing…”, but it is stuck now on “Scanning for new boot loaders; Please wait…”
Have you made any changes to the refind.conf file?
Mine is set at:

....
scanfor internal
....
timeout -1
....
scan_delay 5
....

It is an improvement, we’re getting somewhere now and soon will solve this. So, thanks for sharing!

@poizzon Same here. I tried replacing in S: partition to the latest rEFInd but still getting stuck at “initializing”.

@sebastian-roth Wow thanks a ton! That worked indeed.
Do you happen to know if it’s possible to update all the PCs to the latest using FOG (since they are running a FOGService, but 0.11.19 instead of 0.12.0)?

Correct me if I’m wrong, but I think I have found the cause:

17/08/2021 06:19:03 Data::RSA FOG Server CA cert found
 17/08/2021 06:19:03 Data::RSA ERROR: Certificate validation failed
 17/08/2021 06:19:03 Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: The signature of the certificate cannot be verified. (NotSignatureValid)
 17/08/2021 06:19:03 Middleware::Authentication ERROR: Could not authenticate
 17/08/2021 06:19:03 Middleware::Authentication ERROR: Certificate is not from FOG CA

This is weird cause these PCs are registered in the FOG server. Moreover, there are a lot of PCs that do not stubmle this issue.

@sebastian-roth Sorry for late response.
Here is a log from a PC that when I run a Snapin on it, it stays on “Checked In” and I don’t have a “Reset Encryption Data” button when entering the host.

fog.log

Thanks a ton!!!

edit: Also I noticed it has nothing to do with the windows version, as I see I have some windows 7 PCs that does have “Reset Encryption Data” button and some windows 10 PCs that doesn’t.

I have recently made a snapin to uninstall two programs. The thing is that it is working on the windows 10 PCs here but not on the Windows 7 ones.
I have noticed that the Windows 7 Hosts on the FOG server are missing the “Reset Encryption Data” button is missing, unlike the Windows 10 Hosts. But it does show up in the “Groups” tab

Same Snapin works on one and not on the other. Thanks for all helpers!

Here is the fix:
Try every boot file until you find the right one for you.

This is what I did as I ran out of options and it turned out to be good. Follow this tutorial: https://wiki.fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server under DNSMASQ settings for iPXE

@george1421 said in Unable to boot properly after Radix SmartRecovery installed:

So is it certified for the version of windows 10 you are using?

Yes indeed.

@george1421 said in Unable to boot properly after Radix SmartRecovery installed:

Well it works when fog is not in the picture

Thus I thought that FOG is the problem here. Everything I tried here had a different effect but none actually help me understand how to solve this.
Also someone managed to solve this by changing the boot file, I discovered that the exit-type of the boot types causes the effect, so it seems to me only logical that it has to be the FOG server.

Thanks a lot for all your time and effort.

@george1421 said in Unable to boot properly after Radix SmartRecovery installed:

I’m not going to knock others tutorial on github

This is also shown in FOG’s wiki.

@george1421 said in Unable to boot properly after Radix SmartRecovery installed:

If you were using sanboot then that is an iPXE function (the program that builds the FOG iPXE menu).

Unfortunately sanboot isn’t working at all, even without the software. The weird thing is that Radix works with windows 7.

@george1421 said in Unable to boot properly after Radix SmartRecovery installed:

0x80 (first hard drive in the system)

Maybe cause these PCs have M.2?

@george1421 I have managed to change the boot file but also followed your guide you posted, anyhow it didn’t make any change cause it is still not chaining to windows after the restore phase.

I have found another Reboot to Restore software named DeepFreeze and it manages to do the job well unlike Reboot to Restore Rx and Radix, wonder what is different.

@willingmost7 said in Unable to boot properly after Radix SmartRecovery installed:

I followed a guide on GitHub to change the boot file (under Configuring DHCP section), but it does not seem to work. I will try all the boot files there.

I had to use sudo ln -sf to force the symbolic connetion.

I read on other thread that the fix was done by changing the boot file to ipxe.kpxe.

I followed a guide on GitHub to change the boot file (under Configuring DHCP section), but it does not seem to work. I will try all the boot files there.

Thanks again for all your help, just sharing my progress

@tesparza Thanks a ton for your good will to help! Appreciate.

It’s a paid software. I need it to keep the students from destroying the computers.

I have found another thread talking about this RRRx software (which does the same so I don’t mind using it instead) and he fixed it by replacing the boot file, he used ipxe.kpxe instead of undionly.kkpxe.

And here is the proccess I made trying to figure out the problem: https://forums.fogproject.org/topic/15636/unable-to-boot-properly-after-radix-smartrecovery-installed/2?_=1628169887941

@librarymark I came accross the same error here with a different software that does the same. Couldn’t fix it but I see you managed to fix it and I don’t mind to use RRRx instead of Radix.

Can you walk me through this please? My FOG server is set to undionly.kpxe as far as I know (last time I checked this was long ago). Do I need to change it in /etc/dnsmasq.d/ltsp.conf

@joe-schmitt I have stumbled into the same problem with a different software that suppose to do the same. Where can I find this whitelist (where it’s located) and what’s the command to whitelist the client?

@tesparza Managed to fix it yet?

I opened a thread about it (with a little more progress than here) here:
https://forums.fogproject.org/topic/15636/unable-to-boot-properly-after-radix-smartrecovery-installed

I contacted their support and they couldn’t get onto the problem.

@george1421 Here is a link to the iso, very powerful useful tool.

@george1421 said in Trying to add iPXE option to boot WinPE:

memdisk only works with BIOS based computers not UEFI

PCs there are able to boot both from legacy and UEFI, but their OS is set to legacy boot. Is it possible to set this to boot from UEFI? It won’t cause any problems?