mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
29 KiB
29 KiB
title, description, author, ms.assetid, ms.reviewer, manager, ms.author, ms.pagetype, ms.mktglfcycl, ms.sitesec, ms.prod, ms.date
| title | description | author | ms.assetid | ms.reviewer | manager | ms.author | ms.pagetype | ms.mktglfcycl | ms.sitesec | ms.prod | ms.date |
|---|---|---|---|---|---|---|---|---|---|---|---|
| How to Deploy the App-V 5.1 Server Using a Script | How to Deploy the App-V 5.1 Server Using a Script | dansimp | 15c33d7b-9b61-4dbc-8674-399bb33e5f7e | dansimp | dansimp | mdop, appcompat, virtualization | deploy | library | w10 | 06/16/2016 |
How to Deploy the App-V 5.1 Server Using a Script
In order to complete the appv_server_setup.exe Server setup successfully using the command line, you must specify and combine multiple parameters.
To Install the App-V 5.1 server using a script
-
Use the following tables for more information about installing the App-V 5.1 server using the command line.
Note
The information in the following tables can also be accessed using the command line by typing the following command: appv_server_setup.exe /?.
**Common parameters and Examples**
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p>To Install the Management server and Management database on a local machine.</p></td>
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
<ul>
<li><p>/MANAGEMENT_SERVER</p></li>
<li><p>/MANAGEMENT_ADMINACCOUNT</p></li>
<li><p>/MANAGEMENT_WEBSITE_NAME</p></li>
<li><p>/MANAGEMENT_WEBSITE_PORT</p></li>
<li><p>/DB_PREDEPLOY_MANAGEMENT</p></li>
<li><p>/MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT</p></li>
<li><p>/MANAGEMENT_DB_NAME</p></li>
</ul>
<p>To use a custom instance of Microsoft SQL Server, use the following parameters:</p>
<ul>
<li><p>/MANAGEMENT_SERVER</p></li>
<li><p>/MANAGEMENT_ADMINACCOUNT</p></li>
<li><p>/MANAGEMENT_WEBSITE_NAME</p></li>
<li><p>/MANAGEMENT_WEBSITE_PORT</p></li>
<li><p>/DB_PREDEPLOY_MANAGEMENT</p></li>
<li><p>/MANAGEMENT_DB_CUSTOM_SQLINSTANCE</p></li>
<li><p>/MANAGEMENT_DB_NAME</p></li>
</ul>
<p>Using a custom instance of Microsoft SQL Server example:</p>
<p>/appv_server_setup.exe /QUIET</p>
<p>/MANAGEMENT_SERVER</p>
<p>/MANAGEMENT_ADMINACCOUNT=”Domain\AdminGroup”</p>
<p>/MANAGEMENT_WEBSITE_NAME=”Microsoft AppV Management Service”</p>
<p>/MANAGEMENT_WEBSITE_PORT=”8080”</p>
<p>/DB_PREDEPLOY_MANAGEMENT</p>
<p>/MANAGEMENT_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”</p>
<p>/MANAGEMENT_DB_NAME=”AppVManagement”</p></td>
</tr>
</tbody>
</table>
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p>To Install the Management server using an existing Management database on a local machine.</p></td>
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
<ul>
<li><p>/MANAGEMENT_SERVER</p></li>
<li><p>/MANAGEMENT_ADMINACCOUNT</p></li>
<li><p>/MANAGEMENT_WEBSITE_NAME</p></li>
<li><p>/MANAGEMENT_WEBSITE_PORT</p></li>
<li><p>/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL</p></li>
<li><p>/EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT</p></li>
<li><p>/EXISTING_MANAGEMENT_DB_NAME</p></li>
</ul>
<p>To use a custom instance of Microsoft SQL Server, use these parameters:</p>
<ul>
<li><p>/MANAGEMENT_SERVER</p></li>
<li><p>/MANAGEMENT_ADMINACCOUNT</p></li>
<li><p>/MANAGEMENT_WEBSITE_NAME</p></li>
<li><p>/MANAGEMENT_WEBSITE_PORT</p></li>
<li><p>/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL</p></li>
<li><p>/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE</p></li>
<li><p>/EXISTING_MANAGEMENT_DB_NAME</p></li>
</ul>
<p>Using a custom instance of Microsoft SQL Server example:</p>
<p>/appv_server_setup.exe /QUIET</p>
<p>/MANAGEMENT_SERVER</p>
<p>/MANAGEMENT_ADMINACCOUNT=”Domain\AdminGroup”</p>
<p>/MANAGEMENT_WEBSITE_NAME=”Microsoft AppV Management Service”</p>
<p>/MANAGEMENT_WEBSITE_PORT=”8080”</p>
<p>/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL</p>
<p>/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE =”SqlInstanceName”</p>
<p>/EXISTING_MANAGEMENT_DB_NAME =”AppVManagement”</p></td>
</tr>
</tbody>
</table>
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p>To install the Management server using an existing Management database on a remote machine.</p></td>
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
<ul>
<li><p>/MANAGEMENT_SERVER</p></li>
<li><p>/MANAGEMENT_ADMINACCOUNT</p></li>
<li><p>/MANAGEMENT_WEBSITE_NAME</p></li>
<li><p>/MANAGEMENT_WEBSITE_PORT</p></li>
<li><p>/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME</p></li>
<li><p>/EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT</p></li>
<li><p>/EXISTING_MANAGEMENT_DB_NAME</p></li>
</ul>
<p>To use a custom instance of Microsoft SQL Server, use these parameters:</p>
<ul>
<li><p>/MANAGEMENT_SERVER</p></li>
<li><p>/MANAGEMENT_ADMINACCOUNT</p></li>
<li><p>/MANAGEMENT_WEBSITE_NAME</p></li>
<li><p>/MANAGEMENT_WEBSITE_PORT</p></li>
<li><p>/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME</p></li>
<li><p>/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE</p></li>
<li><p>/EXISTING_MANAGEMENT_DB_NAME</p></li>
</ul>
<p>Using a custom instance of Microsoft SQL Server example:</p>
<p>/appv_server_setup.exe /QUIET</p>
<p>/MANAGEMENT_SERVER</p>
<p>/MANAGEMENT_ADMINACCOUNT=”Domain\AdminGroup”</p>
<p>/MANAGEMENT_WEBSITE_NAME=”Microsoft AppV Management Service”</p>
<p>/MANAGEMENT_WEBSITE_PORT=”8080”</p>
<p>/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME=”SqlServermachine.domainName”</p>
<p>/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE =”SqlInstanceName”</p>
<p>/EXISTING_MANAGEMENT_DB_NAME =”AppVManagement”</p></td>
</tr>
</tbody>
</table>
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p>To Install the Management database and the Management Server on the same computer.</p></td>
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
<ul>
<li><p>/DB_PREDEPLOY_MANAGEMENT</p></li>
<li><p>/MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT</p></li>
<li><p>/MANAGEMENT_DB_NAME</p></li>
<li><p>/MANAGEMENT_SERVER_MACHINE_USE_LOCAL</p></li>
<li><p>/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT</p></li>
</ul>
<p>To use a custom instance of Microsoft SQL Server, use these parameters:</p>
<ul>
<li><p>/DB_PREDEPLOY_MANAGEMENT</p></li>
<li><p>/MANAGEMENT_DB_CUSTOM_SQLINSTANCE</p></li>
<li><p>/MANAGEMENT_DB_NAME</p></li>
<li><p>/MANAGEMENT_SERVER_MACHINE_USE_LOCAL</p></li>
<li><p>/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT</p></li>
</ul>
<p>Using a custom instance of Microsoft SQL Server example:</p>
<p>/appv_server_setup.exe /QUIET</p>
<p>/DB_PREDEPLOY_MANAGEMENT</p>
<p>/MANAGEMENT_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”</p>
<p>/MANAGEMENT_DB_NAME=”AppVManagement”</p>
<p>/MANAGEMENT_SERVER_MACHINE_USE_LOCAL</p>
<p>/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”</p></td>
</tr>
</tbody>
</table>
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p>To install the Management database on a different computer than the Management server.</p></td>
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
<ul>
<li><p>/DB_PREDEPLOY_MANAGEMENT</p></li>
<li><p>/MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT</p></li>
<li><p>/MANAGEMENT_DB_NAME</p></li>
<li><p>/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT</p></li>
<li><p>/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT</p></li>
</ul>
<p>To use a custom instance of Microsoft SQL Server, use these parameters:</p>
<ul>
<li><p>/DB_PREDEPLOY_MANAGEMENT</p></li>
<li><p>/MANAGEMENT_DB_CUSTOM_SQLINSTANCE</p></li>
<li><p>/MANAGEMENT_DB_NAME</p></li>
<li><p>/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT</p></li>
<li><p>/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT</p></li>
</ul>
<p>Using a custom instance of Microsoft SQL Server example:</p>
<p>/appv_server_setup.exe /QUIET</p>
<p>/DB_PREDEPLOY_MANAGEMENT</p>
<p>/MANAGEMENT_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”</p>
<p>/MANAGEMENT_DB_NAME=”AppVManagement”</p>
<p>/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT=”Domain\MachineAccount”</p>
<p>/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”</p></td>
</tr>
</tbody>
</table>
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p>To Install the publishing server.</p></td>
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
<ul>
<li><p>/PUBLISHING_SERVER</p></li>
<li><p>/PUBLISHING_MGT_SERVER</p></li>
<li><p>/PUBLISHING_WEBSITE_NAME</p></li>
<li><p>/PUBLISHING_WEBSITE_PORT</p></li>
</ul>
<p>Using a custom instance of Microsoft SQL Server example:</p>
<p>/appv_server_setup.exe /QUIET</p>
<p>/PUBLISHING_SERVER</p>
<p>/PUBLISHING_MGT_SERVER=”http://ManagementServerName:ManagementPort”</p>
<p>/PUBLISHING_WEBSITE_NAME=”Microsoft AppV Publishing Service”</p>
<p>/PUBLISHING_WEBSITE_PORT=”8081”</p></td>
</tr>
</tbody>
</table>
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p>To Install the Reporting server and Reporting database on a local machine.</p></td>
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
<ul>
<li><p>/REPORTING _SERVER</p></li>
<li><p>/REPORTING _WEBSITE_NAME</p></li>
<li><p>/REPORTING _WEBSITE_PORT</p></li>
<li><p>/DB_PREDEPLOY_REPORTING</p></li>
<li><p>/REPORTING _DB_SQLINSTANCE_USE_DEFAULT</p></li>
<li><p>/REPORTING _DB_NAME</p></li>
</ul>
<p>To use a custom instance of Microsoft SQL Server, use these parameters:</p>
<ul>
<li><p>/REPORTING _SERVER</p></li>
<li><p>/REPORTING _ADMINACCOUNT</p></li>
<li><p>/REPORTING _WEBSITE_NAME</p></li>
<li><p>/REPORTING _WEBSITE_PORT</p></li>
<li><p>/DB_PREDEPLOY_REPORTING</p></li>
<li><p>/REPORTING _DB_CUSTOM_SQLINSTANCE</p></li>
<li><p>/REPORTING _DB_NAME</p></li>
</ul>
<p>Using a custom instance of Microsoft SQL Server example:</p>
<ul>
<li><p>/appv_server_setup.exe /QUIET</p></li>
<li><p>/REPORTING_SERVER</p></li>
<li><p>/REPORTING_WEBSITE_NAME=”Microsoft AppV Reporting Service”</p></li>
<li><p>/REPORTING_WEBSITE_PORT=”8082”</p></li>
<li><p>/DB_PREDEPLOY_REPORTING</p></li>
<li><p>/REPORTING_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”</p></li>
<li><p>/REPORTING_DB_NAME=”AppVReporting”</p></li>
</ul></td>
</tr>
</tbody>
</table>
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p>To Install the Reporting server and using an existing Reporting database on a local machine.</p></td>
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
<ul>
<li><p>/REPORTING _SERVER</p></li>
<li><p>/REPORTING _WEBSITE_NAME</p></li>
<li><p>/REPORTING _WEBSITE_PORT</p></li>
<li><p>/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL</p></li>
<li><p>/EXISTING_REPORTING _DB_SQLINSTANCE_USE_DEFAULT</p></li>
<li><p>/EXISTING_REPORTING _DB_NAME</p></li>
</ul>
<p>To use a custom instance of Microsoft SQL Server, use these parameters:</p>
<ul>
<li><p>/REPORTING _SERVER</p></li>
<li><p>/REPORTING _ADMINACCOUNT</p></li>
<li><p>/REPORTING _WEBSITE_NAME</p></li>
<li><p>/REPORTING _WEBSITE_PORT</p></li>
<li><p>/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL</p></li>
<li><p>/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE</p></li>
<li><p>/EXISTING_REPORTING _DB_NAME</p></li>
</ul>
<p>Using a custom instance of Microsoft SQL Server example:</p>
<p>/appv_server_setup.exe /QUIET</p>
<p>/REPORTING_SERVER</p>
<p>/REPORTING_WEBSITE_NAME=”Microsoft AppV Reporting Service”</p>
<p>/REPORTING_WEBSITE_PORT=”8082”</p>
<p>/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL</p>
<p>/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”</p>
<p>/EXITING_REPORTING_DB_NAME=”AppVReporting”</p></td>
</tr>
</tbody>
</table>
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p>To Install the Reporting server using an existing Reporting database on a remote machine.</p></td>
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
<ul>
<li><p>/REPORTING _SERVER</p></li>
<li><p>/REPORTING _WEBSITE_NAME</p></li>
<li><p>/REPORTING _WEBSITE_PORT</p></li>
<li><p>/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME</p></li>
<li><p>/EXISTING_REPORTING _DB_SQLINSTANCE_USE_DEFAULT</p></li>
<li><p>/EXISTING_REPORTING _DB_NAME</p></li>
</ul>
<p>To use a custom instance of Microsoft SQL Server, use these parameters:</p>
<ul>
<li><p>/REPORTING _SERVER</p></li>
<li><p>/REPORTING _ADMINACCOUNT</p></li>
<li><p>/REPORTING _WEBSITE_NAME</p></li>
<li><p>/REPORTING _WEBSITE_PORT</p></li>
<li><p>/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME</p></li>
<li><p>/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE</p></li>
<li><p>/EXISTING_REPORTING _DB_NAME</p></li>
</ul>
<p>Using a custom instance of Microsoft SQL Server example:</p>
<p>/appv_server_setup.exe /QUIET</p>
<p>/REPORTING_SERVER</p>
<p>/REPORTING_WEBSITE_NAME=”Microsoft AppV Reporting Service”</p>
<p>/REPORTING_WEBSITE_PORT=”8082”</p>
<p>/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME=”SqlServerMachine.DomainName”</p>
<p>/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”</p>
<p>/EXITING_REPORTING_DB_NAME=”AppVReporting”</p></td>
</tr>
</tbody>
</table>
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p>To install the Reporting database on the same computer as the Reporting server.</p></td>
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
<ul>
<li><p>/DB_PREDEPLOY_REPORTING</p></li>
<li><p>/REPORTING _DB_SQLINSTANCE_USE_DEFAULT</p></li>
<li><p>/REPORTING _DB_NAME</p></li>
<li><p>/REPORTING_SERVER_MACHINE_USE_LOCAL</p></li>
<li><p>/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT</p></li>
</ul>
<p>To use a custom instance of Microsoft SQL Server, use these parameters:</p>
<ul>
<li><p>/DB_PREDEPLOY_REPORTING</p></li>
<li><p>/REPORTING _DB_CUSTOM_SQLINSTANCE</p></li>
<li><p>/REPORTING _DB_NAME</p></li>
<li><p>/REPORTING_SERVER_MACHINE_USE_LOCAL</p></li>
<li><p>/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT</p></li>
</ul>
<p>Using a custom instance of Microsoft SQL Server example:</p>
<p>/appv_server_setup.exe /QUIET</p>
<p>/DB_PREDEPLOY_REPORTING</p>
<p>/REPORTING_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”</p>
<p>/REPORTING_DB_NAME=”AppVReporting”</p>
<p>/REPORTING_SERVER_MACHINE_USE_LOCAL</p>
<p>/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”</p></td>
</tr>
</tbody>
</table>
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p>To install the Reporting database on a different computer than the Reporting server.</p></td>
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
<ul>
<li><p>/DB_PREDEPLOY_REPORTING</p></li>
<li><p>/REPORTING _DB_SQLINSTANCE_USE_DEFAULT</p></li>
<li><p>/REPORTING _DB_NAME</p></li>
<li><p>/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT</p></li>
<li><p>/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT</p></li>
</ul>
<p>To use a custom instance of Microsoft SQL Server, use these parameters:</p>
<ul>
<li><p>/DB_PREDEPLOY_REPORTING</p></li>
<li><p>/REPORTING _DB_CUSTOM_SQLINSTANCE</p></li>
<li><p>/REPORTING _DB_NAME</p></li>
<li><p>/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT</p></li>
<li><p>/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT</p></li>
</ul>
<p>Using a custom instance of Microsoft SQL Server example:</p>
<p>/appv_server_setup.exe /QUIET</p>
<p>/DB_PREDEPLOY_REPORTING</p>
<p>/REPORTING_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”</p>
<p>/REPORTING_DB_NAME=”AppVReporting”</p>
<p>/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT=”Domain\MachineAccount”</p>
<p>/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”</p></td>
</tr>
</tbody>
</table>
**Parameter Definitions**
**General Parameters**
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Parameter</th>
<th align="left">Information</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>/QUIET</p></td>
<td align="left"><p>Specifies silent install.</p></td>
</tr>
<tr class="even">
<td align="left"><p>/UNINSTALL</p></td>
<td align="left"><p>Specifies an uninstall.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/LAYOUT</p></td>
<td align="left"><p>Specifies layout action. This extracts the MSIs and script files to a folder without actually installing the product. No value is expected.</p></td>
</tr>
<tr class="even">
<td align="left"><p>/LAYOUTDIR</p></td>
<td align="left"><p>Specifies the layout directory. Takes a string. For example, /LAYOUTDIR=”C:\Application Virtualization Server”</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/INSTALLDIR</p></td>
<td align="left"><p>Specifies the installation directory. Takes a string. E.g. /INSTALLDIR=”C:\Program Files\Application Virtualization\Server”</p></td>
</tr>
<tr class="even">
<td align="left"><p>/MUOPTIN</p></td>
<td align="left"><p>Enables Microsoft Update. No value is expected</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/ACCEPTEULA</p></td>
<td align="left"><p>Accepts the license agreement. This is required for an unattended installation. Example usage: <strong>/ACCEPTEULA</strong> or <strong>/ACCEPTEULA=1</strong>.</p></td>
</tr>
</tbody>
</table>
**Management Server Installation Parameters**
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Parameter</th>
<th align="left">Information</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>/MANAGEMENT_SERVER</p></td>
<td align="left"><p>Specifies that the management server will be installed. No value is expected</p></td>
</tr>
<tr class="even">
<td align="left"><p>/MANAGEMENT_ADMINACCOUNT</p></td>
<td align="left"><p>Specifies the account that will be allowed to Administrator access to the management server This account can be an individual user account or a group. Example usage: <strong>/MANAGEMENT_ADMINACCOUNT=”mydomain\admin”</strong>. If <strong>/MANAGEMENT_SERVER</strong> is not specified, this will be ignored. Specifies the account that will be allowed to Administrator access to the management server. This can be a user account or a group. For example, <strong>/MANAGEMENT_ADMINACCOUNT="mydomain\admin"</strong>.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/MANAGEMENT_WEBSITE_NAME</p></td>
<td align="left"><p>Specifies name of the website that will be created for the management service. For example, /MANAGEMENT_WEBSITE_NAME=”Microsoft App-V Management Service”</p></td>
</tr>
<tr class="even">
<td align="left"><p>MANAGEMENT_WEBSITE_PORT</p></td>
<td align="left"><p>Specifies the port number that will be used by the management service will use. For example, /MANAGEMENT_WEBSITE_PORT=82.</p></td>
</tr>
</tbody>
</table>
**Parameters for the Management Server Database**
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Parameter</th>
<th align="left">Information</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>/DB_PREDEPLOY_MANAGEMENT</p></td>
<td align="left"><p>Specifies that the management database will be installed. You must have sufficient database permissions to complete this installation. No value is expected</p></td>
</tr>
<tr class="even">
<td align="left"><p>/MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT</p></td>
<td align="left"><p>Indicates that the default SQL instance should be used. No value is expected.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/MANAGEMENT_DB_ CUSTOM_SQLINSTANCE</p></td>
<td align="left"><p>Specifies the name of the custom SQL instance that should be used to create a new database. Example usage: <strong>/MANAGEMENT_DB_ CUSTOM_SQLINSTANCE=”MYSQLSERVER”</strong>. If /DB_PREDEPLOY_MANAGEMENT is not specified, this will be ignored.</p></td>
</tr>
<tr class="even">
<td align="left"><p>/MANAGEMENT_DB_NAME</p></td>
<td align="left"><p>Specifies the name of the new management database that should be created. Example usage: <strong>/MANAGEMENT_DB_NAME=”AppVMgmtDB”</strong>. If /DB_PREDEPLOY_MANAGEMENT is not specified, this will be ignored.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/MANAGEMENT_SERVER_MACHINE_USE_LOCAL</p></td>
<td align="left"><p>Indicates if the management server that will be accessing the database is installed on the local server. Switch parameter so no value is expected.</p></td>
</tr>
<tr class="even">
<td align="left"><p>/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT</p></td>
<td align="left"><p>Specifies the machine account of the remote machine that the management server will be installed on. Example usage: <strong>/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT=”domain\computername”</strong></p></td>
</tr>
<tr class="odd">
<td align="left"><p>/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT</p></td>
<td align="left"><p>Indicates the Administrator account that will be used to install the management server. Example usage: <strong>/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT =”domain\alias”</strong></p></td>
</tr>
</tbody>
</table>
**Parameters for Installing Publishing Server**
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Parameter</th>
<th align="left">Information</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>/PUBLISHING_SERVER</p></td>
<td align="left"><p>Specifies that the Publishing Server will be installed. No value is expected</p></td>
</tr>
<tr class="even">
<td align="left"><p>/PUBLISHING_MGT_SERVER</p></td>
<td align="left"><p>Specifies the URL to Management Service the Publishing server will connect to. Example usage: <strong>http://<management server name>:<Management server port number></strong>. If /PUBLISHING_SERVER is not used, this parameter will be ignored</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/PUBLISHING_WEBSITE_NAME</p></td>
<td align="left"><p>Specifies name of the website that will be created for the publishing service. For example, /PUBLISHING_WEBSITE_NAME=”Microsoft App-V Publishing Service”</p></td>
</tr>
<tr class="even">
<td align="left"><p>/PUBLISHING_WEBSITE_PORT</p></td>
<td align="left"><p>Specifies the port number used by the publishing service. For example, /PUBLISHING_WEBSITE_PORT=83</p></td>
</tr>
</tbody>
</table>
**Parameters for Reporting Server**
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Parameter</th>
<th align="left">Information</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>/REPORTING_SERVER</p></td>
<td align="left"><p>Specifies that the Reporting Server will be installed. No value is expected</p></td>
</tr>
<tr class="even">
<td align="left"><p>/REPORTING_WEBSITE_NAME</p></td>
<td align="left"><p>Specifies name of the website that will be created for the Reporting Service. E.g. /REPORTING_WEBSITE_NAME="Microsoft App-V ReportingService"</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/REPORTING_WEBSITE_PORT</p></td>
<td align="left"><p>Specifies the port number that the Reporting Service will use. E.g. /REPORTING_WEBSITE_PORT=82</p></td>
</tr>
</tbody>
</table>
**Parameters for using an Existing Reporting Server Database**
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Parameter</th>
<th align="left">Information</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL</p></td>
<td align="left"><p>Indicates that the Microsoft SQL Server is installed on the local server. Switch parameter so no value is expected.</p></td>
</tr>
<tr class="even">
<td align="left"><p>/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME</p></td>
<td align="left"><p>Specifies the name of the remote computer that SQL Server is installed on. Takes a string. E.g. /EXISTING_REPORTING_DB_ REMOTE_SQL_SERVER_NAME="mycomputer1"</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/EXISTING_ REPORTING _DB_SQLINSTANCE_USE_DEFAULT</p></td>
<td align="left"><p>Indicates that the default SQL instance is to be used. Switch parameter so no value is expected.</p></td>
</tr>
<tr class="even">
<td align="left"><p>/EXISTING_ REPORTING_DB_CUSTOM_SQLINSTANCE</p></td>
<td align="left"><p>Specifies the name of the custom SQL instance that should be used. Takes a string. E.g. /EXISTING_REPORTING_DB_ CUSTOM_SQLINSTANCE="MYSQLSERVER"</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/EXISTING_ REPORTING _DB_NAME</p></td>
<td align="left"><p>Specifies the name of the existing Reporting database that should be used. Takes a string. E.g. /EXISTING_REPORTING_DB_NAME="AppVReporting"</p></td>
</tr>
</tbody>
</table>
**Parameters for installing Reporting Server Database**
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Parameter</th>
<th align="left">Information</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>/DB_PREDEPLOY_REPORTING</p></td>
<td align="left"><p>Specifies that the Reporting Database will be installed. DBA permissions are required for this installation. No value is expected</p></td>
</tr>
<tr class="even">
<td align="left"><p>/REPORTING_DB_SQLINSTANCE_USE_DEFAULT</p></td>
<td align="left"><p>Specifies the name of the custom SQL instance that should be used. Takes a string. E.g. /REPORTING_DB_ CUSTOM_SQLINSTANCE="MYSQLSERVER"</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/REPORTING_DB_NAME</p></td>
<td align="left"><p>Specifies the name of the new Reporting database that should be created. Takes a string. E.g. /REPORTING_DB_NAME="AppVMgmtDB"</p></td>
</tr>
<tr class="even">
<td align="left"><p>/REPORTING_SERVER_MACHINE_USE_LOCAL</p></td>
<td align="left"><p>Indicates that the Reporting server that will be accessing the database is installed on the local server. Switch parameter so no value is expected.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT</p></td>
<td align="left"><p>Specifies the machine account of the remote machine that the Reporting server will be installed on. Takes a string. E.g. /REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT = "domain\computername"</p></td>
</tr>
<tr class="even">
<td align="left"><p>/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT</p></td>
<td align="left"><p>Indicates the Administrator account that will be used to install the App-V Reporting Server. Takes a string. E.g. /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT = "domain\alias"</p></td>
</tr>
</tbody>
</table>
**Parameters for using an existing Management Server Database**
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Parameter</th>
<th align="left">Information</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL</p></td>
<td align="left"><p>Indicates that the SQL Server is installed on the local server. Switch parameter so no value is expected.If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.</p></td>
</tr>
<tr class="even">
<td align="left"><p>/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME</p></td>
<td align="left"><p>Specifies the name of the remote computer that SQL Server is installed on. Takes a string. E.g. /EXISTING_MANAGEMENT_DB_ REMOTE_SQL_SERVER_NAME="mycomputer1"</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/EXISTING_ MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT</p></td>
<td align="left"><p>Indicates that the default SQL instance is to be used. Switch parameter so no value is expected. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.</p></td>
</tr>
<tr class="even">
<td align="left"><p>/EXISTING_MANAGEMENT_DB_ CUSTOM_SQLINSTANCE</p></td>
<td align="left"><p>Specifies the name of the custom SQL instance that will be used. Example usage <strong>/EXISTING_MANAGEMENT_DB_ CUSTOM_SQLINSTANCE=”AppVManagement”</strong>. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/EXISTING_MANAGEMENT_DB_NAME</p></td>
<td align="left"><p>Specifies the name of the existing management database that should be used. Example usage: <strong>/EXISTING_MANAGEMENT_DB_NAME=”AppVMgmtDB”</strong>. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.</p>
<p></p>
<p><strong>Got a suggestion for App-V</strong>? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). <strong>Got an App-V issue?</strong> Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).</p></td>
</tr>
</tbody>
</table>