Pharos Blueprint 5.1 Service Pack 1.2/2.1
One of the features available with the Blueprint Enterprise 5.1 Service Pack 1.2 update is SNMP State Checking. This feature ensures that you do not inadvertently release a job to a device that cannot print (no toner, no paper, error code, service condition, etc.). In order to make use of this feature, there are several requirements that must be met:
- The printer/multifunction device must be configured to allow SNMP GET requests (usually this is just an Enable/Disable SNMP option on the device's Network Settings screen) for SNMP v1/v2.
- The SNMP community name must be public.
- Any network device between the Blueprint server (the one holding your print job and the one hosting the terminal, if they are different servers) and the printer (where you are standing) must allow UDP port 161 and 162. This includes switches, routers and firewalls.
Further, since SNMP is a stateless protocol (it functions under UDP), the Blueprint software relies on a timeout (2 seconds) before attempting to fail a release, so a good communications path is important.
If you are unable to accommodate the 3 requirements listed above, or are unsure of the overall speed between endpoints, it is probably best to disable SNMP State Checking. The procedure to do so is found in the "Blueprint 5.1 Service Pack 1.2 New Features" PDF file included in the downloaded service pack (under the Documentation folder), but I will repeat it here for expediency:
Turning off SNMP State Check
If your device does not support SNMP, the printer will be assumed to be permanently offline. It is possible to turn off/disable the status check for a device. To turn off printer status check, do the following on ALL Blueprint servers:
- Rename or delete the ‘AssetManagement’ directory from the Secure Release Application Data directory. This directory is usually in C:\ProgramData\PharosSystems\SecureRelease\AssetManagement.
- Restart ‘Pharos Systems Secure Release Service’.
That's it! If you do this before engaging the "Reapply Settings" option in the Blueprint Server Configuration tool, you only need to remove or rename the directory, since the Pharos Blueprint services are restarted as part of the "Reapply" function. Also, since most updates occur during a planned outage window, you won't unknowingly cause an employee angst because their job doesn't print (however, since the SNMP state check failed, the job will always be requeued for later release).
Pharos Blueprint 5.1 Service Pack 3.1 through Blueprint 5.2 Service Pack 2.1
SNMP State Checking retains its feature-set in these versions, as well as the device requirements, beginning in Blueprint 5.1 Service Pack 3.1. However, disabling this feature has changed. Of important note, the disablement need not occur across all servers; instead, it can be disabled against only one or a several in a larger deployment.
Turning off SNMP State Check
Locate the GlobalConfig.xml file for Blueprint on the server. By default, it is in C:\ProgramFiles\PharosSystems\Blueprint.
- Find the line <DisableSnmpCheck> line and set its value to true.
- Save the file.
- Restart the Pharos TaskMaster and Secure Release Service services.