New answers tagged windows-service
I found this Microsoft Blog which got me looking at using the server's hostname vs. CNAME. Specifically, the below snippets: If you answered DNS name resolution you would be correct. If name resolution is not working properly in the environment it will cause the application requesting a Kerberos ticket to actually request a Service ticket for the ...
Run the service under an user account to bypass the problem.
Because when you access a UNC share without previously established network credentials, you end up as anonymous. The local SYSTEM account obviously isn't a valid network login.
I ran it manually as ETL suggested, and the problem turned out to be that the jmxremote.password file needs to have its permissions set to only be readable by its owner, which should be set to whichever user the service runs as.
You can try this : (Get-WmiObject Win32_Service -Filter "name='TCBuildAgent'").Change($Null,$Null,$Null,$Null,$Null,$False,'teamcity@omnicorp','password') The 6th parameter correspond to "DesktopInteract", and normally, the service cannot be granted rights to interact with the desktop, unless it is the Local System account.
Top 50 recent answers are included