You are viewing the documentation of TeamCity 2018.x, which is not the most recently released version of TeamCity.
View this page in the latest documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.


Versions Compared


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


If you want to get a pre-configured server right away, put files from a previously configured server into the Data Directory. For each new server you will need to ensure it points to a new database (configured in <Data Directory>\config\database.properties) and change <Data Directory>\config\main-config.xml file not to have "uuid" attribute in the root XML element (so new one can be generated) and setting appropriate value for "rootURL" attribute.

 NotesNotes on configuring Windows for the server setup (based on Windows Server 2016):
- enable Remote desktop connectionscreateconnections
- create dedicated user (e.g. "TeamCity") and assign it administrator permissionsdisablepermissions
- disable disk indexing for all disks (or at least for the diskdisks withwhere TeamCity home and TeamCity Data Directory are locatedcheck Windows located)
- disable real-time protection и cloud-based protection in Windows Defender
- check Windows Firewall is enabled (counter-intuitively this changes Windows network stack behavior to handle more incoming but not yet accepted network connections)
on Windows Firewall settings:
-- enable incoming connections to TeamCity application portsenableports
-- enable ICMP pingsenablepings
-- enable ports for monitoring agent, etc.
- (if IPv6 network is not used) disable ipv6 on network adapter settingsdisablesettings
- disable weekly schedule for fragmentation analyzingdisableanalyzing
- disable "Optimize drive" service
- (for manual updates application) set Windows updates policy to "DownloadOnly" via sconfig utility
- consider enabling jumbo frames and ensuring that the network supports the setting

Using another Version of Tomcat