9 Replies Latest reply on Jul 14, 2014 1:55 PM by Mach6

    Installing LD agent with preferred server

    rickorhino Apprentice

      Currently we copy the LD agents used for provisioning to an OSD folder which contains items we replicate for the preferred servers. We then use an action in PRE-OS to copy the agent to the c: drive.Then in system config we execute that file to install the agent. Before the recent component patch upgrades I believe the system would wait for that agent to install. However now it does not seem to be doing that and just moves to the next tasks.

       

      I would use the action "configure agent"  but it seems to pull this from the core in the ldmain directory. I don't want to replicate all of ldmain to preferred server just for agent installing.

       

      Anyone else noticing what I am?

        • 1. Re: Installing LD agent with preferred server
          LANDave SupportEmployee

          You could create an LDMAIN share and copy only the files that Provisioning uses for that purpose of installing the agent, no?

          • 2. Re: Installing LD agent with preferred server
            Gjstewart Specialist

            I had my agents installing from the c:\ in provisioning. And i saw an issue with the agent after a recent patch release.

             

            I had to recreate the agent from the core after the patch ( even though it should not have affected the agent ) and this worked for me.

             

            I would try creating a new agent with identical settings now you have patched the core and try using that file. See what happens.

            • 3. Re: Installing LD agent with preferred server
              Apprentice

              Should we maybe raise an Enhancement Request for this? Right now, we also copy the self-extracting exe to the client and run it, but I would prefer using the "Configure Agent" action in provisioning if Preferred Server would be used..

              • 4. Re: Installing LD agent with preferred server
                Gjstewart Specialist

                You should be able to still use the 'configure agent' action - i use the c:\ through preference.

                Also I had a custom PowerShell script that mapped to the nearest preferred server and if it was not available would map to the next and so on.

                 

                However in Provsioning now you can choose the action to map to a preferred server? which version of LANDesk are you using?

                 

                Cant you use the Map to preferred server then copy the agent from there to the c:\ - that's what i am doing. Then it acts like the 'configure agent' action.

                 

                However like i said that should still be functioning.

                • 5. Re: Installing LD agent with preferred server
                  Apprentice

                  For me, the advantage of the "Configure Agent" action is, that I wouldn't have to change several Prov. Templates in order to make them use the new agent config (agent_20140701.exe for example). I would only need to change the settings, press "save" and the latest agent would be installed on new clients (as the config is referenced in the Prov. Template). If now (like in the "Deploy Image" action) the Preferred Server would be used, I would be happy.

                   

                  However in Provsioning now you can choose the action to map to a preferred server? which version of LANDesk are you using?

                   

                  Cant you use the Map to preferred server then copy the agent from there to the c:\ - that's what i am doing. Then it acts like the 'configure agent' action.

                  This is true. I could use the MapToPS action (we have 9.5SP2), but not together with the Configure Agent action. LANDesk is always getting the files from the Core, which is bad, when installing in remote locations:

                  Clipboard.jpg

                   

                  The catch is, that our agent configs have different names and this would mean, that I have to adjust several templates when I change them. Right, I use the MapToPS and the self-extracting exe files for agent installation..

                  • 6. Re: Installing LD agent with preferred server
                    Gjstewart Specialist

                    Just a thought - think i tried this a few years ago but cannot remember the outcome... what happens if you mirror the location of the agent files on the preferred server -

                     

                    So set up a Ldlogon share on your pref server and only place the agent files in there?

                     

                    This way you might trick the server - as it finds the exact path it would on the server to the agent files... I cannot remember if it worked for me or not and cannot test it here.

                     

                    just a long shot!

                    • 7. Re: Installing LD agent with preferred server
                      Apprentice

                      Thanks for the tip. Right now, I also cannot test this scenario. But I think this is hard linked in the ConfigHandler. Maybe a LANDesk employee can tell us more about it.

                      • 8. Re: Installing LD agent with preferred server
                        rickorhino Apprentice

                        All of these are good suggestions and I think we will wait to see what they do in 9.6 before suggesting an enhancement.

                        • 9. Re: Installing LD agent with preferred server
                          Employee

                          In 9.6 the Configure Agent action has been revamped, but just a little.  The "standard" agent install will work as normal and go back to the core for everything.  This is the same behavior as 9.5.  We've added the option of using a self contained executable for the agent install.  This option will attempt to download the executable from preferred servers.

                           

                          There are a few more uses for the executable agent install that are part of some of the new 9.6 features that will be made public when 9.6 is released.