Categories

• Technical Help

  Get help with your FOG system.

  FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems
  12k Topics

  114k Posts

  T

  @plegrand 1.5.10 is very old, run on stable branch or working-1.6 you will be fine.

• Announcements

  Get the latest news on what's happening.

  Security Advisories
  184 Topics

  825 Posts

  A

  @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

• General Topics

  View tutorials or talk about FOG in general.

  General Tutorials
  2k Topics

  19k Posts

  D

  @george1421 Thanks for your help.

  I solve the problem with this AutoUnatted.xml

  <?xml version=“1.0” encoding=“utf-8”?>
  <unattend xmlns=“urn:schemas-microsoft-com:unattend”>
  <!-- Bypass OOBE -->
  <settings pass=“oobeSystem”>
  <component name=“Microsoft-Windows-Shell-Setup” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
  <OOBE>
  <HideEULAPage>true</HideEULAPage>
  <HideLocalAccountScreen>true</HideLocalAccountScreen>
  <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
  <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
  <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
  <ProtectYourPC>3</ProtectYourPC>
  <SkipUserOOBE>true</SkipUserOOBE>
  <SkipMachineOOBE>true</SkipMachineOOBE>
  <UnattendEnableRetailDemo>false</UnattendEnableRetailDemo>
  <NetworkLocation>Other</NetworkLocation>
  </OOBE>
  </component>
  <component name=“Microsoft-Windows-International-Core” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
  <SystemLocale>pt-PT</SystemLocale>
  <UILanguage>pt-PT</UILanguage>
  <UserLocale>pt-PT</UserLocale>
  <InputLocale>0816:00000816</InputLocale>
  </component>
  </settings>

  <!-- Run SetupComplete.cmd via PostOOBE --> <settings pass="specialize"> <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Order>1</Order> <Path>reg add "HKEY_LOCAL_MACHINE\SYSTEM\Setup\FirstBoot\PostOobe" /v "00" /t REG_SZ /d "cmd /c C:\Windows\Setup\Scripts\SetupComplete.cmd &amp; exit /b 0" /f</Path> </RunSynchronousCommand> </RunSynchronous> </component> </settings>

  </unattend>

  The AutoUnatted.xml will call the the script C:\Windows\Setup\Scripts\SetupComplete.cmd

  I make the sysprep with AutoUnatted.xml

• Developers

  Report bugs, request features, or get the latest progress.

  General Feature Request Bug Reports
  2k Topics

  21k Posts

  F

  I’m having the exact same behavior.
  Was working on the 27, 28 and 29.

  Stopped working start of this week (2 september)
  Added 3 storage nodes in between.
  1a07ba58-be68-4007-a60c-5532e6c42e41-image.png