Pharos Blueprint 5.5 Sentry Print Service Patch 2604.1607.829

  • Published on May 20, 2026
  • 3 minute(s) read
Prev Next

Important Notes:

  • This Patcher updates the Sentry Print Service previously installed by Blueprint 5.5 or previous Sentry Print updates for Blueprint 5.5. It cannot be applied with earlier or later versions of Blueprint.

  • It is not able to install a Sentry Print Service on an Analyst or Collector where a Sentry Print Service was never installed as part of Blueprint.

  • As Blueprint 6.0 was released before this patch, after applying this patch, upgrade to 6.0 is not supported. Upgrade to Blueprint 6.1 is supported.

The component included in this update is:

Component

Version

MSI Version

Sentry Print Service

2604.1607.829

26.4.23468.0

Note: Due to changes in the component versioning and limitations in MSI versioning, the Sentry Print Service now has two version numbers. The MSI version number is the one that will show in Window's "Add and Remove Programs".

What is new in 5.5 - Sentry Print 2604.1607.829

  • Control Access to Third Party Applications on HP Devices. Blueprint now allows administrators to deny access to third party (non native) applications on supported HP MFPs using Policy Print.

  • Added support for new Canon Models. This update adds support for the following Canon devices, allowing them to be secured with Pharos Sentry Print for Blueprint

    • imageRUNNER DX 4935

    • imageRUNNER DX 6855

    • imageRUNNER DX C359

    • imageRUNNER DX C3930

    • imageRUNNER DX 48xx

    • imageRUNNER DX C48xx

    • imageRUNNER DX 49xx

    • imageRUNNER DX C49xx

    • CX635

    • imageCLASS X MF1333C/C1333iF/i

    • imageForce 6100

  • Added support for new Lexmark Models. This update adds support for the following Lexmark devices, allowing them to be secured with Pharos Sentry Print for Blueprint

    • CX950g

    • CX950se

    • CX951g

    • XC9525

    • CX951se

  • A new Select All button was added for small screen devices to keep the experience consistent with larger screen devices.

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 patcher may be unable to replace files because they are in use. If this happens,

  1. Stop all Application Pools in IIS.

  2. Run the upgrade again.

  3. Start all Application Pools after the patcher succeeds.

Updating Analyst or Collector

Installation Steps

  1. 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 patcher will do this automatically.

  2. Open an elevated Windows command prompt and run SentryPatcher.exe from the command line. No additional parameters are necessary.

  • The patcher 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 patcher. This output will include error messages if the patcher fails.

  • If the patcher fails, you can correct the cause of the error and run SentryPatcher.exe again.

  • At completion, the Patcher may automatically force a restart. Follow the remaining instructions after the restart.

  • To log the installation of MSI files associated with the update, edit <MsiLogFileDirectory> in the SentryPatcher.xml file with a folder path.

To reinstall a Sentry Print Service on Analyst or Collector where a Sentry Print service installed as part of Blueprint and then manually uninstalled.

Use same steps as above.

Automated Server Deployment

Customers with a large number of Blueprint Servers 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 SentryPatcher.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 SentryPatcher.xml file, you can put the password as encrypted text into smtpEncryptedPassword. You can encrypt the password by calling SentryPatcher.exe from the command line with the flag "/encrypt:". e.g. Assume your mail server's password is "MySecretPassword".

    1. Open an elevated command prompt and type in patcher /encrypt:MySecretPassword

    2. SentryPatcher.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.