Pharos Blueprint 5.4 Update 4.1 Sentry Print Service Patch 2411.811.522

Important Notes:

• This Patcher updates the Sentry Print Service previously installed by Blueprint 5.4 Update 4.1. It will not update earlier versions of Blueprint.

• This Patcher 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.

The component included in this update is:

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 Sentry Print Service 2411.811.522

• Removed support for SNMP v1/v2 on Xerox devices. The latest Pharos Systems Sentry Print Service no longer supports SNMPv1/v2 and is only compatible with SNMPv3 configurations. To upgrade to the newest release, ensure all your Secure Release enabled Xerox devices are configured to use SNMPv3 exclusively.
  Note: Update the XeroxSettings.xml file located at the path C:\ProgramData\PharosSystems\Sentry Print Service\Xerox with SNMPv3 configurations that match the printer’s SNMP settings. For more information on how to do this, refer to the Configuring SNMPv3 (Xerox devices only) section of the Pharos Sentry SE50 Deployment Guide.

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

  • AltaLink B8090

  • AltaLink B8045

  • AltaLink EC8056

  • AltaLink C8070

  • AltaLink C8045

  • Primelink B9100

  • PrimeLink B9110

  • PrimeLink C9065

  • VersaLink C415

• Bugfixes

  • Resolved issue causing firmware 3 (FW3) and firmware 4 (FW4) Lexmark devices to experience logon problems after waking from sleep mode.

  • Resolved issue on Ricoh devices where users with display names containing spaces were unable to access the printer's main menu via the More Device Functions button in the Sentry Print app.

  • Resolved issue where secured HP and Ricoh devices would transition from the login screen to a spinning circle before returning to the login screen.

  • Resolved compatibility issue between Sentry Print and Ricoh firmware versions 8.00 and 8.01. Previously, updating secured Ricoh devices to these firmware versions rendered the devices unusable.

  • Resolved issue on the Xerox VersaLink C405 where users encountered the error message "Unable to communicate with the accounting server. Job has been deleted" when attempting to make a copy. After securing a device, you must follow the instructions in the Sentry Print SE50 Deployment Guide to make sure the Server URL is properly configured and directed to the Pharos API.

How to apply this Update

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.

Important: This Patcher 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.

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.