Overview
To provision a managed agent to endpoints, you need to create an agent management service.
If the relevant managed agent is not yet in JetPatch Agent Manager, you will need to add it before creating a service.
All configured management services are listed under their tools in Agents.
| Note: Changes to services will not affect already-deployed services. |
Create a Management Service
Navigate to: Agents → Managed Agents → Choose the relevant Agent → Services.
| Tip: You can also create a new service by duplicating and modifying an existing service. |
Configure the following sections, then click Save.
General
- Service Name
- Agent Version
- Description
Agent Configuration
The fields below are an example using ASR. Configuration varies per agent.
Any OS (Windows and Linux)
| Parameter | Description |
| CS Endpoint | ASR Server IP Address. |
| Passphrase | ASR Passphrase for authentication. |
| Role | Specifies whether Mobility Service (MS) or MasterTarget (MT) should be installed. Possible values: MS | MT. |
| Platform | Specifies the platform on which the Mobility Service is installed. VMware: for VMs on VMware vSphere ESXi/Hyper-V/Physical Servers. Azure: for Azure IaaS VMs. Possible values: VMWare | Azure. |
| Subnet Ranges | Specify the subnet segments to be used (comma-separated). Not used when ‘Use Configured IP Address’ = 0. |
| Use Configured IP Address | Select False to deploy the agent with NAT configuration. If True, the agent will not be configured with NAT after deployment. |
Windows
| Parameter | Description |
| Remove Native Agent if Installed | True: removes the ASR native agent before deploying the JetPatch agent. Note: server reboot is required after removal (vendor requirement) — deployment will not start until rebooted. Upgrade: runs an upgrade to the ASR agent and manages it via JetPatch. Available values: False | True | Upgrade. |
| Reboot Machine after Upgrade | Reboot is mandatory if the version difference since the last reboot is greater than 4. Restart occurs 2 minutes after deployment. |
| Remove ASR Agent on Removal | True: removes the ASR agent on JetPatch removal. Note: server reboot is required — the next deployment will not start until rebooted. False: unmanages the agent from JetPatch without removing the ASR agent itself. |
Linux
| Parameter | Description |
| Remove Native Agent if Installed | True: removes the ASR native agent before deploying the JetPatch agent. Note: server reboot is required after removal — deployment will not start until rebooted. Available values: False | True. |
Agent Server
If you need to complete the agent deployment by running a registration on the agent backend server (or any other script), JetPatch can do it for you.
| Field | Description |
| Select Agent Server | The agent backend server to run the script on. Must be managed by JetPatch and connected at deployment time. |
| Upload Server Plugin | Upload the appropriate plugin script file to be executed. For Windows: CMD (.bat) or VBScript. For Linux: any executable. |
| Policy Groups | Upon registration, assign the agent to a policy group. The script receives the policy groups via environment variables. Ensure the groups are already defined on the Agent server. For multiple groups, enter a comma-separated list. Leave empty to remove the existing assignment. |
| Delay Plugin Script | How long to wait after starting a newly-deployed managed agent before activating the plugin script. Allow enough time for necessary initial managed agent events to take place. |
| Comment | Optional. |
CPU & Memory Control
| Setting | Description |
| Enable Memory and CPU Control | Enables resource control (throttling) on the managed agent. |
| Keep CPU Utilization Under | If the managed agent consumes more CPU than the centrally configured threshold and is competing with other applications or agents, it is limited to the amount configured here. More information. |
| Limit Memory Consumption To | If the managed agent uses more memory than this threshold, it is restarted. If restarted twice due to memory consumption, on the third time it is stopped. More information. |
Advanced Settings
| Setting | Description |
| Automatically Start Agent upon Failure | Enables automatic restart of the agent if it fails. |
| Maximum Number of Auto Starts in a Day | If the agent fails, it will automatically restart up to the defined number of times. After reaching the limit, it will remain in failed status. |
| Log Level | Select the type of log events to record. |
When finished configuring all sections, click Save.
Comments
0 comments
Please sign in to leave a comment.