diff --git a/windows/manage/appv-capacity-planning.md b/windows/manage/appv-capacity-planning.md index eddcb1eb8c..32072d9331 100644 --- a/windows/manage/appv-capacity-planning.md +++ b/windows/manage/appv-capacity-planning.md @@ -63,7 +63,7 @@ You can also manage your App-V environment using an Electronic Software Distribu - With disconnected remote users who cannot connect to the App-V infrastructure. - - When you are running a software management system, such as Configuration Manager 2012. + - When you are running a software management system, such as System Center 2012 Configuration Manager. - When network bandwidth limitations inhibit electronic software distribution. diff --git a/windows/manage/appv-deploy-the-appv-server-with-a-script.md b/windows/manage/appv-deploy-the-appv-server-with-a-script.md index 1394472c33..0821433da2 100644 --- a/windows/manage/appv-deploy-the-appv-server-with-a-script.md +++ b/windows/manage/appv-deploy-the-appv-server-with-a-script.md @@ -11,768 +11,727 @@ ms.prod: w10 # How to Deploy the App-V 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 server using a script** -- Use the following tables for more information about installing the App-V server using the command line. +Use the following tables for more information about installing the App-V 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 /?**. +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** - **Common parameters and Examples** + ++++ + + + + + + +

To Install the Management server and 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

    • +

  • /DB_PREDEPLOY_MANAGEMENT

    • +

  • /MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

    • +

  • /MANAGEMENT_DB_NAME

    • +
+

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

    • +
+

Using a custom instance of Microsoft SQL Server example:

+

/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”

- - - - - - - - - - - -

To Install the Management server and 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

    • -

  • /DB_PREDEPLOY_MANAGEMENT

    • -

  • /MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /MANAGEMENT_DB_NAME

    • -
-

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

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/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”

+ ++++ + + + + + + +

To Install the Management server using 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

    • +
+

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

    • +
+

Using a custom instance of Microsoft SQL Server example:

+

/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”

-   + ++++ + + + + + + +

To install the Management server using 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

    • +
+

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

    • +
+

Using a custom instance of Microsoft SQL Server example:

+

/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 server using 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

    • -
-

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

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/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”

+ ++++ + + + + + + +

To Install the Management database and the Management Server 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

    • +
+

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

    • +
+

Using a custom instance of Microsoft SQL Server example:

+

/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”

  -   + ++++ + + + + + + +

To install 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

    • +
+

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

    • +
+

Using a custom instance of Microsoft SQL Server example:

+

/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”

- - - - - - - - - - - -

To install the Management server using 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

    • -
-

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

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/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 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

    • +
+

Using a custom instance of Microsoft SQL Server example:

+

/appv_server_setup.exe /QUIET

+

/PUBLISHING_SERVER

+

/PUBLISHING_MGT_SERVER=”http://ManagementServerName:ManagementPort”

+

/PUBLISHING_WEBSITE_NAME=”Microsoft AppV Publishing Service”

+

/PUBLISHING_WEBSITE_PORT=”8081”

-   + ++++ + + + + + + +

To Install 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

    • +
+

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

    • +
+

Using a custom instance of Microsoft SQL Server example:

+
    +

  • /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”

    • +
- - - - - - - - - - - -

To Install the Management database and the Management Server 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

    • -
-

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

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/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”

+ ++++ + + + + + + +

To Install the Reporting server and 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

    • +
+

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

    • +
+

Using a custom instance of Microsoft SQL Server example:

+

/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”

  -   + ++++ + + + + + + +

To Install 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

    • +
+

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

    • +
+

Using a custom instance of Microsoft SQL Server example:

+

/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”

- - - - - - - - - - - -

To install 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

    • -
-

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

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/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”

+ ++++ + + + + + + +

To install 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

    • +
+

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

    • +
+

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_SERVER_MACHINE_USE_LOCAL

+

/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”

-   + ++++ + + + + + + +

To install 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

    • +
+

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

    • +
+

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”

- - - - - - - - - - - -

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

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/PUBLISHING_SERVER

-

/PUBLISHING_MGT_SERVER=”http://ManagementServerName:ManagementPort”

-

/PUBLISHING_WEBSITE_NAME=”Microsoft AppV Publishing Service”

-

/PUBLISHING_WEBSITE_PORT=”8081”

+**Parameter Definitions** -   +**General Parameters** - - - - - - - - - - - -

To Install 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

    • -
-

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

    • -
-

Using a custom instance of Microsoft SQL Server example:

-
    -

  • /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”

    • -
+ ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterInformation

/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.

-   +**Management Server Installation Parameters** - - - - - - - - - - - -

To Install the Reporting server and 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

    • -
-

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

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/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”

+ ++++ + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterInformation

/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.

-   +**Parameters for the Management Server Database** - - - - - - - - - - - -

To Install 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

    • -
-

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

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/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”

+ ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterInformation

/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”

