@mapaga said in Windows 7 Deployment Error:

Just for curiosity, why is it important to caputre all partitions?.

Because only with all partitions it will also capture and deploy the partition table. If you set this to a single partition, it will only capture/deploy this partition and won’t touch the partition layout. This is ok if you have the correct layout on the destination system already but will fail otherwise.

@cammykool said in Unable to restore GPT partition tables on one image:

this is the stuff that broke after that init move.

That has nothing to do with the init change. The version information in the FOG web UI is pulled from the fogproject.org server and I would guess either there was a connection issue or your network admin restricted access to this URL.

@tom-elliott I tested on another computer and its working.

on this particular pc its not working. I will try and uninstall fog client from the pc and reinstall it again and will see if it works.

IF it still doesnt work will try to remove from fog server and re add

@sebastian-roth Thank you ! That does it perfectly. I didn’t know that command. Have a good day !

@george1421 I ended up looking for FOG 1.4.4 kernel update issues and found the permissions missing issue and followed what the guy did there. I’m not getting an error anymore.

@fargat There is far too little information to accurately assist you.

Here’s the details we have, so far:
You have FOG Server running on Ubuntu 20.04.
You have Sophos Firewall as DHCP server.
You have tried DNSmasq but it did not work.
You have tried FOG using a Lenovo laptop.
Based on the picture, the laptop is attempting to boot using UEFI stack.

That’s all we have.

We would need:
What version of FOG are you running?
What configuration did you use for DNSmasq?
What DHCP options 66/67 are defined on your Sophos Firewall DHCP Server?
What model of Lenovo laptop are you using? (There are many different models.)
Have you disabled Secure Boot?

There’s most likely going to be many more questions, but a picture and “Firewall is …” doesn’t really help us. Neither are any of the follow up responses you’ve given.

Here’s some resources:
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence
https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_with_dnsmasq

As @EduardoTSeoane has told you, based on the picture your machine is using UEFI stack for booting, but it’s calling the legacy boot file (undionly.kpxe should be ipxe.efi).

Hi

what is solution of the problem

@yeet said in Error trying to restore GPT Partition tables (restorepartitionTablesAndBootLoaders) on different sized drives:

Is this due to the drive being 6gb smaller than the one the image was built on?

Yes, if your Windows 10 is 2004 or a newer build and your are using FOG 1.5.9 or older. That’s because with those versions of Win 10 they put a new recovery partition at the end of the disk and we have updated inits that can handle this in the latest dev-branch version.

Is there a setting I’m missing? I have the image set to single disk, resizable.

That setting is correct but as mentioned above you need the latest inits. Manually download inits (64 bit and 32 bit) and put into /var/www/html/fog/service/ipxe/ on your FOG server. Rename the existing files as backup instead of overwriting!

Now you need to re-capture the image. Maybe even create a new image definition for this to not overwrite your existing image files as a backup. Assign the new image to the host you capture from and schedule the task.

This image captured with the new inits should deploy to devices with smaller disk fine. If not, let us know here.

@george1421 Thanks. My gut feeling was that there were two partitions, one with Windows 7 and the other Windows 10. Just to be on the safe side we just put a whole new image on the new computer and copied everything over and then took a new image of that drive. Thank you for getting back to me.

@brico said in Two HDD - 3 OS Win 10 - Multiboot:

Then we’ll restore on the first disk ! And destroy /dev/sda !

YES! You really need to be careful when deploying. While single partitions are even more tricky you have to be alert when deploying anyhow. Deploy will overwrite whatever is on disk. Thinks can go wrong if you don’t take care of what exactly you do.

So, we’ll try to create 2 hosts (for the same PC)

As you have seen, this is not possible. The basic concepts of FOG don’t allow for more than one host object in the database with the same MAC address.

@greg-plamondon Rejoice too early! Tried to replicate the issue with SubnetGroup plugin installed at first because from the code it looked like this could be it. But exit type settings stayed. Also made the iPXE hidden but same result. Then installed HostStatus plugin but again exit type settings don’t get reset.

I am wondering if it’s possible this was due to an issue in the database that was cleaned out by removing those plugins?!

I see you have used the FOG 1.6.0-alpha version as well. Is this on a different server or do you switch between 1.5.x and 1.6.x on the same server?

@Greg-Plamondon Oh yeah, good point! Block size can be an issue when you connect across routers with different MTU configured.

@george1421 Thank you for your reply, an update caused the fog server to no longer be able to run the mysql service. It has been fixed! Thank the lord lol!

@pep said in Using a separate NIC for multicast:

web = http: //192.168.1.100/fog/ ftp = 192.168.1.100 storage = 192.168.1.100: / images / dev / storageip = 192.168.1.100

Thanks! That works. I can leave my storage settings as default and Multticast will use eno2, then for anything not multicast I can set the correct parameters for eno3.

Just a note that for deployment the storage variable needs to be ip.address:/images/ (without the dev/)

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!

*UPDATE: It is not the FOG server as I was able to boot an OLDER (Legacy) Lenovo to the FOG Main menu screen. SO this appears to be an issue with the newer BIOS/Secure boot or even possibly a NIC incompatibility. I will search elsewhere.

@Tom-Elliott @Wayne-Workman In this case here the installer error was actually helpful to prevent from later issues with two IPs on an interface that were not intentionally configured.

I don’t think it’s worth the effort changing the scripts but feel free to go ahead.

@mesaman0182 From the picture we see that you are using a very old version of FOG. Is this a fresh install? Why did you choose to use that?

Now to answer your question: The one important field you need to set is Host Image. But as we see in the picture you don’t have an image defined yet. So go to the images in the FOG web UI and create one. All the other fields in the host settings can be left as default or empty for now.

@enrico-fazio This is a known issue with Ubuntu 21.04. You need to use the latest dev-branch version with that.