You can install the application either via the setup wizard or silently via a command line with parameters.
Once the installation is finished, MyQ Desktop Client starts running in the background. The application can be found in the Windows Apps menu.
The MyQ Desktop Client Windows service also starts running in the background, and can be found in Windows Services.
Installation via the setup wizard
To install MyQ Desktop Client via the setup wizard, follow the steps below:
Download the latest available version of the installation file from the MyQ Community portal.
Run the installation file. The MyQ Desktop Client setup wizard dialog opens.
Click Next. The End-User License Agreement window opens.
Select I accept the terms in the License Agreement, and click Next. The Select Installation Folder window opens.
Accept the default folder (C:\Program Files\MyQ\Desktop Client) and click Next, or click Browse to select a different path, and click Next. The Server Settings window opens.
Fill in the server settings:
Use fixed server address:
Server address: Enter the IP address or host name of the MyQ server.
Server port: Enter the MyQ server's port. By default, it is 8090 for a secure (SSL) connection.
Get server address via Central server API:
When using this option, you must also set up the IP range of the client PC’s that will be using MDC. Check here for more information.
Server address: Enter the IP address or host name of the MyQ Central server.
Server port: Enter the MyQ Central server's port. By default, it is 8093 for a secure (SSL) connection.
Get server address from CSV file: Select this if you wish MDC to automatically switch between multiple servers on an IP subnet. This is done by uploading a CSV file with the required information, by adding the exact path to the file in the CSV file path field, or by clicking ... and browsing for the file. In case the configuration for the current subnet does not match or something is incorrect on the file or it can't be opened, MDC will go to the disconnected state. The CSV file's headers should be subnet, serveraddress, serverport, and lprport, as seen on the image below.
Validate server certificate: If enabled, the connection between the client and the server requires a certificate. The option is enabled by default.
Click Next once done. The User Authentication window opens.
Select one of the authentication methods and click Next:
Windows single sign-on: With this option selected, the job sender is identified as the OS user account, where the jobs are sent from.
Login: With this option selected, the job sender has to log in under their MyQ credentials. The job sender is then identified as the logged in MyQ user. You can select up to three login options: PIN, Username and password, and ID Card, as well as the Enable the “Remember Me” feature, which is used to display/hide the option to remember the logging user.
List of users: With this option selected, the job sender has to select one of the MyQ user accounts from the list of all MyQ users. The job sender is then identified as the selected MyQ user.
Click Next once done. The Job Processing window opens.
Secure print job forwarding: If enabled, all print jobs received by MDC are automatically forwarded to MyQ Server over a secure LPR protocol.
LPR port for job forwarding: Enter the LPR port of the MyQ server. This is the port that the MyQ Desktop Client listens to and receives print jobs via the LPR protocol. The default port is 515.
Client spooling: Check the box to enable it. This option sets the local storage for the jobs spooled on the user's computer. Add the desired values to the fields below:
Max size of all stored jobs: This is the limit of the local storage (in MB). After the maximum size of the job folder is reached, jobs will be deleted starting from the oldest one, until the size of all stored jobs is below the limit.
Delete jobs after: The spooled job is stored only for the duration of this period (in days).
Append domain name to username: Check the box if you want the jobs to be sent to the MyQ server, spooled as follows: username@computerdomain (firstname.lastname@example.org instead of eliot.kate). This is an advanced option of the MyQ system. Use it only if you need the information about the computer's domain included in the job sender's name.
Click Next once done. The Print Monitoring window opens.
Enable local print monitoring: If enabled, jobs on printers not managed by MyQ server will be accounted.
Limit monitoring to these print ports: Enter the names of the ports that you want to monitor, separated by comma (,). You can use '*' to monitor all name related ports (i.e.: USB* for ports USB1, USB2, etc.). Leave the field empty to monitor all the ports.
What to do when MyQ server is offline: Select one of the available options - Always release the job, Release job only if it complies with cached user restrictions, Discard job.
Click Next. The Fallback Printing window opens. Configure your fallback printing settings (make sure to select Windows single sign-on as the user authentication method if you want to enable fallback printing):
Enabled fallback printing: Select this if you want to enable fallback printing, which means when the server is offline, jobs will be released on a selected printer.
Select from the list of last used printers: Select this to enable fallback printing by showing a pop-up to select the fallback printer from a list of the last used printers.
Prompt for an address: Select this to enable fallback printing by showing a pop-up where you can type the fallback printer's IP address.
Use preconfigured printer: Select this to enable fallback printing by setting the fallback printer’s IP address to print jobs automatically. Address: Enter the IP address or hostname of the backup printing device that you want to use for fallback printing.
MyQ device spool - This option will release the job to the failover printer with an embedded terminal and the printer will report the released job once the connection to the server is back. For more information about the feature, check the MyQ Print Server guide. Select one of the following port options:
10010: Client spooling port for direct print. The job is automatically printed after it is received by the printing device.
10011: Client spooling port for secured hold print. The job is spooled by the printing device and waits there until the user logs in and releases it. It is not possible to release this job on any other printing device.
10012: Client spooling port for pull-print. The job is spooled by the printing device. Once the user logs on any of the devices connected to the same subnet, information about this job is provided, the job is displayed in the list of the available jobs and can be released there.
10013: Client spooling port for delegated print. It works the same as Client spooling pull-print, except that the job can be released by delegates of the sending user.
Device printer port - Select the printer protocol for sending the job to the backup printing device. The job will be reported to the server by the client once the connection to the server is back. After you change the protocol, the Port number automatically changes according to it. The following protocols can be used:
RAW (default port: 9100): Basic printing protocol, set by default.
IPP (default port: 631): Internet printing protocol, no port is used (or needed); all the information is inside the printer address.
IPPS (default port: 443): Secure version of IPP.
LPR: (default port: 515): Line Printer Remote protocol. In the Queue field, enter the name of the queue where the jobs will be sent.
Release options: Choose to Always release the job or Release job only if it complies with cached user restrictions.
Click Next. The Options windows opens.
Enable job parser: Check the box to enable the job parser for client spooling, local print monitoring, and fallback printing. Server spooled jobs are always parsed on the server. Job properties that are parsed and reported: job name, user, computer, job size, BW pages, color pages, copies, paper format, duplex, toner saving, staple, punch, printer language. If the job parser is disabled, only the job name, user, computer, and job size are reported to the server.
Delete pending jobs when the client is idle: Enable this option to delete any pending jobs when the client is idle. Set the duration of the Timeout in minutes. The default is 5 minutes.
Caching of user information used when app is offline: This is used only when MDC cannot connect to MyQ server. Select if you want to cache user information Only when user interacts with the app or With every logon to the operating system (this option may create a higher load on the server).
Click Next. The Ready to Install window opens. Click Install to begin the installation.
Once the installation is done, click Finish to exit the setup wizard.