How to Update TrustPort Management Version 3.0 (or from the version 2.0 to version 3.0)
Objective:
The objective is to update the TrustPort Management server and individual clients to the version 3.0 of the product.
Requirements:
- A server with TrustPort Management server version 2.0 or 3.0 installed.
- Workstations with TrustPort Management client version 2.0 or 3.0 installed.
- The installer package of TrustPort Management server.
-
If a firewall is running on the computers, 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 account prepared for installing the client on the stations. 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:
-
Run the installer package of the TrustPort Management server on the computer where the TrustPort Management server version 2.0 or 3.0 is installed.
-
Click through the individual windows of the installation wizard. In the Upgrading TrustPort Management Server 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 updating configuration files are left intact, only binary files are replaced.
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.
-
After updating run the TrustPort Management console. Open the About menu pane where the new version of TrustPort Management should be displayed.
-
The server is now updated and remains updating of individual clients in the network.
You can follow How to Remotely Install the Client on a Specific Station procedure for updating of the remaining individual clients. Installed TrustPort Management client on a station is automatically updated to the new version during another "push" remote installation of the TrustPort Management client.
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.
-
Path to the installation file is invalid, or is placed on the network and it isn't accessible by Network Access account from the station.
-
A firewall is running blocking remote installation of the client, because some of its 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.
Related references
Main Menu
|