Blueprint Enterprise 5.0 Service Pack 3 Release Notes

Version 1

    This Service Pack 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.It brings the patched files up to version 5.0.7096.

     

    The service pack can be downloaded here: BlueprintEnterprise 5.0 Service Pack 3

     

    Notes
    • This Service Pack can be applied on BP 5.0 Servers - 5.0.7078 and also on Servers with 5.0 SP1 – 5.0.7085 and 5.0 SP2 – 5.0.7085.
    • This Service Pack is a roll-up of SP1, SP2, and SP2 patches 1 to 6.
    • MobilePrint version 1.3.1 is supported with Blueprint 5.0 SP3
    • It is recommended to use the Tracker package shipped with this Service Pack to install or upgrade the Tracker on any workstation or print server, so you can take advantage of the new features and improvements.

    Enhancements

    • Support for Virtual Desktop Infrastructure (VDI) environments.
    • Support for Pharos MobilePrint.
    • Support for tracking in unauthenticated print environments: when users log into their workstations using a local machine account rather than an account validated against a central directory system. When enabled, the Tracker will prompt the user to authenticate against the central directory system and treat all jobs as having been printed by the authenticated user. If user authentication is required for print, Install or upgrade the Tracker using the updated Blueprint 5.0 Tracker package in this patch, passing the additional argument /authenticateusers on the installation command line.
    • Improved performance for Dashboard and Trends reports.
    • If the Tracker disables itself due to a fault such as running low on disk space, it will now re-enable itself when the fault clears. Note, if PretonSaver™ is also installed, and the Tracker automatically re-enables itself, PretonSaver™ will not re-enable until the next log on.
    • The Tracker has been modified to allow no passwords for unauthenticated print environments.
    • Experimental support for the EDI operation GetPharosStation3. It is suitable for use in non-production test environments only.
    • Support for the PS60 Registration Server revision 10686.
    • The Preton Tracker has been modified to allow installation on Citrix.
    • Secure Release Waste Savings Jobs are split into Manually Deleted and Automatically Purged.
    • Added Reports "Waste Savings Overview" and "Waste Savings by Employee".

    Issues Addressed

    This Service Pack addresses the following issues:

    • Slow publication due to an excessive amount of time being spent in the database stored procedure 'DailyPrintJobFilterInsert'.
    • Publication failure when Location change tracking is disabled. Indications of the issue:  
      • 'Track Changes' is set to 'No' on the Change Tracking tab on the Reporting Settings screen in the Administrator.
      • Publication to the data warehouse fails with the following error:         

        Cannot insert the value NULL into column 'BuildingId', table 'tempdb.dbo.#UserLocations ...
    • Publication failure on foreign language editions of Windows. Indications of the issue:  
      • The Windows regional settings for the system account are configured to use a decimal symbol other than '.' (period). This will be the case on foreign language editions of Windows intended for locales that don't use '.' as the decimal separator.
      • Publication to the data warehouse fails with the following error:         

        An exception occurred: Value does not fall within the expected range.
      • The log for the failed publication contains the message 'Exception caught during load'.
    • Slow inter-server communication due to delays introduced by .NET Code Access Security. Indications of the issue:            Note that this issue is only one of many possible explanations for slow system operation. However, this Service Pack can be applied to rule it out as a cause.
      • System operations are taking much longer than expected, e.g. user login at iMFPs is taking 20 seconds or longer.
      • Collector TaskMaster logs suggest that replication calls to the Analyst are taking significantly longer than the network round trip time.
    • Database timeout when publishing to the warehouse.
    • A publication appears to be stuck in progress and the 'Publish to Data Warehouse' button is permanently disabled on the Publications screen in the Blueprint Administrator.
    • Publishing very large numbers of print jobs (over 2 million jobs per day) may fail with out of memory errors.
    • Improved validation of print tracker data to ensure Pages and Sheets values are consistent.
    • Page count fails for secure jobs when user's name contains non-ASCII character(s).
    • Some workstations running the Blueprint Workstation Tracker with Toner Savings functionality hang or freeze during Windows logon.
    • Toner saving is not applied on Citrix applications.
    • A memory leak in the Tracker Authentication Service (which is part of the Task Master) causes the Task Master to use increasing amounts of memory, until it runs out.
    • A problem where the Analyst is unable to provide information to Collector.  This problem exhibits itself by all iMFPs on a Collector getting stuck on "acquiring print jobs..."  and then freezing.
    • A problem where Mobile print is unable to process some attachments of an email with a large number of attachments.  This problem exhibits itself as follows:    
      • A user submits an email with 10 attachments.
      • Some of the attachments fail, with a "resource not available" error message.
    • Note: problem may show intermittently even for emails with a single attachment.
    • Incorrect Policy Violations count in the Employee summary report.
    • Double counting of jobs when MobilePrint components are installed on a PC with a Collector.

    How to apply this Service Pack

    Warning: Blocked Files

    Depending on how this Service Pack or its files were copied to the target machine, some of the files may have been 'blocked' by Windows. Trying to update a Blueprint component with a blocked file will most likely prevent that component from working correctly. To check whether a file is blocked and/or unblock it, right-click the file in Windows Explorer and select 'Properties'.

    Updating Non-Clustered Analyst or Collector

    1. If updating Analyst, make sure you have an up to date backup of the psbprint and psreports databases.
    2. Close the Window's Printers window (if it is open). Close any Pharos applications (e.g. Troubleshooter, Blueprint Administrator) that are open.
      Note: you do not need to stop the Pharos Services. The Service Pack installer will do this automatically.
    3. Open an elevated Windows command prompt and run Patcher.exe from the command line.  No additional parameters are necessary.            
      • The Service Pack installer does not create a log file. It is recommended that you run DebugView (http://technet.microsoft.com/en-us/sysinternals/bb896647) to capture the output of the installer. This output will include error messages if the installer fails.
      • Also, the existing Blueprint files will be backed up to BP50-SP3 in the Temp directory, before they're replaced with the updated versions.
      • If the Service Pack installer fails, you can correct the cause of the error and run Patcher.exe again. Alternatively, you can contact Pharos for manual upgrade instructions, or you can manually recover the files from the BP50-SP3 backup directory.
    4. Open the Blueprint Server Configuration tool and select "File - Re-apply Settings" on the menu bar.
    5. On Analyst, Open the Blueprint Analyst, go to Reporting -> Publications and click on "Publish to Data Warehouse" on the toolbar.

    Updating Clustered Analyst or Collector

    1. If updating Analyst, make sure you have an up to date backup of the psbprint and psreports databases.
    2. Using the Cluster Administrator, take the 'Pharos Systems  TaskMaster', 'Pharos Systems ComTaskMaster', 'Pharos Systems Event Logging Service' and 'Pharos Systems Job Service' offline.
    3. Temporarily change the properties of the 'Print Spooler' and 'TCP/IP Print Server' resources – on the Policies tab, uncheck the option to fail over if restart is unsuccessful. Ensure all nodes are showing “Up” status before proceeding.  Stop the Print Spooler.
    4. On active node of cluster, close the Window's Printers window (if it is open). Close any Pharos applications (e.g. Troubleshooter, Blueprint Administrator) that are open.
    5. Still on active node of cluster, open an elevated Windows command prompt and run Patcher.exe from the command line.  No additional parameters are necessary.            
      • The Service Pack installer does not create a log file. It is recommended that you run DebugView (http://technet.microsoft.com/en-us/sysinternals/bb896647) to capture the output of the installer. This output will include error messages if the installer fails.
      • Also, the existing Blueprint files will be backed up to BP50-SP3 in the Temp directory, before they're replaced with the updated versions.
      • If the Service Pack installer fails, you can correct the cause of the error and run Patcher.exe again. Alternatively, you can contact Pharos for manual upgrade instructions, or you can manually recover the files from the BP50-SP3 backup directory.
    6. Open the Blueprint Server Configuration tool and select "File - Re-apply Settings" on the menu bar, then click Close.
    7. Fail over the node. Keep the 'Pharos Systems  TaskMaster', 'Pharos Systems ComTaskMaster', 'Pharos Systems Event Logging Service','Pharos Systems Job Service' resources offline.
    8. Stop the 'Print Spooler' Service.
    9. Repeat steps 4, 5 and 6 on the second, now active node.
    10. Using the Cluster Administrator, restore the properties of the “Print Spooler” and “TCP/IP Print Server” resources – on the Policies tab and check the option to fail over if restart is unsuccessful.
    11. Using the Cluster Administrator, bring all of the Blueprint resources and the Print Spooler service online.
    12. Click the Test button on the Blueprint Server Configuration Tool.
    13. On Analyst, Open the Blueprint Analyst, go to Reporting -> Publications and click on "Publish to Data Warehouse" on the toolbar.

    On all standalone installations of the Blueprint Administrator (with or without a Workstation Tracker)

    Note:The patcher needs to talk to the parent server of the Administrator you are updating. However, if the Administrator does not have that information (i.e. the Administrator has never been run), the patcher will prompt for the name of the parent server and TCP port information.
    1. Close the Window's Printers window (if it is open). Close any Pharos applications (e.g. Blueprint Administrator) that are open.
      Note: you do not need to stop the Pharos Services. The Service Pack installer will do this automatically.
    2. If the Workstation Tracker is also installed on the computer:
      1. Use the Tracker package included with this service pack to manually update the Tracker.
      2. Open Windows Task Manager and close the PSClientTray.exe process.
    3. Open an elevated Windows command prompt and run Patcher.exe from the command line.  No additional parameters are necessary.
      Note: The Service Pack installer does not create a log file. It is recommended that you run DebugView (http://technet.microsoft.com/en-us/sysinternals/bb896647) to capture the output of the installer. This output will include error messages if the installer fails.
    4. If the Service Pack installer fails, you can correct the cause of the error and run Patcher.exe again. Alternatively, you can contact Pharos for manual upgrade instructions.
    5. If the Workstation Tracker is installed, reboot the machine.

    Upgrading a Citrix Installation

    1. Install Preton Tracker on Citrix.
    2. Run the contained TPCustomPrintJobFilter.sql script against each psjobs database on Analyst.
    3. Policy will need to be reconfigured to avoid duplicate Policy popups, such as application name not equal to 'wfica32.exe'.

    On Print Servers:

    1. On all the Windows Print Servers where tracking is required, use the Blueprint Tracker package contained in the Tracker directory to install or upgrade the Tracker, in place of the one shipped with the original release or previous Service Packs.

    On Windows workstations:

    1. On all the user workstations where tracking is required, use the Blueprint Tracker package contained in the Tracker directory to install or upgrade the Tracker, in place of the one shipped with the original release or previous Service Packs.
    2. If user authentication is required for print, Install or upgrade the Tracker using the updated Blueprint 5.0 Tracker package in this Service Pack, passing the additional argument /authenticateusers on the installation command line.
    3. For information and special considerations pertaining to installation of the Tracker in a VDI environment, refer to the accompanying VDI Support Technote.