Skip to main content
Skip table of contents

Release Notes

MyQ Desktop Client for Windows 10.2

Find details of the improvements in MyQ 10.2 across our full range of solutions here.

MyQ Desktop Client for Windows 10.2 (Patch 1)

16 October, 2024

Improvements

  • NEW FEATURE Users can generate a new PIN on the client if "Users can change PIN" is enabled in the server's User Authentication settings.

  • Local printers that have target address 127.0.0.1/localhost will be ignored in Local Print Monitoring to avoid double accounting when all ports are set to be monitored.

Changes

  • Client Spooling can now operate without IPPS enabled on the server side.

Bug Fixes

  • The Desktop Client might not recover properly if the signed-in user was anonymized or deleted.

  • When the client's login method is changed from Integrated Windows Authentication to using MyQ credentials, the user is not logged out to use the new login method.

  • The "Capture driver" option might not be translated to the language the client is switched to according to the system it runs on.

  • When Scrive Go printers are installed on the system, Desktop Client might not be able to provision printers.

  • LPM allows printing in Color even if Policy is set to Force Mono


MyQ Desktop Client for Windows 10.2

30 August, 2024

Bug Fixes

  • A printer cannot be deployed if has the same port name with different case sensitivity.

  • Custom logo is not displayed in the client.


MyQ Desktop Client for Windows 10.2 RC

8 August, 2024

Improvements

  • Adjustments to Integrated Windows Authentication.

Bug Fixes

  • Context menu translation strings.


MyQ Desktop Client for Windows 10.2 (BETA 2)

19 July, 2024

Improvements

  • Fallback printing is now supported, offering a new user interface for selecting the fallback printer. For each printer in the list, its capabilities are illustrated (support for color/black & white print and A4/A3 paper format), and the provided printer’s location can help the user identify where is the backup printer physically located. Print Server 10.2 Patch 3 + is required.

  • Logging of MDC was improved to include more details.

  • Only members of the administrators' group can access the folder with print jobs on the local computer.

  • Mako updated to version 7.3.1.

  • Added support for IPv6.

Changes

  • Installed printers by printer provisioning do not use the "MyQ" prefix in the printer's name anymore.

Bug Fixes

  • Printer driver is not installed on a computer with ARM processor (Error Printer model was not found inside the downloaded zip driver package).

  • MDC deploys offline queues.

  • The certification warning dialog is not displayed correctly in the German language.

  • Microsoft SSO Login Back button causes error "Log in failed".

  • After upgrade from 8.2/10.0, MDC cannot connect to the server.

  • Updating the printer driver or opening the Capture drivers option might fail with the error "Desktop Client service is not running".


MyQ Desktop Client for Windows 10.2 (BETA)

30 April, 2024

Improvements

  • NEW FEATURE MyQ Desktop Client user interface has been largely redesigned and modernized.

  • NEW FEATURE Printer provisioning can automatically install print drivers and configure printers for printing to MyQ. Users will be provisioned with the correct drivers and queues they have access to. Administrators can use the Desktop Client to capture print drivers and printing defaults in order to utilize them for Printer provisioning.

  • NEW FEATURE Desktop Client can be switched to "Private" or "Public"; the public mode is optimized for use on shared workstations.

  • NEW FEATURE New authentication page supports for login with MyQ credentials (username + PIN, username + password) as well as Sign in with Microsoft (if enabled on the server).

  • NEW FEATURE A list of pending jobs for interaction such as account and project assignment or scripting interaction has been added to the Desktop Client, allowing users to assign e.g. specific project only to selected jobs and immediately select a different project or account for the remaining jobs.

  • NEW FEATURE Users can now modify job properties on the Embedded Terminal also for jobs spooled via Client Spooling. These jobs now also support watermarks, and policies configured on the server are applied.

  • NEW FEATURE All jobs sent by the Desktop Client to the MyQ server are authenticated from the start, this improves security and also enables roaming users to finish their pending jobs (e.g. assign account or project) from any computer they sign in.

  • Added support for client spooling to Epson devices over IPP(S). Requires MyQ Print Server 10.2.

  • Information about the MyQ server can be embedded in the Desktop Client's installer filename; this improves managed deployments such as with Intune and allows administrators to send users links to download the client which will automatically connect to the corresponding server once installed.

  • UDP communication was replaced with WebSockets and HTTP, improving the communication capabilities of the client.

  • Added support of radio group and checkbox group for Desktop Client user interaction scripting.

  • Updated MDC service to use API v3.

  • Mako updated to 7.2.0.

  • OpenSSL updated to 3.1.3.

Changes

  • Configuration was completely removed from the installer as configuration is now done from the MyQ Print Server's Web Interface via Configuration profiles.

  • Unsecure connection option was removed, Desktop Client can operate in two modes – "Strict" for secure-only connection and "Normal" which warns the user when the MyQ server certificate is not trusted. Make sure to deploy the correct CA certificates on clients running the Desktop Client.

  • List of users removed as an authentication method.

  • PIN-only authentication method removed, new authentication uses the combination of username + PIN for improved security.

  • Possible to set paper aliases for the parser of local jobs via config.ini.

  • MyQ Desktop Client now registers only one REST API application on the server (instead of separate applications for Agent and Service).

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.