Testers

@jape said in FOG unable to PXE boot beyond the VLAN/subnet that the server is on:

So perhaps that will complicate things

Yes it will. dhcp works off from broadcast messages, so it communicates by sending out broadcast messages on the same vlan/network. Having 2 dhcp servers on the same network segment will cause you grief.

Fog can integrate into an environment where there is an existing dhcp server no problem. FOG’s internal dhcp server would be typically used if you were to setup an isolated imaging network where there was no device except the pxe booting computer and the fog server.

So lets start out with this, what device is your preexisting dhcp server?

@jape Just to be clear you did not have a preexisting dhcp server on your site until fog was installed? Not even a router or other device that acted in place of a traditional dhcp server? its a bit strange (I feel) that you would have vlans/subnets without an existing dhcp server.

If this is true, no worries its pretty simple to get the remote subnets to work.

@geekyjm Are you using a postdownload script to dynamically update your unattend.xml file so sysprep will join the domain with the settings given by fog?
Or are you using the fog service to join the domain during the oobe firstlogon phase, or after that?

@geekyjm If I remember correctly the certificate is in /opt/fog/ssl ( I think ) but it is in /opt/fog directory or below. be sure to rename the original certificate on the new fog server before you copy over the old certificate. Once copied over reboot the fog server computer.

@geekyjm said in postdownload script:

Is there a new postdownload script I could download and try?

First let me say that post download scripts have nothing to do with Windows or connecting to AD. Your issues are probably not the root cause.

Lets assume you have the FOG client connect the target computer to AD (there are other ways to got about it, but most use the fog client) and you have just changed fog servers.

My bet is that the fog client can no longer talk to the new FOG server, and hence not get the instructions to connect to AD.

When the fog client is installed (like on the precaptured golden image), it tattoos itself to the fog server’s certificate. That certificate is unique to each install of FOG. My bet is that you didn’t copy over the certificate from the old fog server to the new fog server. So the clients are rejecting the new FOG server because the certificates don’t match.

@danibashkov Try single disk non-resizable. Lets see if you can get it past that error. I did find a reference from 2016 on the forum with the same error.

ref: https://forums.fogproject.org/topic/8602/cannot-upload-neverware-cloudready-chromeos-to-fog-e2fsck-failed-to-check-dev-sda20-shrinkpartition

@lacugo If you switch over to the FOG 1.5.9 dev branch (a.k.a FOG 1.5.9.115) it will install cleanly on Debian 11. But sadly not ubuntu 22.04 or centos 8 where php8 is the default install. AS of now FOG only supports PHP7.x until some code refactoring is done.

@rav ok here is the updated file: https://drive.google.com/file/d/1_pJWzun8R5v-PdMWk0j_l1dt8qEZzpjC/view?usp=sharing

What I did here is I see your fog server is at 192.168.5.234. In the config file I set the next server value to 192.168.5.234 The boot file is set dynamically by the config file. The dhcp range (what the isc dhcp server will hand out) is 192.168.5.10 to 192.168.5.200.

replace the existing config file with this one.

At the fog server’s command prompt (su to root to do this).

Issue these commands.
First to stop and then restart the isc-dhcp server (this will load in the new config file)
systemctl restart isc-dhcp-server

wait about 10 seconds

Now lets get the status of the dhcp server.
systemctl status isc-dhcp-server

Hopefully somewhere in the wall of text it will say running.

Now lets ensure that the dhcp server will startup at boot time.
systemctl enable isc-dhcp-server

@rav OK let me work on the file and get it back to you. The short answer is the network defined in the dhcp server is not the same as your fog server network interface.

@rav The config file you provided is for the dhcp client (app that runs on your computer that contacts the dhcp server). the file we are looking for is this: /etc/dhcp/dhcpd.conf