What features and settings have been removed from Blueprint 4.2?

Blog Post created by toleary on Aug 5, 2013
  • Copy and fax apportionment settings have been removed from the Volume Apportionment tab on the Periods > Settings screen. Copy volume determined from a device’s meter reads is apportioned based on the copy transactions on that device. If copy transactions are not available for that device, the copy volume is assigned to the “Unknown user” in the device’s default department. This also applies to surplus volume (e.g. the meter-based volume is greater than the transaction-based volume); the excess volume is assigned to the “Unknown user” in the device’s default department. Inbound fax volume is always assigned to the “Unknown user” in the device’s default department.
  • The centralized page count failure logging mechanism has been removed. This mechanism was used in the past by the Pharos support team. As it required FTP services to function, it has been removed. In addition, the Tracker > Suspect Drivers screen in the Administrator has been removed.
  • A remote Administrator can no longer connect to a Collector. Remote connections required SQL Server. To simplify deployments, the Collector no longer uses SQL Server and hence, remote connections are no longer supported.
  • Administrator Logons on the Collector have been removed. They were required to secure remote Administrator connections – see above.
  • The Secure Release Here > Securable Queues and Secure Release Here > Print Troubleshooting screens have been removed from the Administrator. They are replaced by the Blueprint Secure Queue Configuration tool and Blueprint Secure Release Here Troubleshooter tool respectively.
  • Blueprint Enterprise does not ship with specific terminal types (e.g. Canon iMFP, Omega PS150). Terminal types are added automatically when you connect a new terminal to the Blueprint server.
  • A secured device can no longer be stand-alone (i.e. jobs sent to a secured queue related to that device are only available at that device). A secured device must be a member of a print group. If you have a scenario where a stand-alone device is required, you can create a print group and make that device the only member of that print group.