Topics created by rtarr

@TaTa Glad that worked for you! There hasn’t been any update to the github thread since 1/31, but I was able to compile binaries today using the original buildipxe.sh script without the additional line without error.

@rtarr said in 2 NIC Host: Set 1 NIC to Remote Management/Replication and 2 NIC to Imaging:

I am using two NICs because I want all the imaging to happen on a segregated network and any repo updates or image replication to happen over the LAN NIC. This prevents imaging from happening over our firewall tunnels.

Having a second nic and dedicated imaging network may not be necessary to avoid imaging over the vpn tunnel.

(connect both master node and storage node to your business network)

At the remote site set dhcp options 66 to local storage node IP address and dhcp option 67 to ipxe.efi. -OR- use either dhcp profiles or dnsmasq running on the remote storage node to point to the remote storage node for pxe booting. This will keep from downloading the ipxe boot loader over the vpn tunnel.

At HQ again setup dhcp option 66 to master node ip address and dhcp option 67 to ipxe.efi. On the master node installed the Location plugin. Create your two different locations and assign the storage nodes to those locations.

Now assign the target computers to the proper location, either via the web ui or when you do a full registration.

So at this point you have a local and remote location defined. You have the master node assigned to the local location, the remote storage node to the remote location. You now have the target computers assigned to the proper location.

So now you pxe boot a computer at the remote location. I will pull ipxe.efi from the storage node. The target computer will then make a http call to the master node to find out where its storage node is located. Then if the storage node is local to the pxe booting computer it will image all at the remote site. There will be small update http calls to the master node to let the FOG server where it is in the imaging process.

The only thing you can’t do in this setup is multicast imaging, that can only happen from the master node in any storage group.

@rtarr said in Boot Loop after Sysprepping a Golden Image VM:

It then boots to the login page for the local admin where install packages are located on the desktop.

I’m glad you have it worked out.

To extend what you have done just a bit more (if needed). Look at my unattend.xml script there are sections where to add local keyboard support (if you are not in the US) as well as it should have autoadmin login with a login count number that will cancel the auto admin login after X number of logins. If not you can add it to your unattend.xml file. That in conjunction with the run firstlogincommands where you can install any applications in an unattended manner as the local admin. The last firstlogincommand should be shutdown -r -t 0 that will reboot the computer leaving it at the login window.

I just looked and my posted unattend.xml file in the link does not included this section. I must have removed that before posting. But above is enough info for you to google it.