Pharos Blueprint 5.1 Service Pack 3.1 Release Notes

Version 1

    This Service Pack should be applied to all machines hosting Blueprint server components, i.e. the Analyst, Collector or Administrator. This will bring the patched files up to version 5.1.8321.

    Updated Print Scout packages (version 6.4.0.825) should subsequently be distributed to all workstations and print servers hosting the Blueprint Tracker.

    The service pack can be downloaded here: Blueprint Enterprise 5.1 Service Pack 3.1

     

    Notes

    • This Service Pack includes Blueprint 5.1 Service Pack 2 enhancements and issues addressed.
    • It is recommended to use the Print Scout package shipped with this Service Pack to install or upgrade the Trackers on any workstation or print server, so you can take advantage of the new features and improvements.
    • Support Mobile Print 1.3.2 SP1 version.
    • The Toner Saving Integration supported is 3.3.2.99 or higher and OPIX.

    Enhancements

    • Added reports
      • Waste Savings Overview
      • Waste Savings by Employee
      • Mobile Print Overview
      • Mobile Print by Employee
    • Latest Lyra Database, with 18,000 printer models.
    • Toner Savings mode Monitor is redundant and has been removed.
    • Passwords in Authentication scripts can be encrypted.
    • Password field in Administrator->Device Management->Authentication Methods->Tester is obscured.
    • 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.
    • "Reportable" and "Show In Admin" properties have been added to the Employees context in Administrator.
    • "Show In Admin" property has been added to the Devices context in Administrator.
    • It is no longer necessary to restart the Collectors' "Pharos Systems TaskMaster" service after updating the License on the Analyst.
    • Changes made to allow custom reports creation.
    • 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.
    • SNMP is now used to check device status before releasing secure jobs.
    • Option added to turn off printer status check. Also, the default SNMP request timeout can be modified.
    • Blueprint can be configured to use the Pharos Page Counter or Windows exclusively for page count information.
    • Secure Release now has option to release print jobs using the "Raw" print protocol. Release Mechanism can be configured at Device model level.
    • Added directory service support for Mobile Print 1.3.2.
    • System Health e-mail notification out can be sent to multiple recipients.
    • Support added for the Mac Print Agent. The REST API Interface has to be turned on if using Mac Print Agent.
    • Meter readings and transactions are no longer mixed together in reports.
    • When devices are combined in administrator, MAC Address and Serial Number are moved to the combined device.
    • WSD printer support added to Print Scout.
    • BP Administrator can be resized, minimized, or maximized on Windows 2008R2.
    • Improved application identification when 32 bit applications print on 64 bit Windows.
    • Default tracker logging settings adjusted for improved performance.

    Issues Addressed

    This Service Pack addresses the following issues:

    • On Dashboard report, some currency values use '$', instead of the Windows Regional currency value.
    • Toner Savings Server components no longer need to be installed with Analyst and Collector.
    • Workstations randomly report large numbers of print jobs that did not happen.
    • 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.
    • Custom Reports with a lookup parameter (like Network User ID) that differs from the field used in the underlying SQL query now work.
    • Administrator crashes if the Machines context is opened after a Blueprint 5.1 SP2 or later Print Scout is installed on any Windows 8.1 Workstation or Windows 2012R2 Print Server.
    • When Secure Release is set to retain job files for more than 3 days, intermittently some job files are deleted prematurely.
    • LPR timeouts can be set to greater than 120 seconds.
    • Can delay closing of socket when printing via RAW protocol.

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

    Warning: In use Files

    Under some conditions, the upgrader may be unable to replace files because they are in use. If this happens, 
    1. Stop IIS using the command line 'iisreset /stop'
    2. Run the upgrade again.
    3. Start IIS using the command line 'iisreset /start'

    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 BP51-SP31 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 BP51-SP31 backup directory.
      • At completion the Patcher may automatically force a restart. Follow the remaining instructions after the restart.
    4. 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, SMS, etc.). 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 Clustered Analyst or Collector

    1. If updating Analyst, make sure you have an up to date backup of the psbprint and psreports databases.
    2. Ensure all nodes are showing “Up” status before proceeding. Using the Cluster Administrator, take the 'Pharos Systems  TaskMaster', 'Pharos Systems ComTaskMaster', 'Pharos Systems Event Logging Service' and 'Pharos Systems Secure Release Service' offline.
    3. 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. Using the Cluster Administrator, take the Print Spooler and 'TCP/IP Print Server' resources offline.
    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.            
      • If the Patcher requests a reboot do not do so untill step 10.
      • 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 BP51-SP31 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 BP51-SP31 backup directory.
    8. Still on active node of cluster, Open "Services". Apply the account used by the 'Pharos Systems ComTaskMaster' (Recorded in step 6.) to the 'Pharos Systems Print Agent' service. The Service pack will have replaced the 'Pharos Systems ComTaskMaster' service with the 'Pharos Systems Print Agent' service.
    9. Fail over the node. Keep the 'Pharos Systems  TaskMaster', 'Pharos Systems ComTaskMaster', 'Pharos Systems Event Logging Service','Pharos Systems Secure Release Service' resources offline.
    10. If the Patcher requested a reboot then reboot the node that Patcher.exe has just been run on (now not active)
    11. Repeat steps 3, 4, 5, 6, 7 and 8 on the second, now active node.
    12. Repeat step 9 for this node.
    13. If the Patcher requested a reboot then reboot this node (now not active).
    14. 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.
    15. Using the Cluster Administrator, delete the “Pharos Systems ComTaskMaster” resource.
    16. Using the Cluster Administrator, add a generic service resource, to control the Pharos Systems Print Agent service (same way as a Pharos Systems ComTaskMaster resource was created; on Cluster 2008 for Dependencies add Cluster Disk, Name, and Print Spooler. On the Policies tab, uncheck the setting to fail over all resources if restart is unsuccessful. On the General tab, check Use Network Name for computer name.). More detailed instructions can be found in the Installing the Tracker on a Windows Cluster Server section in TrackerDeploymentGuide.pdf located in the Deployment directory of the CD image.
    17. Using the Cluster Administrator, bring all of the Blueprint resources and the Print Spooler service online.
    18. Click the Test button on the Blueprint Server Configuration Tool.
    19. On Analyst, open the Blueprint Analyst, go to Reporting -> Publications and click on "Publish to Data Warehouse" on the toolbar.

    Updating standalone installations of the Blueprint Administrator

    1. A reboot might be required after the Service Pack is run. This is done automatically so make sure you save any open files prior to applying the Service Pack.
    2. 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.
    3. If Workstation Tracker is installed, applying the Service Pack will update this component too.
    4. 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.
    5. 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.

     

    Updating Tracker on Print Servers

    On all the Windows Print Servers where tracking is required, use the Blueprint Print Scout package contained in the Tracker directory to install or upgrade the Tracker.

    Updating Tracker on Windows Workstations

    Print Scout packages should be distributed to all workstations hosting the Blueprint Tracker, so you can take advantage of the new features and improvements.

     

    Configuring Blueprint

    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.

     

    Integrations

    VPSX Integration

    For the VPSX Integration to work with this Service Pack the following order of install has to be carried out:

    1. Install Blueprint 5.1 Server components.
    2. Install the VPSX Integration.
    3. Apply this Service Pack to all Blueprint Server components.

     

     

    Copyright © 2014 Pharos Systems International