Agent Deployment for Ivanti Endpoint Manager and Endpoint Security
Standard Push: The agent files are located on the core server and distributed via a push task. The credentials used in the Scheduler configuration on the core server are critical for this type of distribution.
- Self-Contained Executable: Agent files are compiled into a completely self-contained executable that is portable. This method is efficient and helps with a lot of network configurations however the executable does not get updated when the configuration changes or when files are updated by patches or new releases. It is recommended to keep these executables in a central location and perhaps date them as well so that they can be rebuilt as needed. Two self-contained executables are created for this option one with status (shows GUI to the user) and one without.
- Advance Agent: The primary purpose of this agent deployment method is to control the amount of bandwidth used during agent install. However, the design has many other uses. The agent is broken up into two files (and MSI and an EXE). The MSI will install a temporary service on the client where it will gradually stream down the main executable and install the agent. The temporary service is removed. Since the temporary service comes in MSI form this design also makes it favorable for deployment using an Active Directory login script. (Note: Including security definitions with the agent can make the primary executable very large and greatly increase agent download/install times)
- Wscfg32.exe: This is an executable located on the core server in the ldlogon sub-folder, by default located (C:\Program Files\LANDesk\ManagementSuite\ldlogon). When executed on a client, it will pull the settings in a default windows configuration and launch an agent install window. Changes can be made to the configuration before starting the agent install.
Other Operating System Information: Macintosh and Linux/Unix agents will work somewhat different than Windows based ones. For details on those agents please check their component landing pages.
General Troubleshooting Recommendations:
The LANDESK agent (just like any other program) can be affected by Anti-virus, Spyware, and other blocking programs. Closing or suspending such programs may help with agent installation. When right-clicking on an agent two of the options will be "Schedule agent deployment" and "Schedule update to agent settings". The difference between these two is that the update will not deploy any files and only make changes to when scan run etc. If a new feature is added to the configuration or removed then a full agent deployment will be required. If an error occurs during the creation of the agent (advance agent or self-contained) a log file is generated. Typically the agent configuration was told to include a certain file and the process either couldn't find the file or didn't have access to it.
Notice: Any E-Learning content is available by default to Members who have a minimum support agreement at the Professional level.