Prerequisites
- See article
- Make sure organizational firewalls allow HTTPS (port 443) communication from the endpoint to the JetPatch server.
You can locally install the connector on any endpoint server. This is useful for connecting endpoints that are not otherwise directly accessible to the management server (eg: endpoints behind a proxy, NAT, or SAAS deployment). There are two ways to accomplish this:
Deploy JetPatch Connector (Windows)
- Installing The Connector Using MSI Package
- Installing The Connector using EXE Package
- Installing Connector Using Domain Group Policy (GPO)
- Installing The Connector Using Microsoft System Center Configuration Manager (SCCM)
- Installing Connector Using Intune
- AWS - Installing Connector on Windows Instance
- Azure - Installing Connector on Windows Instances
- GCP - Installing Connector on Windows Instance
After that, the connector is installed and initiates communication with the JetPatch server, check that the Windows service is running:
- Service name: vAgentManager
- Display Name: Intigua vAgentManager Service
- Process name: vlinkservice64.exe
If the coreserverurl needs to be modified, see article. If there are still issues, generate connector logs from the endpoint and contact the support team.
Deploy JetPatch Connector (Linux)
- Installing the Connector Using BSX Package
- Installing The Connector Using Ansible
- Installing The Connector Using Chef
- Installing The Connector Using Puppet
- Installing The Connector Using Terraform
- AWS - Installing Connector on Linux Instance
- Azure - Installing Connector on Linux Instance
- GCP - Installing Connector on Linux Instance
After that, the connector is installed and initiates communication with the JetPatch server, check that the Linux service is running by checking the following
- /etc/init.d/intigua status
If the coreserverurl needs to be modified, see article. If there are still issues, generate connector logs from the endpoint and contact the support team.
Comments
0 comments
Article is closed for comments.