Printix App: Added more ways to access and navigate between the Print page and the Recents page. From the Recents page you can reprint documents that were printed or deleted within the last 12 hours. You can also reprint documents that were printed directly to the printer.
Azure/Office 365 authentication now support use of on-premise AD via ADFS (Active Directory Federation Services).
Button text Continue with Windows changed to Sign in with Microsoft.
Printix Client for Mac: Printer discovery is now completed as quickly as on Windows.
Printix Anywhere printer: MS Publisher Imagesetter is now used as the print driver on Windows.
The page that lists printers that fail to register is now named: Unregistered printers.
Added support for Panasonic printers.
Printix Client for Windows: In rare situations, where the computer's network interfaces took a long time to initialize, a timing issue could prevent the Printix Service from starting.
Printix Client for Windows: Printers added via Web Services (WSD) were not always converted.
Printix Client for Mac: Printers added via Bonjour were not always converted.
Printix Administrator: Events on the History page now shown with date separator (YYYY-MM-DD).
Printix Administrator: Adding a credit card on the Subscription page was not always possible, also the Confirm link now works in the email: Printix - Please confirm your email address.
Printix Client: Uninstalling and installing Printix Client no longer creates multiple instances of the computer.
Sign in with Microsoft (Azure/Office 365 authentication) would result in the Microsoft error message: AADSTS75011: Authentication method 'WindowsIntegrated' by which the user authenticated with the service doesn't match requested authentication method 'Password, ProtectedTransport'. This would happen in installations that used on-premise AD via ADFS (Active Directory Federation Services).
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.
Translations: These are made with the use of Google Translate. Please inform us about improvements for translations.