Welcome to our knowledgebase

Browse our knowledge base.

Categories

Category - steadyPRINT Agent

Article

steadyPRINT Agent does not start – no database access
It is not possible for the user to set the local default printer via steadyPRINT Agent
Autostart does not work under Windows Vista and higher
steadyPRINT Agent/Center does not start: Application error (ID 1000)
Adding a printer connection fails due to group policy settings
Printer driver installation fails due to missing privileges
Printer connection is not created after assignment via steadyPRINT Center
steadyPRINT Agent remains in offline mode after autostart when using Microsoft Direct Access
steadyPRINT Agent remains in offline mode after autostart
steadyPRINT Agent does not install the latest printer driver
Default printers cannot be set by steadyPRINT Agent under Windows XP
Printer connections in a terminal server session based on the computer name are not set up
No loss of (old) printers from previous terminal sessions
After user login, the steadyPRINT Agent automatically appears in the foreground
Automatic inclusion of printer connections without function that are not administered by steadyPRINT
Determination of status information takes “a long time”
Creating a printer connection is slow
Bandwidth consumption
Deactivate welcome screen does not work on provisioned terminal servers
The license volume is exhausted
Printers are not connected
Using the same printers for local and terminal server sessions
Printer assignment for Thin Clients
Printers are displayed in the root-path again after having been moved into a folder
The steadyPRINT setup is closed with the error “2203”
Setting of (pre-defined) default printers does not work
steadyPRINT Agent is started and a licence message appears immediately
steadyPRINT Agent cannot create a connection to the database
Do you trust this printer?
Make printers available only to specific users
When does steadyPRINT update printer connections?
High load on database server despite high values in performance profiles (fixed in Version 6.5.0)
Automatic update without function
Connecting printers takes a long time
Local default printer does not remain permanently stored
Nested Groups
Support information from Agent
Inventory of computer information
Component overview shows wrong entries
Inventory of local printers and computer information
Agent remains in offline mode after update
Window for selecting the default printer
No autostart of steadyPRINT Agent on terminal servers
Agent terminates unexpectedly after longer runtime (fixed in Version 5.2.1)
Agent no longer works after update to Windows Server 2003
No inventory of local printers
When using collective accounts, Agent on terminal server only starts at first login (fixed in version 5.2.3)
Printers are not connected after update to version 6 (fixed in Version 6.0.1)
Installation of steadyPRINT VPD not possible in Citrix environments
Automatic Logging
Default printer is not maintained for vDirect assignment
Updating printer properties of BranchOffice printers
Create BranchOffice printer assignments by the user
Do I have to carry out an installation on the client for steadyPRINT?
Thin Clients are supported by steadyPRINT. Apart from Windows, are there also other operating systems, such as Linux or Mac OS, supported on Workstations?
Does steadyPRINT also support other user directories such as Novell eDirectory, for example?
Requirements for the use of steadyPRINT
Printer connections cannot be established due to a point-and-print group policy that has not or incorrectly been configured
steadyPRINT Agent freezes after network change (fixed in Version 6.5.4)
Printer mappings under Win2008R2 terminal server
steadyPRINT Agent is offline, steadyPRINT Service without function
Printer driver cannot be deleted/removed/cleared up. Driver still in use
Acceleration of the start process
VPD: Print options Punching and Stapling with MS Word Quick Select do not work
Branch Office print server no longer available
Creating printer connections based on FQDN
Incorrect Client name after taking over session
PIN becomes invalid when changing from master to backup print server
No Windows CAL available, printers are not connected
steadyPRINT Agent is offline, VPD print jobs are not prepared
No autostart of the steadyPRINT Agents on terminal servers
Printer assignment via Center is delayed for users
Importing a new license
Integrated steadyPRINT PDF printer
Extended Logging
+ 67 Article
Show all articles