mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 10:53:43 +00:00
Cleanup in preparation for publishing: part 1
This commit is contained in:
Heidi Lohr
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# What's new in App-V for Windows 10, version 1703 and earlier
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 06/26/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 06/26/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# App-V Capacity Planning
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# About Client Configuration Settings
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Creating and Managing App-V Virtualized Applications
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# How to deploy the App-V databases by using SQL scripts
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# How to deploy the App-V server using a script
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# How to Deploy the App-V Server (new installation)
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Deploying App-V for Windows 10
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Deploying Microsoft Office 2010 by Using App-V
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Deploying Microsoft Office 2013 by Using App-V
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Deploying Microsoft Office 2016 by Using App-V
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Deploying the App-V Sequencer and configuring the client
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Deploying the App-V server
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# App-V Deployment Checklist
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Enable the App-V in-box client
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
|
||||
# Getting started with App-V for Windows 10
|
||||
|
||||
@ -6,9 +6,8 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
|
||||
# High-level architecture for App-V
|
||||
|
||||
>Applies to Windows 10, version 1607.
|
||||
@ -26,58 +25,9 @@ A typical App-V implementation consists of the following elements.
|
||||
|App-V Reporting Server|The App-V Reporting server lets authorized users run and view existing App-V reports and ad hoc reports for managing App-V infrastructure. The Reporting server requires a connection to the App-V reporting database. You can also help increase App-V availability by installing the Reporting server on multiple computers. You should also consider having a network load balancer to keep server requests balanced.|
|
||||
|App-V Client|The App-V client enables packages created using App-V to run on target computers.|
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="30%" />
|
||||
<col width="70%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Element</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V Management server</p></td>
|
||||
<td align="left"><p>The App-V Management server provides overall management functionality for the App-V infrastructure. Additionally, you can install more than one instance of the management server in your environment which provides the following benefits:</p>
|
||||
<ul>
|
||||
<li><p>Fault tolerance and high availability—installing and configuring the App-V Management server on two separate computers can help in situations when one of the servers is unavailable or offline.</p>
|
||||
<p>You can also help increase App-V availability by installing the Management server on multiple computers. In this scenario, consider using a network load balancer to keep server requests balanced.</p></li>
|
||||
<li><p>Scalability—you can add additional management servers as necessary to support a high load. For example, you can install multiple servers behind a load balancer.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V Publishing Server</p></td>
|
||||
<td align="left"><p>The App-V publishing server provides functionality for virtual application hosting and streaming. The publishing server does not require a database connection and supports the following protocols:</p>
|
||||
<ul>
|
||||
<li><p>HTTP and HTTPS</p></li>
|
||||
</ul>
|
||||
<p>You can also help increase App-V availability by installing the Publishing server on multiple computers. You should also consider having a network load balancer to keep server requests balanced.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V Reporting Server</p></td>
|
||||
<td align="left"><p>The App-V Reporting server lets authorized users run and view existing App-V reports and ad hoc reports for managing App-V infrastructure. The Reporting server requires a connection to the App-V reporting database. You can also help increase App-V availability by installing the Reporting server on multiple computers. You should also consider having a network load balancer to keep server requests balanced.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V Client</p></td>
|
||||
<td align="left"><p>The App-V client enables packages created using App-V to run on target computers.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
>[!NOTE]
|
||||
>If you are using App-V with electronic software distribution (ESD), you aren't required to use the App-V Management server. However, you can still use App-V's reporting and streaming functionality.
|
||||
|
||||
## Related topics
|
||||
|
||||
[Getting Started with App-V](appv-getting-started.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- [Getting Started with App-V](appv-getting-started.md)
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# How to install the Management Server on a Standalone Computer and Connect it to the Database
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# How to Install the Publishing Server on a Remote Computer
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# How to install the reporting server on a standalone computer and connect it to the database
|
||||
|
||||
@ -17,7 +17,7 @@ Use the following procedure to install the reporting server on a standalone comp
|
||||
>[!IMPORTANT]
|
||||
>Before performing the following procedure you should read and understand [About App-V reporting](appv-reporting.md).
|
||||
|
||||
**To install the reporting server on a standalone computer and connect it to the database**
|
||||
## Install the reporting server on a standalone computer and connect it to the database
|
||||
|
||||
1. Copy the App-V server installation files to the computer you plan to install it on. To start the App-V server installation, run **appv\_server\_setup.exe** as an administrator, then select **Install**.
|
||||
2. On the **Getting started** page, review and accept the license terms, then select **Next**.
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Install the App-V Sequencer
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Operations for App-V
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# App-V Planning Checklist
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Planning to Use Folder Redirection with App-V
|
||||
|
||||
@ -53,42 +53,9 @@ The following table describes how folder redirection works when %AppData% is red
|
||||
|
||||
|Virtual environment state|Action that occurs|
|
||||
|---|---|
|
||||
|When the virtual environment starts.|The virtual file system (VFS) AppData folder is mapped to the local AppData folder (%LocalAppData%) instead of to the user’s roaming AppData folder (%AppData%).<br>LocalAppData contains a local cache of the user’s roaming AppData folder for the package in use. The local cache is located under ```%LocalAppData%\Microsoft\AppV\Client\VFS\PackageGUID\AppData```<br>The latest data from the user’s roaming AppData folder is copied to and replaces the data currently in the local cache.<br>While the virtual environment is running, data continues to be saved to the local cache. Data is served only out of %LocalAppData% and is not moved or synchronized with %AppData% until the end user shuts down the computer.<br>Entries to the AppData folder are made using the user context, not the system context.|
|
||||
|When the virtual environment starts.|The virtual file system (VFS) AppData folder is mapped to the local AppData folder (%LocalAppData%) instead of to the user’s roaming AppData folder (%AppData%).<br>- LocalAppData contains a local cache of the user’s roaming AppData folder for the package in use. The local cache is located under ```%LocalAppData%\Microsoft\AppV\Client\VFS\PackageGUID\AppData```<br>- The latest data from the user’s roaming AppData folder is copied to and replaces the data currently in the local cache.<br>- While the virtual environment is running, data continues to be saved to the local cache. Data is served only out of %LocalAppData% and is not moved or synchronized with %AppData% until the end user shuts down the computer.<br>- Entries to the AppData folder are made using the user context, not the system context.|
|
||||
|When the virtual environment shuts down.|The local cached data in AppData (roaming) is zipped up and copied to the “real” roaming AppData folder in %AppData%. A time stamp that indicates the last known upload is simultaneously saved as a registry key under ```HKCU\Software\Microsoft\AppV\Client\Packages\<PACKAGE_GUID>\AppDataTime```. App-V keeps the three most recent copies of the compressed data under %AppData% for redundancy.|
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Virtual environment state</th>
|
||||
<th align="left">Action that occurs</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>When the virtual environment starts</p></td>
|
||||
<td align="left"><p>The virtual file system (VFS) AppData folder is mapped to the local AppData folder (%LocalAppData%) instead of to the user’s roaming AppData folder (%AppData%).</p>
|
||||
<ul>
|
||||
<li><p>LocalAppData contains a local cache of the user’s roaming AppData folder for the package in use. The local cache is located under:</p>
|
||||
<p><code>%LocalAppData%\Microsoft\AppV\Client\VFS\PackageGUID\AppData</code></p></li>
|
||||
<li><p>The latest data from the user’s roaming AppData folder is copied to and replaces the data currently in the local cache.</p></li>
|
||||
<li><p>While the virtual environment is running, data continues to be saved to the local cache. Data is served only out of %LocalAppData% and is not moved or synchronized with %AppData% until the end user shuts down the computer.</p></li>
|
||||
<li><p>Entries to the AppData folder are made using the user context, not the system context.</p></li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>When the virtual environment shuts down</p></td>
|
||||
<td align="left"><p>The local cached data in AppData (roaming) is zipped up and copied to the “real” roaming AppData folder in %AppData%. A time stamp that indicates the last known upload is simultaneously saved as a registry key under:</p>
|
||||
<p><code>HKCU\Software\Microsoft\AppV\Client\Packages\<PACKAGE_GUID>\AppDataTime</code></p>
|
||||
<p>App-V keeps the three most recent copies of the compressed data under %AppData% for redundancy.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
|
||||
|
||||
@ -49,48 +49,11 @@ The following table lists server-related protocols used by the App-V servers, an
|
||||
|IIS server|HTTP<br>HTTPS|This server-protocol combination requires a mechanism to synchronize content between the Management Server and the Streaming Server. When using HTTP or HTTPS, use an IIS server and a firewall to protect the server from exposure to the Internet.|Internal|
|
||||
|File|SMB|This server-protocol combination requires support to synchronize the content between the Management Server and the Streaming Server. Use a client computer that's capable of file sharing or streaming.|Internal|
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="20%" />
|
||||
<col width="20%" />
|
||||
<col width="20%" />
|
||||
<col width="20%" />
|
||||
<col width="20%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Server type</th>
|
||||
<th align="left">Protocols</th>
|
||||
<th align="left">External features needed</th>
|
||||
<th align="left">Reporting</th>
|
||||
<th align="left"></th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>IIS server</p></td>
|
||||
<td align="left"><p>HTTP</p>
|
||||
<p>HTTPS</p></td>
|
||||
<td align="left"><p>This server-protocol combination requires a mechanism to synchronize content between the Management Server and the Streaming Server. When using HTTP or HTTPS, use an IIS server and a firewall to protect the server from exposure to the Internet.</p></td>
|
||||
<td align="left"><p>Internal</p></td>
|
||||
<td align="left"></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>File</p></td>
|
||||
<td align="left"><p>SMB</p></td>
|
||||
<td align="left"><p>This server-protocol combination requires support to synchronize the content between the Management Server and the Streaming Server. Use a client computer that's capable of file sharing or streaming.</p></td>
|
||||
<td align="left"><p>Internal</p></td>
|
||||
<td align="left"></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
|
||||
|
||||
## Related topics
|
||||
|
||||
[Planning to deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
|
||||
[Deploying the App-V server](appv-deploying-the-appv-server.md)
|
||||
* [Planning to deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
* [Deploying the App-V server](appv-deploying-the-appv-server.md)
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Planning for App-V
|
||||
|
||||
@ -25,13 +25,8 @@ Use the following information to plan to deploy App-V without disrupting your ex
|
||||
## Other App-V planning resources
|
||||
|
||||
* [Application Virtualization (App-V) overview](appv-for-windows.md)
|
||||
|
||||
* [Getting started with App-V](appv-getting-started.md)
|
||||
|
||||
* [Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
* [Operations for App-V](appv-operations.md)
|
||||
|
||||
* [Troubleshooting App-V](appv-troubleshooting.md)
|
||||
|
||||
* [Technical reference for App-V](appv-technical-reference.md)
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Planning for high availability with App-V Server
|
||||
|
||||
@ -104,4 +104,4 @@ Add or vote on suggestions on the [Application Virtualization feedback site](htt
|
||||
|
||||
## Related topics
|
||||
|
||||
[Planning to deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
* [Planning to deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Planning for the App-V Sequencer and Client Deployment
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Planning for deploying App-V with Office
|
||||
|
||||
@ -93,37 +93,6 @@ The following table describes the integration level of each version of Office, a
|
||||
|Office 2013|Always integrated. Windows operating system integrations cannot be disabled.|
|
||||
|Office 2016|Always integrated. Windows operating system integrations cannot be disabled.|
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left"></th>
|
||||
<th align="left">The modes App-V can sequence this version of Office with</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Office 2007</p></td>
|
||||
<td align="left"><p>Always non-integrated. App-V does not offer any operating system integrations with a virtualized version of Office 2007.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Office 2010</p></td>
|
||||
<td align="left"><p>Integrated and non-integrated mode.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Office 2013</p></td>
|
||||
<td align="left"><p>Always integrated. Windows operating system integrations cannot be disabled.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Office 2016</p></td>
|
||||
<td align="left"><p>Always integrated. Windows operating system integrations cannot be disabled.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
Microsoft recommends deploying Office coexistence with only one integrated Office instance. For example, if you’re using App-V to deploy Office 2010 and Office 2013, you should sequence Office 2010 in non-integrated mode. For more information about sequencing Office in non-integration (isolated) mode, see [How to sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0](http://support.microsoft.com/kb/2830069).
|
||||
|
||||
### Known limitations of Office coexistence scenarios
|
||||
@ -179,91 +148,12 @@ The Office 2013 or Office 2016 App-V package supports the following integration
|
||||
|Primary Interop Assemblies|Support managed add-ins|
|
||||
|Office Document Cache Handler|Allows Document Cache for Office applications|
|
||||
|Outlook Protocol Search Handler|User can search in Outlook|
|
||||
|Active X Controls|For more information on ActiveX controls, refer to [ActiveX Control API Reference](https://msdn.microsoft.com/library/vs/alm/ms440037(v=office.14).aspx).|
|
||||
|Active X Controls|For more information on ActiveX controls, refer to [ActiveX Control API Reference](<https://msdn.microsoft.com/library/vs/alm/ms440037(v=office.14).aspx>).|
|
||||
|OneDrive Pro Icon Overlays|Windows Explorer shell icon overlays when users look at folders OneDrive Pro folders|
|
||||
|Shell extensions||
|
||||
|Shortcuts||
|
||||
|Windows Search||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Integration point</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Skype for Business (formerly Lync) Meeting Join plug-in for Firefox and Chrome</p></td>
|
||||
<td align="left"><p>User can join Skype meetings from Firefox and Chrome</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Sent to OneNote Print Driver</p></td>
|
||||
<td align="left"><p>User can print to OneNote</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>OneNote Linked Notes</p></td>
|
||||
<td align="left"><p>OneNote Linked Notes</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Send to OneNote Internet Explorer add-in</p></td>
|
||||
<td align="left"><p>User can send to OneNote from IE</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Firewall exception for Skype for Business (formerly Lync) and Outlook</p></td>
|
||||
<td align="left"><p>Firewall exception for Skype for Business (formerly Lync) and Outlook</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>MAPI client</p></td>
|
||||
<td align="left"><p>Native apps and add-ins can interact with virtual Outlook through MAPI</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>SharePoint Plug-in for Firefox</p></td>
|
||||
<td align="left"><p>User can use SharePoint features in Firefox</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Mail Control Panel Applet</p></td>
|
||||
<td align="left"><p>User gets the mail control panel applet in Outlook</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Primary Interop Assemblies</p></td>
|
||||
<td align="left"><p>Support managed add-ins</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Office Document Cache Handler</p></td>
|
||||
<td align="left"><p>Allows Document Cache for Office applications</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Outlook Protocol Search handler</p></td>
|
||||
<td align="left"><p>User can search in outlook</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Active X Controls</p></td>
|
||||
<td align="left"><p>For more information on ActiveX controls, refer to [ActiveX Control API Reference](https://msdn.microsoft.com/library/vs/alm/ms440037(v=office.14).aspx).</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>OneDrive Pro Icon Overlays</p></td>
|
||||
<td align="left"><p>Windows Explorer shell icon overlays when users look at folders OneDrive Pro folders</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Shell extensions</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Shortcuts</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Windows Search</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Planning to Deploy App-V with an electronic software distribution system
|
||||
|
||||
|
||||
@ -6,11 +6,11 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Planning to Deploy App-V for Windows 10
|
||||
|
||||
>Applies to Windows 10, version 1607.
|
||||
>Applies to: Windows 10, version 1607
|
||||
|
||||
There are several different deployment configurations and requirements to consider before you deploy App-V for Windows 10. Review this topic for information about what you'll need to make a deployment plan that best meets your needs.
|
||||
|
||||
@ -53,5 +53,4 @@ There are several different deployment configurations and requirements to consid
|
||||
## Other Resources for App-V Planning
|
||||
|
||||
* [Planning for App-V](appv-planning-for-appv.md)
|
||||
|
||||
* [Performance Guidance for Application Virtualization](appv-performance-guidance.md)
|
||||
|
||||
@ -6,11 +6,11 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# Preparing your environment for App-V
|
||||
|
||||
>Applies to Windows 10, version 1607.
|
||||
>Applies to: Windows 10, version 1607
|
||||
|
||||
There are several different deployment configurations and prerequisites that you must consider before creating your deployment plan for Microsoft App-V. The following articles will help you gather the information you need to set up a deployment plan that best suits your business’ needs.
|
||||
|
||||
|
||||
@ -6,11 +6,11 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 04/16/2018
|
||||
---
|
||||
# App-V for Windows 10 prerequisites
|
||||
|
||||
>Applies to Windows 10, version 1607.
|
||||
>Applies to: Windows 10, version 1607
|
||||
|
||||
Before installing App-V for Windows 10, ensure that you have installed all of the following required prerequisite software.
|
||||
|
||||
@ -24,58 +24,9 @@ The following table indicates the software that is already installed for differe
|
||||
|---|---|
|
||||
|Windows 10|All prerequisite software is already installed.|
|
||||
|Windows 8.1|All prerequisite software is already installed.<br>If you're running Windows 8, upgrade to Windows 8.1 before using App-V.|
|
||||
|Windows Server 2016|The following prerequisite software is already installed:<br>Microsoft .NET Framework 4.5<br>Windows PowerShell 3.0<br><br>Installing Windows PowerShell requires a restart.|
|
||||
|Windows Server 2016|The following prerequisite software is already installed:<br>- Microsoft .NET Framework 4.5<br>- Windows PowerShell 3.0<br><br>Installing Windows PowerShell requires a restart.|
|
||||
|Windows 7|No prerequisite software is installed. You must install the software before you can install App-V.|
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Operating system</th>
|
||||
<th align="left">Prerequisite description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows 10</p></td>
|
||||
<td align="left"><p>All prerequisite software is already installed.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Windows 8.1</p></td>
|
||||
<td align="left"><p>All prerequisite software is already installed.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>If you are running Windows 8, upgrade to Windows 8.1 before using App-V.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows Server 2016</p></td>
|
||||
<td align="left"><p>The following prerequisite software is already installed:</p>
|
||||
<ul>
|
||||
<li><p>Microsoft .NET Framework 4.5</p></li>
|
||||
<li><p>Windows PowerShell 3.0</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>Installing Windows PowerShell 3.0 requires a restart.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
</div></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Windows 7</p></td>
|
||||
<td align="left"><p>No prerequisite software is installed. You must install the software before you can install App-V.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## App-V Server prerequisite software
|
||||
|
||||
Install the required prerequisite software for the App-V server components.
|
||||
@ -101,48 +52,13 @@ The following deployment scenarios are not supported:
|
||||
* Installing side-by-side instances of multiple App-V Server versions on the same server.
|
||||
* Installing the App-V server components on a computer that runs server core or domain controller.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Account for installing the App-V Server</p></td>
|
||||
<td align="left"><p>The account that you use to install the App-V Server components must have:</p>
|
||||
<ul>
|
||||
<li><p>Administrative rights on the computer on which you are installing the components.</p></li>
|
||||
<li><p>The ability to query Active Directory Domain Services.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Port and firewall</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Specify a port where each component will be hosted.</p></li>
|
||||
<li><p>Add the associated firewall rules to allow incoming requests to the specified ports.</p></li>
|
||||
</ul>
|
||||
<p></p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Web Distributed Authoring and Versioning (WebDAV)</p></td>
|
||||
<td align="left"><p>WebDAV is automatically disabled for the Management Service.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Supported deployment scenarios</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>A stand-alone deployment, where all components are deployed on the same server.</p></li>
|
||||
<li><p>A distributed deployment.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Unsupported deployment scenarios</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Installing side-by-side instances of multiple App-V Server versions on the same server.</p></li>
|
||||
<li><p>Installing the App-V server components on a computer that runs server core or domain controller.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|Item|Description|
|
||||
|---|---|
|
||||
|Account for installing the App-V Server|The account that you use to install the App-V Server components must have:<br>- Administrative rights on the computer on which you are installing the components.<br>- The ability to query Active Directory Domain Services.|
|
||||
|Port and firewall|- Specify a port where each component will be hosted.<br>- Add the associated firewall rules to allow incoming requests to the specified ports.|
|
||||
|Web Distributed Authoring and Versioning (WebDAV)|WebDAV is automatically disabled for the Management Service.|
|
||||
|Supported deployment scenarios|- A stand-alone deployment, where all components are deployed on the same server.<br>- A distributed deployment.|
|
||||
|Unsupported deployment scenarios|- Installing side-by-side instances of multiple App-V Server versions on the same server.<br>- Installing the App-V server components on a computer that runs server core or domain controller.|
|
||||
|
||||
### Management server prerequisite software
|
||||
|
||||
|
||||
@ -156,7 +156,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
15. The **Create Package** page is displayed. To modify the package without saving it, select **Continue to modify package without saving using the package editor** check box. This option opens the package in the sequencer console so that you can modify the package before it is saved. Select **Next**.
|
||||
|
||||
To save the package immediately, select **Save the package now**. Optionally, add a **Description** that will be associated with the package. Descriptions are useful for identifying the version and other information about the package.
|
||||
To save the package immediately, select **Save the package now**. Optionally, add a **Description** for the package. Descriptions are useful for identifying the version and other important information about the package.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>The system does not support non-printable characters in Comments and Descriptions.
|
||||
@ -176,7 +176,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
4. On the **Type of Application** page, select **Middleware**, and then select **Next**.
|
||||
|
||||
5. On the **Select Installer** page, select **Browse** and specify the installation file for the application. If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Select this option to perform a custom installation** check box, and then select **Next**.
|
||||
5. On the **Select Installer** page, select **Browse** and specify the installation file for the application. If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Select this option to perform a custom installation** check box, then select **Next**.
|
||||
|
||||
6. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name is displayed in the App-V Management Console.
|
||||
|
||||
@ -188,15 +188,15 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
10. On the **Installation Report** page, you can review information about the virtual application package that you have just sequenced. In **Additional Information**, double-click an event to obtain more detailed information. To proceed, select **Next**.
|
||||
|
||||
11. On the **Target OS** page, specify the operating systems that can run this package. To enable all supported operating systems in your environment to run this package, select the **Allow this package to run on any operating system** check box. To configure this package to run only on specific operating systems, select the **Allow this package to run only on the following operating systems** check box and select the operating systems that can run this package. Select **Next**.
|
||||
11. On the **Target OS** page, specify the operating systems that can run this package. To enable all supported operating systems in your environment to run this package, select the **Allow this package to run on any operating system** check box. To configure this package to run only on specific operating systems, select the **Allow this package to run only on the following operating systems** check box and select the operating systems that can run this package. Once you're done, select **Next**.
|
||||
|
||||
12. On the **Create Package** page is displayed. To modify the package without saving it, select **Continue to modify package without saving using the package editor**. This option opens the package in the sequencer console so that you can modify the package before it is saved. Select **Next**.
|
||||
|
||||
To save the package immediately, select **Save the package now**. Optionally, add a **Description** to be associated with the package. Descriptions are useful for identifying the program version and other information about the package.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>The system does not support non-printable characters in Comments and Descriptions.
|
||||
|
||||
>The system does not support non-printable characters in comments and descriptions.
|
||||
|
||||
The default **Save Location** is also displayed on this page. To change the default location, select **Browse** and specify the new location. Select **Create**.
|
||||
|
||||
13. The **Completion** page is displayed. Review the information in the **Virtual Application Package Report** pane as needed, then select **Close**. This information is also available in the **Report.xml** file that is located in the directory specified in step 11 of this procedure.
|
||||
@ -204,7 +204,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
The package is now available in the sequencer. To edit the package properties, select **Edit \[Package Name\]**.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer.
|
||||
>After you have successfully created a virtual application package, you can't run the virtual application package on the computer that is running the sequencer.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Reference in New Issue
Block a user