10 Replies Latest reply on Nov 5, 2015 10:41 AM by mrspike

    Has anyone deployed the LANDesk Agent to Servers

    Rookie

      We are interested in deploying the LANDesk agent to different types of servers in our organization, this would include SQL Server, SEP Servers, Web Servesr, Oracle Servers and possibly Citrix Servers.  Has anyone had any experience doing this and have you experienced any performance problems after deploying the agent to them?

        • 1. Re: Has anyone deployed the LANDesk Agent to Servers
          Specialist

          Over 300 servers (99% virtual). No issues with the agent.

           

          Gotchas ---- be careful of your reboot settings. This can be set in each location: Distribution Packages, OS Provisioning, Patching, and Scheduled tasks (especially recurring).

           

          To help prevent this I only use OS Provisioning to send jobs to servers with a quick time check script to error out if triggered at wrong time.

          • 2. Re: Has anyone deployed the LANDesk Agent to Servers
            MarXtar ITSMMVPGroup

            Don't enable software monitoring. This has no real use on servers and if they are citrix servers then it can cause unnecessary load. Also be careful about adding Real-Time Monitoring. This has hardware monitoring/alerting components that 'could' clash or at least double up on any existing hardware monitoring software on the servers.

             

            Also pay close attention to each of the module settings. Servers are a perfect example of where to use time windows for the scheduled events for inventory scanning, software checks, and vulnerability scans. One of these per module might be enough but consider periods of peak or low load and set your time windows accordingly so these events don't happen during peak periods.

             

            Further into vulnerability scanning/remediation, consider as well the maintenance window settings. These won't prevent systems being scanned (for that use the previous suggestion) but they will prevent patches and associated reboots from being applied outside of those windows. This is an area where a setting per server role is probably the minimum. You may also want to consider your approach to pilot systems and have settings that apply to those too.

             

            Consider as well any Anti-Virus on the servers. Perhaps make sure that any real time scanning that goes on it not constantly intercepting what the agent touches. Protect processes such as ldiscn32.exe, gatherproducts.exe, vuslscan.exe, sdclient.exe and so on.

             

            The agent is absolutely fine on servers, it is simply down to what you choose to put on there and the load you tell it to create.

             

            Mark McGinn

            MarXtar Ltd/MarXtar Corporation

            http://landeskone.marxtar.co.uk

            LANDESK One Development Partner

             

            The One-Stop Shop for LANDESK Enhancements

            • 3. Re: Has anyone deployed the LANDesk Agent to Servers
              Rookie

              Thanks for the information David.  That will assist us with our deployment.

              • 4. Re: Has anyone deployed the LANDesk Agent to Servers
                Rookie

                Thanks for the pointers Mark.  Do you know, can we have a different agent to deploy to the servers than we have for our other devices?  

                • 5. Re: Has anyone deployed the LANDesk Agent to Servers
                  MarXtar ITSMMVPGroup

                  Yes. You can have as many as you want. Just go to Agent Configuration nad copy/edit and existing or create from scratch.

                   

                  With Agent Settings you can have one agent per platform but can apply different behavioural settings to different machines. That way you keep a small number of agent configurations but can make them act differently. The agent config simply stores what you want as a default when it gets installed. It can seem a bit complicated at first but it is very powerful.

                   

                  Mark McGinn

                  MarXtar Ltd/MarXtar Corporation

                  http://landeskone.marxtar.co.uk

                  LANDESK One Development Partner

                   

                  The One-Stop Shop for LANDESK Enhancements

                  • 6. Re: Has anyone deployed the LANDesk Agent to Servers
                    Rookie

                    Thanks Mark, we were not aware we could have multiple agents and have only been deploying to workstations/portables.  The information you provided is very helpful !

                    • 7. Re: Has anyone deployed the LANDesk Agent to Servers
                      Specialist

                      As always Mark is spot on in his detail.

                      To clarify my "No Issues with agent"

                      Back in the old'en days when Windows NT roamed the earth LANDesk, MFC42.dll, Comdlg32.dll, and User32.dll used to really not like each other.

                       

                      Now, as Mark has explained it is all about tuning the agent.

                      • 8. Re: Has anyone deployed the LANDesk Agent to Servers
                        Specialist

                        We have seen BSOD on one of our domain controllers after installing a server agent with XDD, Server 2012 R2 x64 not all tho and have seen that the 9.6SP2 916 patchnotes shows this should be fixed.

                        • 9. Re: Has anyone deployed the LANDesk Agent to Servers
                          phoffmann SupportEmployee

                          In regards to BSOD'ing a server (I've never seen it happen myself), but here's a few good practices.

                           

                          * Do *NOT* install the mirror driver on servers. It's "still a driver" so could theoretically BSOD a box (in case something in the software stack decides not to like it).

                          * Do *NOT* install XDD on a server (same reason - it involves adding actual drivers). "Should be fine" in most situations, but driver issues are a pain in the backside to figure out & resolve. Best to think ahead.

                          * As Mark pointed out - be careful with your reboot & so on settings. As was suggested, a separate set of agent behaviour files / separate agent config is HIGHLY recommended .

                           

                          Hope this helps

                           

                          - Paul Hoffmann

                          • 10. Re: Has anyone deployed the LANDesk Agent to Servers
                            mrspike SSMMVPGroup

                            We have the agent on several hundred servers.  We keep the agent simple, some have never reboot enabled, while others do not.

                             

                            We have had zero issues caused by LANDesk with the exception of some minor patch detection issues here and there.