Page Comparison

...

From time to time, a new GYTPOL client sensor is introduced.

Upon completion of thorough testing and endorsement for public distribution, the GYTPOL team will furnish you with a link to upgrade your current clients sensors to the latest version.

Refer to the steps below to facilitate the automatic upgrade of the GYTPOL client sensor on your workstations and servers.

On-Prem Deployment

1. Retrieve the client sensor files provided by the GYTPOL team and unzip the MSI files into the client sensor updates directory situated at C:\gytpol\data\WebSrv\static\updates (you can substitute "C:" with the GYTPOL Installation folder directory).

...

2. Navigate to the .MSI file and right-click on it. Then, select "Properties" and go to the "Details" tab. Note down the version of the clientsensor, ensuring to record only the first three numbers and omit the trailing zero.

...

4. Please change the following:

   1. Under the "computers" section, you can specify the list of computers you intend to update. By default, it is set to "all," which updates any client sensor reporting to GYTPOL. If you wish to update only specific clientssensors, please list the names of the Endpoints/Servers within the list while maintaining JSON syntax, including commas and quotes. For example:

...

b. Under the "links" section, you should specify the URL from which the clients sensors will download the new version. This URL should include the Fully Qualified Domain Name (FQDN) of the GYTPOL server. This step is required only the first time the file is edited.

...

c.Under the "gytpolClient" section, the name of the client sensor file at the end of the URL specified in step 4.b should be modified. Initially, it appears as an example and should be changed to gytpolClient_x86.msi for 32-bit systems and gytpolClient_x64.msi for 64-bit systems.

...

d. For updating Linux / macOS clientssensors, utilize IP addresses instead of Fully Qualified Domain Names (FQDN) in the client sensor link. Additionally, manually add Linux links to the JSON, incorporating version, clientType, and fileType parameters as shown in the example below (marked green):

...

e. Under the "version" section, input the client sensor file version obtained from step 2. Ensure to include only the first three numbers of the version (e.g., 2.26.5 instead of 2.26.5.0).

...

  "computers": [
    "all"
  ],
  "updateLinks": [
    {
      "link": null,
      "links": [
        "https://gytpol.domain.local:9093/updates/gytpolClient_x86.msi"
      ],
      "version": "2.33.6",
      "clientType": "win-x86",
      "fileType": "msi"
    },
    {
      "link": null,
      "links": [
        "https://gytpol.domain.local:9093/updates/gytpolClient_x64.msi"
      ],
      "version": "2.33.6",
      "clientType": "win-x64",
      "fileType": "msi"
    },
	{
      "link": null,
      "links": [
		"https://17.17.17.17:9093/updates/gytpol-client-1.19.1.8-77_arm64.pkg"
      ],
      "version": "1.19.1.8",
      "clientType": "mac-arm",
      "fileType": "pkg"
    },
	{
      "link": null,
      "links": [
        "https://17.17.17.17:9093/updates/gytpol-client-1.19.1.4-125.x86_64.rpm",
      ],
      "version": "1.19.1.4",
      "clientType": "linux-rpm",
      "fileType": "rpm"
    },
	{
      "link": null,
      "links": [
        "https://17.17.17.17:9093/updates/gytpol-client_1.19.1.4-125_amd64.deb",
      ],
      "version": "1.19.1.4",
      "clientType": "linux-deb",
      "fileType": "deb"
    }
  ]
}

5. Save the file once you have made the necessary modifications.

   If you are using Notepad++, please follow these steps to launch it in Administrator mode and save the file

...

6. Navigate to the System Services. Locate the "GYTPOL Data Repository" service and the "GYTPOL Web UI" service. Restart both services to apply the changes.

Upon the next client sensor communication with the server, your client sensor will automatically fetch the upgrade and undergo a silent upgrade process without requiring any intervention.

SaaS Deployment

Client update batch tasks can be applied to computer groups, which should be created before setting up the update task. To check or create a computer group, please refer to this guide: https://gytpol.atlassian.net/wiki/x/CIBUBg

1. Navigate to the gear icon located in the top right corner, then select "Settings," followed by "Client Updates".

...

2. Click the Plus icon in the Automated Client Update Batches section.

3. Enter a batch name and select the desired computer group from the list. If the group doesn't exist yet, you can create it from this screen.

4. Choose the schedule window for the batch to run:

...

ASAP: The update task will be executed by the GYTPOL Client’s hourly check-in, assuming the computer and client are active.

...

.

...

After day/time: On the next specified [day] and only after a designated [hour] within the provided time [window].

...

You should now see the newly created task in the list.

...

Monitoring Upgrade Progress and

...

Sensor Health

To track the upgrade process or validate its effectiveness, log in to the GYTPOL web portal. Navigate to the Health dashboard by clicking on the gear icon located in the top right corner of the screen. From there, you can monitor the clientssensors' health status and verify that all clients sensors have successfully upgraded to the latest version by reviewing their status on the dashboard. This allows you to ensure that the upgrade process is working as intended and that all clients sensors are running the latest software version.

...