Propalms TSE 7 Upgrade
Please read this document in its entirety BEFORE performing an upgrade.
View the table below to see if your current version of TSE is upgradeable to the most current Propalms TSE version 7.0
| Upgrade Paths | |
| Current Version | Upgrade Available |
| Tarantella SGD 4.0 | NO |
| Propalms TSE 4.1 | NO |
| Propalms TSE 5.0 | NO |
| Propalms TSE 6.0 | NO |
| Propalms TSE 6.5 | YES (All Builds Supported) |
There are no direct upgrade paths available from Propalms TSE (Canaveral IQ) 1.5 or 2.1, 4.0, 4.1, 5.0 or 6.0 to the current version 7. To upgrade from Propalms TSE 5.0 or 6.0 to Propalms TSE 7 you have the below options:
A) Upgrade from v 5.0 to v 6.0 to v6.5 and then upgrade to the Propalms TSE 7.0 software.
B) Do a complete new install of Propalms TSE 7.
Licensing
When upgrading from one of the earlier versions of TSE (Propalms TSE v6.5), new v7 license keys are required. Ensure that you have TSE 7.0 keys ready before attempting an upgrade. These keys can be obtained from Propalms. Your maintenance renewal must be current in order to upgrade to the new version. All customers that have a valid product maintenance contract are entitled to free upgrade keys for the current version.
Customers need to mail the below information to: keys@propalms.com
1) Base Key.
2) Complete company information.
3) Contact details including valid email address.
Have your TSE v7 key ready before starting the upgrade as it needs to be entered during the upgrade process.
Once the upgrade is complete you can re-activate your base key by visiting the following URL: http://www.propalms.com/supportarea/activatekey.html
Important steps before and during upgrade process
IMPORTANT: If your TSE servers including the one which hosts your primary and backup Propalms Database are Windows 2003, 2008 /R2 with SP1/SP2, make the following changes to the DTC settings, servers before carrying out the upgrade (the settings should already be in place if TSE v6.5 is installed and running but moreover it is a good practice to re-confirm before an upgrade). You should ensure these settings are configured on all Propalms TSE Servers including the database server if this is running on another server.
MSDTC Settings:
Open Component Services > Select My Computer > Right click My Computer icon > Select Properties > Select MSDTC tab > Click Security Configuration button and ensure the following options are selected:
Windows 2003
Windows 2008 / Windows 2008 R2
.NET Prerequisite for TSE 7:
This should already be in place as part of TSE v6.x Web role installation.
Propalms TSE servers running the Web role needs .Net framework to be installed prior to upgrading to TSE v7. This is needed for the TSE Console Dashboard page to work on the Propalms TSE Management Console portal. If .Net framework is not installed the Dashboard page in the TSE Console will not work.
The minimum version required is v2.0. It’s also important to ensure that it is enabled and configured in IIS as shown below...
If there is an older version of .Net framework previously installed on the server, one needs to make sure that the latest version of .Net is associated in IIS
1. Clear all Internet Explorer cache, temporary files, and also downloaded installation folders from the Downloaded installations (C:\WINDOWS\Downloaded Program Files) folder on the TSE Web server being upgraded.
2. Do not have SSL enabled on the Depot folder of the servers in your team holding the TSE Web role. Check this using the IIS administrator tool from your web server. If you are implementing SSL for TSE then the Depot folder should not have SSL enabled. Doing so causes problems with application icons not displayed correctly and can cause issues with applications launches and client and install file downloads.
3. Do not have any MMC snap-in tools running while performing the upgrade (Example: Services, Component services, Active directory)
4. We recommend running the upgrade logged into the server as the Propalms TSE Identity account. This is the Domain/local user account under which the Propalms Services run.
5. Make sure that all servers have a "Success" connection status with the primary and backup database in Console > Monitor > Database Connections page. Before starting the upgrade, ensure all TSE Console web sessions are closed. There should be no active TSE Application sessions running on any of the TSE APP servers and all Launchpad Web page sessions should be closed by TSE Users.
6. Stop Propalms TSE services and Propalms COM+ Applications on the TSE server being upgraded before starting the manual upgrade of the Primary TSE Web server. Once the manual upgrade of TSE WEB server is finished, reboot the server, this is Mandatory for the upgrade to finish. Once the upgraded WEB server is restarted, other TSE servers in the team will start the process of AUTO Upgrade.
7. The Web server should be the first server in the team to be upgraded. If you have more than one web server in your team then pick one, do not upgrade both at the same time. Once the primary TSE Web server upgrades, it will prompt for a reboot. Reboot the server immediately. This is Mandatory for the Auto- upgrade of other servers to start.
8. Once the TSE Web server is upgraded it will "push" out the updates to the other (all servers except DMZ-SPR) TSE servers in the team. DO NOT run TSE v7 MSI manually on any other server in the team. Once the main TSE WEB server reboots, Log on to the Propalms Management Console of the upgraded Web Server and you should see other servers as Marked for Upgrade. Each server that gets upgraded should be rebooted. Depending on the roles that TSE server had prior to upgrade, it may or may not prompt for reboot. But in all cases after the server gets upgraded, the server should be restarted. After reboot, the best way to find out if the server has upgraded is to check the status in Console if it changes from "Marked for upgrade" to "Upgrading" to "Upgraded" and on reboot is should say "Installed" status.
9. The DMZ-SPR server has to be manually upgraded. Once the Propalms team is fully upgraded, run the v7 DMZ install MSI on the DMZ server and it should walk through the upgrade process. Reboot the DMZ server once upgraded.
10. Make sure there are no backups scheduled to run or virus scans taking place while performing the upgrade.10. Make sure there are no backups scheduled to run or virus scans taking place while performing the upgrade.
11. In order to take advantage of all new TSE v7 features and enhancement , Propalms TSE Connection manager (PCM) or also commonly called as 'Propalms Client' should be upgraded to PCM 7.0.0.0 on all client machines. After Propalms TSE Web server is upgraded to TSE 7.0, enable the 'Client Upgrade Notification' setting in TSE Console-Options-User, page for all client machines to be notified about the newer v7 client. End users may choose to upgrade their clients to the new v7 or do it at a later time. Their existing v6.5 clients will continue to work with TSE v7 Server after upgrade.
12. The older PCM 6.5.x.x will still be supported to launch applications on TSE v7 upgraded team. Although some of the new features in v7 may not be available with older version clients.
For more information on TSE v7 features or upgrade refer to the TSE Admin, User and Install guide included with the installation files folder. These v7 guides are also available on the Propalms portal. You may log any questions related to TSE on our Support portal at at https://support.propalms.com
Upgrading to Propalms TSE 7
IMPORTANT !!!: Always take a back-up of the Propalms Database before upgrading.
1. Ensure that the Propalms Identity COM+ account (referred to as "Propalms Identity" in TSE v7 install doc) is a local administrator on all the TSE servers and the database servers hosting the primary and secondary Propalms Database.
2. Avoid having Console or Launchpad browser sessions open when doing the upgrade. It's recommended to have Windows UAC turned off when doing the upgrade.
3. Stop Propalms TSE services on the main Propalms Web server which will be upgraded to TSE 7.
4. Shutdown all Propalms COM+ Applications from Component Services Snap-in
Go to Start-RUN, type> dcomcnfg to open Component Service, click on Running process as seen in screen shot and right click and say Shutdown. If you receive an error when trying to shutdown COM+ apps then you can try killing the processes relating to apps from Task Manager by finding matching Process IDs.
5. The other TSE Servers in the team may either be powered off or Propalms Services stopped or kept running while the TSE WEB server is being upgraded. The key is to not have any TSE Console, Launchpad or new Applications being launched while the upgrade is in process.
6. Start the upgrade process by starting the Propalms TSE v7 Installer. We highly recommend starting the TSE install by right clicking the Propalms-TSE.exe and choosing the Run as Administrator option. Ignore the Error "Unable to identify a server with TSE Web role". This will be shown if you have closed down all Propalms Services.
7. The installer detects a previous version of TSE and prompts to stop all TSE services before proceeding.
8. When prompted enter your TSE 7 base key you have been provided.
9. Propalms Com+ Identity Domain user account can be changed if required but we recommend not to change it unless absolutely necessary.
10. At this point, the Propalms Database will be upgraded, if you have not taken a backup of the database yet, it is highly recommended that it is taken. Propalms DB will be permanently modified once Next is clicked.
11. You should see a confirmation showing that the database has been upgraded. Now the installation will proceed with upgrade of TSE Files and components on the server.
NOTE: Propalms DB Upgrade is the most critical aspect of the Upgrade. Once DB is upgraded to v7, even in the instance of upgrade failing during file upgrades, all TSE servers can be upgraded to v7 by doing a clean install of TSE v7 using the RESTORE Server option in TSE v7 Install scheme. None of the TSE configuration, like Apps, Users, and Servers etc. is lost.
12. Role upgrade will start with installation of WEB and other TSE Roles.
13. A final confirmation of TSE Upgrade installation completing is displayed. It's important to restart the server immediately to complete the upgrade process and start the auto upgrade process of other servers in the team.
14. Once restarted, login to TSE v7 Console portal. Go to Manage > Servers. AUTO upgrade of other servers that are marked as "Marked for Upgrade" in the team will start. Power on the servers if they were powered off or start the Propalms Services if they were manually put in the stop state to kick start the upgrade process. You may choose to do this one server at a time to track the upgrade on each server individually or start servers/services on all TSE Servers to force upgrade on all servers simultaneously. It roughly takes 10-15 mins for each server to complete the upgrade process.
Once the TSE Engine service is started the install status for the server should change to "Upgrading" as shown. The server goes into "Upgraded" install status once it finishes the upgrade process.
The TSE server that completes the upgrade will be automatically restarted if it has the TSE APP role . After restart their install status will show as "Installed". This confirms that the upgrade process completed on that server. Other servers running WEB/LB role will briefly show the status as 'Upgraded' and then change their status to 'Installed'. If the server which is powered on and has its Propalms service running does not go in to the "Upgrading" stage or stays in the "Upgrading" stage for a long time , in this case try manually restarting the server . If the server comes up as its install status as "installed" after the reboot, indicates that the server upgraded but for some reason was not able to initiate the auto restart.
15. In an event the upgrade fails on any of the TSE servers, you can force a manual upgrade of the server by carrying out a Propalms TSE Restore server process using the TSE 7 installer. With Propalms TSE Restore none of the TSE configuration information like Apps, Roles are lost for the TSE server. The TSE server is recreated with TSE 7 files using the config information for the TSE server in Propalms Database.
For more information please refer to the Install Guide
