How to Build a Legacy Agent for Windows XP and Server 2003

Version 34

    Verified Product Versions

    LANDESK Management Suite 9.6LANDESK Management Suite 2016.xLANDESK Endpoint Manager 2017.x

    How to Build a Self Contained Executable for Installing Ivanti Endpoint Manager on a Legacy Operating System




    To maintain compatibility with legacy operating systems, a special agent must be created from older code sources.


    A LANDESK EPM agent compiled from the older LDMS code branches is what must be used to continue using Ivanti EPM on these legacy Operating Systems. The Whitepaper attached to this article describes how to build/configure the "Legacy Agent".


    The LDMS 2016.3 release and later no longer support the installation of the agent on Windows XP and Server 2003 systems. Existing agents on Windows XP/2003 will continue to function, but new features will not be available. If you have a large number of Windows XP devices and need to continue installing agents, it is recommended that you use LDMS 2016.0 with SU5. An agent installation can be created and preserved from the previous version, or Windows XP machines can be managed by a previous version of LDMS until they are updated to operating systems supported by Microsoft®.




    To create the LANDESK Agent 2016.0 that is compatible with Windows XP and/or Windows Server 2003, please perform the following.


    1. Set up a Windows Server 2012 R2 server with the same computer name as the new later version core server and with the same IP address as the new later version core server in an isolated environment.
    2. Install LDMS 2016.0* on the Windows Server 2012 R2* created in step 1 above.
    3. Install Software Update 5 (SU5)** for LDMS 2016.0 on the Windows Server 2012 R2 created in step 1 above.
    4. Create a new LANDESK Agent Configuration agent configuration with a unique name.
    5. Create the self-contained LANDESK Agent executable(s).
    6. Copy the executable(s) to the new later version core server.
    7. Run %ldms_home%legacyagent.exe on the new later version core server.

      Legacy Agent.exe.png
    8. Browse to the executable created on the 2016.0 core server.
    9. Browse to the location you wish to save the updated self-contained executable.
    10. Browse to the most recent file in "C:\Program Files (x86)\LANDesk\Shared Files\cbaroot\certs\*.0" and click "Add".
    11. Check the box labeled 'Edit configuration file manually.'
    12. After clicking "Update" the following message will appear:
    13. Browse to the directory stated in this dialog, and locate the agent ini file. In this example, you would locate the file called 'Default Windows Configuration.ini'.
    14. Edit the file, and locate the line ServerName='core name', and replace 'core name' with your new core's hostname.
    15. Next, search for "REG45" and add the following line below that.
      REG46=HKEY_LOCAL_MACHINE, SOFTWARE\LANDesk\ManagementSuite\WinClient\Vulscan\CommandLine, /NoSelfUpdate, , REG_SZ
    16. Click "OK" and the files will be processed and the Legacy Agent will be built in your desired target location.
    17. Repeat steps 7-14 for any further Agent Configurations you wish to process.
    18. After your legacy agent has been deployed, you will need to create a Change Settings task, and push the correct settings to your legacy agents.
      1. Do not use the option 'Schedule update to agent settings', found in agent configuration, as this will break the legacy agent.
      2. For more information on creating a change settings task, please view the following document: How To: Change Agent Settings


    * Download LDMS 2016.0 from here .

    ** Download Software Update 5 ( SU5 ) for LDMS 2016.0 from here.