Pharos Blueprint 4.1 HotFix 1 Release Notes

This HotFix is compatible with Pharos Blueprint Enterprise 4.1. 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.1HF1.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 Systems TaskMaster' and 'Pharos Systems ComTaskMaster' services run on the physical nodes. (Application of the HotFix reverts both services to run as 'Local System'.)
Extract the supplied Blueprint-4.1HF1.zip into a temporary folder.
Using the Cluster Administrator, take the 'Pharos Systems TaskMaster' and 'Pharos Systems ComTaskMaster' 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 both the 'Pharos Systems TaskMaster' and 'Pharos Systems ComTaskMaster', set the startup type to 'Manual' and restore the correct domain user account.
Fail over the node. Keep the 'Pharos Systems TaskMaster' and 'Pharos Systems ComTaskMaster' 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 both the 'Pharos Systems TaskMaster' and 'Pharos Systems ComTaskMaster', set the startup type to 'Manual' and restore the correct domain user account.
Using the Cluster Administrator, bring both of the Blueprint 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.

New Features

The Workstation Tracker can now be installed on 32-bit Windows 7.

The updated Blueprint Workstation Tracker now supports installation on the following operating systems:

Microsoft® Windows 2000 (SP4 or later)
Microsoft® Windows XP (SP2 or later)
Microsoft® Windows Vista (Business, Enterprise or Ultimate)
Microsoft® Windows Server 2003 (SP1 or later) (Terminal Server)
Microsoft® Windows 7 (Professional, Enterprise, and Ultimate)

Important Note about 64-bit: The Workstation Tracker supports 32-bit only; it does not support 64-bit versions of the Windows operating system.

Note: Operating System support for other Blueprint Enterprise components (e.g. Analyst, Collector, Administrator, and Print Server Tracker) does not change with this hotfix. Please refer to the Blueprint Enterprise 4.1 documentation for more information on the supported operating systems.

Resolved Issues

Issues resolved in 4.1 HotFix 1

Jobs printed to server queues using certain drivers, including the HP Universal Print Driver, are not tracked by the Workstation Tracker on Windows Vista.
If a Collector is unable to contact the Analyst to upload a Collector data file, it will periodically generate additional redundant Collector data files until the Analyst becomes contactable again. After applying this HotFix, the Collector will generate a new data file only at the scheduled daily export time.
Newly added Windows print queues on Analyst and Collectors could lose some of their attributes, such as their share name. After applying this HotFix, new print queues will retain all their attributes including their share property.
The Server Profiler, one of the Server Tracker components, might hang or crash on a print server that is using the Ricoh Universal Print Driver.
The Analyst or Collector TaskMaster service crashes intermittently due to threading issues on virtual machines running on multi-processor hardware.
When changing the custom settings of a Lexmark Terminal on the Lexmark iMFP Configuration tab, the changes are not reflected in the Administrator. The Administrator always reverts to the default settings.
On non-English operating systems, entering international characters on the terminal configuration tab in the Blueprint Administrator might result in an error.
Some Novell-based logical printers fail to be normalized, resulting in their volume being excluded from reports.
The Tracker and/or EDI Web Service health tests fail with a '403: Forbidden' error if the 'read' or 'script' permissions are manually removed from the corresponding Blueprint virtual directory using the IIS management console.

Known Issues

You may encounter the following issue during or after application of the HotFix. If so, please follow the suggested workaround.

The HotFix fails with the error 'HotFix process completed. Files needing replacement are still in use'. To work around this issue, stop the 'Pharos Systems ComTaskMaster' and 'Pharos Systems TaskMaster' services, restart the IIS service and use the Windows Task Manager to terminate any Pharos process still running before attempting to apply the HotFix again.