--- schema_version: "1" id: d0abb55feacbb3d58d2af6b8e372f41ca06b61f4fc596e19351a0a154306bdc2 title: Tableau Server Administration Agent collection: tableau version: current locale: en-gb portal_url: https://docs.salesforce.com/tableau/current/en-gb/server/server_process_admin-agent.md canonical_url: https://help.tableau.com/current/server/en-gb/server_process_admin-agent.htm source_site: help.tableau.com content_type: documentation content_hash: 89363ae9e28e8b88b9bdf0ca573e166e55fbf8f7d9d9e2b37b1bff6b4e86515e description: Understand the Tableau Server Administration Agent process. --- [Skip to main content](#main-content) # Tableau Server Administration Agent The Administration Agent monitors the Coordination Service for changes to configuration or topology and delivers new configurations to each service (configuration) or deploys new services and removes old ones (topology). The Administration Agent also checks each of the services for status and reports this back to the Coordination Service. This process will be automatically configured on each node of the cluster during installation – no explicit configuration is required or possible. The Administration Agent may also be referred to as the _TSM Administration Agent._
Process

Administration Agent

StatusStatus of the Administration Agent process is not visible on the Status Page. Use the TSM CLI to view status. For more information, see View Server Process Status
LoggingLogs generated by the Administration Agent process are located in C:\ProgramData\Tableau\Tableau Server\data\tabsvc\logs\tabadminagent. For more information, see Tableau Server Logs and Log File Locations
What happens when an Administration Agent process fails? All other Tableau Server processes running on the same node will display as “unavailable” on the TSM status page. Tableau Server will continue to work as expected, however you will not be able to make configuration/topology changes to the cluster. Failed Administration Agent processes automatically restart as long as the computer itself is otherwise healthy. If the Administration Agent doesn’t start up on the node, you can try to start the service manually by running the following command: `sc start tabadminagent_0`