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

  C

  Hi every one.

  I’ve got the same problem with Dell Pro 16 PC16250.

  The PXE boot stuck at : EFI Stub: Loaded initrd from Linux_EFI_InitRD_Media_Guid device path

  I’ve allready had this message with other models : Dell Latitude 3550 et des Dell Optiplex 3080 SFF, but boot keep going and the deployment start.

  And not with Dell Pro 16 PC16250

  My server (debian 12.12) is up to date.
  Fog is also up to date 1.5.10.1698
  The kernel too : bzImage version : 6.12.35

  I tried to change the DHCP (Debian too) file with snponly.efi : stuck too

  I’ve tried older kernels : 6.1.89, 6.6.9, 6.6.49 : stuck too

  In the BIOS, Secure boot and TPM are disabled

  I’ve tried to add kernel arguments : acpi=off noapic nolapic pci=nomsi nomodeset intel_iommu=off iommu=off

  But no success

• 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 This is probably true. We learned about a security issue and worked to solve that problem. I’m seeing what i can do to recover this feature, but it may take some time.

  This feature is working on the working-1.6 branch if you’re willing to be a little on the bleeding edge (testing would be good for this branch. I’m pretty sure it’ll work for 99% of your needs without much issue, but without enough testers testing this, it’s a slow process.)

  My testing shows with the security issue that was fixed, I’m still able to see the log viewer.

  It’s difficult to simulate between the different 1.5.x and 1.6 for me.

  I’m seeing if I can build a VM that would do the 1.5 side of things, but I’m not putting all my focus into that version of things any more. We are close to 1.6 finally, just need more people letting us know of anything they see.

  If you’re unable to test that I understand, and I’m going to try to fix what I can if I can figure it out, but it’s not a top priority for me at least.

  This feature is useful, but not a make or break thing for FOG’s operationality in my eyes. I hope that makes sense.