@Sebastian-Roth is there a workaround to get devices to boot into the FOG environment, if they wont network boot?

They are the HP Stream 11 Pro G3 EE Models, we currently use it for the G2 and G3 models, I cannot get the G4 or G5 models to network boot into FOG (would love help with a solution, so we can ditch sysprep), we do have to use USB ethernet dongles as these laptops do not have Ethernet ports

So in my environment we all run off laptops, but when I image devices with FOG it cannot differentiate the computers and saves the computer name to the specific Ethernet port it was imaged with.

So essentially when I image one computer, and then try to image a second computer and go to network boot, it will read computer 2 as computer 1 in the inventory.

I fixed the IP address by reinstalling the client on the computer, but the snap in’s still don’t show up in the fog log, and they just stay in the que of active tasks and never get deployed.

I am trying to install Snap ins to my clients and after looking at the log files it looks like they are pointed to the wrong IP Address, but I cant find anywhere in the settings to allow me to make this change from 10.168.60.2 to 10.168.60.3, would this be preventing all my snap ins from installing and just showing up as Queued?

--------------------------------Authentication--------------------------------

7/30/2019 9:40 AM Client-Info Version: 0.11.16
7/30/2019 9:40 AM Client-Info OS: Windows
7/30/2019 9:40 AM Middleware::Authentication Waiting for authentication timeout to pass
7/30/2019 9:40 AM Middleware::Communication Download: http://10.168.60.2/fog/management/other/ssl/srvpublic.crt
7/30/2019 9:40 AM Middleware::Communication ERROR: Could not download file
7/30/2019 9:40 AM Middleware::Communication ERROR: Unable to connect to the remote server
7/30/2019 9:40 AM Middleware::Authentication ERROR: Could not authenticate
7/30/2019 9:40 AM Middleware::Authentication ERROR: The system cannot find the file specified.