-
If you are upgrading the App-V Server from App-V 5.0 SP1 Hotfix Package 3 or later, complete the steps in section [Check registry keys after installing the App-V 5.0 SP3 Server](#bkmk-check-reg-key-svr).
If you are upgrading the App-V Server from App-V SP1 Hotfix Package 3 or later, complete the steps in section [Check registry keys after installing the App-V 5.0 SP3 Server](#bkmk-check-reg-key-svr).
Follow the steps in [How to Deploy the App-V 5.0 Server](how-to-deploy-the-app-v-50-server-50sp3.md).
Prior to App-V 5.0 SP2, the Client Management User Interface (UI) was provided with the App-V Client installation. For App-V 5.0 SP2 installations (or later), you can use the Client Management UI by downloading from [Application Virtualization 5.0 Client UI Application](http://www.microsoft.com/download/details.aspx?id=41186).
+To use the App-V client user interface, download the existing version from [Application Virtualization 5.0 Client UI Application](http://www.microsoft.com/download/details.aspx?id=41186).
Upgrading from App-V 4.x
You must first upgrade to App-V 5.0. You cannot upgrade directly from App-V 4.x to App-V 5.1. For more information, see:
+For more information, see:
“Differences between App-V 4.6 and App-V 5.0” in [About App-V 5.0](about-app-v-50.md)
[Planning for Migrating from a Previous Version of App-V](planning-for-migrating-from-a-previous-version-of-app-v.md)
Follow these steps:
-Do one of the following, depending on the method you are using to upgrade the Management database and/or Reporting database:
-| Database upgrade method | -Step | -
|---|---|
Windows Installer |
-Skip this step and go to step 2, “If you are upgrading the App-V Server...” |
-
SQL scripts |
-Follow the steps in [How to Deploy the App-V Databases by Using SQL Scripts](how-to-deploy-the-app-v-databases-by-using-sql-scripts.md). |
-
If you are upgrading the App-V Server from App-V 5.0 SP1 Hotfix Package 3 or later, complete the steps in section [Check registry keys after installing the App-V 5.0 SP3 Server](#bkmk-check-reg-key-svr).
Follow the steps in [How to Deploy the App-V 5.1 Server](how-to-deploy-the-app-v-51-server.md)
-
See [How to Deploy the App-V 5.0 Server](how-to-deploy-the-app-v-50-server-50sp3.md)
Step 2: Upgrade the App-V Sequencer.
When this step is required |
-You are upgrading from App-V 5.0 SP1 with any subsequent Hotfix Packages that you installed by using an .msp file. |
-
Which components require that you do this step |
-Only the App-V Server components that you are upgrading. |
-
When you need to do this step |
-Before you upgrade the App-V Server to App-V 5.x |
-
What you need to do |
-Using the information in the following tables, update each registry key value under |
-
| Key name | -Description | -
|---|---|
IS_MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED |
-Describes whether a public access account is required to access non-local management databases. Value is set to “1” if it is required. |
-
MANAGEMENT_DB_NAME |
-Name of the Management database. |
-
MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT |
-Account used for read (public) access to the Management database. -Used when |
-
MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT_SID |
-Secure identifier (SID) of the account used for read (public) access to the Management database. -Used when |
-
MANAGEMENT_DB_SQL_INSTANCE |
-SQL Server instance for the Management database. -If the value is blank, the default database instance is used. |
-
MANAGEMENT_DB_WRITE_ACCESS_ACCOUNT |
-Account used for write (administrator) access to the Management database. |
-
MANAGEMENT_DB_WRITE_ACCESS_ACCOUNT_SID |
-Secure identifier (SID) of the account used for write (administrator) access to the Management database. |
-
MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT |
-Management server remote computer account (domain\account). |
-
MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT |
-Installation administrator login for the Management server (domain\account). |
-
MANAGEMENT_SERVER_MACHINE_USE_LOCAL |
-Valid values are: -
|
-
| Key name | -Description | -
|---|---|
MANAGEMENT_ADMINACCOUNT |
-Active Directory Domain Services (AD DS) group or account that is authorized to manage App-V (domain\account). |
-
MANAGEMENT_DB_SQL_INSTANCE |
-SQL server instance that contains the Management database. -If the value is blank, the default database instance is used. |
-
MANAGEMENT_DB_SQL_SERVER_NAME |
-Name of the remote SQL server with the Management database. -If the value is blank, the local computer is used. |
-
| Key name | -Description | -
|---|---|
IS_REPORTING_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED |
-Describes whether a public access account is required to access non-local reporting databases. Value is set to “1” if it is required. |
-
REPORTING_DB_NAME |
-Name of the Reporting database. |
-
REPORTING_DB_PUBLIC_ACCESS_ACCOUNT |
-Account used for read (public) access to the Reporting database. -Used when |
-
REPORTING_DB_PUBLIC_ACCESS_ACCOUNT_SID |
-Secure identifier (SID) of the account used for read (public) access to the Reporting database. -Used when |
-
REPORTING_DB_SQL_INSTANCE |
-SQL Server instance for the Reporting database. -If the value is blank, the default database instance is used. |
-
REPORTING_DB_WRITE_ACCESS_ACCOUNT |
-- |
REPORTING_DB_WRITE_ACCESS_ACCOUNT_SID |
-- |
REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT |
-Reporting server remote computer account (domain\account). |
-
REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT |
-Installation administrator login for the Reporting server (domain\account). |
-
REPORTING_SERVER_MACHINE_USE_LOCAL |
-Valid values are: -
|
-
| Key name | -Description | -
|---|---|
REPORTING_DB_SQL_INSTANCE |
-SQL Server instance for the Reporting database. -If the value is blank, the default database instance is used. |
-
REPORTING_DB_SQL_SERVER_NAME |
-Name of the remote SQL server with the Reporting database. -If the value is blank, the local computer is used. |
-
| Component | -Description | -
|---|---|
Management server |
- Provides overall management functionality for the App-V infrastructure. |
-
Management database |
- Facilitates database predeployments for App-V management. |
-
Publishing server |
- Provides hosting and streaming functionality for virtual applications. |
-
Reporting server |
- Provides App-V 5.1 reporting services. |
-
Reporting database |
- Facilitates database predeployments for App-V reporting. |
-
| Method | -What you need to do | -
|---|---|
You are using a custom Microsoft SQL Server instance. |
- Select Use the custom instance, and type the name of the instance. -Use the format INSTANCENAME. The assumed installation location is the local computer. -Not supported: A server name using the format ServerName\INSTANCE. |
-
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. |
-
| Method | -What you need to do | -
|---|---|
You are using a custom Microsoft SQL Server instance. |
- Select Use the custom instance, and type the name of the instance. -Use the format INSTANCENAME. The assumed installation location is the local computer. -Not supported: A server name using the format ServerName\INSTANCE. |
-
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. |
-
| 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 additional users or groups by using 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 are required 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. |
-
| 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. |
-
| 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. |
-