@sebastian-roth The issue was changing the LAN boot selection from UEFI to CSM Boot. Thanks all!

@george1421 said in What is the PROPER Process for this?:

All of the travel laptops are the same model (we bought them at the same time). I’ve never heard of the unnattendad.xml thing? is there more information on that somewhere for fog?

@Sebastian-Roth No, I didn’t remove it from the domain but could.

I’ve installed the fog-client on PC’s before but don’t see it do anything other than report the last time the computer was ‘online/pingable’ in the fog dashboard.

What’s the process to use the fog-client?

1)install fog-client on the master
2)remove from domain
3)set domain join in the fog dashboard for that image?
4)image a new laptop?

It should, in theory, join the domain then correct?

I have 24 laptops that travel for the company I work for. We host educational meetings around the US, and they all get shipped out roughly 2 times a month.

My old process just grabbed a laptop, run updates, then run a fog capture on it (NOTHING ELSE. No special commands run to ‘clean up’ the image or anything).

Am I doing this right? Should I be running Sysprep after every time? I Don’t want to have to go through the whole setup process of a laptop every time I do windows updates for 24 of them.

I’ve also noticed, after deploying an image to the laptops, the Office 2016 install needs to be ‘activated’ and the computer is technically in the domain and can access some network resources like network drives, but if you try to login with a domain account it says “The security database on the server does not have a computer account for this workstation trust relationship”.

What am I doing wrong? Surely there has to be the ‘right’ way to do imaging so I wouldn’t have to go through all these steps EVERY time I image a computer.

This image should show I have fog installed, and am in the fog folder in x86, however still now fog.log after starting the service.

location was in c:/Program Files (x86)/Fog/ but there is no fog.log file there. I’ve searched and searched even went into each individual folder with the language hoping it was buried.

Yes, i have the fog service installed on the image.

I looked on the computer i imaged, and I have no fog.log in the C drive.

FOG Version : 1.5.2

Windows 10 64bit pro

I cant get domain join working on any of my deployments. Ive went into the fog settings, set up the right OU, username/password combo, and even selected when deploying the image to join AD after successful deployment, but the computer doesn’t actually JOIN the domain.

Any help is appreciated.

I have a new install of FOG, and everything was working. I was able to capture an image, but now when I try to capture another, both on two separate computers/types.

This screenshot is when it is failing :

@sebastian-roth The issue was changing the LAN boot selection from UEFI to CSM Boot. Thanks all!