-   +**Parameters for Installing Publishing Server** - - - - - - - - - - - -

To install 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

    • -
-

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

    • -
-

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_SERVER_MACHINE_USE_LOCAL

-

/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”

+ ++++ + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterInformation

/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

-   +**Parameters for Reporting Server** - - - - - - - - - - - -

To install 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

    • -
-

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

    • -
-

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”

+ ++++ + + + + + + + + + + + + + + + + + + + + +
ParameterInformation

/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 Definitions** + ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterInformation

/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. /EXISITING_REPORTING_DB_NAME="AppVReporting"

  - **General Parameters** +**Parameters for installing Reporting Server Database** - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/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.

+ ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterInformation

/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** - **Management Server Installation Parameters** - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/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.

- -   - - **Parameters for the Management Server Database** - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/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”

- -   - - **Parameters for Installing Publishing Server** - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/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

- -   - - **Parameters for Reporting Server** - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/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** - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/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. /EXISITING_REPORTING_DB_NAME="AppVReporting"

- -   - - **Parameters for installing Reporting Server Database** - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/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** - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/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: /EXISITING_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 [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). Got an App-V issue? Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).

- -   + ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterInformation

/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: /EXISITING_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 [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). Got an App-V issue? Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).

## Related topics diff --git a/windows/manage/appv-install-the-management-and-reporting-databases-on-separate-computers.md b/windows/manage/appv-install-the-management-and-reporting-databases-on-separate-computers.md index 9558f87d73..9f74a81f7a 100644 --- a/windows/manage/appv-install-the-management-and-reporting-databases-on-separate-computers.md +++ b/windows/manage/appv-install-the-management-and-reporting-databases-on-separate-computers.md @@ -17,8 +17,6 @@ Use the following procedure to install the database server and management server >**Note**   After you complete the deployment, the **Microsoft SQL Server name**, **instance name** and **database name** will be required by the administrator installing the service to be able to connect to these databases. -  - **To install the management database and the management server on separate computers** 1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**. @@ -40,11 +38,7 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance 7. On the next **Create New Management Server Database** page, select **Use a remote computer**, and type the remote machine account using the following format: **Domain\\MachineAccount**. >**Note**   - If you plan to deploy the management server on the same computer you must select **Use this local computer**. - -   - - Specify the user name for the management server **Install Administrator** using the following format: **Domain\\AdministratorLoginName**. Click **Next**. + If you plan to deploy the management server on the same computer you must select **Use this local computer**. Specify the user name for the management server **Install Administrator** using the following format: Domain\\AdministratorLoginName. Click **Next**. 8. To start the installation, click **Install**. @@ -66,14 +60,10 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance If you are using a custom database name, then select **Custom configuration** and type the database name. -7. On the next **Create New Reporting Server Database** page, select **Use a remote computer**, and type the remote machine account using the following format: **Domain\\MachineAccount**. +7. On the next **Create New Reporting Server Database** page, select **Use a remote computer**, and type the remote machine account using the following format: Domain\\MachineAccount. **Note**   - If you plan to deploy the reporting server on the same computer you must select **Use this local computer**. - -   - - Specify the user name for the reporting server **Install Administrator** using the following format: **Domain\\AdministratorLoginName**. Click **Next**. + If you plan to deploy the reporting server on the same computer you must select **Use this local computer**. Specify the user name for the reporting server **Install Administrator** using the following format: Domain\\AdministratorLoginName. Click **Next**. 8. To start the installation, click **Install**. @@ -83,7 +73,7 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance 2. To extract the App-V database scripts, open a command prompt and specify the location where the installation files are saved and run the following command: - **appv\_server\_setup.exe** **/LAYOUT** **/LAYOUTDIR=”InstallationExtractionLocation”**. + **appv\_server\_setup.exe** **/LAYOUT** **/LAYOUTDIR=”InstallationExtractionLocation”** 3. After the extraction has been completed, to access the App-V database scripts and instructions readme file: @@ -94,13 +84,13 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance 4. For each database, copy the scripts to a share and modify them following the instructions in the readme file. **Note**   - For more information about modifying the required SIDs contained in the scripts see, [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md). - -   + For more information about modifying the required SIDs contained in the scripts see, [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md).   5. Run the scripts on the computer running Microsoft SQL Server. - **Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). +## Have a suggestion for App-V? + +Add or vote on suggestions [here](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 diff --git a/windows/manage/appv-install-the-management-server-on-a-standalone-computer.md b/windows/manage/appv-install-the-management-server-on-a-standalone-computer.md index 433492faf0..28cdb2f0b8 100644 --- a/windows/manage/appv-install-the-management-server-on-a-standalone-computer.md +++ b/windows/manage/appv-install-the-management-server-on-a-standalone-computer.md @@ -29,13 +29,7 @@ Use the following procedure to install the management server on a standalone com 6. On the **Configure Existing Management Database** page, select **Use a remote SQL Server**, and type the machine name of the computer running Microsoft SQL SQL, for example **SqlServerMachine**. >**Note**   - If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**. - -   - - For the SQL Server Instance, select **Use the default instance**. If you are using a custom Microsoft SQL Server instance, you must select **Use a custom instance** and then type the name of the instance. - - Specify the **SQL Server Database name** that this management server will use, for example **AppvManagement**. + If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**. For the SQL Server Instance, select **Use the default instance**. If you are using a custom Microsoft SQL Server instance, you must select **Use a custom instance** and then type the name of the instance. Specify the **SQL Server Database name** that this management server will use, for example **AppvManagement**. 7. On the **Configure Management Server Configuration** page, specify the AD group or account that will connect to the management console for administrative purposes for example **MyDomain\\MyUser** or **MyDomain\\AdminGroup**. The account or AD group you specify will be enabled to manage the server through the management console. You can add additional users or groups using the management console after installation @@ -45,7 +39,9 @@ Use the following procedure to install the management server on a standalone com 9. To confirm that the setup has completed successfully, open a web browser, and type the following URL: http://managementserver:portnumber/Console. If the installation was successful, you should see the **Management Console** appear without any error messages or warnings being displayed. -**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). +## Have a suggestion for App-V? + +Add or vote on suggestions [here](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 diff --git a/windows/manage/appv-install-the-publishing-server-on-a-remote-computer.md b/windows/manage/appv-install-the-publishing-server-on-a-remote-computer.md index 64a5da1508..414c59f646 100644 --- a/windows/manage/appv-install-the-publishing-server-on-a-remote-computer.md +++ b/windows/manage/appv-install-the-publishing-server-on-a-remote-computer.md @@ -46,23 +46,27 @@ Use the following procedure to install the publishing server on a separate compu 9. To verify that the publishing server is running correctly, you should import a package to the management server, entitle the package to an AD group, and publish the package. Using an internet browser, open the following URL: **http://publishingserver:pubport**. If the server is running correctly information similar to the following will be displayed: - `` + ```syntax + + + - ` ` + + + - ` ` + - ` ` + - ` ` + - ` ` + + ``` - ` ` +## Have a suggestion for App-V? - `` - -**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). +Add or vote on suggestions [here](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 diff --git a/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md b/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md index 92d0971f36..db35c6f9aa 100644 --- a/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md +++ b/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md @@ -34,13 +34,7 @@ Before performing the following procedure you should read and understand [About 6. On the **Configure Existing Reporting Database** page, select **Use a remote SQL Server**, and type the machine name of the computer running Microsoft SQL Server, for example **SqlServerMachine**. **Note**   - If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**. - -   - - For the SQL Server Instance, select **Use the default instance**. If you are using a custom Microsoft SQL Server instance, you must select **Use a custom instance** and then type the name of the instance. - - Specify the **SQL Server Database name** that this reporting server will use, for example **AppvReporting**. + If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**. For the SQL Server Instance, select **Use the default instance**. If you are using a custom Microsoft SQL Server instance, you must select **Use a custom instance** and then type the name of the instance. Specify the **SQL Server Database name** that this reporting server will use, for example **AppvReporting**. 7. On the **Configure Reporting Server Configuration** page. @@ -50,7 +44,9 @@ Before performing the following procedure you should read and understand [About 8. Click **Install**. -**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). +## Have a suggestion for App-V? + +Add or vote on suggestions [here](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 diff --git a/windows/manage/appv-migrating-to-appv-from-a-previous-version.md b/windows/manage/appv-migrating-to-appv-from-a-previous-version.md index 249d1366e3..8baa974696 100644 --- a/windows/manage/appv-migrating-to-appv-from-a-previous-version.md +++ b/windows/manage/appv-migrating-to-appv-from-a-previous-version.md @@ -200,10 +200,10 @@ After you convert an existing package you should test the package prior to deplo   -When converting a package check for failing files or shortcuts. Locate the item in App-V 4.6 package. It could possibly be a hard-coded path. Convert the path. +When converting a package check for failing files or shortcuts, locate the item in App-V 4.6 package. It could possibly be a hard-coded path. Convert the path. **Note**   -It is recommended that you use the App-V sequencer for converting critical applications or applications that need to take advantage of features. See, [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md). +It is recommended that you use the App-V sequencer for converting critical applications or applications that need to take advantage of features. See [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md). If a converted package does not open after you convert it, it is also recommended that you re-sequence the application using the App-V sequencer. diff --git a/windows/manage/appv-prerequisites.md b/windows/manage/appv-prerequisites.md index 5ba350c779..3b9173f2be 100644 --- a/windows/manage/appv-prerequisites.md +++ b/windows/manage/appv-prerequisites.md @@ -50,7 +50,7 @@ The following table indicates the software that is already installed for differe -

Windows Server 2012

+

Windows Server 2016

The following prerequisite software is already installed: