Connecting to Non-Discoverable Endpoints

You can add non-discoverable (non-vSphere, non-EC2) endpoints to JetPatch Agent Manager from either the JetPatch Manager or from the ENdpoint itself.

From the JetPatch Manager

To add an endpoint:

1. In the Servers tab, go to Server Actions > Add Physical Server:

   

2. Configure the following:

   

   • The endpoint's Hostname and IP Address
   • The endpoint's Operating System
   • Access Credentials: If the credentials to this endpoint have already been provided, you can assign them to the endpoint here. Otherwise, you can do this later.
3. Click Save.
4. Configure endpoint user accounts.

Newly-added endpoints appear in the endpoint list with the initial status of Untested. Upon first vAgent deployment or upon a manual Refresh status from the Servers tab, the connection status will be updated and JetPatch Agent Manager will attempt to install the connector on the machine.

-- 

From the Endpoint

You can locally install the connector on any endpoint server. This is useful for connecting servers which are not otherwise accessible to the management server, and also for adding the connector to a base image that will be used to spawn multiple servers later.

To install the connector on a supported endpoint:

1. Make sure organizational firewalls allow HTTPS (port 443) communication from the endpoint to the JetPatch Manager Console.
2. Copy the supplied connector file to the endpoint. Find the connector file on the Server:
   • For Windows endpoints: /usr/share/intigua/bin/vlink-win-win32_x64-<version>.exe
   • For Linux endpoints: /usr/share/intigua/bin/vlink_installer_linux_x64_<version>_Release.bsx
3. On the endpoint, run (make sure to copy all quote signs and slashes correctly):

   <connector> -coreserverurl="https://<hostIP>/vmanage-server/"

   where

   <connector> is the path and filename of the connector file executable, and

   <hostIP> is the IP address (not name) of the server host.

   For example:

   C:\vlink-win-win32_x64-Release-3.2.exe -coreserverurl="https://10.10.1.1/vmanage-server/"

   If the endpoint is already listed in the Console endpoint list, and you still need to locally install the connector (for example, there is a temporary access problem), you must add to the above command: -coreid "<ID>" , replacing <ID> with the ID displayed in the endpoint's Server core ID column in the endpoint list (some of the ID may be hidden; to get the whole string, triple-click it and copy).

   The connector is installed, and initiates communication with JetPatch Agent Manager.

1. To test that the connector has been properly installed, check that the service is running:
   • In Windows:
     • Service name: vAgentManager
     • Display Name: Intigua vAgentManager Service
     • Process name: vlinkservice64.exe
   • In Linux, run:
     • /etc/init.d/intigua status

When installing the connector as part of creating a base image, some cleanups should be made before snapshotting the base image. Stop the service, and delete the following files:

• Files in the directory where connector installation was initiated
  • post_install_log.txt
  • status.bin
  • vlink_installer_*.txt
• In Windows: C:\Program Files\..... (all log files) and in Linux: /usr/loca/intigua/.... (all log files)
  • vAgentManager/channel/status/*.txt
  • vAgentManager/log/*.txt
  • vAgentManager/PackageManager/vlink/log/connector_stdout.txt