Printix Administrator: With support for live updating you are no longer required to use Refresh to see updated lists of users, printers and the status of your printers. Whenever a printer or user is added or deleted this is automatically reflected in the browser. Also the online/offline status of your printers is automatically updated as soon as these events are received.
Easier onboarding of new users. All users now get the email "Get started with Printix..." when they register. The email contains instructions and links to Printix Client and Printix App.
Printix Help Center: New responsive design.
Active Directory connection now defaults to secure LDAPS on port 636.
Setup Assistant: You will not be asked to download, install and sign in to Printix Client if you have already done this. As administrator and upon successful activation of your Printix home, you get the email "Get started with Printix...". The email contains instructions and links to Printix Client, Printix Administrator and Printix App. The setup is described in Getting started in the Printix Administrator Manual.
Printix Administrator: If no print driver was selected, the Print drivers page was stuck in loading and prevented use of search to find and select a print driver.
Printix Administrator: If you checked Automatically add printer for everyone when you invited a Technician, this was not checked on the printer after the printer was added by the Technician.
Printix Administrator: Adding a credit card on the Subscription page could sometimes give an error.
Improved loading time of printers.
Printix App: Design is not the same as Printix Administrator. Redesigned version is coming soon.
Printix Administrator: If you Add a Freedom printer you can click Refresh on the Printers page to get rid of the undesired second instance of the printer.
Printix Administrator: If you experience that live updating is not happening as expected, then Reload the web page.
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.