5 Replies Latest reply on Aug 31, 2015 11:55 AM by tdavenport

    How to make vboot work in LD 9.6 SP2

    GJHorn Specialist

      We've been migrating from LD 9.0 to 9.6 sp2 everything seems to be working except for VBoot. We are still using the old LD 9.0 PXE boot currently. I looked at all the methods in the community for vboot and have installed them but when I turn off pxe on LD 9.0 preferred server and try to boot over the nic on a client device, I don't get any ip address from the LD 9.6 preferred server.

       

      Does anybody have any clues what to look for?


        • 1. Re: How to make vboot work in LD 9.6 SP2
          SupportEmployee

          Hi GJhorn,

           

          You are going to want to update your PXE to the same version as the core. I am not sure if I am understanding this correctly, but you disable PXE and try to get an IP from a preferred server? If this is correct, then this will not work.

          • 2. Re: How to make vboot work in LD 9.6 SP2
            nick.evans SupportEmployee

            Hi GJHorn,

            Are you issuing a provisioning task to a client while it is within Windows so it can vBoot? I'm unclear where your client is that it does not have an IP address, but that you are trying to vboot it?

            • 3. Re: How to make vboot work in LD 9.6 SP2
              tdavenport Specialist

              GJHorn,

               

              1. vBoot provisioning is performed against a machine that has a functioning OS and a running agent. You cannot boot a machine to the NIC and start a vBoot provisioning process. That is not its purpose. If you boot to NIC you must have a PXE Server running on that subnet or have your DHCP Scope options (or IP Helpers) set for a single PXE.
              2. Your preferred server does not issue IP Addresses.
              3. The very first action in a vBoot Provisioning process should be to copy WinPE to that target machine and then issue a reboot command so that it will boot into WinPE. From there, the rest of your provisioning actions will execute in order.
              4. If you want vBoot as an option in your provisioning solution, your preferred server may serve the WinPE file. If it's not present on the preferred server, then it will pull it from the core or other network resource.
              5. I'm on a 9.5 box at this moment but here's a screenshot of a vBoot action. You can only issue this command to a machine with a functioning agent and OS. It downloads the WinPE boot file and then reboots the machine into WinPE.

              vBoot.PNG

              1 of 1 people found this helpful
              • 4. Re: How to make vboot work in LD 9.6 SP2
                GJHorn Specialist

                Thanks for the reply. Let me clarify. I do have PXE boot functioning in the new LD 9.6 now. However, we are looking into VBoot instead. The IP is coming from DHCP via the PXE server on our preferred server successfully.

                 

                I am just wondering how is VBoot configured instead of PXE boot? Is PXE boot still needed?

                • 5. Re: How to make vboot work in LD 9.6 SP2
                  tdavenport Specialist

                  GJHorn,

                   

                  Typically, organizations use both. It's not an "either or" because vBoot does not replace PXE boot provisioning. The only difference is how the target machine receives a copy of WinPE. But it is a critical difference. A machine without a functioning OS needs to PXE boot in order to get provisioned. vBoot only works if the machine has a working OS and a working LD Agent.

                  The scenarios are:

                   

                  vBoot = In place provisioning over en existing OS. Ex. Schedule a provisioning task in the console and drag that target machine into your scheduled provisioning task. The machine must be on and already booted into Windows. PXE is bypassed entirely here. However, that is only possible because the original OS and LD Agent downloaded WinPE prior to rebooting. Great for 1 off deployments or classroom refresh deployments.

                   

                  PXE = Provisioning from a Network boot. Machine can be in any state (No OS, corrupt OS, or functioning OS). The PXE server transfers a copy of WINPE via TFTP to the machine which, in turn, allows the machine to boot into an OS and proceed with the rest of the Prov. Actions. Great for mass deployments and standardized rollouts.

                   

                  vBoot and PXE provisioning templates are identical except for that 1 action that I included in the screenshot. Other than that, they are identical.

                   

                  I hope this helps.

                  1 of 1 people found this helpful