Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • agent process (java) should be able to open outbound HTTP connections to the server address (the same address you use in the browser to view TeamCity UI) and accept inbound HTTP connections from the server to the port specified as "ownPort" property in "<TeamCity agent home>/conf/" file (9090 by default). Please ensure that any firewalls installed on agent, server machine or in the network and network configuration comply with these requirements.
  • have full permissions (read/write/delete) to the following directories: <agent home> (necessary for automatic agent upgrade), <agent work>, and <agent temp>.
  • launch processes (to run builds).



  • Log on as a service (to run as Windows service)
  • Start/Stop service (to run as Windows service, necessary for agent upgrade to work, see also Microsoft KB article)
  • Debug programs (for take process dump functionality to work)
  • Reboot the machine (for agent reboot functionality to work)


titleService system account

To run builds, the build agent should be started under a user with enough permissions for performing a build and managing the service.By default, Windows service in started under SYSTEM ACCOUNT. To change it, use the Services applet (Control Panel|Administrative Tools|Services)


The file <agent home>\launcher\conf\wrapper.conf can also be used to alter agent JVM parameters.

User account that is used to run build agent service should have enough rights to start/stop agent service.


A method for assigning rights to manage services is to use the Subinacl.exe utility from the Windows 2000 Resource Kit. The syntax for this is:
SUBINACL /SERVICE \\MachineName\ServiceName /GRANT=[DomainName]UserName=Access

Using LaunchDaemons Startup Files on MacOSx