From cbd94883e400873446bbfe607a70c67b61d9ad9f Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Mon, 9 Apr 2018 15:21:13 -0700 Subject: [PATCH] Italicized parameters --- ...pv-deploy-the-appv-server-with-a-script.md | 302 +++++++++--------- 1 file changed, 151 insertions(+), 151 deletions(-) diff --git a/windows/application-management/app-v/revision-heidi/appv-deploy-the-appv-server-with-a-script.md b/windows/application-management/app-v/revision-heidi/appv-deploy-the-appv-server-with-a-script.md index bce41eae3d..9d113108c7 100644 --- a/windows/application-management/app-v/revision-heidi/appv-deploy-the-appv-server-with-a-script.md +++ b/windows/application-management/app-v/revision-heidi/appv-deploy-the-appv-server-with-a-script.md @@ -71,23 +71,23 @@ To use the default instance of Microsoft SQL Server, use the following parameter * */MANAGEMENT_SERVER* * */MANAGEMENT_ADMINACCOUNT* -* /MANAGEMENT_WEBSITE_NAME -* /MANAGEMENT_WEBSITE_PORT -* /EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL -* /EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT -* /EXISTING_MANAGEMENT_DB_NAME +* */MANAGEMENT_WEBSITE_NAME* +* */MANAGEMENT_WEBSITE_PORT* +* */EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL* +* */EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT* +* */EXISTING_MANAGEMENT_DB_NAME* ### Custom instance of Microsoft SQL Server for installation with an existing Management database on a local machine To use a custom instance of Microsoft SQL Server, use these parameters: -* /MANAGEMENT_SERVER -* /MANAGEMENT_ADMINACCOUNT -* /MANAGEMENT_WEBSITE_NAME -* /MANAGEMENT_WEBSITE_PORT -* /EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL -* /EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE -* /EXISTING_MANAGEMENT_DB_NAME +* */MANAGEMENT_SERVER* +* */MANAGEMENT_ADMINACCOUNT* +* */MANAGEMENT_WEBSITE_NAME* +* */MANAGEMENT_WEBSITE_PORT* +* */EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL* +* */EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE* +* */EXISTING_MANAGEMENT_DB_NAME* ### Example parameters for using a custom instance of Microsoft SQL Server for installation with an existing Management database on a local machine @@ -108,25 +108,25 @@ To use a custom instance of Microsoft SQL Server, use these parameters: To use the default instance of Microsoft SQL Server, use the following parameters: -* /MANAGEMENT_SERVER -* /MANAGEMENT_ADMINACCOUNT -* /MANAGEMENT_WEBSITE_NAME -* /MANAGEMENT_WEBSITE_PORT -* /EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME -* /EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT -* /EXISTING_MANAGEMENT_DB_NAME +* */MANAGEMENT_SERVER* +* */MANAGEMENT_ADMINACCOUNT* +* */MANAGEMENT_WEBSITE_NAME* +* */MANAGEMENT_WEBSITE_PORT* +* */EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME* +* */EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT* +* */EXISTING_MANAGEMENT_DB_NAME* ### Custom instance of Microsoft SQL Server with an existing Management database on a remote machine To use a custom instance of Microsoft SQL Server, use these parameters: -* /MANAGEMENT_SERVER -* /MANAGEMENT_ADMINACCOUNT -* /MANAGEMENT_WEBSITE_NAME -* /MANAGEMENT_WEBSITE_PORT -* /EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME -* /EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE -* /EXISTING_MANAGEMENT_DB_NAME +* */MANAGEMENT_SERVER* +* */MANAGEMENT_ADMINACCOUNT* +* */MANAGEMENT_WEBSITE_NAME* +* */MANAGEMENT_WEBSITE_PORT* +* */EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME* +* */EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE* +* */EXISTING_MANAGEMENT_DB_NAME* ### Example for using a custom instance of Microsoft SQL Server with an existing Management database on a remote machine @@ -149,21 +149,21 @@ The following examples will show you how to install the Management server and da To use the default instance of Microsoft SQL Server, use these parameters: -* /DB_PREDEPLOY_MANAGEMENT -* /MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT -* /MANAGEMENT_DB_NAME -* /MANAGEMENT_SERVER_MACHINE_USE_LOCAL -* /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT +* */DB_PREDEPLOY_MANAGEMENT* +* */MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT* +* */MANAGEMENT_DB_NAME* +* */MANAGEMENT_SERVER_MACHINE_USE_LOCAL* +* */MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT* ### Custom instance of Microsoft SQL Server for installation on the same computer To use a custom instance of Microsoft SQL Server, use these parameters: -* /DB_PREDEPLOY_MANAGEMENT -* /MANAGEMENT_DB_CUSTOM_SQLINSTANCE -* /MANAGEMENT_DB_NAME -* /MANAGEMENT_SERVER_MACHINE_USE_LOCAL -* /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT +* */DB_PREDEPLOY_MANAGEMENT* +* */MANAGEMENT_DB_CUSTOM_SQLINSTANCE* +* */MANAGEMENT_DB_NAME* +* */MANAGEMENT_SERVER_MACHINE_USE_LOCAL* +* */MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT* ### Example for using a custom instance of Microsoft SQL Server for installation on the same computer @@ -184,21 +184,21 @@ The following examples will show you how to install the Management database and To use the default instance of Microsoft SQL Server, use the following parameters: -* /DB_PREDEPLOY_MANAGEMENT -* /MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT -* /MANAGEMENT_DB_NAME -* /MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT -* /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT +* */DB_PREDEPLOY_MANAGEMENT* +* */MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT* +* */MANAGEMENT_DB_NAME* +* */MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT* +* */MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT* ### Custom instance of Microsoft SQL Server for installing the Management database on a different computer than the Management server To use a custom instance of Microsoft SQL Server, use these parameters: -* /DB_PREDEPLOY_MANAGEMENT -* /MANAGEMENT_DB_CUSTOM_SQLINSTANCE -* /MANAGEMENT_DB_NAME -* /MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT -* /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT +* */DB_PREDEPLOY_MANAGEMENT* +* */MANAGEMENT_DB_CUSTOM_SQLINSTANCE* +* */MANAGEMENT_DB_NAME* +* */MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT* +* */MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT* ### Example for using a custom instance of Microsoft SQL Server for installing the Management database on a different computer than the Management server @@ -219,10 +219,10 @@ The following examples will show you how to install the Publishing server. To use the default instance of Microsoft SQL Server, use the following parameters: -* /PUBLISHING_SERVER -* /PUBLISHING_MGT_SERVER -* /PUBLISHING_WEBSITE_NAME -* /PUBLISHING_WEBSITE_PORT +* */PUBLISHING_SERVER* +* */PUBLISHING_MGT_SERVER* +* */PUBLISHING_WEBSITE_NAME* +* */PUBLISHING_WEBSITE_PORT* ### Example for installing the Publishing server @@ -242,24 +242,24 @@ The following examples will show you how to install the Reporting server and dat To use the default instance of Microsoft SQL Server, use the following parameters: -* /REPORTING _SERVER -* /REPORTING _WEBSITE_NAME -* /REPORTING _WEBSITE_PORT -* /DB_PREDEPLOY_REPORTING -* /REPORTING _DB_SQLINSTANCE_USE_DEFAULT -* /REPORTING _DB_NAME +* */REPORTING_SERVER* +* */REPORTING_WEBSITE_NAME* +* */REPORTING_WEBSITE_PORT* +* */DB_PREDEPLOY_REPORTING* +* */REPORTING_DB_SQLINSTANCE_USE_DEFAULT* +* */REPORTING_DB_NAME* ### Custom instance of Microsoft SQL Server for installing the Reporting server and Reporting database on a local machine To use a custom instance of Microsoft SQL Server, use these parameters: -* /REPORTING _SERVER -* /REPORTING _ADMINACCOUNT -* /REPORTING _WEBSITE_NAME -* /REPORTING _WEBSITE_PORT -* /DB_PREDEPLOY_REPORTING -* /REPORTING _DB_CUSTOM_SQLINSTANCE -* /REPORTING _DB_NAME +* */REPORTING_SERVER* +* */REPORTING_ADMINACCOUNT* +* */REPORTING_WEBSITE_NAME* +* */REPORTING_WEBSITE_PORT* +* */DB_PREDEPLOY_REPORTING* +* */REPORTING_DB_CUSTOM_SQLINSTANCE* +* */REPORTING_DB_NAME* ### Example for using a custom instance of Microsoft SQL Server for installing the Reporting server and Reporting database on a local machine @@ -281,24 +281,24 @@ The following examples will show you how to install the reporting machine on a l To use the default instance of Microsoft SQL Server, use the following parameters: -* /REPORTING _SERVER -* /REPORTING _WEBSITE_NAME -* /REPORTING _WEBSITE_PORT -* /EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL -* /EXISTING_REPORTING_DB_SQLINSTANCE_USE_DEFAULT -* /EXISTING_REPORTING_DB_NAME +* */REPORTING_SERVER* +* */REPORTING_WEBSITE_NAME* +* */REPORTING_WEBSITE_PORT* +* */EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL* +* */EXISTING_REPORTING_DB_SQLINSTANCE_USE_DEFAULT* +* */EXISTING_REPORTING_DB_NAME* ### Custom instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a local machine To use a custom instance of Microsoft SQL Server, use these parameters: -* /REPORTING _SERVER -* /REPORTING _ADMINACCOUNT -* /REPORTING _WEBSITE_NAME -* /REPORTING _WEBSITE_PORT -* /EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL -* /EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE -* /EXISTING_REPORTING _DB_NAME +* */REPORTING_SERVER* +* */REPORTING_ADMINACCOUNT* +* */REPORTING_WEBSITE_NAME* +* */REPORTING_WEBSITE_PORT* +* */EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL* +* */EXISTING_REPORTING_DB_CUSTOM_SQLINSTANCE* +* */EXISTING_REPORTING_DB_NAME* ### Example for using a custom instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a local machine @@ -320,24 +320,24 @@ The following examples will show you how to install the Reporting server and on To use the default instance of Microsoft SQL Server, use the following parameters: -* /REPORTING _SERVER -* /REPORTING _WEBSITE_NAME -* /REPORTING _WEBSITE_PORT -* /EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME -* /EXISTING_REPORTING _DB_SQLINSTANCE_USE_DEFAULT -* /EXISTING_REPORTING _DB_NAME +* */REPORTING_SERVER* +* */REPORTING_WEBSITE_NAME* +* */REPORTING_WEBSITE_PORT* +* */EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME* +* */EXISTING_REPORTING_DB_SQLINSTANCE_USE_DEFAULT* +* */EXISTING_REPORTING_DB_NAME* ### Custom instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a remote machine To use a custom instance of Microsoft SQL Server, use these parameters: -* /REPORTING _SERVER -* /REPORTING _ADMINACCOUNT -* /REPORTING _WEBSITE_NAME -* /REPORTING _WEBSITE_PORT -* /EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME -* /EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE -* /EXISTING_REPORTING _DB_NAME +* */REPORTING_SERVER* +* */REPORTING_ADMINACCOUNT* +* */REPORTING_WEBSITE_NAME* +* */REPORTING_WEBSITE_PORT* +* */EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME* +* */EXISTING_REPORTING_DB_CUSTOM_SQLINSTANCE* +* */EXISTING_REPORTING_DB_NAME* ### Example using a custom instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a remote machine @@ -359,21 +359,21 @@ The following examples will show you how to install the Reporting database and s To use the default instance of Microsoft SQL Server, use the following parameters: -* /DB_PREDEPLOY_REPORTING -* /REPORTING_DB_SQLINSTANCE_USE_DEFAULT -* /REPORTING_DB_NAME -* /REPORTING_SERVER_MACHINE_USE_LOCAL -* /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT +* */DB_PREDEPLOY_REPORTING* +* */REPORTING_DB_SQLINSTANCE_USE_DEFAULT* +* */REPORTING_DB_NAME* +* */REPORTING_SERVER_MACHINE_USE_LOCAL* +* */REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT* ### Custom instance of Microsoft SQL Server for installing the Reporting database on the same computer as the Reporting server To use a custom instance of Microsoft SQL Server, use these parameters: -* /DB_PREDEPLOY_REPORTING -* /REPORTING _DB_CUSTOM_SQLINSTANCE -* /REPORTING _DB_NAME -* /REPORTING_SERVER_MACHINE_USE_LOCAL -* /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT +* */DB_PREDEPLOY_REPORTING* +* */REPORTING_DB_CUSTOM_SQLINSTANCE* +* */REPORTING_DB_NAME* +* */REPORTING_SERVER_MACHINE_USE_LOCAL* +* */REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT* ### Example for using a custom instance of Microsoft SQL Server for installing the Reporting database on the same computer as the Reporting server @@ -394,21 +394,21 @@ The following examples will show you how to install the Reporting database and s To use the default instance of Microsoft SQL Server, use the following parameters: -* /DB_PREDEPLOY_REPORTING -* /REPORTING _DB_SQLINSTANCE_USE_DEFAULT -* /REPORTING _DB_NAME -* /REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT -* /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT +* */DB_PREDEPLOY_REPORTING* +* */REPORTING_DB_SQLINSTANCE_USE_DEFAULT* +* */REPORTING_DB_NAME* +* */REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT* +* */REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT* ### Custom instance of Microsoft SQL Server for installing the Reporting database on a different computer than the Reporting server To use a custom instance of Microsoft SQL Server, use these parameters: -* /DB_PREDEPLOY_REPORTING -* /REPORTING _DB_CUSTOM_SQLINSTANCE -* /REPORTING _DB_NAME -* /REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT -* /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT +* */DB_PREDEPLOY_REPORTING* +* */REPORTING_DB_CUSTOM_SQLINSTANCE* +* */REPORTING_DB_NAME* +* */REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT* +* */REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT* ### Example for using a custom instance of Microsoft SQL Server for installing the Reporting database on a different computer than the Reporting server @@ -437,82 +437,82 @@ Using a custom instance of Microsoft SQL Server example:
| Parameter | Description | |-----------|-------------| -| /QUIET | Specifies silent install. | -| /UNINSTALL | Specifies an uninstall. | -| /LAYOUT | Specifies layout action. This extracts the MSIs and script files to a folder without installing the actual product. No value is expected. | -| /LAYOUTDIR | Specifies the layout directory with a string. For example, ```/LAYOUTDIR="C:\Application Virtualization Server"``` | -| /INSTALLDIR | Specifies the installation directory with a string. For example, ```/INSTALLDIR="C:\Program Files\Application Virtualization\Server"``` | -| /MUOPTIN | Enables Microsoft Update. No value is expected | -| /ACCEPTEULA | Accepts the license agreement. This is required for an unattended installation. For example, ```/ACCEPTEULA``` or ```/ACCEPTEULA=1```. | +| */QUIET* | Specifies silent install. | +| */UNINSTALL* | Specifies an uninstall. | +| */LAYOUT* | Specifies layout action. This extracts the MSIs and script files to a folder without installing the actual product. No value is expected. | +| */LAYOUTDIR* | Specifies the layout directory with a string. For example, ```/LAYOUTDIR="C:\Application Virtualization Server"``` | +| */INSTALLDIR* | Specifies the installation directory with a string. For example, ```/INSTALLDIR="C:\Program Files\Application Virtualization\Server"``` | +| */MUOPTIN* | Enables Microsoft Update. No value is expected | +| */ACCEPTEULA* | Accepts the license agreement. This is required for an unattended installation. For example, ```/ACCEPTEULA``` or ```/ACCEPTEULA=1```. | ### Parameter definitions for Management Server installation parameters | Parameter | Description | |-----------|-------------| -| /MANAGEMENT_SERVER | Specifies that the management server will be installed. No value is expected | -| /MANAGEMENT_ADMINACCOUNT | Specifies the account that will be allowed administrator access to the management server. This account can be an individual user account or a group. For example, ```/MANAGEMENT_ADMINACCOUNT="mydomain\admin"```. If **/MANAGEMENT_SERVER** isn't specified, this parameter will be ignored.| -| /MANAGEMENT_WEBSITE_NAME | Specifies name of the website that will be created for the management service. For example, ```/MANAGEMENT_WEBSITE_NAME="Microsoft App-V Management Service"``` | -| /MANAGEMENT_WEBSITE_PORT | Specifies the port number that will be used by the management service will use. For example, ```/MANAGEMENT_WEBSITE_PORT=82```. | +| */MANAGEMENT_SERVER* | Specifies that the management server will be installed. No value is expected | +| */MANAGEMENT_ADMINACCOUNT* | Specifies the account that will be allowed administrator access to the management server. This account can be an individual user account or a group. For example, ```/MANAGEMENT_ADMINACCOUNT="mydomain\admin"```. If **/MANAGEMENT_SERVER** isn't specified, this parameter will be ignored.| +| */MANAGEMENT_WEBSITE_NAME* | Specifies name of the website that will be created for the management service. For example, ```/MANAGEMENT_WEBSITE_NAME="Microsoft App-V Management Service"``` | +| */MANAGEMENT_WEBSITE_PORT* | Specifies the port number that will be used by the management service will use. For example, ```/MANAGEMENT_WEBSITE_PORT=82```. | ### Parameter definitions for the Management Server Database | Parameter | Description | |-----------|-------------| -| /DB\_PREDEPLOY\_MANAGEMENT | Specifies that the management database will be installed. You must have sufficient database permissions to complete this installation. No value is expected | -| /MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT | Indicates that the default SQL instance should be used. No value is expected. | -| /MANAGEMENT_DB_CUSTOM_SQLINSTANCE | Specifies the name of the custom SQL instance that should be used to create a new database. For example, ```/MANAGEMENT_DB_CUSTOM_SQLINSTANCE="MYSQLSERVER"```. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this parameter will be ignored. | -| /MANAGEMENT_DB_NAME | Specifies the name of the new management database that should be created. For example, ```/MANAGEMENT_DB_NAME="AppVMgmtDB"```. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this will be ignored. | -| /MANAGEMENT_SERVER_MACHINE_USE_LOCAL | Indicates if the management server that will be accessing the database is installed on the local server. This is a switch parameter, so no value is expected. | -| /MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT | Specifies the machine account of the remote machine that the management server will be installed on. For example, ```/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT="domain\computername"```. | -| /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT | Indicates the Administrator account that will be used to install the management server. For example, ```/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT ="domain\alias"```. | +| */DB\_PREDEPLOY\_MANAGEMENT* | Specifies that the management database will be installed. You must have sufficient database permissions to complete this installation. No value is expected | +| */MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT* | Indicates that the default SQL instance should be used. No value is expected. | +| */MANAGEMENT_DB_CUSTOM_SQLINSTANCE* | Specifies the name of the custom SQL instance that should be used to create a new database. For example, ```/MANAGEMENT_DB_CUSTOM_SQLINSTANCE="MYSQLSERVER"```. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this parameter will be ignored. | +| */MANAGEMENT_DB_NAME* | Specifies the name of the new management database that should be created. For example, ```/MANAGEMENT_DB_NAME="AppVMgmtDB"```. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this will be ignored. | +| */MANAGEMENT_SERVER_MACHINE_USE_LOCAL* | Indicates if the management server that will be accessing the database is installed on the local server. This is a switch parameter, so no value is expected. | +| */MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT* | Specifies the machine account of the remote machine that the management server will be installed on. For example, ```/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT="domain\computername"```. | +| */MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT* | Indicates the Administrator account that will be used to install the management server. For example, ```/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT ="domain\alias"```. | ### Parameter definitions for Publishing Server installation parameters | Parameter | Description | |-----------|-------------| -| /PUBLISHING_SERVER | Specifies that the publishing server will be installed. No value is expected. | -| /PUBLISHING_MGT_SERVER | Specifies the URL to Management Service the Publishing server will connect to. For example, ```http://;```. If **/PUBLISHING_SERVER** isn't used, this parameter will be ignored. | -| /PUBLISHING_WEBSITE_NAME | Specifies name of the website that will be created for the publishing service. For example, ```/PUBLISHING_WEBSITE_NAME="Microsoft App-V Publishing Service"```. | -| /PUBLISHING_WEBSITE_PORT | Specifies the port number used by the publishing service. For example, ```/PUBLISHING_WEBSITE_PORT=83```. | +| */PUBLISHING_SERVER* | Specifies that the publishing server will be installed. No value is expected. | +| */PUBLISHING_MGT_SERVER* | Specifies the URL to Management Service the Publishing server will connect to. For example, ```http://;```. If **/PUBLISHING_SERVER** isn't used, this parameter will be ignored. | +| */PUBLISHING_WEBSITE_NAME* | Specifies name of the website that will be created for the publishing service. For example, ```/PUBLISHING_WEBSITE_NAME="Microsoft App-V Publishing Service"```. | +| */PUBLISHING_WEBSITE_PORT* | Specifies the port number used by the publishing service. For example, ```/PUBLISHING_WEBSITE_PORT=83```. | ### Parameter definitions for Reporting Server | Parameter | Description | |-----------|-------------| -| /REPORTING_SERVER | Specifies that the Reporting Server will be installed. No value is expected. | -| /REPORTING_WEBSITE_NAME | Specifies name of the website that will be created for the Reporting Service. For example, ```/REPORTING_WEBSITE_NAME="Microsoft App-V ReportingService"```. | -| /REPORTING_WEBSITE_PORT | Specifies the port number that the Reporting Service will use. For example, ```/REPORTING_WEBSITE_PORT=82```. | +| */REPORTING_SERVER* | Specifies that the Reporting Server will be installed. No value is expected. | +| */REPORTING_WEBSITE_NAME* | Specifies name of the website that will be created for the Reporting Service. For example, ```/REPORTING_WEBSITE_NAME="Microsoft App-V ReportingService"```. | +| */REPORTING_WEBSITE_PORT* | Specifies the port number that the Reporting Service will use. For example, ```/REPORTING_WEBSITE_PORT=82```. | ### Parameters for using an existing Reporting Server database | Parameter | Description | |-----------|-------------| -| /EXISTING\_REPORTING\_DB_SQL_SERVER_USE_LOCAL | Indicates that the Microsoft SQL Server is installed on the local server. This is a switch parameter, so no value is expected. | -| /EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME | Specifies the name of the remote computer that SQL Server is installed on. Takes a string. For example, ```/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME="mycomputer1"```. | -| /EXISTING_REPORTING_DB_SQLINSTANCE_USE_DEFAULT | Indicates that the default SQL instance is to be used. This is a switch parameter, so no value is expected. | -| /EXISTING_REPORTING_DB_CUSTOM_SQLINSTANCE | Specifies the name of the custom SQL instance that should be used. Takes a string. For example, ```/EXISTING_REPORTING_DB_CUSTOM_SQLINSTANCE="MYSQLSERVER"```. | -| /EXISTING_REPORTING_DB_NAME | Specifies the name of the existing Reporting database that should be used. Takes a string. For example, ```/EXISTING_REPORTING_DB_NAME="AppVReporting"```. | +| */EXISTING\_REPORTING\_DB_SQL_SERVER_USE_LOCAL* | Indicates that the Microsoft SQL Server is installed on the local server. This is a switch parameter, so no value is expected. | +| */EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME* | Specifies the name of the remote computer that SQL Server is installed on. Takes a string. For example, ```/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME="mycomputer1"```. | +| */EXISTING_REPORTING_DB_SQLINSTANCE_USE_DEFAULT* | Indicates that the default SQL instance is to be used. This is a switch parameter, so no value is expected. | +| */EXISTING_REPORTING_DB_CUSTOM_SQLINSTANCE* | Specifies the name of the custom SQL instance that should be used. Takes a string. For example, ```/EXISTING_REPORTING_DB_CUSTOM_SQLINSTANCE="MYSQLSERVER"```. | +| */EXISTING_REPORTING_DB_NAME* | Specifies the name of the existing Reporting database that should be used. Takes a string. For example, ```/EXISTING_REPORTING_DB_NAME="AppVReporting"```. | ### Parameter definitions for Reporting Server database installation | Parameter | Description | |-----------|-------------| -| /DB\_PREDEPLOY\_REPORTING | Specifies that the Reporting Database will be installed. DBA permissions are required for this installation. No value is expected | -| /REPORTING_DB_SQLINSTANCE_USE_DEFAULT | Specifies the name of the custom SQL instance that should be used. Takes a string. For example, ```/REPORTING_DB_CUSTOM_SQLINSTANCE="MYSQLSERVER"```. | -| /REPORTING_DB_NAME | Specifies the name of the new Reporting database that should be created. Takes a string. For example, ```/REPORTING_DB_NAME="AppVMgmtDB"```. | -| /REPORTING_SERVER_MACHINE_USE_LOCAL | Indicates that the Reporting server that will be accessing the database is installed on the local server. This is a switch parameter, so no value is expected. | -| /REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT | Specifies the machine account of the remote machine that the Reporting server will be installed on. Takes a string. For example, ```/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT = "domain\computername"```. | -| /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT | Indicates the Administrator account that will be used to install the App-V Reporting Server. Takes a string. For example, ```/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT = "domain\alias"```. | +| */DB\_PREDEPLOY\_REPORTING* | Specifies that the Reporting Database will be installed. DBA permissions are required for this installation. No value is expected | +| */REPORTING_DB_SQLINSTANCE_USE_DEFAULT* | Specifies the name of the custom SQL instance that should be used. Takes a string. For example, ```/REPORTING_DB_CUSTOM_SQLINSTANCE="MYSQLSERVER"```. | +| */REPORTING_DB_NAME* | Specifies the name of the new Reporting database that should be created. Takes a string. For example, ```/REPORTING_DB_NAME="AppVMgmtDB"```. | +| */REPORTING_SERVER_MACHINE_USE_LOCAL* | Indicates that the Reporting server that will be accessing the database is installed on the local server. This is a switch parameter, so no value is expected. | +| */REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT* | Specifies the machine account of the remote machine that the Reporting server will be installed on. Takes a string. For example, ```/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT = "domain\computername"```. | +| */REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT* | Indicates the Administrator account that will be used to install the App-V Reporting Server. Takes a string. For example, ```/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT = "domain\alias"```. | ### Parameters for using an existing Management Server database | Parameter | Description | |-----------|-------------| -| /EXISTING\_MANAGEMENT\_DB_SQL_SERVER_USE_LOCAL | Indicates that the SQL Server is installed on the local server. Switch parameter so no value is expected. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this variable will be ignored. | -| /EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME | Specifies the name of the remote computer that SQL Server is installed on. Takes a string. For example, ```/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME="mycomputer1"```. | -| /EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT | Indicates that the default SQL instance is to be used. Switch parameter so no value is expected. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this variable will be ignored. | -| /EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE | Specifies the name of the custom SQL instance that will be used. For example, ```/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE="AppVManagement"```. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this will be ignored. | -| /EXISTING_MANAGEMENT_DB_NAME | Specifies the name of the existing management database that should be used. For example, ```/EXISTING_MANAGEMENT_DB_NAME="AppVMgmtDB"```. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this will be ignored. | +| */EXISTING\_MANAGEMENT\_DB_SQL_SERVER_USE_LOCAL* | Indicates that the SQL Server is installed on the local server. Switch parameter so no value is expected. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this variable will be ignored. | +| */EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME* | Specifies the name of the remote computer that SQL Server is installed on. Takes a string. For example, ```/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME="mycomputer1"```. | +| */EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT* | Indicates that the default SQL instance is to be used. Switch parameter so no value is expected. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this variable will be ignored. | +| */EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE* | Specifies the name of the custom SQL instance that will be used. For example, ```/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE="AppVManagement"```. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this will be ignored. | +| */EXISTING_MANAGEMENT_DB_NAME* | Specifies the name of the existing management database that should be used. For example, ```/EXISTING_MANAGEMENT_DB_NAME="AppVMgmtDB"```. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this will be ignored. | ## Have a suggestion for App-V? @@ -520,4 +520,4 @@ Add or vote on suggestions on the [Application Virtualization feedback site](htt ## Related topics -[Deploying the App-V Server](appv-deploying-the-appv-server.md) +[Deploying the App-V Server](appv-deploying-the-appv-server.md) \ No newline at end of file