Upgrading Trackers

Trackers are upgraded using upgrade packages. These are created and deployed in the same way as standard install packages (refer to the “Blueprint Installation Guide”). Simply select the Upgrade action instead of Install when creating a package.

When creating an upgrade package, you should also create new installation and uninstallation packages. The new installation package should be used for new workstations.

Handling New and Existing Workstations

A Tracker upgrade package will only perform an upgrade. If the Tracker is not already installed, the upgrade package will exit without installing the Tracker.

To handle the scenario where existing workstations need to be upgraded and new workstations need to be installed, you will need to ensure that the original installation package is still deployed to any new workstations (e.g. if you have created a deployment package in SMS). The installation package should be pushed to the new workstation before the upgrade package is pushed.

Alternatively, a new combined deployment package could be created. The package would check for the presence of the Tracker. If a Tracker is not detected, the Tracker installation package is used. If a Tracker is detected, the Tracker upgrade package is used. Both the Tracker installation and Tracker upgrade packages should be of the same version. Use a deployment tool (e.g. SMS) to ensure that the combined deployment package is run only once on each workstation; otherwise, the deployment package will constantly attempt to upgrade a workstation.

To detect if a Tracker is already installed, you can:

  • Check the Windows services for a “Pharos ComTaskMaster” service.
  • Check the registry for the key: HKEY_LOCAL_MACHINE\Software\PharosSystems\InstalledComponents\Tracker

Note: For 3.1 and 3.2 Trackers, you can detect that a Tracker is installed by checking the registry
HKEY_LOCAL_MACHINE\Software\PharosSystems\InstalledComponents\3100

Upgrading Trackers on Cluster

The following are the steps required when upgrading a clustered 3.5 Release 2 Print Server Tracker to Blueprint 4.2:

  1. Using the Cluster Administrator, take the “Pharos ComTaskMaster” resource offline.
  2. Open the Services Manager on the first node and record the domain account that the “Pharos Systems ComTaskMaster” is running under. It is assumed that you know the password for this account.
  3. Run the upgrade package on the first node.
  4. Open the Services Manager on the first node and select the “Pharos Systems ComTaskMaster” service. Change the startup type to “Manual” and configure the logon account back to the domain account recorded in step 2.
  5. Fail over the cluster to the second node.
  6. Run the upgrade package on the second node.
  7. Open the Services Manager on the first node and select the “Pharos Systems ComTaskMaster” service. Change the startup type to “Manual” and configure the logon account back to the domain account recorded in step 2.
  8. Using the Cluster Administrator, bring the “Pharos ComTaskMaster” resource back online.