Closed yosiasz closed 6 years ago
In most cases, yes, it should be what's used in the login tab. Keep in mind it needs to be an actual user, either registered with the machine or Active Directory. If it can't find the user, it would fall back to the local system account.
NT AUTHORITY\LOCAL SERVICE is not working, the output is as described above where it appears to fallback to the NTA\SYSTEM account.
Specifying svc.user.account = 'LOCAL SERVICE'
also has the same effect.
I'm running into similar problems, though it's entirely possible it's me being stupid. I've tried
service.user.domain = "domain";
service.user.account = "samaccountname";
service.user.password = "password";
as well as
service.user.domain = "domain";
service.user.account = "samaccountname@domain";
service.user.password = "password";
as well as
service.user.account = "domain/samaccountname";
service.user.password = "password";
as well as a local account, all to no avail, the service always runs as LOCAL SYSTEM. I am running the script from an administrative command prompt with domain admin permissions (win8.1).
Just in case anyone else is running into this issue I wanted to update this with the solution. I dove into the source code and found that instead of using the documentation based solution:
svc.user.domain = 'mydomain.local';
svc.user.account = 'username';
svc.user.password = 'password';
you'll need to use the following:
svc.logOnAs.domain = 'mydomain.local';
svc.logOnAs.account = 'username';
svc.logOnAs.password = 'password';
I think the documentation should be updated to correct the instructions. @coreybutler
Thanks for bringing this up @nick-beers. This should be consistent across all node-{os} packages.
Greetings,
Great tool! When creating a service and specifying domain, username and password, is this the user name used in the Logon tab of the service property? Because if it is, it is not sticking, it just shows, local System account enabled.
Thanks!