Pharos Blueprint 4.2 HotFix 1 Release Notes

This HotFix is compatible with Pharos Blueprint Enterprise 4.2. It applies to all Blueprint components.

Installation

This HotFix should be applied to all machines hosting Blueprint server components, i.e. the Analyst, Collector or Administrator. Updated Tracker packages should subsequently be distributed to all workstations and print servers hosting the Blueprint Tracker.

Applying the HotFix to a non-clustered Blueprint server

On each Analyst, Collector and Administrator machine:

Extract the supplied Blueprint-4.2HF1.zip into a temporary folder.
If the server is a Terminal Server run 'change user /install' from a command prompt.
Run the contained PharosSystems.Blueprint.Hotfix.exe.
If the server is a Terminal Server run 'change user /execute' from a command prompt.

Use the Blueprint Administrator to create an install or upgrade package containing the new Print Tracker components.
Distribute the Tracker package using your usual software distribution mechanism.

Applying the HotFix to a clustered Blueprint server

This section outlines special instructions for applying this HotFix to a Blueprint Analyst or Collector installed on Microsoft Cluster Server.

Before starting, note the domain account under which the Pharos Services - 'Pharos Systems TaskMaster', 'Pharos Systems ComTaskMaster', 'Pharos Systems Event Log Service’, and 'Pharos Systems Job Service' run on the physical nodes. (Application of the HotFix reverts Pharos Systems services to run as 'Local System'.)
Extract the supplied Blueprint-4.2HF1.zip into a temporary folder.
Using the Cluster Administrator, take the 'Pharos Systems TaskMaster', 'Pharos Systems ComTaskMaster', 'Pharos Systems Event Log Service’, and 'Pharos Systems Job Service' resources offline.
Run PharosSystems.Blueprint.Hotfix.exe on the active node. When the Server Configuration Tool (SCT) appears, click the Apply button.
Open the Services Manager on the active node. For the 'Pharos Systems TaskMaster', 'Pharos Systems ComTaskMaster', 'Pharos Systems Event Log Service’, and 'Pharos Systems Job Service', set the startup type to 'Manual' and restore the correct domain user account.
Fail over the node. Keep the 'Pharos Systems TaskMaster', 'Pharos Systems ComTaskMaster', 'Pharos Systems Event Log Service’, and 'Pharos Systems Job Service' resources offline.
Run PharosSystems.Blueprint.Hotfix.exe on the second, now active, node. When the SCT appears, click the Apply button.
Open the Services Manager on the active node. For the 'Pharos Systems TaskMaster', 'Pharos Systems ComTaskMaster', 'Pharos Systems Event Log Service’, and 'Pharos Systems Job Service', set the startup type to 'Manual' and restore the correct domain user account.
Using the Cluster Administrator, bring all the Pharos systems resources online.
Click the Test button on the Server Configuration Tool.
Use Blueprint Administrator to create an install or upgrade package containing the new Print Tracker components.
Distribute the Tracker package using your usual software distribution mechanism.

Resolved Issues

Issues resolved in 4.2 HotFix 1

The Pharos Systems TaskMaster service and/or SQL Server service consume 100% of the CPU when Policy Print is enabled.
Jobs printed to server queues using HP or Konica Minolta Universal Print Drivers are printed in spite of policy cancellation on the workstation.
The Pharos Systems Job Service and Pharos Systems Task Master service leak memory under heavy, sustained Secure Release Here load.