1 2 Previous Next 19 Replies Latest reply on Nov 29, 2017 3:22 AM by phoffmann

    how to configure DHCP server or Router to have Landesk as a PEX server

    Rookie

      Currently, we have a Windows WDS as our PEX server and set up ip helper on routers virtual interface. It works 75% times that sometimes with PEX server not found/time out errors. I found out that Landesk has a built in function for PXE boot. That's why we are moving this approach to make Landesk 2016 as a PXE boot server.   I would like to know how to configure DHCP server or Router to have Landesk as a PEX boot server without any PEX representative on each subnets. 

      Correct me wrong, from my understanding about PXE Representative, it needs to have at least one one each subnet. If the PXE Representatives are down on this subnet, you will lose you PEX boot option on this subnet. If this is right, I don't want to have more administrative time to manage those PXE Representatives.

      So, I need to configure my DHCP server with option 43 and 60 set, can someone explain a little more on detail with examples? From the documentation How to configure DHCP to work with LANDESK PXE boot , it said not option 66 and 67, if you are using Landesk PXE boot.

      if I set ip helper on routers virtual interface, is this a better option?

      Pro and Con on each configurations?

        • 1. Re: how to configure DHCP server or Router to have Landesk as a PEX server
          RobLent Specialist

          We are using a single server for our PXE server.

           

          We did this as we had this already in previous versions of LANDesk anyway.

           

          Just need the IP helper on your routers/switches to point to the PXE servers IP address.

           

          You can't use the Core server as a PXE representative as it can't have an agent on it and this is needed to enable PXE.

           

          Hope this helps.

          • 2. Re: how to configure DHCP server or Router to have Landesk as a PEX server
            Rookie

            Can you be a little more specific?

            Your PXE server is the same as LANDesk Server or your PXE server is a single WDS server?

            Do you need any PXE representative on any subnets?

            If you have a network diagram, that it be very helpful.

             

            thank you

            • 3. Re: how to configure DHCP server or Router to have Landesk as a PEX server
              phoffmann SupportEmployee

              What version of LDMS / EPM are you on?

               

              Around 2016.3 (if I'm not mistaken), we introduced a self-electing option for PXE reps (to ensure that if even a dedicated box goes down, "someone else" can go on carry the torch).

               

              Otherwise, our PXE reps are primarily made so you DON'T have to reconfigure your routers. There's a few DHCP options you may want to look at though here -- How to configure DHCP to work with LANDESK PXE boot -- !

               

              And you may generally want to study a few of the BKM's from the OS Provisioning landin page -- OS Deployment and Provisioning -- here.

               

              Also - moving this thread over into OS Provisioning section, since't it's not really related to agent deployment.

               

              That should help you a bit .

              • 4. Re: how to configure DHCP server or Router to have Landesk as a PEX server
                Rookie

                We are using LDMS 10.1. Yes, I read all documentations and still having problem on understanding.

                • 5. Re: how to configure DHCP server or Router to have Landesk as a PEX server
                  RobLent Specialist

                  We are using the single PXE server configuration as it was already there and all the switches/routers were already configured with the IP helper to forward PXE requests to it.

                   

                  If we were to setup new now we would probably not bother doing that but it was already there.

                   

                  When we moved to 2016.3 I just put an agent on that server with the Self electing PXE service configured and let LANDesk do the rest.

                   

                  We do have one other device using Self electing PXE which is in our LAB but most of the time PXE requests go to the main server which makes sense as the routers/switches are configured to do that.

                  • 6. Re: how to configure DHCP server or Router to have Landesk as a PEX server
                    phoffmann SupportEmployee

                    OK - which parts do you have issue with?

                     

                    Have a look at this Momentum webinar ([Tech Brief On-Demand Webinar 2016] Provisioning with LANDESK Management Suite ) / grab the materials attached -- I explain in some detail how our PXE process works. Visual stuff may help I hope .

                     

                    Having a clearer idea what you're struggling with would help.

                     

                    Simple explanation:

                    • We only need a single PXE representative per broadcast domain (not the same as site). If you don't know what a broadcast domain is - essentially, anything that'll hear a UDP packet sent out on the local network is a broadcast domain ... that's USUALLY a site, but doesn't have to be. Note that this PXE Representative is (usually) a device with a LANDesk CLIENT installed - and NOT the Core Server!

                     

                    • That PXE representative's job is to pick up the PXE - DHCP requests in each broadcast domain and fobs them off to the Core Server via civilised TCP and essentially goes "Hey - so I got this guy ... do I need to do anything with him?" ... and they handle it from there. So we're quite router friendly in that regard, since you don't NEED to do any UDP-forwarding or anything like that.

                     

                    • The PXE reps are PROBABLY somewhat similar to WDS servers (in as far as - they pick up PXE requests) but they then pass them off to the Core Server (the central server), who then checks "do we have oustanding Provisioning jobs for those guys" and then passes a decision on to the PXE rep of the "Yes - tell this guy to boot into WIN PE and start template XYZ" or "Nope - nothing for this guy - he can boot into Windows". The PXE rep is pretty much "just" a middle man to make routers not be a "£$)(*" nightmare for the PXE process (which is not exactly operating on a robust protocol level) .

                     

                    ... it's really quite simple. PXE proxies make router configuration a non issue ... have one in each subnet that you're intending to use for OS Provisioning (that's where client self-electing services come in to make your life easier). And the PXE rops "simply" pass messages back & forth (in essence) between the client & the Core Server.

                     

                    Does that make sense now?

                    • 7. Re: how to configure DHCP server or Router to have Landesk as a PEX server
                      Rookie

                      Sorry, Paul, it seems  this is my misunderstanding . My colleague told me that Landesk Core Server can be a PXE server and we can get rid of our current clunky WDS Server.  However, I couldn't find any PXE service on Landesk Core Server.

                       

                      Please correct me wrong,

                      1. If I don't have a WDS/PXE on my network, I need at least one PXE representative per broadcast domain.

                      2. Landesk Core Server can not be your PXE server neither PXE representative.

                      3. If I have a WDS/PXE, I don't need any PXE representative.

                       

                      Thank you,

                      • 8. Re: how to configure DHCP server or Router to have Landesk as a PEX server
                        RobLent Specialist

                        Kudos phoffmann  I love reading your explanations. 

                        • 9. Re: how to configure DHCP server or Router to have Landesk as a PEX server
                          MarXtar ITSMMVPGroup

                          NPS_JZ

                           

                          1. If I don't have a WDS/PXE on my network, I need at least one PXE representative per broadcast domain.

                           

                          As you already have IP forwarding enabled then you 'could' do as RobLent suggests and put PXE services on the system you have using the IP address that the forwarding goes to. This would possibly be the easiest.

                           

                          For this you would install an agent with an agent setting that enables PXE Subnet Elected services.  You would then in the console make sure to enable PXE services for the subnet that the client is on so that the election runs and that machine is selected. For more detail look at PXE subnet elected services in the guide as that should tell you what needs to be configured.

                           

                          2. Landesk Core Server can not be your PXE server neither PXE representative.

                           

                          It is 'not supported' if you install an agent on the Core Server and make it a PXE representative. This doesn't mean it won't work, just that it isn't recommended.

                           

                          3. If I have a WDS/PXE, I don't need any PXE representative.

                           

                          a WDS PXE server will only server WDS. To use Ivanti OS Provisioning you need an Ivanti PXE Representative. You should not have both running on the same broadcast domain as they will clash.

                           

                           

                           

                          What is a PXE Subnet Elected Representative?

                           

                          What you say about needing a PXE server on every broadcast domain is true about all PXE based solutions as PXE is a broadcast based technology. You have circimvented this in the case of WDS by taking advantage of functionality in your routers. Ivanti developed technology to remove the need to configure routers to do this (as not everybody can do this) and this is the Subnet Elected Services. With this, you could allow any of your managed devices to become a PXE server. An election within the broadcast domain would take place, one machine would be selected, the required files for PXE downloaded (such as the boot.wim) and PXE services are now available on that subnet. If the elected machine goes offline then another machine would be elected in its place.

                           

                          By doing this you get PXE services on all subnets (or at least the ones you choose to make them available on within the console) without needing to reconfigure routers AND without needing to deploy a system on each subnet specifically for this purpose.

                           

                          It isn't ideal for everyone but it is quite a nifty bit of technology.

                           

                          HOWEVER - as you have forwarding enabled if you choose the Ivanti subnet elected method it would make sense to disable that forwarding so you don't get odd behaviors in the future. It is still common though to do what you have been doing and to just have the one server acting as the PXE (you still need to have the election but you just make it so that only one machine could possibly win it).

                           

                          Hope this helps fill the gaps a bit.

                           

                          Mark McGinn

                          MarXtar Ltd/MarXtar Corporation

                          http://ivantione.marxtar.com

                          Ivanti One Development Partner

                           

                          Try MarXtar State Management for Ivanti to Better Understand and Manage your Assets

                          1 of 1 people found this helpful
                          • 10. Re: how to configure DHCP server or Router to have Landesk as a PEX server
                            phoffmann SupportEmployee

                            What MarXtar said.

                             

                            As an exercise in "COULD it be done" - you could PROBABLY hack away at the WDS PXE server, and inject our boot images, but that'd be needlessly painful & high in maintenance. Easier to use what's been created for it - the Client Self-Electing Platform (CSEP).

                             

                            That means you CAN leave it running on a single server (essentially - reusing your existing WDS server) or be more network friendly & have CSEP set one up at each site / broadcast domain and have the network stuff no longer forward UDP / PXE requests across the corporate network (which usually network people would be quite grateful for in my experience).

                             

                            While the Core *CAN* have the PXE rep stuff installed on itself, it's discouraged to do so in live environments (it's usually fine for testing). As was pointed out, it's not a supported config -- and while for testing it's usually fine, there's usually too much chance for things to go awry (usually "at the worst time possible") and if it ends up taking bits of the Core Server with it (and/or IIS) then that'll really get you in trouble.

                             

                            If you're absolutely in a dearth for a box (it does NOT have to be a server - we're quite shameless & able to use regular clients as PXE reps) then you can use your Core - but you will want to move away from that as soon as possible.

                             

                            Does that (along with MarXtar's explanation) cover about everything ?

                            • 11. Re: how to configure DHCP server or Router to have Landesk as a PEX server
                              Rookie

                              It's a very helpful discussion.

                              Let me fully understand each service functionality then I will know which is my best choice for my network.

                              • That PXE representative's job is to pick up the PXE - DHCP requests in each broadcast domain and fobs them off to the Core Server via civilised TCP and essentially goes "Hey - so I got this guy ... do I need to do anything with him?" ... and they handle it from there. So we're quite router friendly in that regard, since you don't NEED to do any UDP-forwarding or anything like that.

                              The Client Self-Electing Platform (CSEP), is this working as the same as setting DHCP server scope 66 and 67 to server address and boot file path? Therefore, I don't need any PXE representative because I have the DHCP server settings.

                              ... it's really quite simple. Yes, it is simple but people make it convoluted.

                              My intention is not to set up the client self-electing services on each subnet because some of our subnet might not have landesk client on all the time.

                              However, I would like to get rid of the WDS.

                              what does ivanti recommend?

                               

                              • 13. Re: how to configure DHCP server or Router to have Landesk as a PEX server
                                MarXtar ITSMMVPGroup

                                The Ivanti recommendation is to use CSEP as that is their technology and is supported by them.

                                 

                                Whether this recommendation works for you does depend on how your environment works. For example, do you absolutely need to have PXE services on every subnet all of the time? If you do, what is the likelihood that only the machine you are trying to boot to PXE will be the only machine on that subnet?

                                 

                                'Most' organisations use PXE in certain locations/subnets so CSEP would be fine. If your is different then the mechanism you have been using with WDS might be necessary. It works, but it is not Ivanti's and therefore not officially supported. The CSEP method reduces the download from the central subnet since the PXE Rep has all of the required PXE files held locally.

                                 

                                As mentioned though the PXE forwarding you have been using works perfectly well, so if I was configuring your site and there was a doubt that the CSEP model would not be sufficient, 'I' would have no hesitation to use your existing forwarding model.

                                 

                                Mark McGinn

                                MarXtar Ltd/MarXtar Corporation

                                http://ivantione.marxtar.com

                                Ivanti One Development Partner

                                 

                                Try MarXtar Enterprise Notifer for Ivanti to Better Communicate with Your Service Subscribers

                                Try MarXtar State Management for Ivanti to Better Understand and Manage your Assets

                                • 14. Re: how to configure DHCP server or Router to have Landesk as a PEX server
                                  Rookie

                                  Thank you for your times and your detailed explanations.

                                  1 2 Previous Next