@chenguy I guess I would have to ask why are you not using an unattend.xml file?

At my company we don’t use the FOG client to manage the computers post imaging so that means FOG is not renaming the computer, connecting it to AD, or placing it in the correct OU. My environment is a bit complex so the hostname and AD OU location is calculated during imaging with the results updated in the unattend.xml file before FOG releases the computer and the target computer is rebooted. This is done before OOBE/WinSetup starts for the first time. Using this approach you can use the load and go method of image deployment where you don’t register the computer with FOG and FOG will forget about the computer once imaged. Understand using this method without the FOG client there is no post imaging management included including snapin deployment. We have other tools for that.

Using the unattend.xml file alone we can select the desired keyboard layout, computer name, connect to AD, etc.