@george1421 @sebastian-roth

Thank you both for your help. I am trying to understand as much as possible before asking questions. I did confirm with my boss that we are using a Windows Server 2012 R2 for DHCP and was able to find this. It looks like we are only setup for undionly.kpxe. Thee were the only entries.

There is an IP address above undionly.kpxe, I just didn’t want to show our internal IP address. That IP address does match what is on the FOG web server.

So I should be able to just follow the link @Sebastian-Roth sent me for Using Windows Server 2012 (R1 and later) DHCP Policy, correct? My question for that is for Step 3, does the “ASCII” field value determine the string value for Step 10? If I go with PXEClient:Arch:00007 in step 3, can I still choose the string value of snponly.efi or would I have to use ipxe.efi?

Another idea I had wanted to ask about is the possibility of editing the scope option for 067 Bootfile Name from undionly.kxpe to snponly.efi. Would this be a quicker and easier way to test if snponly.efi or ipxe.efi will work before doing the DHCP policy?

@george1421

Hello george1421,

I don’t believe I am using dnsmasq or an isc-dhcp server. I believe we are using a Windows Server 2012 R2 for DHCP. I would have to ask my boss about that to be sure.

Although I am confused, I thought FOG wasn’t setup to handle UEFI originally. I thought you would have to change it from legacy BIOS to UEFI to allow for ipxe.efi. I mean none of our ByteSpeed’s would connect to FOG unless we configured the BIOS for each machine CSM for legacy BIOS.

So should I try updating FOG and the kernel first before changing anything?

@sebastian-roth

Hello Sebastian-roth,

So to configure with snponly.efi how do I do that? I haven’t found any instruction on how to do so.

Secondly, you mentioned to do a firmware upgrade to the latest version. Are you referring to FOG or the Lenovo’s? I believe the Lenovo’s M75s BIOS are fully updated.

Hello,

I have another question about some new computers we got. We got 6 new Lenovo M75s computers that are UEFI only. When I try to PXE boot, this is what happens.

After this, the machine proceeds to boot up to the Windows 10 installation we put via a USB. All of my other machines when we do PXE boot get to this screen by FOG for image deployment.

So I believe the reason why these Lenovo’s are not getting to this screen is because all my current ByteSpeed’s can be chosen to be set to UEFI or BIOS for PXE boot. We set the ByteSpeed’s all for legacy BIOS and they can get to FOG project screen with no issue and deploy my images to them. Although since these Lenovo’s do not have this option, my FOG server must be configured for legacy BIOS only. Someone please let me know if I am correct about this assumption.

In case anyone was wondering what I have done to the Lenovo’s, I have disabled secure boot, disabled IPv6 network stack, and set the primary boot sequence with PXE.

One last thing to mention is that my FOG server is out of date. Would a simple update fix this issue? Perhaps changing the kernel?

If updating or kernel change won’t work, then I believe my options are:

1. Since it is only 6 computers just use Windows USB installation.
2. Change all ByteSpeed computers from legacy BIOS to UEFI and configure TFTP for snponly.efi or ipxe.efi
3. Configure TFTP for BIOS and UEFI Co-Existence

Any help you can give is greatly appreciated. I am still new at this and still learning. If am wrong about anything or my assumptions, please let me know.

Thank you
Bluedude84

@Sebastian-Roth Hello, sorry it took so long, but I finally got my hands on a USB/SATA adapter. I was able to use disk management to have a look at the drives.

This is what I got as soon as I launched disk management.

I changed it to make it online, and then it changed to this.
Image Continued

The good news is that out of the 5 drives, I was able to use diskpart command via the command line and clean 4 of the hard drives. Once I cleaned those 4 hard drives, I was able to reconnect them and access the BIOS and get to FOG to deploy an image. I think I will just toss the 5th hard drive. Its pretty old and it is only a 80GB drive. Not sure if these photos will give you any information as to why this happened or what I did to cause this.

@Sebastian-Roth Figures I would screw up something this bad. I don’t have time today to try that. I do have a Lenovo desktop, in the building somewhere. Once I find it, I’ll try connecting it to that and see if it is able to boot.

I tried to hot swap in a bad image hard drive. I thought it read you could do that with SATA connections. I kept good drive connected initially, and booted into Windows 10. Once I was in, I reconnected the bad image drive and opened disk management. Unfortunately, it would only recognize the hard drive with the good image. It did not recognize the bad image hard drive. I do not have a USB/SATA adapter,. My buddy may have one. I am going to ask him if he does, if I could borrow it. Although, its going to be a few days before I can do any of this.

@Sebastian-Roth I scheduled the debug and plugged in one of the four hard drives with the bad image. PXE is enabled and first priority to boot and this is all it is doing.

F2 or DEL does nothing and will not let me continue any further.

@Sebastian-Roth So I am not sure what you are saying in that first paragraph. Are you saying I shouldn’t capture with resizable because FOG can’t resize it anyway? What should then I set the Image Type too then?

Also, I stated that the pics yesterday is from a working image. Yesterday, I over wrote the bad image in FOG with this good capture. Although, the bad image is still on these 4 nonfunctioning hard drives. Whenever I have one of these four hard drives plugged in, even with a another good hard drive with a good image and with PXE enabled with PXE set to boot first, the machine is unable to do anything.

I will try and schedule a debug, but I doubt it is going to work. I will let you know if it does.

@Tom-Elliott
Hello Tom-Elliott,

I was able to get access to one of the user accounts. Here is the info you requested.
ls -l /var/www

ls -l /var/www/html

@Sebastian-Roth
So I was able to figure out the password to one of the user accounts on Ubuntu. I was also able to get XRDP installed and working. I was able to finally get the information you asked for. Although the bad image that I had, I copied over with a capture that is working. I don’t know if this is going to help anymore, but here is the info you requested.
d1.partitions

d1.minimum.partitions

d1.fixed_size_partitions