How to Upgrade TrustPort Management from Version 1.0 to Version 2.0 (previous version)
Objective:
Upgrade the server and even all clients of TrustPort Management from version 1.0 to version 2.0. Upgrade of TrustPort Management version 1.0 to version 3.0 is not supported. It's necessary to update at version 2.0 at first and upgrade to version 3.0 as a next step.
Requirements:
- A server with TrustPort Management Server version 1.0 installed.
- A workstation with TrustPort Management Client version 1.0 installed.
- TrustPort Management Server version 2.0 installation package
-
If a firewall is running on the computer, the following ports must be opened to allow communication between the server and stations. The specific ports are the following:
- allow UDP connections in both directions on port 9090,
- allow TCP connections in both directions on port 9675,
- for the management console on the server allow internal TCP connections on port 20394 (can be set to another port while installing the server), on the TrustPort Management server it is necessary to allow even outgoing connections
- allow incoming TCP connections on port 135 for RPC,
- allow outgoing TCP connections on port 139 for RPC,
- allow incoming TCP connections on port 445 for resource sharing on Windows,
- allow incoming TCP connections on port 1042 for resource sharing on Windows.
-
It is necessary to have an user accounts prepared for installing the client on a station.
The user account set for installing the client may need to be set according to the type of network:
- Installing in networks with a domain – in this case, in principle it is possible to use any domain account that has local administrator rights, ie. belonging to the local administrator group.
- Installing in networks without a domain – in this case, a domain account cannot be used. A local account must be used that belongs to the local administrator group.
Procedure:
- Uninstall TrustPort PC Security from all stations, including the TrustPort Management server, if applicable. Uninstalling can be carried out by running the file "c:\Program Files\Common Files\TrustPort\bin\uninst.exe" with the parameter /SILENT.
- Schedule to restart all stations using the command available in the console and set it to warn users of that fact. Restarting stations is not necessary if you will not be requiring to install TrustPort PC Security.
- On the computer with TrustPort Management version 1.0, remove from Windows system Scheduled Tasks the task called At with some number, such as: At1, containing the file path to the installation directory of TrustPort Management version 1.0
- On the computer with TrustPort Management version 1.0 installed run the TrustPort Management Server version 2.0 installation package.
-
Click through the individual windows of the installation wizard. In the
Upgrading TrustPort Management
window, the installed version number and also the new version number are displayed.
During the installation process, first all TrustPort Management services are stopped and then restarted. For this reason you will be logged out from the
Management console
if you were previously logged in.
During upgrading settings and policies for individual stations and groups are deleted and replaced by replacement configuration files. This is due to the fact that certain files in the new version are incompatible with those of the previous version. - At this moment you can upgrade TrustPort Management from version 2.0 to version 3.0.
Warning! Under no condition when upgrading, should users uninstall version 1.0 and install version 2.0 without deleting the previous configuration files beforehand! In such a case the program installer will not be able to distinguish the fact that a version 1.0 to 2.0 is being performed and not an updating of a 2.0 build. Without previously deleting the configuration files, TrustPort Management will not work correctly.
When upgrading TrustPort Management the following are the most common problems:
- During installation the SYSTEM account is automatically used. If you set a different Program Execution Rights account in advanced settings then this account does not exist on the station, does not have administrator rights or has the wrong password information.
- The file path to the upgrader file is not valid or it was not possible to log in from the station to the network using the Network Access account.
- A firewall is running blocking remote installation of the client, because some of the rules will not allow the request.
- In the Local Security Policy (it is placed in the Start->Control Panels->Administrative Tools menu folder) the Network access: Sharing and security model for local accounts item, that is located in the Security Settings\Local Policies\Security Options, has a different value from the Classic - Local users authenticate as themselves. In such cases the operating system blocks remote installations automatically. This applies only for computers that are not part of a domain.
- The station is not a Microsoft network client, does not have installed the Share files and printers in Microsoft networks service or does not have default administrator sharing allowed (C$, D$, ADMIN$, atd.).
- An operating system other than Windows 2000 or higher is running on the target station.
- TrustPort Management is installed on the target station that is controlled by the other TrustPort Management server.