Welcome to our Knowledge Base

Enter your search terms below.

< All topics

No autostart of the steadyPRINT Agents on terminal servers

Description of the problem

After the installation of the steadyPRINT Agent on a terminal server, the steadyPRINT Agent does not start automatically on user login.

Reason: The autostart entry in the registry was not created. This can happen if the installation of the steadyprint.msi was not performed via an elevated prompt or if the installation was performed with a quiet parameter (if applicable via software distribution).


Manually set the autostart entry in the registry once (if applicable via script/software distribution/GPP). The following entry refers to version 8.0, in case you are using a different steadyPRINT version, the path to spclienthost.exe can differ from the specified path.

Set the entry C:\Program Files (x86)\steadyPRINT 8.0\spclienthost.exe in the Key Userinit HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon.

As an alternative, the steadyprint.msi can be uninstalled and reinstalled via an elevated promt (Alternatively, kann eine Deinstallation und erneute Installation der steadyprint.msi über eine elevated prompt ausgeführt werden (start command line as administrator).

ID: 20108 | Zur deutschen Version

Was this article helpful?
0 out Of 5 Stars
5 stars 0%
4 stars 0%
3 stars 0%
2 stars 0%
1 stars 0%
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Back Make printers available only to specific users
Next Overview for storing user- and object-related data within steadyPRINT