Page Comparison

...

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

Once fully tested and approved Upon completion of thorough testing and endorsement for public releasedistribution, you will receive the GYTPOL team will furnish you with a link from GYTPOL team in order to update upgrade your existing clients to a newer current sensors to the latest version.

Please see Refer to the steps below steps in order to auto-upgrade to facilitate the automatic upgrade of the GYTPOL client sensor on your Windows Servers workstations and Workstationsservers.

On-Prem Deployment

1. Download Retrieve the client sensor files sent to you provided by the GYTPOL team and extract unzip the MSI files to into the client updates folder located in sensor updates directory situated at C:\gytpol\data\WebSrv\static\updates (“C:\” can be replaced you can substitute "C:" with the GYTPOL Installation folder directory).

...

In case you have files If any files already exist in that folder already, please proceed to overwrite and replace them with the newly downloaded files.

2. Right Click on Navigate to the .MSI file > Properties > Details and note and right-click on it. Then, select "Properties" and go to the "Details" tab. Note down the version of the client (sensor, ensuring to record only the first 3 three numbers , without the last 0)and omit the trailing zero.

...

3. Navigate to the GYTPOL installation folder directory, typically located at C:\gytpol\data\Analyzer\Config (“C:\” can be replaced with the GYTPOL Installation folder directory), and open you can replace "C:" with the actual installation folder path). Then, open the file named clientUpgrade.json using Notepad++ or Notepad with elevated Notepadprivileges.

4. Please change the following:

   1. “computers”: Under the "computers" section, you can specify the list of computers you are updating. The default setting is “all” and it will update any client that will report to GYTPOL. In case you want to update only a certain list of clients, please write intend to update. By default, it is set to "all," which updates any sensor reporting to GYTPOL. If you wish to update only specific sensors, please list the names of the Endpoints/Servers in within the list , while keeping a json syntax (i.e maintaining JSON syntax, including commas and quotes). For example:

“computers”: [

“pc01”,”pc02”,”srv01”,”dc02”

],

b. “links”: Under the "links" section, you should specify the URL in from which the clients are downloading sensors will download the new version from. Need to provide the GYTPOL server FQDN (applies . 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).

If you are using a utilizing the Remote Employees feature, you can also add include additional links from a web-facing server, such as servers like DMZ, AWS, or Azure servers. The Ensure these links should be added in a json syntaxare added using JSON syntax. For example:

"links": [

      "https://_gytpol:9093/updates/gytpolClient_x64.msi",

"https://some-webserver.domain.com/path-to-msi.msi"

        ],

c. gytpolClient: The Under the "gytpolClient" section, the name of the client sensor file at the end of the “link” in the URL specified on in step 4.b.■  In the initial file should be modified. Initially, it appears as an example . Please change it and should be changed to gytpolClient_x86/.msi for 32-bit systems and gytpolClient_x64.msi files accordingly (marked in yellow).■  You need to change it only for the first upgrade - after that - leave it as it isfor 64-bit systems.

After the initial upgrade, it should remain unchanged.

d. Linux clients update: please use IP address instead of the FQDN in the client link.■  Linux links should be added manually to the json according to the example below, including the version, clientType and fileType (marked in green).For updating Linux / macOS sensors, utilize IP addresses instead of Fully Qualified Domain Names (FQDN) in the 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. “version”: the client file version you previously checked on step 2. Remember: only the first 3 numbers (for example - Under the "version" section, input the sensor file version obtained from step 2. Ensure to include only the first three numbers of the version (e.g., 2.26.5 and not 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

...

5. the file

...

6. Go Navigate to GYTPOL the System Services and restart “. Locate the "GYTPOL Data Repository” " service and “the "GYTPOL Web UI” " service.

...

6. Restart both services to apply the changes.

Upon the next client sensor communication with the Serverserver, your client sensor will pull automatically fetch the upgrade and silently upgrade itself.

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

...

undergo a silent upgrade process without requiring any intervention.

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

...

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 time: Only after a designated [hour] and within the provided time [window].

• 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.

...

Validating client upgrade

Once the clients are upgraded, login to the GYTPOL web portal and review the clients health status under Health dashboard and make sure all clients are upgraded to the latest version:of the screen. From there, you can monitor the sensors' health status and verify that all 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 sensors are running the latest software version.

...