Changelog 2017-06

MDM for Windows 10: Support for deployment of Printix Client with Microsoft Intune and Windows Installer through MDM. This modern method uses the Mobile Device Management (MDM) capabilities built into Windows 10. If you have not completely moved to Windows 10 you can use Microsoft Intune and Windows Installer, as this supports both Windows 10, 8.1, 8 and 7.
Single Sign-on (SSO): In organizations that use Azure Active Directory Domain Join, users who sign in to their Windows 10 computer with their Microsoft work or school account are automatically signed into the Printix Client. Works with Windows 10 editions: Pro, Enterprise and Education. Microsoft does not support Azure AD Join on the Windows 10 Home edition.
Sign in with Google. If your organization is using the Gmail service with your email domain you can Enable Google authentication and have users automatically register the first time they sign in with their Google work or school account (not @gmail.com).

Instead of prompting each Azure AD user to accept the reading of their profile, this can be accepted once and for all by the administrator by clicking Accept for all users on the Azure AD tab on the Authentication page in Printix Administrator.
Improved support for environments that use web proxies.
Improved page counter readings from Brother printers.
Printix Administrator: On the Printer properties page you can assign the printer to another Network. On the Computer properties page you can modify the Network name.
Printix Client: To not confuse users, Diagnostics is now hidden on the client menu. How to see diagnostics.
In the Printix Administrator Manual and Printix User Manual sections are now numbered to make it easier to refer people over the phone to a manual topic for further info.

Printing via the cloud failed if the file could not be uploaded within 100 seconds. Problem most likely to occur with a combination of a slow Internet connection (ADSL2+) and large printable files (8 MB or bigger).
Attempts to release documents would sometimes fail with Release not possible, even though the computer with the document was powered on and network connected.
Printix Client for Windows: Printers connected with a WSD port on Windows 7 (32-bit and 64-bit) are now converted to Printix.
On Windows the Printix Service did not start in some rare cases.
The status of Printix printers in the Print dialog of Microsoft Word and PowerPoint would after printing be reported as: "Ready: 1 document waiting". Now the status is reported as: "Ready".
If you added or modified a print driver configuration and this involved opening the Advanced tab and clicking the Printing Defaults… button to configure per-printer defaults, then when clicking OK or Apply you would see the message: “Printer settings could not be saved. The parameter is incorrect.” Now changes to Printing Defaults, can be saved.

Printix Client for Windows: On Windows 7 (32-bit and 64-bit) at sign in, it may complain about missing System.web.dll and errors in production.js. This happens if Microsoft .NET Framework 3.5 is installed. To resolve, upgrade to Microsoft .NET Framework 4.
Printix Client for Windows: If you open the Control Panel, Features and Programs and click Printix Client the Product version is that of the initially installed Printix Client. The current version number can be seen on the Printix Client Diagnostics dialog.
Printix Client for Mac: Documents printed to a Printix Anywhere printer is always tracked as 1 page.
Translations: These are made with the use of Google Translate. Please inform us about improvements for translations.