Pharos Blueprint 6.1 Sentry Print Service Patch 2607.1001.5425

Important Notes:

• This Patcher updates the Sentry Print Service previously installed by Blueprint 6.1 or later. It will not update earlier versions of Blueprint.

• Canon: Customers in the Asia/Pacific/Japan region with Canon devices should NOT apply this update; elsewhere, Canon devices should be resecured following this update

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 6.1 - Sentry Print 2607.1001.5425

Ricoh Enhancements

• Logoff confirmation prompt control - The logoff confirmation prompt on Ricoh IM devices has been removed. Users are no longer presented with an unnecessary extra step when logging off the device.

• Secure Print icon auto-placement - The Secure Print app icon is now automatically placed on the device home screen after securing. Previously, the icon was hidden in the device apps folder, requiring administrators to manually move it on each device individually, a particularly burdensome task in large-scale deployments.

• Faster Re-securing of Ricoh Devices - Re-securing Ricoh devices has been significantly optimized. The process has been reduced from approximately 15-20 minutes to under 10 minutes per device, improving deployment speed for large-scale fleet updates.

Konica Minolta Bugfixes

The following fixes address issues impacting Konica Minolta MFP functionality and user workflows.

• Unable to remove the Pharos Secure Print application from MFPs with blank administrator passwords - If a Konica Minolta MFP had a blank administrator password, the Pharos Secure Print application could be registered but could not be removed. Both registration and removal now work correctly regardless of the password configuration.

• First card swipe fails to log in the user when the MFP has been idle - When a KM MFP had been idle for a period (login page no longer displayed, screensaver potentially shown), swiping a proximity card would briefly show a “waiting” screen followed by the login screen, but the user was not logged in. A second card swipe was required to authenticate. A single card swipe on an idle MFP now logs the user in immediately, as expected.

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 either a) Sentry Print service installed as part of Blueprint and then manually uninstalled, or b) Sentry Print was never installed.

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.