• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. diogo.seabra
    3. Topics
    D
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 7
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by diogo.seabra

    • D

      Unsolved Dnsmasq on your FOG server

      FOG Problems
      • • • diogo.seabra
      8
      0
      Votes
      8
      Posts
      1.7k
      Views

      george1421G

      @diogo-seabra As for the picture, I think we need to clearly define your network.

      dnsmasq works by using broadcast messages. So that means dnsmasq will only work on the local subnet. If your pxe booting computers are on a different subnet then you will need to add the fog server’s IP address to the list in the dhcp relay service on your router.

      Also if you have dhcp snooping enabled on your network switches, that may also cause dnsmasq to not respond properly.

    • D

      Inject drivers via Fog

      Tutorials
      • • • diogo.seabra
      5
      0
      Votes
      5
      Posts
      739
      Views

      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

    • 1 / 1