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

Updating printer properties of BranchOffice printers

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.

Read more

Default printer is not maintained for vDirect assignment

Description of the problem

In our company steadyPRINT vDirect printers are exclusively assigned via groups. In this context we have noticed that the default printer set by the user is not maintained after the restart. Can you provide further assistance?

Read more

Automatic Logging

Description of the problem

We have noticed that steadyPRINT creates log files in the user profile, or more precisely in the AppData directory. This is desirable and helps us in troubleshooting. Is it possible to adjust the logging so that steadyPRINT writes less information, i.e. only errors?

Read more