We have a dev install of TeamCity Enterprise running on Windows Server 2008 R2 x64 with build two agents installed locally and a third agent installed on a Windows Server 2003 machine. Our Production TeamCity Enterprise install is on Windows Server 2003 machines. All agents are installed as a windows service.
The Agents on our production install and the dev Windows Server 2003 machine report their user.name the same as the account for the windows service (in our case svc-build-d). On the Windows Server 2008 R2 machine, they report SYSTEM. Other parameters, like user.home on the Windows Server 2008 R2 machine, contain svc-build-d. The service controller (services.msc) shows svc-build-p. Restarting the agent service, TeamCity web service, and the entire machine did not resolve the issue.
Adding system.user.name=svc-build-d to the buildAgent.properties file has been the only way for me to get the correct username on the Windows Server 2008 R2 machine. This is important to us because we use user name as agent requirements in our CI.
Is this a known issue or is there something else I can try, short of overriding the value, to fix this?