Pharos Blueprint 5.0 Service Pack 4.1 Release Notes

Version 1

    This Service Pack should be applied to all machines hosting Blueprint 5.0 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.7109.

    Notes

    • This Service Pack includes SP1, SP2, SP3 and SP3 patches 1 to 3.
    • Any previous integrations of Mobile Print will stop working once SP4.1 is applied. You must upgrade to MobilePrint version 1.3.2 Patch2.
    • 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.
    • 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".
    • Some Brother print drivers check the printer status by sending special print jobs with no pages.  The tracker has been updated to recognise and ignore these jobs.
    • The confirmation check box that must be checked before a person can print a job that violates policy can be removed from the Policy Popup.
    • Latest Lyra Database, with 18,000 printer models.
    • Health e-mail out can be sent to multiple recipients.
    • Support Secure Release Raw printing. Release Mechanism can be configured at Device model level.
    • Check device status before releasing secure jobs. Secure jobs will be retained if the target device is not online. Device availability rules can be customized using configuration file.
    • Option added to turn off printer status check. Also, the default SNMP request timeout can be modified.
    • A copy of the SQLite database is now held in-memory by default instead of on disk. Keeping the SQLite Database in-memory will significantly improve the overall performance of the Secure Release system.

    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:      
      • 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.
            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.    
    • 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.
    • Fixes Window Spooler crashing on 64 bit Windows 7 workstations when Websense and Blueprint Workstation Tracker are both installed.
    • When Workstation Tracker is installed and Windows EnumPrinters() API is called with certain values, no printers are returned. (An issue for an AT&T internal program.) This has been fixed.
    • Secure Release no longer fails jobs that have control characters in the Job Name, which could result in Printer Queues not processing any jobs.
    • Eliminated deadlock that can occur when two terminals replicate their data at the same time.
    • Errors calculating Number of Devices and Models in the Dashboard report.

    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-SP4 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-SP4 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. Ensure all nodes are showing “Up” status before proceeding. Temporarily change the properties of the 'Print Spooler' and if installed the 'TCP/IP Print Server' resources – on the Policies tab, uncheck the option to fail over if restart is unsuccessful. Stop the Print Spooler and 'TCP/IP Print Server' resources.
    4. Stop the Windows Print Spooler Service.
    5. 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.
    6. Still on active node of cluster, open "Services" and write down the account the 'Pharos Systems ComTaskMaster' is using(Found on 'Log On' Tab.) You will need this for step 8.
    7. 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-SP4 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-SP4 backup directory.
    8. Still on active node of cluster, Open "Services" and restore the 'Pharos Systems ComTaskMaster' account. (Recorded in step 6.)
    9. Open the Blueprint Server Configuration tool and select "File - Re-apply Settings" on the menu bar, then click Close.
    10. Fail over the node. Keep the 'Pharos Systems  TaskMaster', 'Pharos Systems ComTaskMaster', 'Pharos Systems Event Logging Service','Pharos Systems Job Service' resources offline.
    11. If the Patcher requested a reboot then reboot the node that Patcher.exe has just been run on (now not active)
    12. Repeat steps 3, 4, 5, 6, 7 ,8 and 9 on the second, now active node.
    13. Repeat step 10 for this node
    14. If the Patcher requested a reboot then reboot this node (now not active)
    15. 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.
    16. Using the Cluster Administrator, bring all of the Blueprint resources and the Print Spooler service online.
    17. Click the Test button on the Blueprint Server Configuration Tool.
    18. On Analyst, open the Blueprint Analyst, go to Reporting -> Publications and click on "Publish to Data Warehouse" on the toolbar.

    Automated Deployment to Collectors

    Customers with a large number of collectors may want to deploy this Service Pack using an automated software deployment tool (e.g. IBM's Tivoli).  Note: Automated deployment is not supported for versions earlier than 5.0 Patch 9 (5.0.7082). This is because updating from an earlier version would require re-applying settings via the Server Configuration Tool. To help with this process, the Patcher can be configured to send an e-mail at the end of the patching process indicating the patching attempt's success or failure.       The configuration is held in the file Patcher.xml. Modify the file as follows:        

    1. Change the <automated> element from "false" to "true".
    2. Set to to the e-mail address you want the notification sent to.
    3. Set from to the e-mail address you want the notification to claim it was sent from.
    4. Set smtpServerHost to the FQDN of the mail server.
    5. Leave smtpServerPort alone, unless the mail server is using a non-standard port. Or you want the communication encrypted using SSL.
    6. If the mail server and its Host are configured to support SSL, you can change useSSL to "true" and smtpServerPort to the SSL port (usually 465).
    7. Set smtpUserName and smtpPassword to the user and password needed to use the mail server.
    8. If you do not want to put an unencrypted password in the Patcher.xml file, you can put the password as encrypted text into smtpEncryptedPassword. You can encrypt the password by calling Patcher.exe from the command line with the flag "/encrypt:". e.g. Assume your mail server's password is "MySecretPassword".            
      1. Open a command prompt and type in patcher /encrypt:MySecretPassword
      2. Patcher.exe will return EncryptedPassword:L9EMZX9r1CkvI8rNybP/dikf09zwBPLMfl6OMk7/nXOCgZQpaePQDoGDULN3eAbe"
      3. Set smtpEncryptedPassword="L9EMZX9r1CkvI8rNybP/dikf09zwBPLMfl6OMk7/nXOCgZQpaePQDoGDULN3eAbe"
    9. If your deployment tool will run the patcher under an account that has permission to send e-mails, then you can set useDefaultCredentials to "true" and leave smtpUserName, smtpEncryptedPassword and smtpPassword blank.

    Updating 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'.

    Updating Tracker 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.

    Updating Tracker on Windows workstations

    1. On all the user workstations where tracking is required, use the Blueprint Tracker package contained in the Deployment 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, and pass 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.

    Configuring Mobile Print 1.3.2Patch2 with Blueprint 5.0SP4.1

    1. Apply SP4.1 to all Blueprint Server.
    2. Apply Patch2 to Mobile Print 1.3.2.
    3. On the Blueprint Servers stop the 'Pharos Systems TaskMaster'.
    4. Delete the MobilePrint Plugins, typically in  C:\ProgramData\PharosSystems\Blueprint\SecureRelease\Plugins.
    5. Start 'Pharos Systems TaskMaster'.

    Turning off printer status check

    If your device does not support SNMP, the printer will be assumed to be permanently offline. It is possible to turn off/disable the status check for a device.

           To turn off printer status check, do the following on ALL Blueprint servers:

    1. Modify the GlobalConfig.xml file in the Blueprint program data directory (usually C:\ProgramData\PharosSystems\Blueprint). It is recommended that you back up the file before modifying it.
    2. Add the following line to the SecureReleaseConfig section: <DisableSnmpCheck>True</DisableSnmpCheck>
    3. Restart the Pharos Systems Job Service.

    Note: the new element <DisableSnmpCheck> added to the GlobalConfig.xml is case sensitive.

    Modifying the default SNMP request timeout

    The default SNMP request timeout is 2000ms. To modify this follow the steps:

    1. Modify the GlobalConfig.xml file in the Blueprint program data directory (usually C:\ProgramData\PharosSystems\Blueprint). It is recommended that you back up the file before modifying it.
    2. Add the following line to the SecureReleaseConfig section with the new value for the SNMP request timeout: <SnmpRequestTimeout>3000</SnmpRequestTimeout>
    3. Restart the Pharos Systems Job Service.

    Note: the new element <SnmpRequestTimeout> added to the GlobalConfig.xml is case sensitive.

    Enabling the option to remove the CheckBox from Policy Popup (if desired)

    To enable the option to remove the confirmation check box before a person can print a job that violates policy the following SQL must be run against the psbprint database:

    update PolicySettings set PolicySettingsText = replace(cast(PolicySettingsText as nvarchar(max)), '<Settings>', '<Settings NoWarningCheckbox="true">')

    Note: turning this option ON or OFF can only be done from the Database.

    Setting Cross-Server Release to use Direct Printing

    Cross-Server Release occurs when a secure print job is held on one Collector and the Terminal requesting the job be printed on communicates with a different Collector.  When this happens, the job is normally sent from the Collector that holds the job to the Terminal's Collector and then to the device.This is done because often the Collector holding the job will not be able to communicate with the device, due to firewalls, NAT, etc.If the Collector holding the jobs is able to communicate with all print devices, it is possible to configure the Collector that holds the jobs to send the jobs directly to devices requesting print. This is called "Direct Printing". To enable Direct Printing:

    1. Modify the GlobalConfig.xml file on the Collector that holds the print jobs. This file is in the Blueprint program data directory (usually C:\ProgramData\PharosSystems\Blueprint). It is recommended that you back up the file before modifying it.
    2. Add the following line to the SecureReleaseConfig section <DirectCrossServerRelease>true</DirectCrossServerRelease>
    3. Restart the Pharos Systems Job Service.