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 new file mode 100644 index 0000000000..43733ec805 --- /dev/null +++ b/windows/application-management/app-v/revision-heidi/appv-deploy-the-appv-server-with-a-script.md @@ -0,0 +1,503 @@ +--- +title: How to Deploy the App-V Server Using a Script (Windows 10) +description: How to Deploy the App-V Server Using a Script +author: MaggiePucciEvans +ms.pagetype: mdop, appcompat, virtualization +ms.mktglfcycl: deploy +ms.sitesec: library +ms.prod: w10 +ms.date: 04/19/2017 +--- +# How to deploy the App-V server using a script + +>Applies to Windows Server 2016. + +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 server using a script + +Use the following lists and tables for more information about installing the App-V server using the command line. + +The information in the following lists and tables can also be accessed through the command line by entering the following command: ```appv\_server\_setup.exe /?```. + +## How to use common parameters to install the Management server and Management database on a local machine + +### Parameters for a default instance of Microsoft SQL Server for a new installation on a local machine + +To use the default instance of Microsoft SQL Server, use the following parameters: + +* /MANAGEMENT_SERVER +* /MANAGEMENT_ADMINACCOUNT +* /MANAGEMENT_WEBSITE_NAME +* /MANAGEMENT_WEBSITE_PORT +* /DB_PREDEPLOY_MANAGEMENT +* /MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT +* /MANAGEMENT_DB_NAME + +### Parameters for a custom instance of Microsoft SQL Server for a new installation on a local machine + +To use a custom instance of Microsoft SQL Server, use the following parameters: + +* /MANAGEMENT_SERVER +* /MANAGEMENT_ADMINACCOUNT +* /MANAGEMENT_WEBSITE_NAME +* /MANAGEMENT_WEBSITE_PORT +* /DB_PREDEPLOY_MANAGEMENT +* /MANAGEMENT_DB_CUSTOM_SQLINSTANCE +* /MANAGEMENT_DB_NAME + +### Example parameters for using a custom instance of Microsoft SQL Server for a new installation on a local machine + +```SQL +/appv_server_setup.exe /QUIET +/MANAGEMENT_SERVER +/MANAGEMENT_ADMINACCOUNT="Domain\AdminGroup" +/MANAGEMENT_WEBSITE_NAME="Microsoft AppV Management Service" +/MANAGEMENT_WEBSITE_PORT="8080" +/DB_PREDEPLOY_MANAGEMENT +/MANAGEMENT_DB_CUSTOM_SQLINSTANCE="SqlInstanceName" +/MANAGEMENT_DB_NAME="AppVManagement" +``` + +## How to use common parameters to install the Management server using an existing Management database on a local machine + +### Default instance of Microsoft SQL Server for installation with an existing Management database on a local machine + +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_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 + +### Example parameters for using a custom instance of Microsoft SQL Server for installation with an existing Management database on a local machine + +```SQL +/appv_server_setup.exe /QUIET +/MANAGEMENT_SERVER +/MANAGEMENT_ADMINACCOUNT="Domain\AdminGroup" +/MANAGEMENT_WEBSITE_NAME="Microsoft AppV Management Service" +/MANAGEMENT_WEBSITE_PORT="8080" +/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL +/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE ="SqlInstanceName" +/EXISTING_MANAGEMENT_DB_NAME ="AppVManagement" +``` + +## How to install the Management server with an existing Management database on a remote machine + +### Default instance of Microsoft SQL Server with an existing Management database on a remote machine + +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 + +### 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 + +### Example for using a custom instance of Microsoft SQL Server with an existing Management database on a remote machine + +```SQL +/appv_server_setup.exe /QUIET +/MANAGEMENT_SERVER +/MANAGEMENT_ADMINACCOUNT="Domain\AdminGroup" +/MANAGEMENT_WEBSITE_NAME="Microsoft AppV Management Service" +/MANAGEMENT_WEBSITE_PORT="8080" +/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME="SqlServermachine.domainName" +/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE ="SqlInstanceName" +/EXISTING_MANAGEMENT_DB_NAME ="AppVManagement" +``` + +## To install the Management database and the Management Server on the same computer + +### Default instance of Microsoft SQL Server when the Management database and the Management Server are on the same computer + +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_SERVER_MACHINE_USE_LOCAL +* /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT + +### Custom instance of Microsoft SQL Server when the Management database and the Management Server are 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 + +### Example for using a custom instance of Microsoft SQL Server when the Management database and the Management Server are on the same computer + +```SQL +/appv_server_setup.exe /QUIET +/DB_PREDEPLOY_MANAGEMENT +/MANAGEMENT_DB_CUSTOM_SQLINSTANCE="SqlInstanceName" +/MANAGEMENT_DB_NAME="AppVManagement" +/MANAGEMENT_SERVER_MACHINE_USE_LOCAL +/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT="Domain\InstallAdminAccount" +``` + +## Installing the Management database on a different computer than the Management server + +### Default instance of Microsoft SQL Server for installing the Management database on a different computer than the Management server + +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 + +### 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 + +### Example for using a custom instance of Microsoft SQL Server for installing the Management database on a different computer than the Management server + +```SQL +/appv_server_setup.exe /QUIET +/DB_PREDEPLOY_MANAGEMENT +/MANAGEMENT_DB_CUSTOM_SQLINSTANCE="SqlInstanceName" +/MANAGEMENT_DB_NAME="AppVManagement" +/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT="Domain\MachineAccount" +/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT="Domain\InstallAdminAccount" +``` + +## Installing the Publishing server + +### Default instance of Microsoft SQL Server for installing 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 + +### Example for installing the Publishing server + +/appv_server_setup.exe /QUIET
+/PUBLISHING_SERVER
+/PUBLISHING_MGT_SERVER="http://ManagementServerName:ManagementPort"
+/PUBLISHING_WEBSITE_NAME="Microsoft AppV Publishing Service"
+/PUBLISHING_WEBSITE_PORT="8081" + +## Installing the Reporting server and Reporting database on a local machine + +### Default instance of Microsoft SQL Server for installing the Reporting server and Reporting database on a local machine + +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 + +### 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 + +### Example for using a custom instance of Microsoft SQL Server for installing the Reporting server and Reporting database on a local machine + +```SQL +/appv_server_setup.exe /QUIET +/REPORTING_SERVER +/REPORTING_WEBSITE_NAME="Microsoft AppV Reporting Service" +/REPORTING_WEBSITE_PORT="8082" +/DB_PREDEPLOY_REPORTING +/REPORTING_DB_CUSTOM_SQLINSTANCE="SqlInstanceName" +/REPORTING_DB_NAME="AppVReporting" +``` + +## Installing the Reporting server using an existing Reporting database on a local machine + +### Default instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a local machine + +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 + +### 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 + +### Example for using a custom instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a local machine + +```SQL +/appv_server_setup.exe /QUIET +/REPORTING_SERVER +/REPORTING_WEBSITE_NAME="Microsoft AppV Reporting Service" +/REPORTING_WEBSITE_PORT="8082" +/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL +/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE="SqlInstanceName" +/EXITING_REPORTING_DB_NAME="AppVReporting" +``` + +## Installing the Reporting server using an existing Reporting database on a remote machine + +### Default instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a remote machine + +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 + +### 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 + +### Example using a custom instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a remote machine + +```SQL +/appv_server_setup.exe /QUIET +/REPORTING_SERVER +/REPORTING_WEBSITE_NAME="Microsoft AppV Reporting Service" +/REPORTING_WEBSITE_PORT="8082" +/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME="SqlServerMachine.DomainName" +/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE="SqlInstanceName" +/EXITING_REPORTING_DB_NAME="AppVReporting" +``` + +## Installing the Reporting database on the same computer as the Reporting server + +### Default instance of Microsoft SQL Server for installing the Reporting database on the same computer as the Reporting server + +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 + +### 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 + +### Example for using a custom instance of Microsoft SQL Server for installing the Reporting database on the same computer as the Reporting server + +```SQL +/appv_server_setup.exe /QUIET +/DB_PREDEPLOY_REPORTING +/REPORTING_DB_CUSTOM_SQLINSTANCE="SqlInstanceName" +/REPORTING_DB_NAME="AppVReporting" +/REPORTING_SERVER_MACHINE_USE_LOCAL +/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT="Domain\InstallAdminAccount" +``` + +## Installing the Reporting database on a different computer than the Reporting server + +### Default instance of Microsoft SQL Server for installing the Reporting database on a different computer than the Reporting server + +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 + +### 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 + +### Example for using a custom instance of Microsoft SQL Server for installing the Reporting database on a different computer than the Reporting server + +```SQL +Using a custom instance of Microsoft SQL Server example:
+/appv_server_setup.exe /QUIET
+/DB_PREDEPLOY_REPORTING
+/REPORTING_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
+/REPORTING_DB_NAME="AppVReporting"
+/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT="Domain\MachineAccount"
+/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT="Domain\InstallAdminAccount" +``` + +## Parameter definitions + +* [General parameters](#parameter-definitions-for-general-parameters) +* [Management Server installation parameters](#parameter-definitions-for-management-server-installation-parameters) +* [Management Server Database parameters](#parameter-definitions-for-the-management-server-database) +* [Publishing Server installation parameters](#parameter-definitions-for-publishing-server-installation-parameters) +* [Reporting Server parameters](#parameter-definitions-for-reporting-server) +* [Parameters for using an existing Reporting Server database](#parameters-for-using-an-existing-reporting-server-database) +* [Reporting Server database installation parameters](#parameter-definitions-for-reporting-server-database-installation) +* [Parameters for using an existing Management Server database](#parameters-for-using-an-existing-management-server-database) + +### Parameter definitions for general parameters + +| 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 actually installing the product. No value is expected. | +| /LAYOUTDIR | Specifies the layout directory. Takes a string. For example, /LAYOUTDIR="C:\Application Virtualization Server" | +| /INSTALLDIR | Specifies the installation directory. Takes a string. E.g. /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. Example usage: **/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 to Administrator access to the management server This account can be an individual user account or a group. Example usage: **/MANAGEMENT_ADMINACCOUNT="mydomain\admin"**. If **/MANAGEMENT_SERVER** 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, **/MANAGEMENT_ADMINACCOUNT="mydomain\admin"**. | +| /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. Example usage: **/MANAGEMENT_DB_CUSTOM_SQLINSTANCE="MYSQLSERVER"**. If /DB_PREDEPLOY_MANAGEMENT is not specified, this will be ignored. | +| /MANAGEMENT_DB_NAME | Specifies the name of the new management database that should be created. Example usage: **/MANAGEMENT_DB_NAME="AppVMgmtDB"**. If /DB_PREDEPLOY_MANAGEMENT is not 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. 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. Example usage: **/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. Example usage: **/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. Example usage: **http://<management server name>:<Management server port number>**. If /PUBLISHING_SERVER is not 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. E.g. /REPORTING_WEBSITE_NAME="Microsoft App-V ReportingService" | +| /REPORTING_WEBSITE_PORT | Specifies the port number that the Reporting Service will use. E.g. /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. 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. E.g. /EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME="mycomputer1" | +| /EXISTING_REPORTING_DB_SQLINSTANCE_USE_DEFAULT | Indicates that the default SQL instance is to be used. 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. E.g. /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. E.g. /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. E.g. /REPORTING_DB_CUSTOM_SQLINSTANCE="MYSQLSERVER" | +| /REPORTING_DB_NAME | Specifies the name of the new Reporting database that should be created. Takes a string. E.g. /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. 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. E.g. /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. E.g. /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 is specified, this 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. E.g. /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 is specified, this will be ignored. | +| /EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE | Specifies the name of the custom SQL instance that will be used. Example usage **/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE="AppVManagement"**. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored. | +| /EXISTING_MANAGEMENT_DB_NAME | Specifies the name of the existing management database that should be used. Example usage: **/EXISTING_MANAGEMENT_DB_NAME="AppVMgmtDB"**. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored. | + +## Have a suggestion for App-V? + +Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). + +## Related topics + +[Deploying the App-V Server](appv-deploying-the-appv-server.md) diff --git a/windows/application-management/app-v/revision-heidi/appv-deploy-the-appv-server.md b/windows/application-management/app-v/revision-heidi/appv-deploy-the-appv-server.md index f706094ca7..10c630221a 100644 --- a/windows/application-management/app-v/revision-heidi/appv-deploy-the-appv-server.md +++ b/windows/application-management/app-v/revision-heidi/appv-deploy-the-appv-server.md @@ -60,45 +60,44 @@ ms.date: 04/19/2017 | You are using a custom database name. | Select **Custom configuration** and type the database name.
The database name must be unique, or the installation will fail.| 10. On the **Configure** page, accept the default value: **Use this local computer**. - >**Note** - > If you are installing the Management server and Management database side by side, some options on this page are not available. In this case, the appropriate options are selected by default and cannot be changed. + >[!NOTE] + >If you're installing the Management server and Management database side-by-side, the appropriate options are selected by default and cannot be changed. 11. On the **Configure** (Management Server Configuration) page, specify the following: | Item to configure | Description and examples | | - | - | - | Type the AD group with sufficient permissions to manage the App-V environment. | Example: MyDomain\MyUser

After installation, you can add users or groups on the management console. However, global security groups and Active Directory Domain Services (AD DS) distribution groups are not supported. You must use Domain local or Universal groups to perform this action.| - | **Website name**: Specify the custom name that will be used to run the publishing service.
| If you do not have a custom name, do not make any changes.| - |**Port binding**: Specify a unique port number that will be used by App-V. | Example: **12345**
Ensure that the port specified is not being used by another website. | + | Specify AD group | Specify the AD group with sufficient permissions to manage the App-V environment. Example: MyDomain\MyUser

After installation, you can add users or groups on the management console. However, global security groups and Active Directory Domain Services (AD DS) distribution groups are not supported. You must use Domain local or Universal groups to perform this action.| + |Website name | Specify the custom name that will be used to run the publishing service.
If you do not have a custom name, you don't have to change it.| + |Port binding | Specify a unique port number that will be used by App-V. Example: **12345**
Ensure that the port specified is not being used by another website. | 12. On the **Configure Publishing Server Configuration** page, specify the following: | Item to configure | Description and examples | | - | - | - | Specify the URL for the management service. | Example: http://localhost:12345 | - | **Website name**: Specify the custom name that will be used to run the publishing service.| If you do not have a custom name, do not make any changes. | - | **Port binding**: Specify a unique port number that will be used by App-V. | Example: 54321
Ensure that the port specified is not being used by another website. | + | Specify the management service URL | Example: http://localhost:12345 | + | Website name | Specify the custom website name that will be used to run the publishing service.
If you do not have a custom name, do not make any changes. | + | Port binding | Specify a unique port number that will be used by App-V. Example: 54321
Ensure that the port specified is not being used by another website. | 13. On the **Reporting Server** page, specify the following: | Item to configure | Description and examples | | - | - | - | **Website name**: Specify the custom name that will be used to run the Reporting Service. | If you do not have a custom name, do not make any changes. | - | **Port binding**: Specify a unique port number that will be used by App-V. | Example: 55555
Ensure that the port specified is not being used by another website. | + | Website name | Specify the custom name that will be used to run the Reporting Service.
If you do not have a custom name, do not make any changes. | + | Port binding | Specify a unique port number that will be used by App-V. Example: 55555
Ensure that the port specified is not being used by another website.| 14. To start the installation, click **Install** on the **Ready** page, and then click **Close** on the **Finished** page. -15. To verify that the setup completed successfully, open a web browser, and type the following URL: +15. To verify that the setup completed successfully, open a web browser, and type the following URL with the bracketed variables adjusted according to your specifications in the earlier steps: - **http://\<_Management server machine name_\>:\<_Management service port number_\>/console.html**. + ```http://:/console.html``` - Example: **http://localhost:12345/console.html**. If the installation succeeded, the App-V Management console is displayed with no errors. + Example: ```http://localhost:12345/console.html```. If the installation succeeded, the App-V Management console will display with no errors. ## Have a suggestion for App-V? -Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). +Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). + +For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). ## Related topics -- [Deploying App-V](appv-deploying-appv.md) - -- [How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services](appv-install-the-management-and-reporting-databases-on-separate-computers.md) - -- [How to Install the Publishing Server on a Remote Computer](appv-install-the-publishing-server-on-a-remote-computer.md) - -- [How to Deploy the App-V Server Using a Script](appv-deploy-the-appv-server-with-a-script.md) +* [Deploying App-V](appv-deploying-appv.md) +* [How to install the management and reporting databases on separate computers from the management and reporting services](appv-install-the-management-and-reporting-databases-on-separate-computers.md) +* [How to install the publishing server on a remote computer](appv-install-the-publishing-server-on-a-remote-computer.md) +* [How to deploy the App-V server using a script](appv-deploy-the-appv-server-with-a-script.md) \ No newline at end of file