- Printix Client for Windows version 1.1.1085.0.
- Printix Client for Mac version 1.1.873.0.
- To better assist companies that want to have printers on a separate network, isolated from users, you can now install Printix Client on a computer that has two network adapters (one for the printer network and one for the computer network), and then have it forward the print data to the printers on the printer network. Print data is sent via TCP port 21335. For additional information see the Printix Administrator Manual.
- Step-by-step procedure for deploying Printix Client with Intune on Azure.
- The Printix Client icon will feature a yellow dot when the Printix Client is on an Unknown network or if the Connection failed to the Internet/Printix Cloud.
- To cope with Windows firewall policies that disable replying to ICMP Echo Requests, Printix Client is no longer relying on the ping command to check the status of computers. The ping command is still used to discover printers.
- Printix Administrator Manual: Improved description of how to get started if your company has multiple networks. Added new section: Enable BYOD.
- Printix Redirector: The printing user's Active Directory username is now transferred to ensure the user becomes the owner of the document in the Follow/Pull print queue offered by third party Follow Me solutions, such as PaperCut, SafeCom and Equitrac. If you have a previous version of Printix Redirector this update must be done manually. Going forward updates will happen automatically.
- Deploying Printix Client via Microsoft Intune and Windows Installer through MDM did not work. An additional syntax has been introduced for the command line arguments. Example: WRAPPED_ARGUMENTS=/id:cbfce0b5-da2a-4cb6-b7f7-a04ee31cac90, where the id value should be replaced with your Printix ID as shown in the name of the MSI file.
- On HP Photosmart Prem C410 series the page count is now correct.
- On Canon iR-ADV C5235/5240 UFR II the page count is now always 0. Before there was a risk of reporting an arbitrary page count.
- Printix Client for Windows: In very rare cases, print anywhere functionality did not work, because Printix Client failed to install two required packages in the installation subfolders /gs and /sPdf. The installation failed with the message: Cannot determine compressed stream type.
- Printix Client for Windows: Printix Anywhere printer did not install on Windows Server 2012 R2.
- Printix Client for Mac: Document names are now shown with their correct name. Since 2017-06-12 (version 1.1.795.0.) document names were unintentionally show as: No JobName.
- Printix Client for Mac: Use own DNS lookup functions instead of functions from Mono framework.
- Printix Client for Mac: Large prints did not always print and could result in the print dialog showing: Unable to add document to print job. Problem was caused by excess memory usage. Large prints are now only handled in memory if the size (content length) is less than 10MB. Otherwise the print data is streamed to disk.
- 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.
Please sign in to leave a comment.