Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added section to include how to change default port

...

  • An up-to-date collector that has connected to the Virsae platform and is reachable by remote workers.
  • A copy of the silent installer.
  • Configured a group in the web portal
  • Administrator-level permissions on the machine where the client will be installed.
  • If you are wanting to use a Windows-based VSM Collector for VSM Everywhere, you will need to use a Client Gateway 2 version.

Getting What You Need

If you do not have one or any of the above-mentioned requirements, the following sections will provide instructions on how to meet these requirements.

...

See the Web Portal Configuration section to learn about configuring groups.

Getting Client Gateway 2 (If using a Window-based VSM Collector)

See this article for information on how to get and set up a Client Gateway 2 VSM Collector.

Web Portal Configuration
Anchor
WebPortalConfig
WebPortalConfig

...

You can also specify which port to connect by using a colon after the IP Address/FQDN, e.g. 192.10.10.10:6226 will specify that the VSM Everywhere client should connect to the collector on port 6226.

If no port is specified the default port of 8444 will be used.

...

Code Block
languageyml
// Command Prompt
> msiexec /i "C:\Path\To\MachineProxyAgentE_Installer.msi" /qn /norestart /L*v "C:\path\to\install.log" CGWS="192.10.10.10:6226;192.10.10.15:2662" GROUP="NZ/AUS"

//Powershell
> Start-Process msiexec.exe -Wait -ArgumentList '/i C:\Path\To\MachineProxyAgentE_Installer.msi /qn /norestart /L*v C:\path\to\install.log CGWS=192.10.10.10:6226;192.10.10.15:2662 GROUP=NZ/AUS'

Changing Communication Port Between Collector and VSM Everywhere (Optional)
Anchor
CommPort
CommPort

In order for the VSM Everywhere client to connect on a port that is not 8444, you will need to change the port that a VSM Collector listens on.

The documentation below details this process for both Linux Virtual Machine (VM) and Windows-based collectors.

Note

This configuration is unnecessary if you do not need the collector to listen in on a different port.

Changing Listening Port For a Linux-based Collector

Open a console session to a Linux VM.

Stop the VSM Client Gateway by typing the following command:


Code Block
languageyml
$sudo systemctl stop clientgateway.service


Next, type:


Code Block
languageyml
$sudo nano /opt/ADSClientGateway/ADSServiceHost.cfg

This will open up the Client Gateway configuration file.

Image Added


Find the configuration item with the key "Client Gateway Server Port"

Image Added


Update the number inside the Value tag to your required port number.

Image Added


Once all changes have been made, save the change press 'Ctrl+O' and then press 'Enter' to write out the changes. To close the 'nano' editor press 'Ctrl+X'.

Once the changes have been saved, restart the Client Gateway by entering the following:


Code Block
languageyml
$sudo systemctl start clientgateway.service


Changing Listening Port For a Windows-based Collector

Access the Windows Machine that contains the Windows-based VSM Collector

Open Notepad.exe as an administrator and then open the ADSServiceHost_UCSP_Client_Gateway.cfg file. The default path to the configuration file is C:\Program Files\Virsae Group\Client Gateway).

Search for <Key>Client Gateway Server Port</Key> and in the line below this

Change the value between the Value tags from 8444 to your required port number.

Image Added

Note

This will only work for Client Gateway version 2.