...
With workers now having the ability and choice to work from home, VSM Everywhere (VSMe) provides customers and business partners with a tool to help monitor and diagnose unmanaged systems that are active outside of an office environment.
...
What You Will Need
Before installing the VSM Everywhere VSMe client you will need the following:
- An up-to-date collector that has connected to the Virsae platform and is reachable by remote workers or a Virsae Cloud CollectorIf you are using a Windows-based VSM Collector for VSM Everywhere, you will need to use the Client Gateway 2 version.A Virsae Cloud Collector and the URL and Port for this collector
- A copy of the VSMe silent installer.
- A VSM Everywhere profile group configured in the web portal
- Administrator-level permissions on the machine where the VSM Everywhere VSMe client will be installed.
Getting What You Need
...
- .
Configuring
...
With the introduction of VSM Everywhere, VSM customers and business partners have been given the ability to configure more than one collector under the same location.
a Cloud Collector
The VSMe client is designed to communicate with a VSM Cloud Collector. Click here for instructions on setting up an Equipment Location with the 'Appliance' type set to Virtual (Virsae Cloud).
Once a VSM Cloud Collector has been administered please contact support@virsae.com to request the URL and Port for this To set up an additional collector under a single location, simply follow the same steps that are described in this article with the new collector.
Getting the Silent Installer
Contact your VSM Administrator for a copy of the VSM Everywhere VSMe installer package.
Configuring a VSM Everywhere Profile Group
See the Web Portal Configuration section to learn about configuring profile 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.
...
...
Before a VSM Everywhere VSMe client can start tracking the performance of a system, it must first know what what metrics it needs to track. This is determined by creating a VSMe Profile group.
Go To create a Profile Group go to the Virsae Web Portal and then navigate to Service Desk > Equipment Locations > VSM Everywhere.
Customer
...
View (
...
of Equipment Locations):
Business Partner
...
view (
...
of Equipment Locations):
VSM Everywhere
...
(From Equipment Locations):
After reaching the Once you reach the Profile Groups page, you will see the following.
A profile group represents a set of tracked metrics that the VSM Everywhere VSMe client will track.
Let's To configure a profile group, click the "+" button at the bottom of the group list to begin adding a new group.
...
Enter a group name and choose which metrics you want wish to track. Once complete click the 'Add Group' button
The table below describes what each option represents.
| Field | Description |
|---|---|
| Group Name | The name of the profile group. |
| Set As Default Group | If a collector cannot find a group that is requested by a VSM Everywhere client, this is the group that will be used. |
| Performance Counter Probe Enable | Enables the Performance Counter probe. If this option is not selected, you cannot select the "Disk", "Memory", "Process", and "Processor" options. |
| Disk | Tracks the disk usage of a system. |
| Memory | Tracks the memory usage of a system. |
| Process | Tracks the ...... of a running process on the host system. |
| Processor | Tracks the CPU usage of a system. |
| Speed Test Probe Enable | Enables the Speed Test Probe, which measures ........internet performance from the host |
| Note |
|---|
A collector MUST have a default group. When you create your first group, it will automatically be set as the default. |
...
You can edit groups at any point by pressing the "Edit Group" button. All fields are editable.
| Note |
|---|
A collector MUST have a default group. As such, you can only REPLACE default groups when editing. |
You can also delete groups at any time. All groups are deletable.
| Note |
|---|
A collector MUST have a default group. As such, when a default group is deleted and another group is available, it will be set as the default automatically. |
...
After everything has been set up, to install VSM EverywhereVSMe, use the MachineProxyAgentE_Installer.msi to install via a command-line interface.
...
CGWS Argument Anchor Collector Collector
| Collector | |
| Collector |
CGWS takes a semi-colon separated list of IP addresses or Fully Qualified Domain Names (FQDNs) that represent the location of collectors that a VSM Everywhere client can connect to.
VSM Everywhere has the ability to connect to multiple collectors in case one collector is unreachable or overcapacity.
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.
...
The CGWS argument is used to specify the URL and port that the VSMe client will communicate to your VSM Cloud Collector.
Please
...
contact support@virsae.com for
...
the URL and
...
Port to use in this argument.
...
If you use the non-default port, you will need to also change the port that the collector communicates on as well.
...
in this example it is a356dhgj4g5j690f9e333a60da991.vl-beta.virsae.io:443
| Code Block | ||
|---|---|---|
| ||
// Command Prompt > msiexec /i "C:\Path\To\MachineProxyAgentE_Installer.msi" /qn /norestart /L*v "C:\path\to\install.log" CGWS="192a356dhgj4g5j690f9e333a60da991.10vl-beta.10virsae.10:6226;192.10.10.15:2662io:443" //Powershell > Start-Process msiexec.exe -Wait -ArgumentList '/i C:\Path\To\MachineProxyAgentE_Installer.msi /qn /norestart /L*v C:\path\to\install.log CGWS=192a356dhgj4g5j690f9e333a60da991.10vl-beta.10virsae.10:6226;192.10.10.15:2662io:443' |
GROUP ArgumentAnchor Group Group
| Group | |
| Group |
The GROUP argument takes the group name of a group VSMe Profile Group configured inside of a web portal. If VSM Everywhere is installed with no group name, or if the collector could not find the requested group, the default group Profile Group will be used instead.
| Code Block | ||
|---|---|---|
| ||
// Command Prompt > msiexec /i "C:\Path\To\MachineProxyAgentE_Installer.msi" /qn /norestart /L*v "C:\path\to\install.log" CGWS="192a356dhgj4g5j690f9e333a60da991.10vl-beta.10virsae.10:6226;192.10.10.15:2662io:443" 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=192a356dhgj4g5j690f9e333a60da991.10vl-beta.10virsae.10:6226;192.10.10.15:2662io:443 GROUP=NZ/AUS' |
Uninstall Command
...
| Code Block | ||
|---|---|---|
| ||
// Command Prompt
> msiexec /x "C:\Path\To\MachineProxyAgentE_Installer.msi" /qn /norestart /L*v "C:\path\to\uninstall.log"
//Powershell
> Start-Process msiexec.exe -Wait -ArgumentList '/x C:\Path\To\MachineProxyAgentE_Installer.msi /qn /norestart /L*v C:\path\to\uninstall.log' |
...
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 | ||
|---|---|---|
| ||
$sudo systemctl stop clientgateway.service |
Next, type:
| Code Block | ||
|---|---|---|
| ||
$sudo nano /opt/ADSClientGateway/ADSServiceHost.cfg |
This will open up the Client Gateway configuration file.
Find the configuration item with the key "Client Gateway Server Port"
Update the number inside the Value tag to your required port number.
...
' |
...
Once the changes have been saved, restart the Client Gateway by entering the following:
| Code Block | ||
|---|---|---|
| ||
$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.
| Note |
|---|
| This will only work for Client Gateway version 2. |