Menu
▾
▴
#129 Grant "log on as service" rights when installing a service
When installing as a windows service it would be really handy if the user that are configured to run the service is granted the "log on as service" rights.
If the user does not have the rights to log on a service it will be impossible to start the service.
This API call can do it:
http://msdn.microsoft.com/en-us/library/ms721786\(v=vs.85).aspx
Tobias,
I'm very sorry for the long delay.
I have implemented your suggestion. It will be part of the next release.
The suggestion about the CPU affinity still needs a while until I can implement it for all supported platforms (Win, linux, hpux, aix, mac, freebsd etc....) . So please hold on for a little bit more.
Best Regards,
Hi,
There seems to be a bug in the implementaion.
In 3.5.10 it works if using a local account. But if trying to add a service that should run as a domain user it will not set the "log on as service" rights.
It prints "OpenPolicy failed 1722" in the prompt instead.
I have added
wrapper.debug=TRUE
wrapper.console.loglevel=DEBUG
to the conf file and get this output:
ServiceInstaller.exe -i RoboServer.conf wrapper.ntservice.account=kapow.local\tt wrapper.ntservice.password.prompt=true wrapper.nts
ervice.name="RoboServer8.1.6" wrapper.ntservice.starttype=AUTO_START wrapper.app.parameter.1="-service" wrapper.app.parameter.2="socket:50000"
Service command: "\\vmware-host\Shared Folders\trunk\build\win64dist\bin\ServiceInstaller.exe" -s "\\vmware-host\Shared Folders\trunk\build\win64dist\bin\RoboServer.conf" wrapper.ntservice.name=RoboServer8.1.6 wrapper.ntservice.starttype=AUTO_START wrapper.app.parameter.1=-service wrapper.app.parameter.2=socket:50000 wrapper.console.flush=true wrapper.internal.namedpipe=0099929698
Prompting for account password...
Please input the password for account 'kapow.local\tt': ********
OpenPolicy failed 1722
RoboServer8.1.6 service installed.
Environment: Windows 7, 3.5.10 standard.
Tobias,
thank you very much for your report.
I'm very sorry for the trouble this might have caused you. I was reviewing the part of the code responsible for doing that and could fix the bug...
best regards,
Christian
Tobias,
I'm sorry for the delay on getting back to you.
We have released version 3.5.12 last week, which should fix the issue for the domain users when granting "log on as service".
I would appreciate if you could give it a try.
Thank you,
Christian
I can confirm that it works now. I have tested it on Windows 7 x64.
Hello Tobias,
thank you for your feedback.
I always appreciate your contribution with your ideas.
thank you,
Christian