Categories

• Technical Help

  Get help with your FOG system.

  FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems
  12.3k
  Topics
  113.5k
  Posts

  D

  Hello all,
  I followed the configuration: server to make Dnsmasq my FOG server, but when I go to test the results we are unable to boot and the error PXE-E16 no valid offer received appears.

  Our ltsp.conf file:

  Don’t function as a DNS server:

  port=0

  Log lots of extra information about DHCP transactions.

  log-dhcp

  Set the root directory for files available via FTP.

  tftp-root=/tftpboot

  The boot filename, Server name, Server Ip Address

  dhcp-boot=undionly.kpxe,172.22.21.18

  Disable re-use of the DHCP servername and filename fields as extra option space. That’s to avoid confusing some old or broken DHCP clients.

  dhcp-no-override

  inspect the vendor class string and match the text to set the tag

  dhcp-vendorclass=BIOS,PXEClient:Arch:00000
  dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
  dhcp-vendorclass=UEFI,PXEClient:Arch:00007
  dhcp-vendorclass=UEFI64,PXEClient:Arch:00009

  Set the boot file name based on the matching tag from the vendor class (above)

  dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,172.22.21.18
  dhcp-boot=net:UEFI,ipxe.efi,172.22.21.18
  dhcp-boot=net:UEFI64,ipxe.efi,172.22.21.18

  PXE menu. The first part is the text displayed to the user. The second is the timeout, in seconds.

  pxe-prompt=“Booting FOG Client”, 1

  The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86, Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI This option is first and will be the default if there is no input from the user.

  pxe-service=X86PC, “Boot to FOG”, undionly.kpxe
  pxe-service=X86-64_EFI, “Boot to FOG UEFI”, ipxe.efi
  pxe-service=BC_EFI, “Boot to FOG UEFI PXE-BC”, ipxe.efi

  Subnets=

  dhcp-range=<fog_server_IP>,proxy
  dhcp-range=192.168.10.0,proxy,255.255.255.0
  dhcp-range=172.30.20.0,proxy,255.255.255.0

  The service runining ok and in windows dhcp i have option 66 to point to FOG server

  Any help?

• 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
  2.5k
  Topics
  18.5k
  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
  2.3k
  Topics
  20.9k
  Posts

  T

  @Fog_Newb probaly just typoed it and i went with it too lol.