From time to time, a new GYTPOL client is released.
Once fully tested and approved for public release, you will receive a link from GYTPOL team in order to update your existing clients to a newer version.
Please see the below steps in order to auto-upgrade the GYTPOL client on your Windows Servers and Workstations.
On-Prem Deployment
Download the client files sent to you by GYTPOL team and extract the MSI files to the client updates folder located in C:\gytpol\data\WebSrv\static\updates (“C:\” can be replaced with the GYTPOL Installation folder directory)
In case you have files in that folder already, please overwrite and replace them.
Right Click on the .MSI file > Properties > Details and note the version of the client (only the first 3 numbers, without the last 0).
Navigate to GYTPOL installation folder C:\gytpol\data\Analyzer\Config (“C:\” can be replaced with the GYTPOL Installation folder directory), and open clientUpgrade.json using Notepad++ or elevated Notepad.
Please change the following:
“computers”: 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 the names of the Endpoints/Servers in the list, while keeping a json syntax (i.e commas and quotes):
“computers”: [
“pc01”,”pc02”,”srv01”,”dc02”
],
b. “links”: the URL in which the clients are downloading the new version from. Need to provide the GYTPOL server FQDN (applies only the first time the file is edited).
If you are using a Remote Employees feature, you can also add additional links from a web-facing server, such as DMZ, AWS or Azure servers. The links should be added in a json syntax:
"links": [
"https://_gytpol:9093/updates/gytpolClient_x64.msi",
"https://some-webserver.domain.com/path-to-msi.msi"
],
c. gytpolClient: The name of the client file at the end of the “link” in the URL specified on step 4.b.
■ In the initial file it appears as an example. Please change it to gytpolClient_x86/x64.msi files accordingly (marked in yellow).
■ You need to change it only for the first upgrade - after that - leave it as it is.
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).
e. “version”: the client file version you previously checked on step 2.
Remember: only the first 3 numbers (for example - 2.26.5 and not 2.26.5.0).
Please save the file.
If you are using Notepad++, please launch it in Administrator mode and save it.
Go to GYTPOL System Services and restart “GYTPOL Data Repository” service and “GYTPOL Web UI” service.
On the next client communication with the Server, your client will pull 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
Navigate to the gear icon located in the top right corner, then select "Settings," followed by "Client Updates".
Click the Plus icon in the Automated Client Update Batches section.
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.
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:
