Acceleration of the start process

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.

Read more

Printer connections cannot be established due to a point-and-print group policy that has not or incorrectly been configured

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.

Read more

steadyPRINT Agent is offline, steadyPRINT Service without function

Description of the problem

With some client operating systems we realized that the steadyPRINT Agent is permanently offline.

Symptoms:

  • The steadyPRINT Agent is offline
  • The steadyPRINT Service is being performed
  • The credentials for the database connection are not hashed in the registry under computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\steadySUITE\steadyPRINT\PAS.
  • The PAS does not create a debug-log

Reason: The reason is a bug in the .NET Framework.

Read more

Printer driver cannot be deleted/removed/cleared up. Driver still in use

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?

Read more

Creating printer connections based on FQDN

Problem description Due to an internal changeover, we would like to create the printer connections with the FQDN, e.g. „\\printserver01.steadyprint.com\printer01“. […]

Printer mappings under Win2008R2 terminal server

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?

Read more

Branch Office print server no longer available

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.

Read more

steadyPRINT Agent freezes after network change

Description of the problem

We have increasingly rolled out the steadyPRINT Agent on usual Windows workstations. We have realized that after a network change the Agent sometimes freezes. Is this a known problem?

Read more

Incorrect Client name after taking over session

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:

  1. The user logs on to the terminal server. The client name is correctly identified.
  2. The user logs on to the terminal server via another computer and takes over the existing/disconnecte session. In this case the client name from the first session might remain.

If computers are now assigned via the client name, they will possibly be incorrect as the new client name has not been determined correctly.

Read more

Create BranchOffice printer assignments by the user

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?

Read more