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

  B

  Slight correction, it seems the file associations are correct until we run our post imaging snapin. Then once we boot the computer again, they have reverted.

  All the snapin does is set the wallpaper, adds a few WIFI networks from XML files, and installs Splashtop.

• 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

  T

  @Clebboii Figured it out and should be workign without breaking security, in dev-branch. Please give it a shot or as I asked earlier, happy to have another tester on 1.6 branch 🙂