@RLane simple add this section into unattend.xml

<FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>REG ADD &quot;HKLM\System\CurrentControlSet\Control\Network\NewNetworkWindowOff&quot; /F</CommandLine> <Order>1</Order> <RequiresUserInput>false</RequiresUserInput> </SynchronousCommand> </FirstLogonCommands>

it solve my issue

@Tom-Elliott another FOG parameter. Not very clean but typically FOG will be installed in a unique local and not traverse across.

Possibly also something in the language file to control what the system "thinks’ the system partition is called?

its okay thanks for your help

0_1500471038531_091f047d-6905-4f8b-81ae-16f6e29ee5ec-image.png

ok thanks for reply i will upgrade my fog version

i like the idea of using /quit instead of /shutdown and getting sure the shutdown is a real one with shutdown -s -t 0 -f 😉
I never used the chkdsk portion but it would not do any harm 😄 but wasting time :p… well i do a defrag instead.

If there is still a hdd i think it would make sense to defrag before you write cereal to it 😉

If you repull and install the latest version of the working-1.3.4 branch you should have the error thrown corrected for now.

Thanks for reporting.

@Wayne-Workman The info he is showing is from the “readme.md” file.

While we are not in “stable” form yet, the readme’s are updated so when I pull in the working-1.3.4 into the master branch I don’t have to remember to edit these files.

@laintimes I was short with my response, I do apologize. But you described that your problem is hosts are waiting in the queue for imaging (in line for 5, in line for 10, … ). This only happens when there are no more available slots. Which is why I asked you to look into Web Interface -> Task Management and see if there are any tasks in there that may be stuck.

i dont know how to update topic status to solved