Limitations
Print Roaming with multiple servers within WAN (Far-roaming mode)
Printing jobs over far roaming is currently not available using a new client in combination with Job Service.
Offline accounting - parsing of duplex and copy count information works only for PCL and PCL 6 jobs
Due to the limitation in the current version of mako-parser library, only PCL and PCL 6 (PCL XL) jobs have correctly parsed information regarding duplex and number of copies. Other formats return the default value of duplex, 1 copy.
Rule based engine
Compatibility table of print languages and rules:
Rule | PCL 6 | PCL 5 | PS | XPS | XCP | |
|---|---|---|---|---|---|---|
Convert to simplex |
| N/A | ||||
Convert to duplex |
| N/A | ||||
Convert to grayscale | N/A | |||||
Print more than once |
| N/A | ||||
Watermark | N/A | |||||
PJL headers | N/A |
Manual print location selection
Due to limited usage of manual print location selection, it is not fully compatible when combined with "SiteServerSources" set to "jobservice". In this case, both main locations ("jobservices") and their obtained locations in their cluster are combined together in the dropdown for the user to choose from. Also, when a different main location ("jobservice") is selected, its cluster locations are not immediately obtained, and the Spooler service needs to be restarted first. Also, when the location is changed, you might need to log in again.
YSoft Client v3 network-level load balancing, network-level failover
Load balancer must send all requests from the client to the same job service, and infinite affinity must be set for the load balancer if support for user notifications is required.
Scenarios that are not supported for YSoft Client V3 + load balancer:
Spool cleaning is not working if the client disconnects, the job service receives a delete request from SPOC, and then the client connects to a different job service.
If user notifications are set in Rule-Based Engine, they will not be displayed on the user workstation.
Auto update of YSoft Client v3.
Job data and meta data must be forwarded to the same site server
Mobile Print Server and Mobile Integration Gateway
Mobile Print Server / Mobile Integration Gateway and Client v3 integration is not supported. FSP is required if MPS / MIG functionality is needed.
Processor architectures limitations
Currently the YSoft Client V3 on ARM64 architecture machines is supported only for Windows 11 64bit operating system.