--- title: "Blueprint Enterprise 5.3 Update 1: Release Notes" slug: "blueprint-enterprise-53-update-1-release-notes" updated: 2024-06-19T20:20:25Z published: 2024-06-19T20:20:25Z canonical: "kb.pharos.com/blueprint-enterprise-53-update-1-release-notes" --- > ## Documentation Index > Fetch the complete documentation index at: https://kb.pharos.com/llms.txt > Use this file to discover all available pages before exploring further. # Blueprint Enterprise 5.3 Update 1: Release Notes This update 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.3.10546.** Print Scout package (**version 7.14.0.2990**) should be distributed to all Workstations where Serverless Printing feature will be used. ## **What's new in 5.3 - Update 1 Release** - Policy Print UI moved from Silverlight to Electron. Allowing screen readers to be used with Policy Print. - New Logon Roles (e.g. "Manage Devices", "Manage Event Log") have been added. - Audit Log of logons by administrative staff. - New Health test that sends warning 30 days before Blueprint license is due to end. - Email + PIN authentication. ### Limitations - If "Integrated Security" is used to connect to MS SQL, the Print Center won't work after applying this release. To fix, set the **Pharos** **ASP.NET** **v4.0** App Pool in IIS to use an account that has MS SQL permissions. Refer to the "New Features" document in the Pharos Community for more information. ### Notes - The built-in account is now the only logon that can use username and password. This upgrade will remove any other logons that use username and password. - All other logons must use domain authentication, i.e., you must specify the domain and network ID for each user who will have permission(s) to manage Blueprint. Alternately, instead of creating logons for individual users, you can assign Blueprint roles to Active Directory Groups and allow users to inherit Blueprint management permissions via their group memberships. ## How to apply this Update ### Warning: Blocked Files Depending on how this update 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 all the Application Pools in IIS. 2. Run the upgrade again. 3. Start all the Application Pools after the patcher succeeds. ### **Updating Analyst or Collector** #### Installation Steps 1. If updating Analyst, make sure you have an up to date backup of the psbprint database. 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 update 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 update installer does not create a log file**. It is recommended that you run DebugView ([http://technet.microsoft.com/en-us/sysinternals/bb896647](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 **BP53 in the Temp directory**, before they're replaced with the updated versions. - If the update 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 update 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 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 with the Blueprint Administrator, applying the update 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 update installer does not create a log file**. It is recommended that you run DebugView ([http://technet.microsoft.com/en-us/sysinternals/bb896647](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 update is run. This is done automatically so make sure you save any open files prior to applying the update. 4. If the update 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. ## Integrations ### MobilePrint MobilePrint is NOT affected by applying this update. Also, MobilePrint installed AFTER update is applied will work with no further configuration changes. MobilePrint 2.2.1 does not support TLS 1.2 and will not work if TLS 1.2 is the only cipher suite enabled. The latest version of MobilePrint 2.3 has full support for TLS 1.2. ### Other Updated versions of the following integrations are included in this update. - Apple Airprint - HP ePrint - MobilePrint - Pharos Print Center - VPSX ### VPSX, HP ePrint, and Apple UTF-8 Integration - Any previously installed version of these Integrations will stop working once the update is applied. After applying this update, you will need to re-install the integration using the version included with this Update. i.e. replace the deployed DLLs with the new versions. If TLS 1.2 is the ONLY cipher suite enabled the VPSX SRH integration will not work. ## Related - [Pharos Blueprint 5.3 Update 5 Release Notes](/pharos-blueprint-53-update-5-release-notes.md) - [Pharos Blueprint 5.3 Update 4 Release Notes](/pharos-blueprint-53-update-4-release-notes.md) - [Pharos Blueprint 5.4 - Update 3 Release Notes](/pharos-blueprint-54-update-3-release-notes.md) - [Pharos Blueprint Enterprise 5.3 Update 3](/pharos-blueprint-enterprise-53-update-3.md) - [Pharos Blueprint 5.4 - Update 1 Release Notes](/pharos-blueprint-54-update-1-release-notes.md)