New Features:

PaperCut NG v24.0.3 is available for PaperCut NG customers. The following changes have been introduced:

• Internet access is required when upgrading to v24.0.3 NG and syncing entitlements. PaperCut NG must be able to connect to a new Global Entitlements Service to sync its installed license entitlements. Existing licenses will be activated automatically on upgrade. See Important points to know about PaperCut NG/MF licensing (Internet connection requirements) for more information.
• New ‘Registration’ page. Added a ‘Registration’ page within the PaperCut NG admin interface to display license details and PaperCut contact details. See Managing entitlements for more information. [PO-1299]
• Deactivating an installation. The ‘Registration’ page contains a new button for PaperCut NG administrators to deactivate the installation. Clicking this button clears out the entitlements that the install has claimed so the entitlements can be reused for another site, or another fresh install. This requires a connection to the Global Entitlements Service. See Managing entitlements for more information. [PO-1658]
• Environments with multiple application servers. Due to the new mechanism for syncing entitlements, multiple Application Servers will sync to a single source of entitlements for the customer. This means that PaperCut NG environments that are using the same license file on each server will now use a single set of licensed items. Prior to upgrading to v24, customers must ensure that their license covers the total number of devices used across their Application Servers. See Important points to know about PaperCut NG/MF licensing (Global set of entitlements) for more information. [PO-1302]
• Updated EULA. The EULA has been updated for version 24. See End User License Agreement (EULA) for more information. [PO-2072]

Security:

• Updated third party dependancies [PO-1725][PO-2306]

Fixes:

• Increased the grace period for existing customers who upgrade to 24.x that cannot access the Global Entitlements Service from 30 to 120 days. See Known issue PO-2223 (Internet connection required) for more information. [PO-2440]
• Fixed a rare issue where bulk user actions could create/update a user to have the same primary username as another user’s alias. For bulk user operations, the primary username will now always take priority and the clashing alias will be removed. [PO-2143]
• Fixed a problem that when an end user clicks on the shared PCClient/win/pc-client-local-cache.exe file in the server folder, the cached version of the desktop client was always 1.0.0.0, which prevented timely updates of the user client binaries to the end user computers. [PO-1877]
• Google Cloud Directory: Multi-domain user syncing for normalized (aka domain-less) user names. [PO-2341]
• Fixed the setup of user groups to reflect changes made to the sync domain(s) specified. [PO-2380]
• Added the ability to batch import internal users without having to specify passwords (reverting back to the behavior prior to version 22.1.0). [PO-2236]
• Fixed a web-SSO issue that caused admins to be incorrectly redirected to the logout page. [PO-1812]
• Fixed an issue where a user sync was occurring on a secondary sync source when disabled. [PO-2403]
• Fixed a bug that allowed the creation of new internal users with usernames already taken for other users’ aliases in both UI and server command CLI. Also fixed a bug in the server command that could create a new standard user with a username already taken as another user’s alias. [PO-1506]
• User Sync: Improved user card PIN encoding times, and added an option to configure encoding strength. [PO-2226]
• Fixed an issue that prevented the user client and release station from launching in conjunction with screen readers such as NVDA. [PO-1700]

Print Provider:

• Sharp PostScript printer drivers and PPDs: Fixed an issue that caused incorrect total and color page counts when using booklet or poster print mode. [PIE-744]
• Fixed an issue that could cause delays when releasing print jobs if the ‘ServerName’ configuration is set. [PIE-762]

Other notes:

• A DB upgrade does occur when upgrading to this version.