To be able to provision a managed agent to endpoints, you need to create an agent management service. If the relevant managed agent isn't yet in JetPatch Agent Manager, you will need to add it before creating a service.
All configured management services are listed under their Tools under Policy and Tools
You can Edit the configuration of existing management service, or Delete an existing service.
Changes to services will not affect already-deployed services.
To create a management service:
Go to: Policy and Tools > Choose the relevant Tool, Go to Services.
** You can create a new service or duplicated and modify an existing service by clicking on
Configure the following:
- Enter Service Name, Select agent version, Description
- Enter OS Infomation:
- Service Port: The port must be a valid TCP port (a number between 1 and 65535 inclusive)
- Remove native agent if it's installed: Indicate if you would like the native agent to be removed.
- Provisioning API Key: A provisioning key must be specified to provision the host during installation
- Collector Host Name or IP Address: Hostname/IP Address of the Agent Collector service
- Windows configuration
- CS Endpoint: ASR Server IP Address.
- Passphrase: ASR Passphrase for Auth.
- Role: Specifies whether Mobility Service (MS) should be installed or MasterTarget(MT) should be installed. Possible Values - MS | MT
- Platform: Specifies the platform on which the Mobility Service is getting installed - VMware : use this value if you are installing mobility service on a VM running on VMware vSphere ESXi Hosts, Hyper-V Hosts and Phsyical Servers - Azure : use this value if you are installing agent on a Azure IaaS VM Possible Values: VMWare | Azure
- Subnet Ranges: Specify the subnet segments that should be in used (comma separated). This range won't be used when 'Use Configured IP Address' = 0.
- Remove native agent if it's installed:Select True in order to remove ASR native agent in order to deploy the JetPatch agent. Please note that after the removal of the ASR agent, the server should be rebooted (requested by vendor). In case that a native agent is exist, and selected "True", it will be removed, but the deployment of ASR wont start on the endpoint server until the server will be rebooted. Select Upgrade in order to run an upgrade to the ASR agent and to manage it by JetPatch. Available parameters False/True/Upgrade.
- Reboot Machine after Upgrade: Reboot is mandatory if the difference between agent version during last reboot and current version is greater than four (4). Restarting is 2 minutes after deployment
- Use Configured IP Address: Select False in order to deploy the agent with NAT configuration. Selecting True, after deployment the agent will not be configured with NAT configuration.
- Remove ASR agent on removal: Select True in order to remove the ASR agent using JetPatch removal operation. Please note that after the removal of the ASR agent, the server should be rebooted (requested by vendor). In case that selected "True", it will be removed, but the next deployment of ASR wont start on the endpoint server until it will be rebooted. Select False in order unmanage the agent by JetPatch. Using False the ASR will not be removed, only the JetPatch management will be removed from the agent.
- Linux configuration should
- Configure Firewall Rules: Would like to configure firewall rules, Select " True or Fales
- Instance Type: Select the instance type, the default type is host
- Use Proxy Settings: Use 0 for direct Proxy connection or 1 for http proxy from Linux environment variables or specified proxy URL
- Select Agent server: The server must be connected
- Upload server plugin: Here you can upload the appropriate plugin script file to be executed. Choose any extension for Linux server, .bat or .vbs for Windows
- Policy groups: Upon registration assign the Agent to a policy group.
Make sure the policy 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. Make sure to allow enough time for necessary initial managed agent events to take place.
- Comment: Optional
CPU & Memory Control
- Enable Memory and CPU Control Enables resource control (throttling) on the managed agent.
- Keep managed agent CPU utilization under If the managed agent consumes more CPU than the centrally configured threshold, and is competing with applications or other agents for CPU resources, the managed agent is limited to the amount of CPU configured here.
- Limit managed agent memory consumption to: If the managed agent uses more memory than this threshold, the managed agent is restarted. If the managed agent has been restarted twice due to memory consumption, on the third time it is just stopped.
- Automatically start agent upon failure
- Maximum number of auto starts in a day: If the agent fails it will continue to automatically start for the number of times that is defined here, after reaching the number defined it will remain in failed status.
- Log level: Select type of Log event