Blueprint Enterprise 5.2 Service Pack 5.4: Release Notes

Document created by bheffernan@pharos.com on Mar 7, 2019Last modified by bheffernan@pharos.com on Mar 7, 2019
Version 2Show Document
  • View in full screen mode

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

Print Scout package (version 7.10.0.2548) should be distributed to all Workstations where Print Scout Secure Release printing feature will be used.

 

Notes

  • This Service Pack includes all previously released BP 5.2 Service Packs.
  • Pre-requisites required before running this Service Pack:
    1. Microsoft® .NET Framework 4.6.1.
    2. WCF HTTP Activation has to be enabled on all Blueprint Servers.
    3. Firewall on Analyst & Collectors needs to be configured to allow inbound connections on TCP port 7777.
  • Pre-requisites installed by this Service Pack.
    1. Microsoft® SQL Native Client 11. (Analyst and Administrator Only installations)

 

What's new in Service Pack 5.4

  • Print Scout Secure Release is designed to eliminate the workflow impact that network speed imposes upon remote/branch offices, enabling these locations to also participate in a Secure Release deployment, but without the printing inefficiencies of the traditional Wide Area Network. Jobs submitted through the new "Pharos Secure Printer" queue stay on the workstation and are released from the workstation; the Collector is simply notified of the print job and forwards the release request to the workstation, which then releases the job directly to the printer.
  • Print Center changes:
    • The new System Monitor tab provides indication of the overall health of the Blueprint system.
    • A new Themes tab allows you to customize the look and feel of your Print Center website, so it matches your organization’s branding.
    • Various improvements to the Event Log. For example, you can now search by server group, select events based on time zone, etc.
  • Support for MobilePrint 2.3
  • Support for running Reports against a database server using TLS 1.2.
    • Reports are modified at load time to use the SQL Native Client 11 driver installed with this service pack.

 

Limitations of Service Pack 5.4

  • SNMP check is not applied when releasing a Print Scout Secure Release job.
  • Devices that the Print Scout Secure Release jobs are released to have to support IPP or RAW release mechanisms.
  • Load Balancer environment with Print Scout Secure Release is not supported in this release.
  • Policy is not applied to Print Scout Release jobs. This will be supported in further releases.
  • To faciliate migrating from workstation to Print Center delegates, it is possible to have both Workstation and Print Center Delegates enabled. If both are enabled, then as long as a user has not set any Print Center Delegates, Workstation delegates will behave normally. Once a user sets Print Center Delegates, then any delegates that are set at the Workstation level will be ignored.However, the Print Scout is not aware of the Print Center Delegates so the workstation shows inaccurate delegate notification.
  • After Service Pack is applied, the time for the events prior to upgrade will be incorrect as the events were timestamped using local machine't time. After SP 5.4 the events are timestamped using UTC time.

 

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 Analyst or Collector

Server prerequisites - enabling Windows HTTP Activation

If you use Windows 2012 or Windows 2012 R2, the steps are:

  1. Start up the Server Manager and Add Roles and Features Wizard. Step through the wizard until you reach the Features screen.
  2. If you use .NET 4.5, expand the item .NET Framework 4.5 Features and the sub-item WCF Services. If the option HTTP Activation is not listed as installed, select it.
  3. Click Next and Install to install the feature.

If you use Windows 2008 R2 SP1, the steps are:

  1. Start up the Server Manager and under Features Summary, select Add Features.
  2. In the Add Features dialog that opens, expand the item .NET Framework 3.5.1 Features and the sub-item WCF Activation. If the option HTTP Activation is not listed as installed, select it.
  3. Click Next and Install to install the feature.

Installation Steps

  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 BP52-SP5.4 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.
    • 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).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

If Workstation Tracker is installed along the Blueprint Administrator, applying the Service Pack will NOT update the Tracker.

  1. Close the Window's Printers window (if it is open).
  2. 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.
  3. 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.
  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.

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.

 

    1. Note that the /serverlessurl option is not available for print servers

Updating Tracker on Windows Workstations

  1. Workstation Print Scouts must be upgraded to take advantage of the new Print Scout Secure Release printing functionality. To upgrade a Print Scout with Secure Release mode include the following arguments on the command line:
    /serverurl=”<hostname>” /serverlessurl=http://<hostname> OR
    /serverurl=”<hostname>” /serverlessurl=https://<hostname>
  2. On the Workstation, a windows print queue called “Pharos Secure Printer” will have been added. Use this print queue for Print Scout Secure Release print jobs.

Integrations

Pharos Print Center

For the Pharos Print Center Integration to work with this Service Pack the following order of install is recommended:

  1. Apply Service Pack 5.4 to all Blueprint server components (this can be done in stages).
  2. Upgrade Pharos Print Center to the latest version (4.1).
  3. Restart IIS (on the server where the Pharos Print Center Integration is installed).

MobilePrint

Service Pack 5.4 has added support for Mobile Print 2.3. MobilePrint 2.3 has full support for TLS 1.2.MobilePrint is NOT affected by applying Service Pack 5.4. Also, MobilePrint installed AFTER Service Pack 5.4 was applied will work with no further configuration changes.

Sentry

When TLS 1.2 is the ONLY cipher suite enabled, Sentry Base version 2.0.6.14627 or above has to be installed.

Other

Updated versions of the following integrations are included in this Service Pack.

  • Pharos Print Center
  • HP ePrint
  • VPSX

 

Any previously installed VPSX and HP e-Print Integrations will stop working once Service Pack 5.4 is applied. If TLS 1.2 is the ONLY cipher suite enabled the VPSX SRH integration will not work.

Attachments

    Outcomes