# Silent install

> Install Test Manager silently on your machine through the command-line. For this option, you need to download and open a command-line to run the [UiPath Test Manager installation kit](https://download.uipath.com/UiPathTestManager.msi). Alternatively, if you execute through PowerShell, you can call the installation package using `.\UiPathTestManager.msi`.

Install Test Manager silently on your machine through the command-line. For this option, you need to download and open a command-line to run the [UiPath Test Manager installation kit](https://download.uipath.com/UiPathTestManager.msi). Alternatively, if you execute through PowerShell, you can call the installation package using `.\UiPathTestManager.msi`.

Make sure that your environment is ready, by meeting the and requirements.

:::important
The `APPPOOL_IDENTITY_TYPE` and `DB_AUTHENTICATION_MODE` commands are case sensitive.
:::

## Commands

The following section lists the available command-line parameters, including options and default values.

 <colgroup>
  <col/>
  <col/>
 </colgroup>
 
  
     Command  
     Description  
  
 
 
  
    <code>INSTALLDIR</code> (Optional) 
    Enables you to install Test Manager in a custom location. By default, TestManager is installed in <code>C:\Program Files (x86)\UiPath\TestManager</code> . 
  
  
    <code>WEBSITE_PORT</code> (Optional) 
    The port you want to use to enable the communication between the machine and Test Manager. If not specified, the default value is set to <code>443</code> to enable HTTPS. Since Orchestrator is using the same port, you need to specify a different one, if you have both components installed on the same machine. 
  
  
    <code>CERTIFICATE_SUBJECT</code> (Optional) 
     The name of the SSL certificate you want to use to secure connections with Test Manager. If not specified, the full machine name is used as default.  If you have multiple certificates with the same subject, you need to specify the thumbprint from Certificate Manager Tool.  
  
  
    <code>PORT_DO_VALIDATE</code> (Optional) 
    Enables you to select whether the website port availability validation is performed or not. Set to <code>1</code> to perform validation. Otherwise, set to <code>0</code> if you do not want to perform validation. 
  
  
    <code>PORT_FIREWALL</code> (Optional) 
    Enables you to select if the firewall rules are automatically added for this port. Set to <code>1</code> to create firewall rules. Otherwise, set to <code>0</code> if you do not want to set firewall rules. 
  
  
    <code>HOST_NAME</code> 
    Add the Fully Qualified Domain Name (FQDN) or the DNS name of the server (for example, <code>yourTestManagerInstance.yourDomain.com</code> ). This is the server host name for the virtual or physical instance of Test Manager. 
  
  
    <code>APPPOOL_IDENTITY_TYPE</code> 
     The type of application pool you are using for Test Manager. You can use one of the following parameters: 
      
         <code>SpecificUser</code> - Select this option to run the Test Manager website under an existing Windows or Domain Identity. You need to fill in the Username and Password fields; 
         <code>ApplicationPoolIdentity</code> - Select this option to run the Test Manager website under the default identity of the application pool. 
      

  
  
    <code>APPPOOL_USER_NAME</code> * 
   
      
         Mandatory command if <code>APPPOOL_IDENTITY_TYPE</code> is configured with the <code>SpecificUser</code> option.  The username running the application pool.  
      

  
  
    <code>APPPOOL_USER_PASSWORD</code> * 
   
      
         Mandatory command if <code>APPPOOL_IDENTITY_TYPE</code> is configured with the <code>SpecificUser</code> option.  The password of the user that is running the application pool.  
      

  
  
    <code>DB_SERVER_NAME</code> 
     The name of the server on which the database you want to use is located.  
  
  
    <code>DB_DATABASE_NAME</code> 
     The name of the database you want to connect to.  
  
  
    <code>DB_AUTHENTICATION_MODE</code> 
     Enables you to choose the authentication method for the database. You can use one of the following parameters: 
      
         <code>WindowsIntegrated</code> - This is the default option. If you choose this option, Test Manager connects to the database using the detected IIS Application Pool's Windows account and creates the database using the Windows Credentials of the currently logged in user; 
         <code>ServerAuthentication</code> - Choose this option to use your SQL Server Credentials. You need to fill in the SQL Username and Password fields. 
      

  
  
    <code>DB_USER_NAME</code> * 
   
      
         Mandatory command if <code>DB_AUTHENTICATION_MODE</code> is configured with the <code>ServerAuthentication</code> option.  The SQL database user.  
      

  
  
    <code>DB_USER_PASSWORD</code> * 
   
      
         Mandatory command if <code>DB_AUTHENTICATION_MODE</code> is configured with the <code>ServerAuthentication</code> option.  The SQL database user password.  
      

  
  
    <code>ORCHESTRATOR_URL</code> 
     The URL of the parent Orchestrator instance that you want to use.  
  
  
    <code>IDENTITY_URL</code> 
    The URL of the Identity endpoint of the Orchestrator instance specified by the <code>ORCHESTRATOR_URL</code> parameter. 
  
  
    <code>TEST_MANAGER_URL</code> 
     The URL of the Test Manager instance that will be created.  
  
  
    <code>ORCHESTRATOR_TENANT_NAME</code> 
    The Orchestrator tenant that you want to integrate with Test Manager. Set the value to <code>Default</code> if you want to use the default tenant. Otherwise, you need to specify the tenant name. 
  
  
    <code>ORCHESTRATOR_ADMIN_PASSWORD</code> 
    The administrator password of the Orchestrator tenant specified by the <code>ORCHESTRATOR_TENANT_NAME</code> parameter. 
  
  
    <code>IDENTITY_INSTALLATION_TOKEN</code> 
     The token generated through the Orchestrator Identity. You can generate the token in Orchestrator Identity Management by logging in as the host tenant. For more information, see  Generate an installation access token  .  
  
  
    <code>/q</code> 
     Installs the specified UiPath features silently, without displaying the user interface. Use this mode only for unattended installations.  
  
  
    <code>/l*vx &lt;LogFile&gt;</code> (Optional) 
     Generates an installer log file at the specified path. You can send the file further to our support team if, for any reason, you encounter difficulties during the installation process.  
  
 

## Shell Script Sample

```
UiPathTestManager.msi `
CERTIFICATE_SUBJECT=UserMachine.company.com `
APPPOOL_IDENTITY_TYPE=SpecificUser `
APPPOOL_USER_NAME=AppPoolUser `
APPPOOL_USER_PASSWORD=Password `
DB_SERVER_NAME=. `
DB_DATABASE_NAME=UiPathTestManagerDatabaseName `
DB_AUTHENTICATION_MODE=ServerAuthentication `
DB_USER_NAME=DatabaseUsername `
DB_USER_PASSWORD=Password `
WEBSITE_PORT=555 `
ORCHESTRATOR_URL=https://UserMachine.company.com `
IDENTITY_URL=https://UserMachine.company.com/identity `
TEST_MANAGER_URL=https://UserMachine.company.com:555 `
ORCHESTRATOR_TENANT_NAME=Default `
ORCHESTRATOR_ADMIN_PASSWORD=Password `
IDENTITY_INSTALLATION_TOKEN=GeneratedThroughOrchestratorIdentityManagement `
/q `
/l*xv <LogFile>
```

:::tip
Check out the following additional actions:
* [Encrypt Test
Manager Config File](https://docs.uipath.com/test-manager/standalone/2024.10/installation-guide/test-manager-config-file-encryption).
:::