.png)
Multi-server Architecture
An ideal solution for businesses with remote branches where administration is centralized and simplified, is to implement multi-server architecture. When MyQ is installed in several branches, collecting data by the MyQ Central server from MyQ Site servers in branches is very easy. This functionality is useful, especially for the customers who run several branch offices and want to have overall statistical information and one
administration console accessible from one place.
Thanks to MyQ, IT resources are consolidated in one single place and become more efficient.
As opposed to the Print Server (standalone) model, where all parts of the MyQ system run on one server, the multi-server model consists of one Central server and multiple site servers. All site servers are connected to the central one.
The MyQ Central Server's Role
The Central server represents the headquarters. It has three basic roles:
License management for all Sites.
User import and synchronization.
Central replication server for statistical data so the administrator can run all the reports from this server.
The administrator of the MyQ Central server can access and manage all site servers from the MyQ Central Server web administrator interface.
The Central server cannot be used as a print server and its options are restricted solely to its central management role. Therefore, it is not possible to administer printing devices or print jobs there.
The MyQ Site Servers' Roles
The MyQ site server represents a branch. The site servers work as print servers and perform local management of printing devices and print jobs. Their function and management options are like those of a
standalone server. The sites synchronize the users with the Central server through secured communication.
Access to a site server is conveniently done through the MyQ Central server interface or remotely.
Job Roaming
The Job Roaming feature enables users to transfer their jobs from one location to another: jobs sent to one branch can be printed on printing devices at any other branch.
The administrator can choose between a Separate and a Shared job list for remote jobs. If a Shared list is chosen, the remote jobs are automatically downloaded and are available in My Jobs, marked with the source server's IP address or hostname.
The job roaming feature does not have to be centrally managed: Job roaming between two locations depends exclusively on the settings of the site servers locations.