Added a new config key ’-stack-dump’ that enables users to opt-out of the enhanced logging.Fixed a bug that stopped the Kyocera embedded application from installing on devices running Java versions lower than 1.8 PO-28.Fixed an issue that prevents the embedded Kyocera app from crashing in certain circumstances.Fixed an issue that caused a site server warning dialog to be displayed when performing automated installations.Fixed an issue that caused incorrect color page number and page size PO-197.Fixed an issue that a grayscale image might be treated as color when printing via Mobility Print PC-17826.Fixed an issue introduced in PaperCut 20.1.1 that prevented PaperCut desktop clients from connecting to the PaperCut server when server.enable-async-requests was set to “Y”.Fixed an issue that caused Windows client dlls to not be included when installing on Mac or Linux.Fixed an issue that could cause some LDAP group members to not be synced correctly.Updated Java Runtime Environment to version 11.0.9.Enabled a clean shutdown when stopping the PaperCut service on Linux.Added sendStringParametersAsUnicode=false to the template SQL Server database URL (to ensure that queries use indexes and run fast) PO-204.Added a housekeeping job to delete obsolete font files from the temp folder on startup.Improved the performance of “Sign in with Google” to Mobility Print (especially when synchronizing users from many domains).Added to the “Change Details” description that card/ID numbers can contain numbers, text and symbols.Updated the build instructions for the C# example code.Updated the example C# code supplied in ServerCommandProxy.cs to show latest web services API features.Enhanced the Admin UI to display a status message if Universal Print is configured but the MS Universal Print connector is not running.Or simply upgrade to Windows Server Core 2016, which does include this DLL.20.1.3 Build 56199 Print Provider version 105. To do so, open PowerShell, mount the DVD or ISO to the D: drive, run Install- WindowsFeature Server-Gui-Mgmt-Infra -Source wim:D:\sources\install.wim:2, then restart the server. Install the Server-Gui-Mgmt-Infra feature of Windows to obtain the d2d1.dll.Manually copy the d2d1.dll file from C:\Windows\System32\d2d1.dll on a non-Core version of Windows to \runtime\win64\jre\bin.Thankfully we know of a few different ways to get this working. The reason for this failure is that this version of Server Core is missing a DLL (d2d1.dll), which is a dependency of another DLL (awt.dll) which in turn is required for the 3rd party library ( OpenJDK 11) we use to generate reports in version 19 and above. We’ve heard reports from customers that reports fail to generate when running PaperCut NG/MF version 19 on Windows Server 20 R2. Q Are there any other gotchas I should know about? You can modify defaults further by referring to our guide on installing PaperCut NG/MF via the command line. You may need to run the installer with the command line option of /silent or /verysilent. Q I tried running the installer, but nothing displayed on the screen? This will need to be performed remotely as the Windows Server Core environment generally does not have a web browser. Once this installer process has been completed, you will be prompted to open a web browser to complete the install configuration. The installer does not have problems running in the limited environment that Windows Server Core provides. When installing PaperCut NG/MF to any supported Windows Server Core edition, you need to use command-line tools to start the PaperCut NG/MF installation. Q How does the installation differ from a typical install? However, customers are advised that Windows Core requires advanced System Administration skills and experience to deploy and manage successfully. In short, yes, as of version 10.6, PaperCut NG/MF can be installed to Windows Server Core editions to provide a print management solution. Q Does PaperCut NG/MF run on Windows Core editions?
0 Comments
Leave a Reply. |