Articles in this section

Installing The Connector Using MSI Package

Note: If you have a GPO, there is no need to fully configure the MSI (the only mandatory method is JetPatch Manager URL).

Introduction of the MSI Package

JetPatch MSI Package can do a lot of actions to easily prepare your environment in one installation.

Here is a list of what the MSI package is capable of:

Notes

Requirements

  1. Download the Connector MSI.
  2. The endpoint should have a connection to the JetPatch Manager during installation time.
  3. The configuration file should be in the same directory as the MSI installation.
  4. JetPatch API key to connect to JetPatch and download the needed files.
  5. The initiating user that installs the MSI should have administrator privileges.
  6. Make sure the Auto Intigua Distribution Tool is pointing to a correct Intigua Management Tool.

 

7. Optional: If there is a WSUS certificate located in the environment - check WSUS Certificate section. Only applicable if SSL is enabled on WSUS (required for SAAS deployments)

8. Optional: If you want to deploy the 3rd party certificate to the endpoints - check 3rd Party Certificate section. Only applicable if 3rd party patching is required.

Method 1- Prepare The MSI Package With Configuration File

When installing the Connector using MSI Installer the configuration file vlink.settings as to be downloaded and placed in the same directory as the vLink-Installer.msi. Then vLink.settings will have to be fulfilled with the following properties:

  • manager_ip_hostname - The IP or full hostname of the manager server.
  • apiuser- The username for accessing the API of the manager.
  • apikey - The API key for accessing the API of the manager.
  • prefer_ipv4 (default "no")- Prefer IPv4 communication over IPv6. yes/no.
  • wsus_ip_hostname (optional) - The IP or full hostname of the WSUS server (if not applicable, delete this line).
    • Do not add HTTP/HTTPS or 8530/8531.  This is controlled based on whether or not wsus_cert is filled out.
wsus_ip_hostname=wsus.domain.com

If wsus_ip_hostname exists, then the following configuration values are also available:

  • wsus_cert (optional) - The filename of the WSUS certificate that’s located in the JetPatch Manager (only required if using WSUS with SSL, if not applicable, delete this line)
  • wpp_cert (optional) - The filename of the 3rd party patching certificate that’s located in the JetPatch Manager (only required if using 3rd Party Patching, if not applicable, delete this line).

Example file below, with all optional values filled:

[Settings]
manager_ip_hostname=jetpatch-server.domain.com
apiuser=admin
apikey=E002374DD-13C4-4FA0-888C-4615351C60EC
wsus_ip_hostname=wsus.domain.com
wsus_cert=wsus.cert
wpp_cert=wpp.crt
prefer_ipv4=no
 

Method 2 - Prepare the MSI Package For Command Line

When installing the Connector using the command line, parameters have to be configured as a one-liner command.

  • MANAGER_IP_HOSTNAME - The IP or full hostname of the manager server.
  • APIUSER- The username for accessing the API of the manager.
  • APIKEY - The API key for accessing the API of the manager.
  • PREFER_IPV4 (optional) (default "no")- Prefer IPv4 communication over IPv6. yes/no.
  • WSUS_IP_HOSTNAME (optional) - The IP or full hostname of the WSUS server (if not applicable, delete this line).
    • Do not add HTTP/HTTPS or 8530/8531.  This is controlled based on whether or not wsus_cert is filled out.
wsus_ip_hostname=wsus.domain.com

If WSUS_IP_HOSTNAME exists, then the following configuration values are also available:

  • WSUS_CERT (optional) - The filename of the WSUS certificate that’s located in the JetPatch Manager (only required if using WSUS with SSL, if not applicable, delete this line)
  • WPP_CERT(optional) - The filename of the 3rd party patching certificate that’s located in the JetPatch Manager (only required if using 3rd party patching, if not applicable, delete this line).

Example of installation command with all optional values filled (finalized with /qn for a quiet installation):

msiexec /i vLink-Installer.msi MANAGER_IP_HOSTNAME=jetpatch-server.domain.com APIUSER=admin APIKEY=DXF8AXXA-793D-419X-88X1-61X82X8542X0 WSUS_IP_HOSTNAME=wsus-server.domain.com WSUS_CERT=wsus.crt WPP_CERT=wpp.crt PREFER_IPV4=no /qn

 

Installation

1. Prepare the vlink.settings or alternatively Prepare the command line with the right properties, based on your environment.

2. Run the MSI installation

3. Now connect to your JetPatch server and check that you can see the machine on the "Servers" page.

mceclip2.png

 

Verification and Troubleshooting

To verify the Connector was installed successfully:

  1. Check that the connector folder has been created - "%SystemDrive%:\program files\Intigua" (usually located in "C" drive).
  2. Check that the Connector service - "Intigua vAgentManager Service" (service name = "vAgentManager") is running
  3. If the coreserverurl needs to be modified, see this article.

In addition to that, the MSI is sending installation logs to JetPatch for troubleshooting purposes.

  • On end-client machine, the logs can be found in %usr_path%\AppData\Local\Temp\Intigua
  • On JetPatch server, the logs can be found in /usr/share/intigua/installation-logs folder, inside the JetPatch file-system.

For JetPatch server, the path can be changed by putting a different path to installation-logs.path property inside the intigua.properties file.

Note - After any logs upload, JetPatch will trigger a clean-up operation that will check:

  1. If the number of logs exists in the folder is more than installation-logs.clean-up.number (in intigua.properties file) - old logs will be deleted. (default = 100)
  2. If the age of existing logs is more than installation-logs.clean-up.old.days (in intigua.properties file) - they will be deleted. (default = 120)

If there are still issues, generate connector logs from the endpoint and contact the Support Team.

Related articles

Comments

0 comments

Article is closed for comments.