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“. […]
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.
Description of the problem
We would like to exclusively use steadyPRINT BranchOffice printer assignments in future. The end user himself should be able to create them via the steadyPRINT Agent. At the moment this is only possible for Windows printer assignments via the Agent. An assignment via the steadyPRINT Center, however, works without problems. Could you provide further assistance?
Description of the problem
We are comprehensively using BranchOffice assignments in steadyPRINT. We have noticed that settings made on the print server are transferred to the Client and then to the BranchOffice printer with a delay. Generally this is not a problem for us but we would like to find out the reason.
Description of the problem:
We have recently renamed a printer on the print server and noticed that it is now no longer reconnected on the Clients. Can you provide further assistance?
