The most basic deployment, typically small company or an office.

YSoft SafeQ can be installed on dedicated or print server. Print jobs are routed through YSoft SafeQ, which additionally controls access to multifunction devices and printers. Each location has its own individual YSoft SafeQ installation and is managed independently. YSoft SafeQ server offers failover based on synchronized application-level redundancy or operating system clustering. (learn more)

For detailed sizing information, please see Hardware requirements.

Basic deployment with multiple interconnected locations (several locations, slow WAN connection between locations).

ORS servers, centralized administration and reporting is required. In this situation, printing and MFP access at the largest location are managed by a YSoft SafeQ CML server, with other locations handled by independent ORS server(s). The entire system is managed from one central location.

NOTES: Each ORS can handle only a limited number of printers. It is highly recommended that a failover system be established by means of server virtualization, clustering, or daily backup procedures. 

For detailed sizing information, please see Hardware requirements.

For detailed distributed system information, please see Distributed Server System - Private Cloud.

For customers with multiple locations that are all about the same size, we recommend the use of a fully distributed environment with a centralized administrative location.
Print servers for individual buildings should be equipped with a YSoft SafeQ ORS application, which manages printing and MFP access within the local building. The YSoft SafeQ CML system is used only as a centralized management, integration, and reporting point. Online connection between the CML server and ORS servers is required, even if the connection is slow.

 NOTES: Each ORS can handle only a limited number of printers. It is highly recommended that a failover system be established by means of server virtualization, clustering, or daily backup procedures. 

This architecture cannot be used in situations where the Payment System is required.

For detailed sizing information, please see Hardware requirements.

For detailed information about distributed server system, please read Distributed Server System - Private Cloud.

For organizations with an extensive network of branches (connected by a relatively slow WAN) and a large central headquarters (several buildings on a high-speed MAN), the following architecture is recommended:

Every customer site with more than 20 users has a print server. This print server can be virtual, dedicated, or shared with other applications. Although many of the remote site locations may not have a constant connection to the main data center, some connection to the main data center is required, even if slow. The print server at each location manages all printing and copy locally and is equipped with an installed YSoft SafeQ Offline Remote Spooler (ORS) service. Each ORS can handle only a limited number of printers. It is highly recommended that a failover system be established by means of server virtualization, clustering, or daily backup procedures. 

 A data center with a YSoft SafeQ Enterprise Central Management Layer (CML) cluster (2-4 servers) is distributed across headquarters locations and provides central administration and integration services. The CML cluster also directly handles printing services in the locations directly connected to the data center (a maximum of 100 devices can be connected to each CML server).

 The data center also includes YSoft SafeQ Central Reporting Services (CRS Enterprise), which provides access to all required reports via MS SQL OLAP and Analysis Services.

For detailed sizing information, please see Hardware requirements.

For detailed information about distributed server system, please read Distributed Server System - Private Cloud.

For the largest global organizations with a large number of devices and multiple locations across large metropolitan areas or campuses, ORS server farms or clusters should be used.

With this type of company, the vast majority of users usually print at their home location. However, some users frequently travel among buildings throughout the metropolitan area. In that case, fully transparent Print roaming is required. To enable Print roaming, clustered ORS servers are used. Each cluster manages its own location, or is part of a larger high-speed network that covers a metropolitan area "within walking distance." Single ORS servers are used only for smaller remote offices. Printing via an ORS cluster is fully transparent to the user. The system can be configured so that meta data are synchronized between ORS clusters (with a defined delay) so there is fully transparent Print roaming among ORS clusters as well. However, because the print job data remain at the original location, print speed can be affected by network bandwidth and latency.

Typically with this type of large organization, some users also frequently travel among remote locations or different areas. These users require the ability to release the print job at any location, wherever they are. To meet those needs, additional steps (manual selection or pre-roaming in the background) are required to release the jobs at any location. To achieve that, this architecture utilizes a"super CML" system, which is not dedicated for printing, but which coordinates Print Roaming between CML clusters and ORS systems.

For detailed sizing information, please see Hardware requirements.

For detailed information about distributed server system, please read Distributed Server System - Private Cloud.

YSoft SafeQ can be deployed in additional environments. However, each case must be considered and analyzed individually.

Please consult any special uses of YSoft SafeQ with YSoft representatives.