Known Issues and Limitations
PMC Known Issues and Limitations
API
PMC Version | Limitation |
---|---|
3.21 | Locations can be created/update via API using incorrect formats for the combination of locationData & locationType parameters. |
3.0 | Enabling plain API port on API service doesn’t open port 7303. Workaround is to restart the server hosting the API service. |
Core
PMC Version | Limitation |
---|---|
3.44 | When log4j2.xml file is updated, the log level on server is set to the value of pmcLogLevel parameter in this file. |
3.38 | Offline server cache is currently not working as intended and is under review. |
3.10 | When using loadbalancer without sticky session, webclients are not supported. |
3.0 | In some configurations, expired jobs not printed counts as printed in reports. |
3.0 | Page range print option does not work for TCP and IPP protocols. |
Authentication
PMC Version | Limitation |
---|---|
3.43 | For Microsoft Entra and Okta identity providers, SAML is supported when using Service Account configuration. |
3.40 | Nested/transitional LDAP group memberships are not supported for ACL. Users must be direct members of the group configured in the respective ACL. |
3.26 | Cannot update an access control entry related to an inactive authentication provider. |
3.11 | Duplicate Card IDs can be set for the same user via PMC Web UI & API. |
3.10 | Google authentication limited to use with Chromebooks for user creation. |
3.0 | IPP can in some configurations fail with “Authentication error” for Windows workstations joined an Azure domain with Azure AD configured in PMC. Workaround: Use PMC Client to distribute IPP queues or specify simple username in IPP path. |
3.0 | Azure AD authentication does not support multi-factor authentication “MFA”. To enable 1FA authentication if 2FA is required, is to whitelist the PMC server making authentication requests in Azure. Alternative is to use the “One-time password” feature in PMC or Azure/ADFS single-sign-on. |
3.0 | Azure AD Authentication – user cannot login to PMC if they have a ‘sharepoint admin’ role in Azure AD. |
PMC Web UI
PMC Version | Limitation |
---|---|
3.39 | When using a native scanning feature such as "Scan to my email," the scan job may initially appear as a print job type on the "My documents" page until fully processed. |
3.20 | Errors appear on Web UI when making modifications concurrently on Access Control by multiple users on the same customer. |
3.0 | Internal Error in PMC Web UI when trying to delete pending print job from shutdown PMC Client running local storage. |
3.0 | PMC Web UI screen may become unresponsive after deleting a pending job from a storage which is offline/no longer available. |
Mobile Printing
PMC Version | Limitation |
---|---|
3.24 | Airprint is not working with iOs version 15.5 |
PMC Client
PMC Version | Limitation |
---|---|
3.27 | In case of a heavy load, PMC may start additional nodes and use them to store documents submitted to the cloud. After the load returns to normal, these nodes will shut down in order to conserve resources. As the documents are not stored in a shared cache, it is not possible to release a document stored on a terminated node. This problem can be solved by submitting the document(s) again. |
3.19 | The default printer within PMC Client may not always be set. |
3.15 | At the moment, you can not set up any default driver options on the PMC Client for Mac OS. For instance, BW/color and simplex/duplex as default. This is possible on the Windows PMC lient. |
3.0 | the print queues are not removed if uninstalling just after printing and before logout. |
3.0 | For Citrix thin clients or Windows Terminal Services clients, user or location specific printers are not supported. Print queues created by the PMC Client on Windows thin clients, are all created as shared among all sessions on the Citrix or Terminal Services host. When the PMC Client detects the session is running in a Terminal Services session, it will not delete printers on custom logout. |
3.0 | macOS PMC Client – print + staple using Adobe Reader DC with collate option not working as expected. |
Search
PMC Version | Limitation |
---|---|
3.10 | Search function does not return results for Servers. You can utilise the Servers view and filter for Secondary Gateways by status (All/Online/Offline/Disabled/Updateable) to view these. |
3.0 | Nested group lookup not supported. |
Security
PMC Version | Limitation |
---|---|
3.8 | TLS 1.3 cannot be enabled for channel communications over Port 2560 (messaging between Primary and Secondary Gateway, PMC Client in “Local Storage” mode and Primary) – Limitation removed from version 3.24 |
System Infrastructure
PMC Version | Limitation |
---|---|
3.0 | On SUSE Linux default installations, the Linux servers own hostname doesn’t always resolve to itself, depending on outside network DNS/DHCP configuration. Make sure the server can resolve its own hostname. |
Users
PMC Version | Limitation |
---|---|
3.0 | Not all permission checks are enforced. Permissions relating to print functionality, such as Color Print, Copy, Scan etc, are not in effect. |
Scan Workflows
PMC Version | Limitation |
---|---|
3.35 | Append/Prepend overwrite behavior does not work with PDF/A files produced by OCR. |
3.35 | The Compact PDF output format doesn't work properly in combination with all processing steps except Scan separation by page count — the scanned file is split into multiple pages. |
Printing
PMC Version | Limitation |
---|---|
3.44 | The landscape layout for PDF files does not work properly when the user selects the "Print using system dialog..." option in a web browser. |
3.38 | Booklet bind direction Left to Right is always used. |
Embedded Applications
General Embedded Functionality
PMC Version | Limitation |
---|---|
3.30 | One-time passwords can only be used for card enrollment and Web UI. It is not for logging in and printing, scanning, or copying at the terminal. |
3.22 | Amount of copies cannot be reduced on embedded clients if job is sent with multiple copies. |
3.20 | Embedded clients are limited to displaying 50 Pull Print jobs at any one time. |
3.0 | Not able to login to embedded release clients in the offline mode for Azure user. |
Brother Embedded Application
PMC Version | Limitation |
---|---|
3.22 | Incorrect pages & totals are displayed on reports for copies using the duplex option. |
3.22 | Scan reports are not displayed on PMC Web UI. |
3.21 | Card enrolment does not work with DNS & secure link. |
3.21 | Logout by card swipe does not work. |
3.18 | Unable to uninstall Brother embedded and after uninstalling user can still login & perform print functionalities. |
3.15 | Card swipe from Brother device home page may not enable login – swipe to login from application screen if affected. |
Canon Embedded Application
PMC Version | Limitation |
---|---|
3.13 | The Canon embedded client only works with DNS using HTTP protocol via port 8704. |
3.44 | Canon Embedded Terminal can be installed only on MFDs in Europe. |
HP OXPd Embedded Application
PMC Version | Limitation |
---|---|
3.22 | Color scan jobs are registered as BW under Reports. |
3.12 | Devices must have a screen size bigger than 2.7 inches. |
HP WorkPath Embedded Application
PMC Version | Limitation |
---|---|
3.25 | User department & groups are not displayed on Job History API for Scan jobs. |
KM IWS Embedded Application
PMC Version | Limitation |
---|---|
3.24 | Copy jobs not reported for bizhub C227 & C250i. |
3.15 | Logout by card swipe not working. |
3.15 | Unable to wake up KM MFD with IWS from sleep mode using card swipe. |
3.13 | No notification or message if the scanned document is too big to be sent by email. |
KM OpenAPI Embedded Application
PMC Version | Limitation |
---|---|
3.25 | Web client is configured with Short ID instead of “username+password” (on the KM Bizhub C250i). |
3.21 | MS Azure OAuth2 & Okta user login & card enrolment does not work with no domain & OTP. |
3.21 | Logout by card swipe does not work for the currently logged user. |
3.21 | Card enrolment fails for LDAP users if no domain is entered. |
Kyocera Embedded Application
PMC Version | Limitation |
---|---|
3.41 | Usernames longer than 32 characters are not supported for Kyocera devices. |
3.36 | Y Soft card reader is not compatible with Kyocera terminals. |
Lexmark Embedded Application
PMC Version | Limitation |
---|---|
3.23 | Copy jobs not displaying under Reporting. |
3.22 | Cannot convert duplex jobs to simplex. |
3.22 | BW jobs are registered as color jobs under PMC Web UI Reports. |
3.0 | The embedded terminal cannot be uninstalled from the administration Web UI. |
3.0 | Unable to uninstall the Lexmark embedded. |
Ricoh SOP Embedded Application Gen1
PMC Version | Limitation |
---|---|
3.21 | ShortID & Password characters are not hidden immediately by asterix on device. |
3.21 | Using “admin” as a local PMC admin username cannot login. Workaround is to use a different username for the local PMC admin user. |
3.0 | Deployment report in UI as Installed in some rare cases despite Device not reachable error. |
Sharp Embedded Application
PMC Version | Limitation |
---|---|
3.23 | Username & ShortID login options are always available even if not included in embedded config. |
3.0 | User is not logged out by card swipe. |
3.0 | The Sharp embedded terminal cannot be uninstalled from the administration Web UI. |
3.0 | While installing the sharp if the printer is rebooting then status on the GUI is struck in “installing”. |
3.0 | Screen is not refreshed automatically when the configuration is changed from UserId login to ShortId login. |
3.0 | If the card reader is disconnected from the printer, not possible to login with username and password. |
Xerox Embedded Application
PMC Version | Limitation |
---|---|
3.23 | Xerox VersaLink C605X – Copy Reporting is not working. |
3.23 | Xerox VersaLink – Delete job & refresh job list buttons not working. |
3.22 | Login for previous account still possible after new install & configure. |
3.20 | Card enrolment is not possible. |
3.20 | Advanced print button is not working. |
3.0 | Fails to deploy to C405 and 7845 as these models cannot support DNS/hostname for AuthenticationHostAddress. Workaround is to add secondary servers IP address to Account domains and map to server gateway with terminal service, in which case the IP address is used for Xerox Smart Auth AuthenticationHostAddress. |
3.0 | Copy and scan reporting not supported for Xerox embedded client. |
Xerox Gen 2 Cloud Terminal
PMC Version | Limitation |
---|---|
3.48 | A simplex or duplex short-edge job changed to a duplex long-edge job in basic finishing options is printed as a simplex job. |