Dienst als User in XP starten

[swatchy]

Hi!

Wie kann ich einen User Rechte geben,
damit er einen Dienst starten kann?
Möchte PCAnywhere 12 einsetzen. Der User soll eine Hostverbindung
sebständig aufrufen können. Da das Programm die Hostverbindung als Dienst installiert, kann ein User die Hostverbindung nicht starten.

Vielen Dank

Swatchy

[spunz]

wenn pcANYWHERE die verbindung als dienst startet, kann diese durch den user nicht nochmals gestartet werden. du den hacken "mit windows starten" entfernen, dann kann der user die verbindung nach bedarf selber starten.

[swatchy]

Danke für Deine Anwort, aber Sie hilft leider nicht.
Der Haken bei Windows starten ist nicht gesetzt.
Aber der "als Dienst starten" schon . Ist Grau und kann daher nicht
weggeklickt werden.
Ein normaler User kann leider keinen Dienst starten.

[zigeina]

du musst im dienste konfigurations fenster den dienst auf manuell starten setzen, dann wird er nicht mit windows start automatisch gestartet.

es gibt das recht "anmelden als dienst", dann läuft der dienst unter diesem account. aber das willst du sicher nicht.
du könntest den benutzer in die gruppe power user geben, vielleicht darf er dann den dienst starten., aber nur wenn der dienst nicht läuft.

normalerweise sollte das die applikation dahinter machen.

[kikakater]

Das wird Dir helfen, den Dienst zu starten:

NetExec

NetExec Features
What sets NetExec apart from similar tools

NetExec, first released in 1997, was one of the first tools for Windows NT providing the functionality to run a program under a foreign account. In the meantime there are many so-called "su" tools with similar basic functions available. Beginning with Windows 2000 even Mircosoft ships such a tool, named "RunAs.exe".

However, NetExec contains a lot of unique features:

* Desktop-Manager
The Desktop-Manager lets you create addition login-sessions, each running on its own desktop. This brings the Windows XP "Fast user switching" feature to your Windows NT/Windows 2000 box. But even Windows XP users will love it, as Desktop-Manager is much simpler to use and consumes fewer (a lot fewer!) system ressources.
* Create your own clients
Using the CustomClient-Creator add-on, you can create special .EXE-files, that run a predefined command line under a different account. The command line and the password are stored encrypted inside the .EXE.
* No special privileges needed
Some su-tools require that certain, high power privileges like SeTcbPrivilege ("Act as part of operating System") are assigned to user accounts. This is very dangerous because it gives users the power to make themself member of the Administrators group! NetExec does not need such privileges.
* Extended security features
NetExec contains even more features for enhanced security. Additional sessions can be closed automatically, desktops can be password protected and much more.
* Extended network support
NetExec was designed for optimal usage in client server environments. Roaming profiles are full supported. Novell- or Windows networks are supported by special functions.
* Complete command line interface
Besides a very comfortable GUI NetExec is completely usable from the command line. Some special command line options make NetExec a first choice in advanced batch file scenarios like automatic software rollouts.
* Temporary Administrator group memberships
Another feature that make NetExec a excellent choice for software installation scenarios are extended group memberships. Using this feature it is possible to run a process under a non-privileged user account, but inside this process the user becomes also a member of the Administrators group. Therefore the app uses the profile, settings and home directory of the non-privileged user account, but runs with Administrator privileges.
* Multilanguage support
User interface and help files are available in English and German languages. The preferred language can be changed at runtime and is stored as a per user setting.
* Runs on Terminal Services
Most su-tools fail completly, if used from a terminal session hosted on Windows 2000 Advanced Server. The same problem applies to Windows XPs additional logon session created by "Fast user switching". NetExec works even well in such scenarios.

[kikakater]

Doppelpost