What is the Legacy Agent?
After LD 8.8 the LANDesk agent for mac that can be installed on OS9, 10.2.8, and 10.3.9 became a legacy agent.
Post LD 9.0 SP2, 10.4.11 and 10.5.8 PPC also became a legacy agent. What that means is they are no longer updated and are in an as is state.
Post 9.5 SP2 10.6.x became legacy as well.
What do I need to install the legacy agent?
You will need the following to prepare the legacy agent for use in your environment:
- A machine running mac OSX.
- The .0 file(s) off of your core (found in ..\LANDesk\managementSuite\ldlogon).
- The MacLegacyAgent.pkg.zip file for OS 9, 10.2.8 or 10.3.9, the 9SP2MacLegacyAgent.mpkg.zip for 10.4.11 or 10.5.8 PPC, or 10.6LegacyAgent for 10.6.x and 10.7Legacy agent for 10.7.x
- A text editor (not a word processor) to edit plist and xml files. A word processor is designed to edit documents for printing and includes a lot of formatting information that can potentially cause issues. If you are unsure about what to use then Bare Bones offers a free text editor called TextWrangler which will allow you to accomplish the steps in this article.
How do I create the mac legacy agent for my environment?
Configuring the agent can vary depending on which settings you want to change. The agent attached to this article has the default (recommended) settings however even if you choose not to change any of the settings some configuration is still required. To configure the agent take the following steps.
- Copy the .0 file(s) and the MacLegacyAgent.pkg.zip and/or the 9SP2MacLegacyAgent.mpkg.zip or any of the other agents that are available to download to a machine running mac OSX (windows will strip all the permissions from the .pkg file and render it unusable.)
- Unzip the MacLegacyAgent.pkg.zip or the 9SP2MacLegacyAgent.mpkg.zip or other agents that are available.
- Right click MacLegacyAgent.pkg or the LDMSClient.mpkg and choose Show Package Contents from the menu.
- If editing the LDMSClient.mpkg, you'll need to subsequently go to the Packages folder, right click and choose Show Package Contents on the baseagent.pkg
Configure the legacy agent to communicate with your core (REQUIRED)
- Copy the .0 file(s) into the respective /Contents/Resources folder.
- Open /Contents/Resources/com.landesk.ldms.plist in an editor.
- Using the search/find command locate ServerIPAddress and replace the <string> value with the core server FQDN or IP Address.
- Save your changes
Configure the local scheduled tasks (Optional)
- Open /Contents/Resources/ldcron.xml with a text editor.
- By default ldapm (<ldapm>) runs every 4 hours with a 30 min randomizer. Change the numbers as appropriate for your environment. Hours can also be changed to days if so desired.
- By default the inventory scanner (<ldscan>) runs every day with a 120 min randomizer. Change the numbers as appropriate for your environment. Days can also be changed to hours if so desired.
- By default the patch scanner (<ldpatch>) runs every 7 days with a 120 min randomizer. Change the numbers as appropriate for your environment. Days can also be changed to hours if so desired.
- It is highly recommended that you do not change the settings for sdclean (<sdclean>).
- After making any changes save the ldcron.xml file and close the editor.
Change the Client Configuration Name (Optional)
- Open /Contents/Resources/ldconfig.xml
- Replace <ClientConfigurationName> with the client configuration name that you desire.
- Save your changes.
Putting the mac legacy agent on your core
- After configuring the legacy agent the rename the MacLegacyAgent.pkg or LDMSClient.mpkg file to the name you desire.
- Compress the resultant file into a .zip
- Copy the newly editied .zip file to your core server(s) placing it in the ../LANDesk/ManagementSuite/ldlogon/mac folder.
How do I deploy the mac legacy agent?
The Mac legacy agent can be pushed to machines that currently have the LANDesk agent on them through software distribution or some other utility. New agents can be deployed with a custom SSH script and a command prompt; additional information regarding this script can be found in the link below. Unfortunately, you cannot push the Mac legacy agent via the LANDESK console.