mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-07 18:17:22 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into appv51-OPcleanup
This commit is contained in:
Maggie Evans
commit
9ce41f0b17
@ -79,7 +79,6 @@
|
||||
##### [How to Access the Client Management Console 5.1](how-to-access-the-client-management-console51.md)
|
||||
##### [How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server 5.1](how-to-configure-the-client-to-receive-package-and-connection-groups-updates-from-the-publishing-server-51.md)
|
||||
#### [Migrating to App-V 5.1 from a Previous Version](migrating-to-app-v-51-from-a-previous-version.md)
|
||||
##### [Check Registry Keys before installing App-V 5.x Server](check-reg-key-svr.md)
|
||||
##### [How to Convert a Package Created in a Previous Version of App-V 5.1](how-to-convert-a-package-created-in-a-previous-version-of-app-v51.md)
|
||||
##### [How to Migrate Extension Points From an App-V 4.6 SP2 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md)
|
||||
##### [How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-51-for-a-specific-user.md)
|
||||
|
||||
@ -197,7 +197,7 @@ Complete the following steps to upgrade each component of the App-V infrastructu
|
||||
</tbody>
|
||||
</table>
|
||||
<p> </p></li>
|
||||
<li><p>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).</p></li>
|
||||
<li><p>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).</p></li>
|
||||
<li><p>Follow the steps in [How to Deploy the App-V 5.0 Server](how-to-deploy-the-app-v-50-server-50sp3.md).</p></li>
|
||||
</ol></td>
|
||||
</tr>
|
||||
|
||||
@ -63,7 +63,7 @@ See the following links for the App-V 5.1 software prerequisites and supported c
|
||||
## <a href="" id="bkmk-migrate-to-51"></a>Migrating to App-V 5.1
|
||||
|
||||
|
||||
Use the following information to upgrade to App-V 5.1 from earlier versions. See [Migrating to App-V 5.1 from a Previous Version](migrating-to-app-v-51-from-a-previous-version.md) for more information.
|
||||
Use the following information to upgrade to App-V 5.1 from earlier versions. See [Migrating from a Previous Version](migrating-from-a-previous-version-app-v-50.md) for more information.
|
||||
|
||||
### Before you start the upgrade
|
||||
|
||||
@ -90,7 +90,7 @@ Review the following information before you start the upgrade:
|
||||
</ol>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>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).</p>
|
||||
<p>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).</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
@ -98,7 +98,7 @@ Review the following information before you start the upgrade:
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Upgrading from App-V 4.x</p></td>
|
||||
<td align="left"><p>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:</p>
|
||||
<td align="left"><p>For more information, see:</p>
|
||||
<ul>
|
||||
<li><p>“Differences between App-V 4.6 and App-V 5.0” in [About App-V 5.0](about-app-v-50.md)</p></li>
|
||||
<li><p>[Planning for Migrating from a Previous Version of App-V](planning-for-migrating-from-a-previous-version-of-app-v.md)</p></li>
|
||||
@ -147,35 +147,7 @@ Complete the following steps to upgrade each component of the App-V infrastructu
|
||||
<div>
|
||||
|
||||
</div></td>
|
||||
<td align="left"><p>Follow these steps:</p>
|
||||
<ol>
|
||||
<li><p>Do one of the following, depending on the method you are using to upgrade the Management database and/or Reporting database:</p>
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Database upgrade method</th>
|
||||
<th align="left">Step</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows Installer</p></td>
|
||||
<td align="left"><p>Skip this step and go to step 2, “If you are upgrading the App-V Server...”</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>SQL scripts</p></td>
|
||||
<td align="left"><p>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).</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<li><p>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).</p></li>
|
||||
<li><p>Follow the steps in [How to Deploy the App-V 5.1 Server](how-to-deploy-the-app-v-51-server.md)</p></li>
|
||||
<p> </p></li>
|
||||
</ol></td>
|
||||
<td align="left"><p>See [How to Deploy the App-V 5.0 Server](how-to-deploy-the-app-v-50-server-50sp3.md)</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Step 2: Upgrade the App-V Sequencer.</p></td>
|
||||
@ -202,7 +174,7 @@ App-V 5.1 packages are exactly the same as App-V 5.0 packages. There has been no
|
||||
## <a href="" id="bkmk-whatsnew"></a>What’s New in App-V 5.1
|
||||
|
||||
|
||||
These sections are for users who are already familiar with App-V and want to know what has changed in App-V 5.1. If you are not already familiar with App-V, you should start by reading [Planning for App-V 5.1](planning-for-app-v-51.md).
|
||||
These sections are for users who are already familiar with App-V and want to know what has changed in App-V 5.1. If you are not already familiar with App-V, you should start by reading [Planning for App-V 5.0](planning-for-app-v-50-rc.md).
|
||||
|
||||
### <a href="" id="bkmk-win10support"></a>App-V support for Windows 10
|
||||
|
||||
|
||||
@ -1,238 +0,0 @@
|
||||
---
|
||||
title: Check Registry Keys before installing App-V 5.x Server
|
||||
description: Check Registry Keys before installing App-V 5.x Server
|
||||
ms.assetid:
|
||||
author: jamiejdt
|
||||
---
|
||||
|
||||
# Check Registry Keys before installing App-V 5.x Server
|
||||
|
||||
If you are upgrading the App-V Server from App-V 5.0 SP1 Hotfix Package 3 or later, complete the steps in this section before installing the App-V 5.x Server
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>When this step is required</strong></p></td>
|
||||
<td align="left"><p>You are upgrading from App-V 5.0 SP1 with any subsequent Hotfix Packages that you installed by using an .msp file.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Which components require that you do this step</strong></p></td>
|
||||
<td align="left"><p>Only the App-V Server components that you are upgrading.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>When you need to do this step</strong></p></td>
|
||||
<td align="left"><p>Before you upgrade the App-V Server to App-V 5.x</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>What you need to do</strong></p></td>
|
||||
<td align="left"><p>Using the information in the following tables, update each registry key value under <code>HKLM\Software\Microsoft\AppV\Server</code> with the value that you provided in your original server installation. Completing this step restores registry values that may have been removed when App-V 5.0 SP1 Hotfix Packages were installed.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**ManagementDatabase key**
|
||||
|
||||
If you are installing the Management database, set these registry keys under `HKLM\Software\Microsoft\AppV\Server\ManagementDatabase`.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Key name</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>IS_MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED</p></td>
|
||||
<td align="left"><p>Describes whether a public access account is required to access non-local management databases. Value is set to “1” if it is required.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>MANAGEMENT_DB_NAME</p></td>
|
||||
<td align="left"><p>Name of the Management database.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT</p></td>
|
||||
<td align="left"><p>Account used for read (public) access to the Management database.</p>
|
||||
<p>Used when <code>IS_MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED</code> is set to 1.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT_SID</p></td>
|
||||
<td align="left"><p>Secure identifier (SID) of the account used for read (public) access to the Management database.</p>
|
||||
<p>Used when <code>IS_MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED</code> is set to 1.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>MANAGEMENT_DB_SQL_INSTANCE</p></td>
|
||||
<td align="left"><p>SQL Server instance for the Management database.</p>
|
||||
<p>If the value is blank, the default database instance is used.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>MANAGEMENT_DB_WRITE_ACCESS_ACCOUNT</p></td>
|
||||
<td align="left"><p>Account used for write (administrator) access to the Management database.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>MANAGEMENT_DB_WRITE_ACCESS_ACCOUNT_SID</p></td>
|
||||
<td align="left"><p>Secure identifier (SID) of the account used for write (administrator) access to the Management database.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT</p></td>
|
||||
<td align="left"><p>Management server remote computer account (domain\account).</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT</p></td>
|
||||
<td align="left"><p>Installation administrator login for the Management server (domain\account).</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>MANAGEMENT_SERVER_MACHINE_USE_LOCAL</p></td>
|
||||
<td align="left"><p>Valid values are:</p>
|
||||
<ul>
|
||||
<li><p><strong>1</strong> – the Management service is on the local computer, that is, MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT is blank.</p></li>
|
||||
<li><p><strong>0</strong> - the Management service is on a different computer from the local computer.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**ManagementService key**
|
||||
|
||||
If you are installing the Management server, set these registry keys under `HKLM\Software\Microsoft\AppV\Server\ManagementService`.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Key name</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>MANAGEMENT_ADMINACCOUNT</p></td>
|
||||
<td align="left"><p>Active Directory Domain Services (AD DS) group or account that is authorized to manage App-V (domain\account).</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>MANAGEMENT_DB_SQL_INSTANCE</p></td>
|
||||
<td align="left"><p>SQL server instance that contains the Management database.</p>
|
||||
<p>If the value is blank, the default database instance is used.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>MANAGEMENT_DB_SQL_SERVER_NAME</p></td>
|
||||
<td align="left"><p>Name of the remote SQL server with the Management database.</p>
|
||||
<p>If the value is blank, the local computer is used.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**ReportingDatabase key**
|
||||
|
||||
If you are installing the Reporting database, set these registry keys under `HKLM\Software\Microsoft\AppV\Server\ReportingDatabase`.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Key name</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>IS_REPORTING_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED</p></td>
|
||||
<td align="left"><p>Describes whether a public access account is required to access non-local reporting databases. Value is set to “1” if it is required.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>REPORTING_DB_NAME</p></td>
|
||||
<td align="left"><p>Name of the Reporting database.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>REPORTING_DB_PUBLIC_ACCESS_ACCOUNT</p></td>
|
||||
<td align="left"><p>Account used for read (public) access to the Reporting database.</p>
|
||||
<p>Used when <code>IS_REPORTING_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED</code> is set to 1.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>REPORTING_DB_PUBLIC_ACCESS_ACCOUNT_SID</p></td>
|
||||
<td align="left"><p>Secure identifier (SID) of the account used for read (public) access to the Reporting database.</p>
|
||||
<p>Used when <code>IS_REPORTING_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED</code> is set to 1.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>REPORTING_DB_SQL_INSTANCE</p></td>
|
||||
<td align="left"><p>SQL Server instance for the Reporting database.</p>
|
||||
<p>If the value is blank, the default database instance is used.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>REPORTING_DB_WRITE_ACCESS_ACCOUNT</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>REPORTING_DB_WRITE_ACCESS_ACCOUNT_SID</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT</p></td>
|
||||
<td align="left"><p>Reporting server remote computer account (domain\account).</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT</p></td>
|
||||
<td align="left"><p>Installation administrator login for the Reporting server (domain\account).</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>REPORTING_SERVER_MACHINE_USE_LOCAL</p></td>
|
||||
<td align="left"><p>Valid values are:</p>
|
||||
<ul>
|
||||
<li><p><strong>1</strong> – the Reporting service is on the local computer, that is, REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT is blank.</p></li>
|
||||
<li><p><strong>0</strong> - the Reporting service is on a different computer from the local computer.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**ReportingService key**
|
||||
|
||||
If you are installing the Reporting server, set these registry keys under `HKLM\Software\Microsoft\AppV\Server\ReportingService`.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Key name</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>REPORTING_DB_SQL_INSTANCE</p></td>
|
||||
<td align="left"><p>SQL Server instance for the Reporting database.</p>
|
||||
<p>If the value is blank, the default database instance is used.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>REPORTING_DB_SQL_SERVER_NAME</p></td>
|
||||
<td align="left"><p>Name of the remote SQL server with the Reporting database.</p>
|
||||
<p>If the value is blank, the local computer is used.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
@ -1,269 +0,0 @@
|
||||
---
|
||||
title: How to Deploy the App-V 5.1 Server
|
||||
description: How to Deploy the App-V 5.1 Server
|
||||
ms.assetid: 4729beda-b98f-481b-ae74-ad71c59b1d69
|
||||
author: jamiejdt
|
||||
---
|
||||
|
||||
# How to Deploy the App-V 5.1 Server
|
||||
|
||||
|
||||
Use the following procedure to install the Microsoft Application Virtualization (App-V) 5.1 server. For information about deploying the App-V 5.1 Server, see [About App-V 5.1](about-app-v-51.md#bkmk-migrate-to-51).
|
||||
|
||||
**Before you start:**
|
||||
|
||||
- Ensure that you’ve installed prerequisite software. See [App-V 5.1 Prerequisites](app-v-51-prerequisites.md).
|
||||
|
||||
- Review the server section of [App-V 5.1 Security Considerations](app-v-51-security-considerations.md).
|
||||
|
||||
- Specify a port where each component will be hosted.
|
||||
|
||||
- Add firewall rules to allow incoming requests to access the specified ports.
|
||||
|
||||
- If you use SQL scripts, instead of the Windows Installer, to set up the Management database or Reporting database, you must run the SQL scripts before installing the Management Server or Reporting Server. See [How to Deploy the App-V Databases by Using SQL Scripts](how-to-deploy-the-app-v-databases-by-using-sql-scripts51.md).
|
||||
|
||||
**To install the App-V 5.1 server**
|
||||
|
||||
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it.
|
||||
|
||||
2. Start the App-V 5.1 server installation by right-clicking and running **appv\_server\_setup.exe** as an administrator, and then click **Install**.
|
||||
|
||||
3. Review and accept the license terms, and choose whether to enable Microsoft updates.
|
||||
|
||||
4. On the **Feature Selection** page, select all of the following components.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Component</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Management server</p></td>
|
||||
<td align="left"><p>Provides overall management functionality for the App-V infrastructure.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Management database</p></td>
|
||||
<td align="left"><p>Facilitates database predeployments for App-V management.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Publishing server</p></td>
|
||||
<td align="left"><p>Provides hosting and streaming functionality for virtual applications.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Reporting server</p></td>
|
||||
<td align="left"><p>Provides App-V 5.1 reporting services.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Reporting database</p></td>
|
||||
<td align="left"><p>Facilitates database predeployments for App-V reporting.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
5. On the **Installation Location** page, accept the default location where the selected components will be installed, or change the location by typing a new path on the **Installation Location** line.
|
||||
|
||||
6. On the initial **Create New Management Database** page, configure the **Microsoft SQL Server instance** and **Management Server database** by selecting the appropriate option below.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Method</th>
|
||||
<th align="left">What you need to do</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>You are using a custom Microsoft SQL Server instance.</p></td>
|
||||
<td align="left"><p>Select <strong>Use the custom instance</strong>, and type the name of the instance.</p>
|
||||
<p>Use the format <strong>INSTANCENAME</strong>. The assumed installation location is the local computer.</p>
|
||||
<p>Not supported: A server name using the format <strong>ServerName</strong>\<strong>INSTANCE</strong>.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>You are using a custom database name.</p></td>
|
||||
<td align="left"><p>Select <strong>Custom configuration</strong> and type the database name.</p>
|
||||
<p>The database name must be unique, or the installation will fail.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
7. 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.
|
||||
|
||||
|
||||
|
||||
8. On the initial **Create New Reporting Database** page, configure the **Microsoft SQL Server instance** and **Reporting Server database** by selecting the appropriate option below.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Method</th>
|
||||
<th align="left">What you need to do</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>You are using a custom Microsoft SQL Server instance.</p></td>
|
||||
<td align="left"><p>Select <strong>Use the custom instance</strong>, and type the name of the instance.</p>
|
||||
<p>Use the format <strong>INSTANCENAME</strong>. The assumed installation location is the local computer.</p>
|
||||
<p>Not supported: A server name using the format <strong>ServerName</strong>\<strong>INSTANCE</strong>.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>You are using a custom database name.</p></td>
|
||||
<td align="left"><p>Select <strong>Custom configuration</strong> and type the database name.</p>
|
||||
<p>The database name must be unique, or the installation will fail.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
9. 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.
|
||||
|
||||
|
||||
|
||||
10. On the **Configure** (Management Server Configuration) page, specify the following:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Item to configure</th>
|
||||
<th align="left">Description and examples</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Type the AD group with sufficient permissions to manage the App-V environment.</p></td>
|
||||
<td align="left"><p>Example: MyDomain\MyUser</p>
|
||||
<p>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 <strong>Domain local</strong> or <strong>Universal</strong> groups are required to perform this action.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Website name</strong>: Specify the custom name that will be used to run the publishing service.</p></td>
|
||||
<td align="left"><p>If you do not have a custom name, do not make any changes.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Port binding</strong>: Specify a unique port number that will be used by App-V.</p></td>
|
||||
<td align="left"><p>Example: <strong>12345</strong></p>
|
||||
<p>Ensure that the port specified is not being used by another website.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
11. On the **Configure** **Publishing Server Configuration** page, specify the following:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Item to configure</th>
|
||||
<th align="left">Description and examples</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Specify the URL for the management service.</p></td>
|
||||
<td align="left"><p>Example: http://localhost:12345</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Website name</strong>: Specify the custom name that will be used to run the publishing service.</p></td>
|
||||
<td align="left"><p>If you do not have a custom name, do not make any changes.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Port binding</strong>: Specify a unique port number that will be used by App-V.</p></td>
|
||||
<td align="left"><p>Example: 54321</p>
|
||||
<p>Ensure that the port specified is not being used by another website.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
12. On the **Reporting Server** page, specify the following:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Item to configure</th>
|
||||
<th align="left">Description and examples</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Website name</strong>: Specify the custom name that will be used to run the Reporting Service.</p></td>
|
||||
<td align="left"><p>If you do not have a custom name, do not make any changes.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Port binding</strong>: Specify a unique port number that will be used by App-V.</p></td>
|
||||
<td align="left"><p>Example: 55555</p>
|
||||
<p>Ensure that the port specified is not being used by another website.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
13. To start the installation, click **Install** on the **Ready** page, and then click **Close** on the **Finished** page.
|
||||
|
||||
14. To verify that the setup completed successfully, open a web browser, and type the following URL:
|
||||
|
||||
**http://<Management server machine name>:<Management service port number>/Console.html**.
|
||||
|
||||
Example: **http://localhost:12345/console.html**. If the installation succeeded, the App-V Management console is displayed with no errors.
|
||||
|
||||
**Got 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/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Deploying App-V 5.1](deploying-app-v-51.md)
|
||||
|
||||
[How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services](how-to-install-the-management-and-reporting-databases-on-separate-computers-from-the-management-and-reporting-services51.md)
|
||||
|
||||
[How to Install the Publishing Server on a Remote Computer](how-to-install-the-publishing-server-on-a-remote-computer51.md)
|
||||
|
||||
[How to Deploy the App-V 5.1 Server Using a Script](how-to-deploy-the-app-v-51-server-using-a-script.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -8,11 +8,10 @@ author: jamiejdt
|
||||
# Migrating to App-V 5.1 from a Previous Version
|
||||
|
||||
|
||||
With Microsoft Application Virtualization (App-V) 5.1, you can migrate your existing App-V 4.6 or App-V 5.0 infrastructure to the more flexible, integrated, and easier to manage App-V 5.1 infrastructure.
|
||||
However, you cannot migrate directly from App-V 4.x to App-V 5.1, you must migrate to App-V 5.0 first. For more information on migrating from App-V 4.x to App-V 5.0, see [Migrating from a Previous Version](migrating-from-a-previous-version-app-v-50.md)
|
||||
With Microsoft Application Virtualization (App-V) 5.1 you can migrate your existing App-V 4.6 infrastructure to the more flexible, integrated, and easier to manage App-V 5.1 infrastructure.
|
||||
|
||||
**Note**
|
||||
App-V 5.1 packages are exactly the same as App-V 5.0 packages. There has been no change in the package format between the versions and therefore, there is no need to convert App-V 5.0 packages to App-V 5.1 packages.
|
||||
App-V 5.1 packages are exactly the same as App-V 5.0 packages. There has been no change in the package format between the versions and so there is no need to convert App-V 5.0 packages to App-V 5.1 packages.
|
||||
|
||||
For more information about the differences between App-V 4.6 and App-V 5.1, see the **Differences between App-4.6 and App-V 5.0 section** of [About App-V 5.0](about-app-v-50.md).
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user