ORS - Printing without ORS server - ORS server Failure

This chapter describes how to set up the printers in case of ORS failure to sustain the printing functionality.

images/s/-3eliqb/8502/404359a7d2ab19c9c7c58d12013124a386b28257/_/images/icons/emoticons/lightbulb_on.svg Please note that in some cases (depending on the environment size and the seriousness of the failure) it might be faster to just restore the ORS without performing any reconfiguration described here.

The following scenarios are available:

A) Reconnect all devices from failed ORS to the CML server

This step requires reconfiguration as follows:

  • Move all devices from failed ORS to CML via YSoft SafeQ web interface.

  • Reconfigure all hardware terminals to connect to the CML instead of the failed ORS.

  • Reconfigure all print drivers (or YSoft SafeQ clients) to connect to the CML server (all print drivers that were sending print jobs to the ORS must be re-connected to the CML).

  • Reinstall all embedded terminals that were moved from failed ORS server to functional ORS server.

images/s/-3eliqb/8502/404359a7d2ab19c9c7c58d12013124a386b28257/_/images/icons/emoticons/warning.svg Moving devices from ORS to CML will be reflected also in statistics (device will be shown in a different group for the period when it has been moved).
images/s/-3eliqb/8502/404359a7d2ab19c9c7c58d12013124a386b28257/_/images/icons/emoticons/warning.svg Moving too many devices to CML might overload the CML node. See hardware sizing for maximal amount of connected MFPs to the CML.

B) Reconnect all devices from failed ORS to any other existing ORS

This step requires reconfiguration as follows:

  • Move all devices from failed ORS to a functional ORS via YSoft SafeQ web interface.

  • Reconfigure all hardware terminals to connect to the functional ORS instead of the failed ORS.

  • Reconfigure all print drivers (or YSoft SafeQ clients) to connect to any running ORS server (all print drivers that were sending print jobs to the ORS must be re-connected to any running ORS - due to job roaming functionality users can send job to one ORS and release it via another one).

  • Reinstall all embedded terminals that were moved from failed ORS server to functional ORS server.

images/s/-3eliqb/8502/404359a7d2ab19c9c7c58d12013124a386b28257/_/images/icons/emoticons/warning.svg Moving devices from failed ORS to another one will be reflected also in statistics (device will be shown in a different group for the period when it has been moved).
images/s/-3eliqb/8502/404359a7d2ab19c9c7c58d12013124a386b28257/_/images/icons/emoticons/warning.svg Moving too many devices to another ORS might overload the functional ORS. See hardware sizing for maximal amount of connected MFPs to the ORS.

C) Reconnect all devices directly to the printer

This step requires additional reconfiguration steps:

  • Reconfigure all print drivers (or YSoft SafeQ clients) to send print job directly to the MFP. The instructions are the same as described in article CML - Printing without CML.

images/s/-3eliqb/8502/404359a7d2ab19c9c7c58d12013124a386b28257/_/images/icons/emoticons/warning.svg All jobs delivered to the MFP this way will not be accounted.