@walyson621 Please post the contents of the text files d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions of this image here in the forums. Find those files in the /images/OPTIPLEX3000/ directory on your FOG server.

I would like to update this thread, we found that the problem was with the DHCP Lease for some reason. We cleared the lease and now it is booting normally. It was very odd that this was an issue because we pulled another of the same machine from the box and it worked without any problems.

@JJ-Fullmer Just stumbled upon this again. Added a hint in the web UI (ref).

You might also add this to the documentation. Although when I looked into adding the hint to working-1.6 as well I saw that with the new web UI you actually have a checkbox for file deletion on deletemulti as well as single delete. So it’s only for FOG 1.5.x.

@joez455 normally yes, but I’m not going to guarantee it as I can’t know every case. I would highly suggest backing up the images folder, the /opt/fog folder, and a backup of the current database. Just to be safe of course.

@george1421
Thank you George, I’ll give it a go! Appreciate it.

@george1421 : Thank a lot for your fast && accurate answer. Have a nice day !

Did you ever find a fix for this issue? I have the same problem. I have a work around but its not really a fix for sure. If I use an external usb-c nic dongle it images fine, but this for sure is not a long term solution. If you ever figured this out i would be glad to hear how.

Thanks

@tom-elliott Excellent, thanks for your time.

@BrentC Probably the HDD you captured from is larger than the SSD you want to deploy to, right? What size are they each?

Please post the contents of the text file /images/LeahHolland/d1.minimum.partitions here in the forums. It contains the partition layout and we’ll surely figure out why it doesn’t deploy.

@bmick10 said in Renaming Windows10 Device with Secure Boot:

So I can ping from Windows computer but not our fog server.

One final check is to use the windows computer to get the IP address of that registered computer. Ensure you can ping the IP address of that computer. If you can then the issue is…

You need to setup DNS resolution on the FOG server so that it resolves the computer name correctly. You do this through the /etc/resolve.conf file OR for the linux distro that you use, if you have the gui for the FOG server linux OS, then use the network manager to set the DNS server to the IP address of your Windows DNS server (typically your AD DC). Make sure the search domain is set to your AD domain (i.e. ad.bigco.com)

As far as Fog changing settings for UEFI may I ask how that could happen

FOG will not do that. It doesn’t touch UEFI settings. I’m just saying that is only one of the few ways to upset secure boot, well actually bit locker. Secure boot only deals with the OS starting up.

@tom-elliott Awesome, thanks very much for your help.

@scott-boucher what is and version? If it’s Ubuntu 16.04 I would suggest upgrading to a more recent version and trying again. Ubuntu 16.04 is out of support and likely is stuck using repo that is no longer supported on it.

@tom-elliott hard to say. Most PCs are left running so I wouldn’t know if they were woken up or not. I can try to find a couple more to monitor.

@sebastian-roth This works great, replaced xinit.xz and all successful now. Thanks!

@sebastian-roth I wanted to try and keep our exisitng pxeboot menu with an option in that menu to load the fog pxe menu.

i’ve reaslied that would limit so many features of automation that it would make more sense to just add any menu items we already have from our exiting pxe menu and add them to the fog one.

@sebastian-roth Well I ran into a snag by not being able to multicast to deploy images. So for now I have left the Fog server as the master node. If I run into a space issue further down the road I can always move images over to the NAS and vice-versa. Space was really the only reason for using the NAS.

There’s also this article:
https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

i actually think i’ve found the steps

Part 3 FOG Storage Node Configuration](https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node/21?page=2)

@sebastian-roth
@george1421

So updating firmware fixed the issue.

I’m not sure why but some middle firmware versions weren’t working. The 790s with A11 worked fine, but A18 produced the error, and then when they updated to A21 it worked.

We can mark this as solved. I appreciate everyone helping.

@mesaman0182 Ubuntu server is preferred. Stick to 20.04 for now. FOG has not been tested with 21.04. I hear there are a few bugs since Ubuntu changed quite a bit between the two versions.

So 10.118.0.59/16 is valid for your network?

It would be interesting to see if arp -a would return any hear arp requests. These settings look good, it should be working.