Description of the problem
We have extended our license volume by additional Windows CAL licenses so that steadyPRINT can be provided to all users in our company. We have realized, however, that after the import of the new licenses some clients are still unable to apply the license and thus to get the printers connected. Could you provide further assistance?
Description of the problem
I would like to use double-sided printing for a multi-page document. There are several setting options at different places. Where do I set the correct setting?
Description of the problem
I would like to print a multi-page Microsoft Word document with the print option “stapling”. My printer is equipped with a stapling unit. If this option is specified in Word, the paper leaves the printer without being stapled.
What am I doing wrong?
Description of the problem
As in some environments there might be delays during the login process of the steadyPRINT Agent due to different libraries and program dependencies, Microsoft offers the option to have *.dll-files loaded to the so-called Global Assembly Cache (for more information click here.
Description of the problem
It may occur that printer connections that require a driver installation cannot be established. This means that the printers to be connected are displayed in the steadyPRINT Agent but that the printer connection, however, cannot be established under Microsoft. This is often caused by a faulty or non-configuration of the point-and-print group policy.
Description of the problem
When deleting a printer, printer drivers are not removed although this function is enabled in the Agent profiles. 
Could you provide further assistance?
Problem description Due to an internal changeover, we would like to create the printer connections with the FQDN, e.g. „\\printserver01.steadyprint.com\printer01“. Is it possible to adjust the name when connecting the printers via steadyPRINT?
Description of the problem
We are using the steadyPRINT Agent on a terminal server with Windows Server 2008 R2.
Printer assignments with vName, vPrinter and vDirect are created via the Agent and are visible for all users with s server session, but not for the assigned users.
Can you provide further assistance?
Description
If you are using Branch Office Server licenses, please contact your account manager or our support team as these licenses have been eliminated and the functionalities are now provided in a different way.
Description of the problem
It may sometimes happen that in a terminal server environment the client name is not correctly determined when reconnecting the session from another computer.
Scenario:
If computers are now assigned via the client name, they will possibly be incorrect as the new client name has not been determined correctly.
