• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Windows Boot Manager boot option disappears after Image

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    4
    38
    5.8k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      Sebastian Roth Moderator
      last edited by Sebastian Roth

      @JJ-Fullmer Good questions. Maybe I am on the wrong track with my thinking it’s simply the UEFI boot entries missing.

      @ConJon Can you please help us gather some more information on this? I figured that we have most of the tools in the FOS system already. Please schedule a debug capture task for your master. Start the client and when you get to the shell run passwd to set a root password and ip a s to get the IP information. Then use putty or plain ssh command from another machine to remotely connect to the client in debug mode so you can copy&paste the output of the following commands:

      efibootmgr
      efibootmgr -v
      efivar -l
      halt
      

      Make sure you copy all the information from each of the three commands (before shutting it down via halt) and post them in the here in the forum.

      Then cancel that debug task and schedule a new debug deploy task on one of your destination machines (best if you have one that has not been messed with at all and maybe another one that you have already deployed to). Boot up, set password, connect via SSH, run the commands and post output here.

      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

      C 1 Reply Last reply Reply Quote 0
      • C
        ConJon @JJ Fullmer
        last edited by

        @JJ-Fullmer
        I am all ears. 🙂
        Yep we use sysprep
        It happens right after the fog imaging completes
        We have tried both a vm and physical. Happens on both. (We prefer a physical Dell Lattitude 7490)
        UEFI

        JJ FullmerJ 1 Reply Last reply Reply Quote 0
        • C
          ConJon @Sebastian Roth
          last edited by Sebastian Roth

          @Sebastian-Roth

          [root@localhost ~]# ip a s
          1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
              link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
              inet 127.0.0.1/8 scope host lo
                 valid_lft forever preferred_lft forever
              inet6 ::1/128 scope host 
                 valid_lft forever preferred_lft forever
          2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
              link/ether 54:bf:64:6f:e5:e2 brd ff:ff:ff:ff:ff:ff
              inet 10.1.4.65/8 brd 10.255.255.255 scope global noprefixroute enp0s31f6
                 valid_lft forever preferred_lft forever
              inet6 fe80::295c:4c7e:648e:be88/64 scope link noprefixroute 
                 valid_lft forever preferred_lft forever
          
          [root@localhost ~]# efibootmgr
          BootCurrent: 0001
          Timeout: 2 seconds
          BootOrder: 0001,0000,0003,0004
          Boot0000* Windows Boot Manager
          Boot0001* CentOS
          Boot0003* Onboard NIC(IPV4)
          Boot0004* Onboard NIC(IPV6)
          
          [root@localhost ~]# efibootmgr -v
          BootCurrent: 0001
          Timeout: 2 seconds
          BootOrder: 0001,0000,0003,0004
          Boot0000* Windows Boot Manager  VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...o................
          Boot0001* CentOS        HD(1,GPT,b8575a92-ec48-4c92-a8dc-98de1280cf59,0x800,0x64000)/File(\EFI\centos\shimx64.efi)
          Boot0003* Onboard NIC(IPV4)     /Pci(0x1f,0x6)/MAC(54bf646fe5e2,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
          Boot0004* Onboard NIC(IPV6)     /Pci(0x1f,0x6)/MAC(54bf646fe5e2,0)/IPv6([::]:<->[::]:,0,0)..BO
          
          [root@localhost ~]# efivar -l
          bash: efivar: command not found
          [root@localhost ~]#
          
          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by Sebastian Roth

            @ConJon said in Windows Boot Manager boot option disappears after Image:

            efivar: command not found

            Well that’s kind of strange. I am sure I had used that command just an hour ago in my test FOS system. Nevermind.

            The output you gave, is that the source master machine? I suppose it is. Please see if you can get me the outputs of a clean destination machine as well…

            In you initial post you said something about “Windows Boot Manager” so I expected you to have Windows installed only. But seems like you have CentOS as well and that is your default boot too. Is that correct? There is nothing wrong about this. I am just learning how to mess with those EFI entries in detail…

            Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

            Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

            C 1 Reply Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by Sebastian Roth

              @ConJon said:

              ... Windows Boot Manager VenHW(...

              That’s interesting, I would have expected to see something similar to HD(1,GPT,...)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI) instead. But hey, I am still a bit new to this.

              Just make sure you tell me which machine you got the results from.

              Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

              Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

              C 1 Reply Last reply Reply Quote 0
              • JJ FullmerJ
                JJ Fullmer Testers @ConJon
                last edited by

                @ConJon Hmmm, do you happen to know how your sysprep unattend is configured as far as boot phases?
                i.e. ours goes like this (super simplified summary)

                Capture:

                Install Windows -> ctrl+shift+f3 to enter audit mode from oobe screen - > add customizations -> Run sysprep /audit /reboot /unattend:unattendfile
                -> sysprep Audit System phase -> sysprep Audit User phase -> sysprep Generalize phase -> Shutdown -> Upload to fog

                Deploy :

                Fog images the machine -> sysprep specialize phase -> sysprep oobe phase -> firstlogoncommands/custom provisioning/snapins etc.

                In our case the uefi boot options/order change I believe either during the specialize or oobe phase when it creates the windows boot manager option. I then have a function in my custom provisioning that makes refind the default boot manager. I might have details on that elsewhere in the forum, can dig them up if you’re interested in using refind as a default boot manager. It’s a fun solution that also makes booting to fog or the uefi firmware settings much easier.

                Granted @Sebastian-Roth’s solution of fixing it within fog is better.

                Have you tried the FogApi powershell module? It's pretty cool IMHO
                https://github.com/darksidemilk/FogApi
                https://fogapi.readthedocs.io/en/latest/
                https://www.powershellgallery.com/packages/FogApi
                https://forums.fogproject.org/topic/12026/powershell-api-module

                C 1 Reply Last reply Reply Quote 0
                • C
                  ConJon @Sebastian Roth
                  last edited by

                  @Sebastian-Roth SO for my inactivity, yes so our Fog Machine is set up on a CentOS desktop. Not a virtual machine itself. Our infrastructure is a little messed up right now so we didn’t want to add more to it. I will grab you a destination device as soon as I can.

                  1 Reply Last reply Reply Quote 0
                  • C
                    ConJon @Sebastian Roth
                    last edited by

                    @Sebastian-Roth I got those results from our FOG Server. The machine that stores and deploys images.

                    1 Reply Last reply Reply Quote 0
                    • C
                      ConJon @JJ Fullmer
                      last edited by Sebastian Roth

                      @JJ-Fullmer
                      I’ll look through this and try to simplify it like you did. But below is the unatended file we are using.
                      Also yes, I would love it if you could find that refind function in the forums. As long as it also has instructions on how to properly set it up.

                      Again, thank you guys for all the help so far!!!

                      <?xml version="1.0" encoding="UTF-8"?>
                      <unattend xmlns="urn:schemas-microsoft-com:unattend">
                      	<settings pass="generalize">
                      		<component name="Microsoft-Windows-Security-SPP" 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">
                      			<SkipRearm>1</SkipRearm>
                      		</component>
                      		<component name="Microsoft-Windows-PnpSysprep" 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">
                      			<PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
                      			<DoNotCleanUpNonPresentDevices>false</DoNotCleanUpNonPresentDevices>
                      		</component>
                      		<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">
                      			<DoNotCleanTaskBar>false</DoNotCleanTaskBar>
                      			<RegisteredOrganization>Tabitha Healthcare</RegisteredOrganization>
                      			<RegisteredOwner>Administrator</RegisteredOwner>
                      		</component>
                      	</settings>
                      	<settings pass="specialize">
                      		<component name="Microsoft-Windows-Security-SPP-UX" 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">
                      			<SkipAutoActivation>true</SkipAutoActivation>
                      		</component>
                      		<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">
                      			<ComputerName>TabithaImagedPC</ComputerName>
                      			<CopyProfile>true</CopyProfile>
                      			<TimeZone>Central Standard Time</TimeZone>
                      			<DoNotCleanTaskBar>false</DoNotCleanTaskBar>
                      			<DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>
                      			<BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled>
                      		</component>
                      		<component name="Microsoft-Windows-IE-InternetExplorer" 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">
                      			<BlockPopups>no</BlockPopups>
                      			<DisableFirstRunWizard>true</DisableFirstRunWizard>
                      			<ShowLeftAddressToolbar>true</ShowLeftAddressToolbar>
                      			<ShowInformationBar>true</ShowInformationBar>
                      			<Window_Title_CN>Tabitha Healthcare</Window_Title_CN>
                      			<Home_Page>https://www.tabitha.org</Home_Page>
                      		</component>
                      		<component name="Microsoft-Windows-UnattendedJoin" 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">
                      			<Identification>
                      				<JoinWorkgroup>WORKGROUP</JoinWorkgroup>
                      			</Identification>
                      		</component>
                      		<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>net user Administrator /active:yes</Path>
                      					<WillReboot>Never</WillReboot>
                      				</RunSynchronousCommand>
                      			</RunSynchronous>
                      		</component>
                      	</settings>
                      	<settings pass="oobeSystem">
                      		<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">
                      			<InputLocale>en-US</InputLocale>
                      			<SystemLocale>en-US</SystemLocale>
                      			<UserLocale>en-US</UserLocale>
                      			<UILanguage>en-US</UILanguage>
                      			<UILanguageFallback>en-US</UILanguageFallback>
                      		</component>
                      		<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">
                      			<AutoLogon>
                      				<Password>
                      					<Value>1234T@b</Value>
                      					<PlainText>true</PlainText>
                      				</Password>
                      				<LogonCount>3</LogonCount>
                      				<Enabled>true</Enabled>
                      				<Username>Administrator</Username>
                      			</AutoLogon>
                      			<FirstLogonCommands>
                      				<SynchronousCommand wcm:action="add">
                      					<Description>Windows License Key</Description>
                      					<Order>1</Order>
                      					<CommandLine>cscript %SystemRoot%\system32\slmgr.vbs /ipk X2KCV-NYKXG-JGDT3-TDJHK-WTYQB</CommandLine>
                      					<RequiresUserInput>false</RequiresUserInput>
                      				</SynchronousCommand>
                      				<SynchronousCommand wcm:action="add">
                      					<Description>Activate Windows</Description>
                      					<Order>2</Order>
                      					<CommandLine>cscript %SystemRoot%\system32\slmgr.vbs /ato</CommandLine>
                      					<RequiresUserInput>false</RequiresUserInput>
                      				</SynchronousCommand>
                      				<SynchronousCommand wcm:action="add">
                      					<Description>Disable Consumer Features</Description>
                      					<Order>3</Order>
                      					<CommandLine>reg add HKLM\Software\Policies\Microsoft\Windows\CloudContent /v DisableWindowsConsumerFeatures /t REG_DWORD /d 1 /f</CommandLine>
                      					<RequiresUserInput>false</RequiresUserInput>
                      				</SynchronousCommand>
                      				<SynchronousCommand wcm:action="add">
                      					<Description>Control Panel Icon Size</Description>
                      					<Order>4</Order>
                      					<CommandLine>reg add "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel" /v AllItemsIconView /t REG_DWORD /d 1 /f</CommandLine>
                      					<RequiresUserInput>false</RequiresUserInput>
                      				</SynchronousCommand>
                      				<SynchronousCommand wcm:action="add">
                      					<Description>Control Panel View</Description>
                      					<Order>5</Order>
                      					<CommandLine>reg add "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel" /v StartupPage /t REG_DWORD /d 0 /f</CommandLine>
                      					<RequiresUserInput>false</RequiresUserInput>
                      				</SynchronousCommand>
                      				<SynchronousCommand wcm:action="add">
                      					<Description>Control Panel View</Description>
                      					<Order>6</Order>
                      					<CommandLine>Netsh WLAN add profile filename="C:/Wi-Fi-TAB-Corp.xml"</CommandLine>
                      					<RequiresUserInput>false</RequiresUserInput>
                      				</SynchronousCommand>
                      				<SynchronousCommand wcm:action="add">
                      					<Description>Domain and Name</Description>
                      					<Order>7</Order>
                      					<CommandLine>powershell -ExecutionPolicy ByPass -noexit -File C:\EXECUTE2.ps1</CommandLine>
                      					<RequiresUserInput>true</RequiresUserInput>
                      				</SynchronousCommand>
                      			</FirstLogonCommands>
                      			<OOBE>
                      				<HideEULAPage>true</HideEULAPage>
                      				<ProtectYourPC>1</ProtectYourPC>
                      				<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                      				<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                      				<HideLocalAccountScreen>true</HideLocalAccountScreen>
                      				<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                      			</OOBE>
                      			<DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>
                      			<BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled>
                      			<UserAccounts>
                      				<AdministratorPassword>
                      					<Value>1234T@b</Value>
                      					<PlainText>true</PlainText>
                      				</AdministratorPassword>
                      				<LocalAccounts>
                      					<LocalAccount wcm:action="add">
                      						<Password>
                      							<Value>1234T@b</Value>
                      							<PlainText>true</PlainText>
                      						</Password>
                      						<Description>Local Administrator</Description>
                      						<DisplayName>Administrator</DisplayName>
                      						<Group>Administrators</Group>
                      						<Name>Administrator</Name>
                      					</LocalAccount>
                      				</LocalAccounts>
                      			</UserAccounts>
                      			<WindowsFeatures>
                      				<ShowMediaCenter>false</ShowMediaCenter>
                      				<ShowInternetExplorer>true</ShowInternetExplorer>
                      			</WindowsFeatures>
                      			<RegisteredOrganization>Tabitha Healthcare</RegisteredOrganization>
                      			<RegisteredOwner>Administrator</RegisteredOwner>
                      			<DoNotCleanTaskBar>false</DoNotCleanTaskBar>
                      		</component>
                      	</settings>
                      </unattend>
                      
                      JJ FullmerJ 1 Reply Last reply Reply Quote 0
                      • S
                        Sebastian Roth Moderator
                        last edited by

                        @ConJon said in Windows Boot Manager boot option disappears after Image:

                        I got those results from our FOG Server. The machine that stores and deploys images.

                        I wasn’t asking you to run those commands on your FOG server! As described earlier please schedule a debug task on your client, set a password, connect via SSH and get the information right from the client(s). This information is specific for each machine and it’s of not much help to grab it from your FOG server.

                        So please re-read my earlier post, grab the information from your client(s) and post here.

                        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                        1 Reply Last reply Reply Quote 0
                        • JJ FullmerJ
                          JJ Fullmer Testers @ConJon
                          last edited by

                          @ConJon Looks like you’ve got it set up as

                          generalize - > upload
                          deploy -> specialize -> oobe

                          I’m looking through my generalize and audit system configs to see if there’s anything that might be helping me out with the boot changes. On most my hp computers the boot manager changes in the boot order automatically. We have a few outliers once in a while that don’t change after the fog deploy, like some acer switch 3/5 tablets.

                          What model exactly is this happening on again?
                          It looks like you just said prodesk, but there is a prodesk 400 and a prodesk 600. There are also different generations and different form factors and that can make a difference too. I have some prodesk 400’s and 600’s of the mini formfactor in G3 and g4 I can test against to see if I can give you a working example

                          Have you tried the FogApi powershell module? It's pretty cool IMHO
                          https://github.com/darksidemilk/FogApi
                          https://fogapi.readthedocs.io/en/latest/
                          https://www.powershellgallery.com/packages/FogApi
                          https://forums.fogproject.org/topic/12026/powershell-api-module

                          1 Reply Last reply Reply Quote 0
                          • JJ FullmerJ
                            JJ Fullmer Testers
                            last edited by

                            Another question. When imaging what do you set the default boot option to?
                            i.e. do you change the boot order to network/pxe first, or are you leaving it default and hitting f12 to get to the network boot?

                            I change my boot order then when it boots after imaging, if fog didn’t change the boot order it’ll still boot through the fog refind boot to disk menu.
                            Then my set-bootmgr function comes into play. Before getting into that though (which involves a bit of setup by the by, a bit of configuration on the fog server end and a bit of configuration on the unattend and files included in your image)

                            But I’m curious if booting through the pxe boot after imaging will get you into an automated process to start out.

                            Have you tried the FogApi powershell module? It's pretty cool IMHO
                            https://github.com/darksidemilk/FogApi
                            https://fogapi.readthedocs.io/en/latest/
                            https://www.powershellgallery.com/packages/FogApi
                            https://forums.fogproject.org/topic/12026/powershell-api-module

                            1 Reply Last reply Reply Quote 0
                            • S
                              Sebastian Roth Moderator
                              last edited by

                              @ConJon Do you have any news on this topic? Did you get to pull the requested UEFI boot loader information from your machines?

                              Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                              Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                              jmasonJ 1 Reply Last reply Reply Quote 0
                              • jmasonJ
                                jmason @Sebastian Roth
                                last edited by

                                @Sebastian-Roth I have this issue on the Dell 7730 as well, but after the successful deploy in debug task mode the CentOS boot option reappeared, however the new long name for the windows partition is still there, also the new long name for the linux drive/partition is still there even after the CentOS boot option reappeared.

                                Another problem was that when the CentOS came back into the bios it was placed at the top of the boot order sequence, which breaks PXE boot requiring a reboot into setup to correct.

                                dell7730bios-bootsequence.PNG

                                I believe that I ran across something related to that on the forums while searching for other information, but at the time I didn’t care what the drive/partition was called here so long as it worked.

                                1 Reply Last reply Reply Quote 0
                                • S
                                  Sebastian Roth Moderator
                                  last edited by

                                  @ConJon Any news on this from your side? I’ll mark this solved otherwise.

                                  Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                  Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                                  C 2 Replies Last reply Reply Quote 0
                                  • C
                                    ConJon @Sebastian Roth
                                    last edited by

                                    @Sebastian-Roth My apologies, it has been extremely busy over here. We are in the process of replacing all of our access points and our server infrastructure as well. I haven’t had time to check this for a long time.

                                    C 1 Reply Last reply Reply Quote 0
                                    • C
                                      ConJon @ConJon
                                      last edited by

                                      @ConJon We did move the fog server to our server cluster so it is now on VMWare on our infrastructure instead of a lone desktop unit. We still have this issue though.

                                      1 Reply Last reply Reply Quote 0
                                      • C
                                        ConJon @Sebastian Roth
                                        last edited by

                                        @Sebastian-Roth However, those commands give me a “command doesn’t exist” error

                                        1 Reply Last reply Reply Quote 0
                                        • S
                                          Sebastian Roth Moderator
                                          last edited by Sebastian Roth

                                          @Sebastian-Roth said in Windows Boot Manager boot option disappears after Image:

                                          efibootmgr
                                          efibootmgr -v
                                          efivar -l

                                          Those commands definitely exist within the FOS Linux system that boots up your clients to capture/deploy an image. If you see an error running those commands, please take a picture and post here.

                                          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                                          C 2 Replies Last reply Reply Quote 0
                                          • C
                                            ConJon @Sebastian Roth
                                            last edited by

                                            @Sebastian-Roth

                                            [Wed Mar 13 root@fogclient ~]# efibootmgr
                                            BootCurrent: 0002
                                            Timeout: 2 seconds
                                            BootOrder: 0004,0002,0003
                                            Boot0000* Windows Boot Manager
                                            Boot0002* Onboard NIC(IPV4)
                                            Boot0003* Onboard NIC(IPV6)
                                            Boot0004* UEFI: SK hynix SC311 SATA 256GB, Partition 2
                                            Boot0008* Onboard NIC(IPV6)
                                            [Wed Mar 13 root@fogclient ~]# efibootmgr -v
                                            BootCurrent: 0002
                                            Timeout: 2 seconds
                                            BootOrder: 0004,0002,0003
                                            Boot0000* Windows Boot Manager  HD(1,GPT,e0da240b-3f6f-464d-8a41-76bcc1094b40,0x800,0xfa000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....L..............
                                            Boot0002* Onboard NIC(IPV4)     PciRoot(0x0)/Pci(0x1f,0x6)/MAC(1065301053d5,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
                                            Boot0003* Onboard NIC(IPV6)     PciRoot(0x0)/Pci(0x1f,0x6)/MAC(1065301053d5,0)/IPv6([::]:<->[::]:,0,0)..BO
                                            Boot0004* UEFI: SK hynix SC311 SATA 256GB, Partition 2  HD(2,GPT,b6c6cb54-cd8a-4007-a463-4bcfe288178b,0xfa000,0x32000)/File(EFI\Microsoft\Boot\bootmgfw.efi)..BO
                                            Boot0008* Onboard NIC(IPV6)     PciRoot(0x0)/Pci(0x1f,0x6)/MAC(1065301053d5,0)/IPv6([::]:<->[::]:,0,0)..BO
                                            [Wed Mar 13 root@fogclient ~]# efivar -l
                                            65cbd9d9-ab77-4a61-b288-2763405d588a-BootOneDevice
                                            d719b2cb-3d3a-4596-a3bc-dad00e67656f-dbx
                                            01368881-c4ad-4b1d-b631-d57a8ec8db6b-ColdReset
                                            eaec226f-c9a3-477a-a826-ddc716cdc0e3-OfflineUniqueIDEKPubCRC
                                            77fa9abd-0359-4d32-bd60-28f4e78f784b-CurrentPolicy
                                            5990c250-676b-4ff7-8a0d-529319d0b254-BootFFFC
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-PKDefault
                                            074e1e48-8132-47a1-8c2c-3f14ad9a66dc-AmiEntryS3Addr
                                            01368881-c4ad-4b1d-b631-d57a8ec8db6b-FPDT_Volatile
                                            bb983ccf-151d-40e1-a07b-4a17be168292-MemoryOverwriteRequestControlLock
                                            9cb2e73f-7325-40f4-a484-659bb344c3cd-SOFTWAREGUARDSTATUS
                                            b697de83-1ab6-42c4-9dee-a806c637818b-COMPAL
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOutDev
                                            0a602c5b-05a0-40c4-9181-edcd891d0036-SMBIOS_ENTRY_ADDR
                                            5990c250-676b-4ff7-8a0d-529319d0b254-BootFFF7
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-PlatformLang
                                            b08f97ff-e6e8-4193-a997-5e9e9b0adb32-CpuSetupVolatileData
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-ErrOut
                                            77fa9abd-0359-4d32-bd60-28f4e78f784b-Kernel_SiStatus
                                            368b3152-563d-4670-8d94-47a9fa8c4c16-BiosGuardRecoveryAddressVariable
                                            4b3082a3-80c6-4d7e-9cd0-583917265df1-MaximumTableSize
                                            4b3082a3-80c6-4d7e-9cd0-583917265df1-SmbiosScratchBuffer
                                            5432122d-d034-49d2-a6de-65a829eb4c74-MeSetupStorage
                                            3a21751e-bd32-4825-8754-82a47f01b09b-GsetLegacyIplDefaultValue
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-PlatformLangCodes
                                            5990c250-676b-4ff7-8a0d-529319d0b254-BootFFFE
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-PK
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0003
                                            73dad563-8f27-42af-918f-8651eb0a93ef-Ep
                                            01368881-c4ad-4b1d-b631-d57a8ec8db6b-MonotonicCounter
                                            8e1a7a52-df0d-460d-a825-d08acf2bb44d-InSetup
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-KEKDefault
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-BootCurrent
                                            193dfefa-a445-4302-99d8-ef3aad1a04c6-RstSataFastEnumVar
                                            c54906f9-eb09-4457-a007-4154652fcfa5-UserDefaults
                                            01368881-c4ad-4b1d-b631-d57a8ec8db6b-AssetTag
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-VendorKeys
                                            66b36b33-8094-424d-ba45-e876d62c45c1-ePSAVersion
                                            5990c250-676b-4ff7-8a0d-529319d0b254-BootFFFB
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0000
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-SecureBoot
                                            65cbd9d9-ab77-4a61-b288-2763405d588a-BootList
                                            77fa9abd-0359-4d32-bd60-28f4e78f784b-Kernel_ATPSiStatus
                                            2d2edd10-1661-47e3-bdff-581f2a63ec0d-LastModeState
                                            ba1d893b-803e-4b26-a3de-585703ff7bd6-TbtHRStatusVar
                                            0a602c5b-05a0-40c4-9181-edcd891d0003-GNVS_PTR
                                            5990c250-676b-4ff7-8a0d-529319d0b254-BootFFF6
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0008
                                            c60aa7f6-e8d6-4956-8ba1-fe26298f5e87-EPCBIOS
                                            eaec226f-c9a3-477a-a826-ddc716cdc0e3-UnlockIDCopy
                                            01368881-c4ad-4b1d-b631-d57a8ec8db6b-ServiceTag
                                            4b3082a3-80c6-4d7e-9cd0-583917265df1-SmbiosEntryPointTable
                                            e224eaa0-4358-6ac8-3cce-daa44e54f638-DellVar01
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-OsIndicationsSupported
                                            01368881-c4ad-4b1d-b631-d57a8ec8db6b-DellMonotonicCounter
                                            eaec226f-c9a3-477a-a826-ddc716cdc0e3-OfflineUniqueIDEKPub
                                            7f3301c7-2405-4765-aa2e-d9ed28aea950-GsetUefiIplDefaultValue
                                            4a67b082-0a4c-41cf-b6c7-440b29bb8c4f-LoaderEntryRebootReason
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-dbxDefault
                                            a66919d2-6c45-403e-b00a-9bce58e97315-OsType
                                            90d93e09-4e91-4b3d-8c77-c82ff10e3c81-CpuSmm
                                            01368881-c4ad-4b1d-b631-d57a8ec8db6b-SataPortNumber
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-BootOrder
                                            5990c250-676b-4ff7-8a0d-529319d0b254-BootFFFD
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-KEK
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0002
                                            77fa9abd-0359-4d32-bd60-28f4e78f784b-Kernel_EntRevokeSiStatus
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-ConInDev
                                            c54906f9-eb09-4457-a007-4154652fcfa5-FactoryDefaults
                                            77fa9abd-0359-4d32-bd60-28f4e78f784b-Kernel_RvkSiStatus
                                            5990c250-676b-4ff7-8a0d-529319d0b254-BootFFF8
                                            8ebe3d07-3420-4bfa-8c13-3a4e0fae6860-DIAGEEPROM_VAR
                                            e20939be-32d4-41be-a150-897f85d49829-MemoryOverwriteRequestControl
                                            77fa9abd-0359-4d32-bd60-28f4e78f784b-Kernel_WinSiStatus
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-BootOptionSupport
                                            01368881-c4ad-4b1d-b631-d57a8ec8db6b-PostScreenIsChanged
                                            4b3082a3-80c6-4d7e-9cd0-583917265df1-SmbiosV3EntryPointTable
                                            eda41d22-7729-5b91-b3ee-ba619921cefa-IntUcode
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-SignatureSupport
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-ErrOutDev
                                            368b3153-563d-4610-8d94-47a9fa8c4c16-BiosGuardCapsuleVariable
                                            d719b2cb-3d3a-4596-a3bc-dad00e67656f-db
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-Timeout
                                            77fa9abd-0359-4d32-bd60-28f4e78f784b-Kernel_SkuSiStatus
                                            a9b5f8d2-cb6d-42c2-bc01-b5ffaae4335e-PBRDevicePath
                                            4da4f952-2516-4d06-8975-65036403a8c7-RstOptaneConfig
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0004
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-dbDefault
                                            45cf35f6-0d6e-4d04-856a-0370a5b16f53-DefaultBootOrder
                                            8be4df61-93ca-11d2-aa0d-00e098032b8c-SetupMode
                                            
                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 1 / 2
                                            • First post
                                              Last post

                                            208

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project