Deleting an old section about migrating clients - no longer applies

This commit is contained in:
JanKeller1 2016-08-12 15:00:53 -07:00
parent c8b046634a
commit e14fdf3198

View File

@ -207,45 +207,8 @@ It is recommended that you use the App-V sequencer for converting critical appli
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.
 
[How to Convert a Package Created in a Previous Version of App-V](appv-convert-a-package-created-in-a-previous-version-of-appv.md)
## Migrating Clients
The following table displays the recommended method for upgrading clients.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Task</th>
<th align="left">More Information</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Upgrade your environment to the latest version of App-V 4.6</p></td>
<td align="left"><p>[Application Virtualization Deployment and Upgrade Considerations](https://technet.microsoft.com/en-us/itpro/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy).</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Sequence and roll out App-V packages. As needed, unpublish App-V 4.6 packages.</p></td>
<td align="left"><p>[How to Sequence a New Application with App-V](appv-sequence-a-new-application.md).</p></td>
</tr>
</tbody>
</table>
 
**Important**  
You must be running the latest version of App-V 4.6 to use coexistence mode. Additionally, when you sequence a package, you must configure the Managing Authority setting, which is in the **User Configuration** is located in the **User Configuration** section.
 
## Migrating the App-V server Server Full Infrastructure