deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 18:33:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Cleanup part 2

Browse Source
This commit is contained in:
Heidi Lohr
2018-04-16 16:24:56 -07:00
parent fc9bfefb3f
commit 791d29ade3
35 changed files with 59 additions and 1280 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
windows/application-management/app-v/revision-heidi/appv-about-appv.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# What's new in App-V for Windows 10, version 1703 and earlier
>Applies to Windows 10, version 1703 and earlier.
>Applies to: Windows 10, version 1703 and earlier
Microsoft Application Virtualization (App-V) for Windows 10 delivers Win32 applications to users as virtual applications. Virtual applications are installed on centrally managed servers and delivered to users as a service in real time and on an as-needed basis. Users launch virtual applications from familiar access points and interact with them as if they were installed locally.

2
windows/application-management/app-v/revision-heidi/appv-capacity-planning.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# App-V Capacity Planning
>Applies to Windows Server 2016.
>Applies to: Windows Server 2016
The following recommendations can be used as a baseline to help determine capacity planning information that is appropriate to your organization’s App-V infrastructure.

2
windows/application-management/app-v/revision-heidi/appv-client-configuration-settings.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# About Client Configuration Settings
>Applies to Windows 10, version 1607.
>Applies to: Windows 10, version 1607
The Microsoft Application Virtualization (App-V) client stores its configuration in the registry. Understanding how the register's format for data works can help you better understand the client, as you can configure many client actions by changing registry entries. This topic lists the App-V client configuration settings and explains their uses. You can use Windows PowerShell to modify the client configuration settings. For more information about using Windows PowerShell and App-V see [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md).

47
windows/application-management/app-v/revision-heidi/appv-creating-and-managing-virtualized-applications.md
View File

@ -88,53 +88,6 @@ The following table lists the supported shell extensions:
|Column handler|Allows creating and displaying custom columns in **Windows Explorer Details view**. It can be used to extend sorting and grouping.|
|Preview handler|Enables a preview of a file to be displayed in the Windows Explorer Preview pane.|
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Handler</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Context menu handler</p></td>
<td align="left"><p>Adds menu items to the context menu. It is called before the context menu is displayed.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Drag-and-drop handler</p></td>
<td align="left"><p>Controls the action where right-click, drag and drop and modifies the context menu that appears.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Drop target handler</p></td>
<td align="left"><p>Controls the action after a data object is dragged and dropped over a drop target such as a file.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Data object handler</p></td>
<td align="left"><p>Controls the action after a file is copied to the clipboard or dragged and dropped over a drop target. It can provide additional clipboard formats to the drop target.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Property sheet handler</p></td>
<td align="left"><p>Replaces or adds pages to the property sheet dialog box of an object.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Infotip handler</p></td>
<td align="left"><p>Allows retrieving flags and infotip information for an item and displaying it inside a pop-up tooltip upon mouse hover.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Column handler</p></td>
<td align="left"><p>Allows creating and displaying custom columns in <strong>Windows Explorer Details view</strong>. It can be used to extend sorting and grouping.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Preview handler</p></td>
<td align="left"><p>Enables a preview of a file to be displayed in the Windows Explorer Preview pane.</p></td>
</tr>
</tbody>
</table>
## Copy on Write (CoW) file extension support
Copy on write (CoW) file extensions allow App-V to dynamically write to specific locations contained in the virtual package while it is being used.

2
windows/application-management/app-v/revision-heidi/appv-deploy-appv-databases-with-sql-scripts.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# How to deploy the App-V databases by using SQL scripts
>Applies to Windows Server 2016.
>Applies to: Windows Server 2016
Use the following instructions to use SQL scripts, rather than the Windows Installer, to:

2
windows/application-management/app-v/revision-heidi/appv-deploy-the-appv-server-with-a-script.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# How to deploy the App-V server using a script
>Applies to Windows Server 2016.
>Applies to: Windows Server 2016
In order to complete the **appv_server_setup.exe** server setup successfully using the command line, you must specify and combine multiple parameters.

2
windows/application-management/app-v/revision-heidi/appv-deploy-the-appv-server.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# How to Deploy the App-V Server (new installation)
>Applies to Windows Server 2016.
>Applies to: Windows Server 2016
## Before you start

7
windows/application-management/app-v/revision-heidi/appv-deploying-appv.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# Deploying App-V for Windows 10
>Applies to Windows 10, version 1607.
>Applies to: Windows 10, version 1607
App-V supports several different deployment options. Review this topic for information about the tasks that you must complete at different stages in your deployment.
@ -35,15 +35,10 @@ The following sections describe how to use App-V to deliver Microsoft Office as
## Other App-V deployment resources
* [Application Virtualization (App-V) overview](appv-for-windows.md)
* [Getting started with App-V](appv-getting-started.md)
* [Planning for App-V](appv-planning-for-appv.md)
* [Operations for App-V](appv-operations.md)
* [Troubleshooting App-V](appv-troubleshooting.md)
* [Technical reference for App-V](appv-technical-reference.md)
## Have a suggestion for App-V?

163
windows/application-management/app-v/revision-heidi/appv-deploying-microsoft-office-2010-wth-appv.md
View File

@ -74,169 +74,6 @@ The following table provides a full list of supported integration points for Off
|Active X Controls:<br>- Groove.SiteClient<br>- PortalConnect.PersonalSite<br>- SharePoint.openDocuments<br>- SharePoint.ExportDatabase<br>- SharePoint.SpreadSheetLauncher<br>- SharePoint.StssyncHander<br>- SharePoint.DragUploadCtl<br>- SharePoint.DragDownloadCtl<br>- Sharpoint.OpenXMLDocuments<br> - Sharepoint.ClipboardCtl<br>- WinProj.Activator<br>- Name.NameCtrl<br>- STSUPld.CopyCtl<br>- CommunicatorMeetingJoinAx.JoinManager<br>- LISTNET.Listnet<br>- OneDrive Pro Browser Helper|Active X Control. <br><br>For more information about ActiveX controls, see the [ActiveX Control API Reference](<https://msdn.microsoft.com/library/office/ms440037(v=office.14).aspx>).||
|OneDrive Pro Icon Overlays|Windows explorer shell icon overlays when users look at folders OneDrive Pro folders||
<table>
<colgroup>
<col width="33%" />
<col width="33%" />
<col width="33%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Extension Point</th>
<th align="left">Description</th>
<th align="left">Office 2010</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Lync meeting Join Plug-in for Firefox and Chrome</p></td>
<td align="left"><p>User can join Lync meetings from Firefox and Chrome</p></td>
<td align="left"><p></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>
<td align="left"><p>Yes</p></td>
</tr>
<tr class="odd">
<td align="left"><p>OneNote Linked Notes</p></td>
<td align="left"><p>OneNote Linked Notes</p></td>
<td align="left"><p></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>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><p>Firewall Exception for Lync and Outlook</p></td>
<td align="left"><p>Firewall Exception for Lync and Outlook</p></td>
<td align="left"><p></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>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><p>SharePoint Plugin for Firefox</p></td>
<td align="left"><p>User can use SharePoint features in Firefox</p></td>
<td align="left"><p></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>
<td align="left"><p>Yes</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>
<td align="left"><p></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>
<td align="left"><p></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>
<td align="left"><p>Yes</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/office/ms440037(v=office.14).aspx).</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><p>   Groove.SiteClient</p></td>
<td align="left"><p>Active X Control</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><p>   PortalConnect.PersonalSite</p></td>
<td align="left"><p>Active X Control</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><p>   SharePoint.openDocuments</p></td>
<td align="left"><p>Active X Control</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><p>   SharePoint.ExportDatabase</p></td>
<td align="left"><p>Active X Control</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><p>   SharePoint.SpreadSheetLauncher</p></td>
<td align="left"><p>Active X Control</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><p>   SharePoint.StssyncHander</p></td>
<td align="left"><p>Active X Control</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><p>   SharePoint.DragUploadCtl</p></td>
<td align="left"><p>Active X Control</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><p>   SharePoint.DragDownloadCtl</p></td>
<td align="left"><p>Active X Control</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><p>   Sharpoint.OpenXMLDocuments</p></td>
<td align="left"><p>Active X Control</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><p>   Sharepoint.ClipboardCtl</p></td>
<td align="left"><p>Active X control</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><p>   WinProj.Activator</p></td>
<td align="left"><p>Active X Control</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><p>   Name.NameCtrl</p></td>
<td align="left"><p>Active X Control</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><p>   STSUPld.CopyCtl</p></td>
<td align="left"><p>Active X Control</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><p>   CommunicatorMeetingJoinAx.JoinManager</p></td>
<td align="left"><p>Active X Control</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><p>   LISTNET.Listnet</p></td>
<td align="left"><p>Active X Control</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><p>   OneDrive Pro Browser Helper</p></td>
<td align="left"><p>Active X Control]</p></td>
<td align="left"><p></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>
<td align="left"><p></p></td>
</tr>
</tbody>
</table>
## Additional resources
### Office 2013 App-V Packages Additional Resources

336
windows/application-management/app-v/revision-heidi/appv-deploying-microsoft-office-2013-with-appv.md
View File

@ -24,36 +24,9 @@ The following table will direct you to more information about which versions of
|Information to review|Description|
|---|---|
|[Supported versions of Microsoft Office](appv-planning-for-using-appv-with-office.md#bkmk-office-vers-supp-appv)|Supported versions of Office and deployment types (for example, desktop, personal Virtual Desktop Infrastructure (VDI), and pooled VDI), and Office licensing options.|
|[Supported versions of Microsoft Office](appv-planning-for-using-appv-with-office.md#bkmk-office-vers-supp-appv)|- Supported versions of Office<br>- Supported deployment types like desktop, personal Virtual Desktop Infrastructure (VDI), and pooled VDI<br>- Office licensing options.|
|[Planning for using App-V with coexisting versions of Office](appv-planning-for-using-appv-with-office.md#bkmk-plan-coexisting)|Considerations for installing different versions of Office on the same computer.|
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Information to review</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>[Supported versions of Microsoft Office](appv-planning-for-using-appv-with-office.md#bkmk-office-vers-supp-appv)</p></td>
<td align="left"><ul>
<li><p>Supported versions of Office</p></li>
<li><p>Supported deployment types (for example, desktop, personal Virtual Desktop Infrastructure (VDI), pooled VDI)</p></li>
<li><p>Office licensing options</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>[Planning for using App-V with coexisting versions of Office](appv-planning-for-using-appv-with-office.md#bkmk-plan-coexisting)</p></td>
<td align="left"><p>Considerations for installing different versions of Office on the same computer</p></td>
</tr>
</tbody>
</table>
### Packaging, publishing, and deployment requirements
Before you deploy Office with App-V, review the following requirements.
@ -62,52 +35,7 @@ Before you deploy Office with App-V, review the following requirements.
|---|---|
|Packaging|All Office applications you wish to deploy to users must be in a single package.<br>In App-V and later, you must use the Office Deployment Tool to create packages. The Sequencer doesn't support package creation.<br>If you're deploying Microsoft Visio 2013 and Microsoft Project 2013 along with Office, you must include them in the same package with Office. For more information, see [Deploying Visio 2013 and Project 2013 with Office](#bkmk-deploy-visio-project).|
|Publishing|You can only publish one Office package per client computer.<br>You must publish the Office package globally, not to the user.|
|Deploying Office 365 ProPlus, Visio Pro for Office 365, or Project Pro for Office 365 to a shared computer using Remote Desktop Services.|You must enable [shared computer activation](https://docs.microsoft.com/en-us/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus).<br>You don’t use shared computer activation if you’re deploying a volume licensed product, such as Office Professional Plus 2013, Visio Professional 2013, or Project Professional 2013.|
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Task</th>
<th align="left">Requirement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Packaging</p></td>
<td align="left"><ul>
<li><p>All Office applications you wish to deploy to users must be in a single package.</p></li>
<li><p>In App-V and later, you must use the Office Deployment Tool to create packages. The Sequencer doesn't support package creation in this version.</p></li>
<li><p>If you are deploying Microsoft Visio 2013 and Microsoft Project 2013 along with Office, you must include them in the same package with Office. For more information, see [Deploying Visio 2013 and Project 2013 with Office](#bkmk-deploy-visio-project).</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>Publishing</p></td>
<td align="left"><ul>
<li><p>You can only publish one Office package per client computer.</p></li>
<li><p>You must publish the Office package globally, not to the user.</p></li>
</ul></td>
</tr>
<tr class="odd">
<td align="left"><p>Deploying any of the following products to a shared computer, for example, by using Remote Desktop Services:</p>
<ul>
<li><p>Office 365 ProPlus</p></li>
<li><p>Visio Pro for Office 365</p></li>
<li><p>Project Pro for Office 365</p></li>
</ul></td>
<td align="left"><p>You must enable [shared computer activation](https://docs.microsoft.com/en-us/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus).</p>
<p>You don’t use shared computer activation if you’re deploying a volume licensed product, such as:</p>
<ul>
<li><p>Office Professional Plus 2013</p></li>
<li><p>Visio Professional 2013</p></li>
<li><p>Project Professional 2013</p></li>
</ul></td>
</tr>
</tbody>
</table>
|Deploying Office 365 ProPlus, Visio Pro for Office 365, or Project Pro for Office 365 to a shared computer using Remote Desktop Services.|You must enable [shared computer activation](https://docs.microsoft.com/en-us/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus).<br>You don’t need to use shared computer activation if you’re deploying a volume licensed product, such as Office Professional Plus 2013, Visio Professional 2013, or Project Professional 2013.|
### Excluding Office applications from a package
@ -116,36 +44,7 @@ The following table describes the recommended methods for excluding specific Off
|Task|Details|
|---|---|
|Use the **ExcludeApp** setting when you create the package by using the Office Deployment Tool.|Enables you to exclude specific Office applications from the package when the Office Deployment Tool creates the package. For example, you can use this setting to create a package that contains only Microsoft Word.<br>For more information, see [ExcludeApp element](https://docs.microsoft.com/en-us/DeployOffice/configuration-options-for-the-office-2016-deployment-tool?ui=en-US&rs=en-US&ad=US#excludeapp-element).|
|Modify the **DeploymentConfig.xml** file|Modify the DeploymentConfig.xml file after creating the package. This file contains the default package settings for all users on a computer running the App-V Client.<br>For more information, see [Disabling Office 2013 applications](#bkmk-disable-office-apps).|
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Task</th>
<th align="left">Details</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Use the <strong>ExcludeApp</strong> setting when you create the package by using the Office Deployment Tool.</p></td>
<td align="left"><ul>
<li><p>Enables you to exclude specific Office applications from the package when the Office Deployment Tool creates the package. For example, you can use this setting to create a package that contains only Microsoft Word.</p></li>
<li><p>For more information, see [ExcludeApp element](https://technet.microsoft.com/library/jj219426.aspx#BKMK_ExcludeAppElement). (CHECK LINK)</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>Modify the DeploymentConfig.xml file</p></td>
<td align="left"><ul>
<li><p>Modify the DeploymentConfig.xml file after creating the package. This file contains the default package settings for all users on a computer running the App-V Client.</p></li>
<li><p>For more information, see [Disabling Office 2013 applications](#bkmk-disable-office-apps).</p></li>
</ul></td>
</tr>
</tbody>
</table>
|Modify the **DeploymentConfig.xml** file|Modify the **DeploymentConfig.xml** file after creating the package. This file contains the default package settings for all users on a computer running the App-V Client.<br>For more information, see [Disabling Office 2013 applications](#bkmk-disable-office-apps).|
## Creating an Office 2013 package for App-V with the Office Deployment Tool
@ -160,35 +59,9 @@ Before you start, make sure that the computer on which you are installing the Of
|Prerequisite|Description|
|---|---|
|Prerequisite software|.Net Framework 4|
|Prerequisite software|.NET Framework 4|
|Supported operating systems|64-bit version of Windows 8 or later<br>64-bit version of Windows 7|
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Prerequisite</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Prerequisite software</p></td>
<td align="left"><p>.Net Framework 4</p></td>
</tr>
<tr class="even">
<td align="left"><p>Supported operating systems</p></td>
<td align="left"><ul>
<li><p>64-bit version of Windows 8 or later</p></li>
<li><p>64-bit version of Windows 7</p></li>
</ul></td>
</tr>
</tbody>
</table>
>[!NOTE]
>In this topic, the term “Office 2013 App-V package” refers to subscription licensing and volume licensing.
@ -254,31 +127,6 @@ The XML file included in the Office Deployment Tool specifies the product detail
|```/download```|This downloads the Office 2013 applications that you specify in the **Customconfig.xml** file. These bits can be later converted in an Office 2013 App-V package with Volume Licensing.|
|```\\server\Office2013\Customconfig.xml```|This passes the XML configuration file required to complete the download process. In this example, the file used is **Customconfig.xml**. After using the download command, Office applications should be found in the location specified in the XML configuration file, which in this example is ```\\Server\Office2013```.|
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p><code>\\server\Office2013</code></p></td>
<td align="left"><p>This is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml.</p></td>
</tr>
<tr class="even">
<td align="left"><p><code>setup.exe</code></p></td>
<td align="left"><p>This is the Office Deployment Tool.</p></td>
</tr>
<tr class="odd">
<td align="left"><p><code>/download</code></p></td>
<td align="left"><p>This downloads the Office 2013 applications that you specify in the <strong>Customconfig.xml</strong> file. These bits can be later converted in an Office 2013 App-V package with Volume Licensing.</p></td>
</tr>
<tr class="even">
<td align="left"><p><code>\\server\Office2013\Customconfig.xml</code></p></td>
<td align="left"><p>This passes the XML configuration file required to complete the download process. In this example, the file used is <strong>customconfig.xml</strong>. After using the download command, Office applications should be found in the location specified in the configuration xml file, in this example \\Server\Office2013.</p></td>
</tr>
</tbody>
</table>
#### Customizable attributes and elements of the XML file
|Input and description|Example|
@ -290,51 +138,6 @@ The XML file included in the Office Deployment Tool specifies the product detail
|Version (attribute of Add element):<br>Optional. Specifies a build to use for the package. Defaults to latest advertised build (as defined in v32.CAB at the Office source).|```15.1.2.3```|
|SourcePath (attribute of Add element):<br>Specifies the location where the applications will be saved to.|```Sourcepath="\Server\Office2013”```|
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Input and description</th>
<th align="left">Example</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Add element:<br>Specifies the products and languages to include in the package.</p></td>
<td align="left"><p>N/A</p></td>
</tr>
<tr class="even">
<td align="left"><p>OfficeClientEdition (attribute of Add element):<br>Specifies the edition of Office 2013 product to use: 32-bit or 64-bit. The operation fails if <strong>OfficeClientEdition</strong> is not set to a valid value.</p></td>
<td align="left"><p><code>OfficeClientEdition=&quot;32&quot;</code></p>
<p><code>OfficeClientEdition=&quot;64&quot;</code></p></td>
</tr>
<tr class="odd">
<td align="left"><p>Product element:<br>Specifies the application. Project 2013 and Visio 2013 must be specified here as an added product to be included in the applications.</p></td>
<td align="left"><p><code>Product ID =&quot;O365ProPlusRetail &quot;</code></p>
<p><code>Product ID =&quot;VisioProRetail&quot;</code></p>
<p><code>Product ID =&quot;ProjectProRetail&quot;</code></p>
<p><code>Product ID =&quot;ProPlusVolume&quot;</code></p>
<p><code>Product ID =&quot;VisioProVolume&quot;</code></p>
<p><code>Product ID = &quot;ProjectProVolume&quot;</code></p></td>
</tr>
<tr class="even">
<td align="left"><p>Language element:<br>Specifies the language supported in the applications.</p></td>
<td align="left"><p><code>Language ID=&quot;en-us&quot;</code></p></td>
</tr>
<tr class="odd">
<td align="left"><p>Version (attribute of Add element):<br>Optional. Specifies a build to use for the package. Defaults to latest advertised build (as defined in v32.CAB at the Office source).</p></td>
<td align="left"><p><code>15.1.2.3</code></p></td>
</tr>
<tr class="even">
<td align="left"><p>SourcePath (attribute of Add element):<br>Specifies the location in which the applications will be saved to.</p></td>
<td align="left"><p><code>Sourcepath = &quot;\\Server\Office2013”</code></p></td>
</tr>
</tbody>
</table>
### Convert the Office applications into an App-V package
After you download the Office 2013 applications through the Office Deployment Tool, use the Office Deployment Tool to convert them into an Office 2013 App-V package. You'll need to make sure to have the right procedure depending on your licensing model.
@ -352,44 +155,6 @@ After you download the Office 2013 applications through the Office Deployment To
|Office 2013 with Visio 2013|ProPlusVolume<br>VisioProVolume|O365ProPlusRetail<br>VisioProRetail|
|Office 2013 with Visio 2013 and Project 2013|ProPlusVolume<br>VisioProVolume<br>ProjectProVolume|O365ProPlusRetail<br>VisioProRetail<br>ProjectProRetail|
<table>
<colgroup>
<col width="33%" />
<col width="33%" />
<col width="33%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Product ID</th>
<th align="left">Volume Licensing</th>
<th align="left">Subscription Licensing</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p><strong>Office 2013</strong></p></td>
<td align="left"><p>ProPlusVolume</p></td>
<td align="left"><p>O365ProPlusRetail</p></td>
</tr>
<tr class="even">
<td align="left"><p><strong>Office 2013 with Visio 2013</strong></p></td>
<td align="left"><p>ProPlusVolume</p>
<p>VisioProVolume</p></td>
<td align="left"><p>O365ProPlusRetail</p>
<p>VisioProRetail</p></td>
</tr>
<tr class="odd">
<td align="left"><p><strong>Office 2013 with Visio 2013 and Project 2013</strong></p></td>
<td align="left"><p>ProPlusVolume</p>
<p>VisioProVolume</p>
<p>ProjectProVolume</p></td>
<td align="left"><p>O365ProPlusRetail</p>
<p>VisioProRetail</p>
<p>ProjectProRetail</p></td>
</tr>
</tbody>
</table>
#### How to convert the Office applications into an App-V package
1. In Notepad, reopen the CustomConfig.xml file, and make the following changes to the file:
@ -443,7 +208,7 @@ After you download the Office 2013 applications through the Office Deployment To
For example:
```POwerShell
```PowerShell
\\server\Office2013\setup.exe /packager \\server\Office2013\Customconfig.xml \\server\share\Office2013AppV
```
@ -457,35 +222,6 @@ After you download the Office 2013 applications through the Office Deployment To
|```\\server\Office2013\Customconfig.xml```|This passes the configuration XML file, which in this example is named "Customconfig," that has been prepared for the packaging stage.|
|```\\server\share\Office2013AppV```|This specifies the location of the newly created Office App-V package.|
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p><code>\\server\Office2013</code></p></td>
<td align="left"><p>This is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, which in this example is named <bold>Customconfig.xml</bold>.</p></td>
</tr>
<tr class="even">
<td align="left"><p><code>setup.exe</code></p></td>
<td align="left"><p>This is the Office Deployment Tool.</p></td>
</tr>
<tr class="odd">
<td align="left"><p><code>/packager</code></p></td>
<td align="left"><p>This creates the Office 2013 App-V package with Volume Licensing as specified in the <strong>Customconfig.xml</strong> file.</p></td>
</tr>
<tr class="even">
<td align="left"><p><code>\\server\Office2013\Customconfig.xml</code></p></td>
<td align="left"><p>This passes the configuration XML file, which in this example is named "Customconfig," that has been prepared for the packaging stage.</p></td>
</tr>
<tr class="odd">
<td align="left"><p><code>\\server\share\Office2013AppV</code></p></td>
<td align="left"><p>This specifies the location of the newly created Office App-V package.</p></td>
</tr>
</tbody>
</table>
After you run the **/packager** command, the following folders will appear in the directory where you specified the package should be saved:
* **App-V Packages**, which contains an Office 2013 App-V package and two deployment configuration files.<br>
@ -517,32 +253,6 @@ Deploy the App-V package for Office 2013 by using the same methods you use for a
|Enable Windows PowerShell scripting on the App-V clients.|To publish Office 2013 packages, you must run a script. Package scripts are disabled by default on App-V clients. To enable scripting, run the following Windows PowerShell command:<br>```Set-AppvClientConfiguration –EnablePackageScripts 1```|
|Publish the Office 2013 package globally.|Extension points in the Office App-V package require installation at the computer level.<br>When you publish at the computer level, no prerequisite actions or redistributables are needed, and the Office 2013 package globally enables its applications to work like natively installed Office, eliminating the need for administrators to customize packages.|
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Prerequisite or requirement</th>
<th align="left">Details</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Enable Windows PowerShell scripting on the App-V clients</p></td>
<td align="left"><p>To publish Office 2013 packages, you must run a script.</p>
<p>Package scripts are disabled by default on App-V clients. To enable scripting, run the following Windows PowerShell command:</p>
<pre class="syntax" space="preserve"><code>Set-AppvClientConfiguration –EnablePackageScripts 1</code></pre></td>
</tr>
<tr class="even">
<td align="left"><p>Publish the Office 2013 package globally</p></td>
<td align="left"><p>Extension points in the Office App-V package require installation at the computer level.</p>
<p>When you publish at the computer level, no prerequisite actions or redistributables are needed, and the Office 2013 package globally enables its applications to work like natively installed Office, eliminating the need for administrators to customize packages.</p></td>
</tr>
</tbody>
</table>
### How to publish an Office package
Run the following command to publish an Office package globally, wtih the bracketed value replaced by the path to the App-V package:
@ -631,8 +341,6 @@ You may want to disable specific applications in your Office App-V package. For
You may want to disable shortcuts for certain Office applications instead of unpublishing or removing the package. The following example shows how to disable shortcuts for Microsoft Access.
**To disable shortcuts for Office 2013 applications**
1. Open a Deployment Configuration File in Notepad and search for “Shortcuts”.
2. To disable certain shortcuts, delete or comment out the specific shortcuts you don’t want. You must keep the subsystem present and enabled. For example, in the example below, delete the Microsoft Access shortcuts, while keeping the subsystems &lt;shortcut&gt; &lt;/shortcut&gt; intact to disable the Microsoft Access shortcut.
@ -665,7 +373,7 @@ Many additional settings can be changed through modifying the Deployment Configu
To upgrade an Office 2013 package, use the Office Deployment Tool. To upgrade a previously deployed Office 2013 package, perform the following steps.
**How to upgrade a previously deployed Office 2013 package**
#### How to upgrade a previously deployed Office 2013 package
1. Create a new Office 2013 package through the Office Deployment Tool that uses the most recent Office 2013 application software. The most recent Office 2013 bits can always be obtained through the download stage of creating an Office 2013 App-V Package. The newly created Office 2013 package will have the most recent updates and a new Version ID. All packages created using the Office Deployment Tool have the same lineage.
@ -702,38 +410,6 @@ This section describes the requirements and options for deploying Visio 2013 and
|Create two different packages and deploy each one to a different group of users|Create and deploy the following packages:<br>A package that contains only Office—deploy to computers whose users need only Office.<br>A package that contains Office, Visio, and Project—deploy to computers whose users need all three applications.|
|Create just one package for the whole organization, or for users who share computers|Follow these steps:<br>1. Create a package that contains Office, Visio, and Project.<br>2. Deploy the package to all users.<br>3. Use [AppLocker](https://docs.microsoft.com/en-us/windows/security/threat-protection/applocker/applocker-overview) to prevent specific users from using Visio and Project.|
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Goal</th>
<th align="left">Method</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Create two different packages and deploy each one to a different group of users</p></td>
<td align="left"><p>Create and deploy the following packages:</p>
<ul>
<li><p>A package that contains only Office - deploy to computers whose users need only Office.</p></li>
<li><p>A package that contains Office, Visio, and Project - deploy to computers whose users need all three applications.</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>If you want only one package for the whole organization, or if you have users who share computers:</p></td>
<td align="left"><p>Follows these steps:</p>
<ol>
<li><p>Create a package that contains Office, Visio, and Project.</p></li>
<li><p>Deploy the package to all users.</p></li>
<li><p>Use [AppLocker](https://technet.microsoft.com/itpro/windows/keep-secure/applocker-overview) to prevent specific users from using Visio and Project.</p></li>
</ol></td>
</tr>
</tbody>
</table>
## Additional resources
### Additional resources for Office 2013 App-V Packages

16
windows/application-management/app-v/revision-heidi/appv-deploying-microsoft-office-2016-with-appv.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# Deploying Microsoft Office 2016 by Using App-V
>Applies to Windows 10, version 1607.
>Applies to: Windows 10, version 1607
Use the information in this article to use Application Virtualization (App-V) to deliver Microsoft Office 2016 as a virtualized application to computers in your organization. For information about using App-V to deliver Office 2013, see [Deploying Microsoft Office 2013 by using App-V](appv-deploying-microsoft-office-2013-with-appv.md). For information about using App-V to deliver Office 2010, see [Deploying Microsoft Office 2010 by using App-V](appv-deploying-microsoft-office-2010-with-appv.md).
@ -157,10 +157,10 @@ After you download the Office 2016 applications through the Office Deployment To
>[!NOTE]
>You can use the Office Deployment Tool to create App-V packages for Office 365 ProPlus. Creating packages for the volume-licensed versions of Office Professional Plus or Office Standard is not supported.
| Product ID | Subscription licensing |
|--------------------------------------------------|-------------------------------------------------------------|
| Office 2016 | O365ProPlusRetail |
| Office 2016 with Visio 2016 | O365ProPlusRetail<br>VisioProRetail |
| Product ID | Subscription licensing |
|---|---|
| Office 2016| O365ProPlusRetail |
| Office 2016 with Visio 2016 | O365ProPlusRetail<br>VisioProRetail |
| Office 2016 with Visio 2016 and Project 2016 | O365ProPlusRetail<br>VisioProRetail<br>ProjectProRetail |
#### How to convert the Office applications into an App-V package
@ -268,7 +268,7 @@ To manage your Office App-V packages, use the same operations as you would for a
The following steps will tell you how to enable Office plug-ins with your Office package. To use Office plug-ins, you must use the App-V Sequencer to create a separate package that only contains the plug-ins (you can't use the Office Deployment Tool to create the plug-ins package). After that, create a connection group that contains the Office package and the plug-ins package.
To enable plug-ins for Office App-V packages:
#### Enable plug-ins for Office App-V packages
1. Add a Connection Group through App-V Server, System Center Configuration Manager, or a Windows PowerShell cmdlet.
2. Sequence your plug-ins using the App-V Sequencer. Ensure that Office 2016 is installed on the computer that will be used to sequence the plug-in. We recommend that you use Office 365 ProPlus (non-virtual) on the sequencing computer when sequencing Office 2016 plug-ins.
@ -294,7 +294,7 @@ You can also disable specific applications in your Office App-V package. For exa
>[!NOTE]
>To exclude specific Office applications when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting.
#### To disable an Office 2016 application
#### Disable an Office 2016 application
1. Open a Deployment Configuration File with a text editor such as **Notepad** and search for “Applications."
2. Search for the Office application you want to disable, for example, Access 2016.
@ -324,7 +324,7 @@ You can also disable specific applications in your Office App-V package. For exa
You may want to disable shortcuts for certain Office applications instead of unpublishing or removing the package. The following example shows how to disable shortcuts for Microsoft Access.
#### To disable shortcuts for Office 2016 applications
#### Disable shortcuts for Office 2016 applications
1. Open a Deployment Configuration File in Notepad and search for “Shortcuts”.
2. To disable certain shortcuts, delete or comment out the specific shortcuts you don’t want. You must keep the subsystem present and enabled. The following example shows how to delete the Microsoft Access shortcuts while keeping the subsystems `<shortcut> </shortcut>` intact.

2
windows/application-management/app-v/revision-heidi/appv-deploying-the-appv-sequencer-and-client.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# Deploying the App-V Sequencer and configuring the client
>Applies to Windows 10, version 1607.
>Applies to: Windows 10, version 1607
The App-V Sequencer and client let administrators to virtualize and run virtual applications.

2
windows/application-management/app-v/revision-heidi/appv-deploying-the-appv-server.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# Deploying the App-V server
>Applies to Windows Server 2016
>Applies to: Windows Server 2016
You can install the Application Virtualization (App-V) server components using different deployment configurations, which are described in this topic. Before you install the server features, review the server section of [App-V security considerations](appv-security-considerations.md).

2
windows/application-management/app-v/revision-heidi/appv-deployment-checklist.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# App-V Deployment Checklist
>Applies to Windows 10, version 1607.
>Applies to: Windows 10, version 1607
This checklist outlines the recommended steps and items to consider when deploying App-V features. Use it to organize your priorites while you deploy App-V. You can copy this checklist into a spreadsheet program and customize it for your use.

2
windows/application-management/app-v/revision-heidi/appv-enable-the-app-v-desktop-client.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# Enable the App-V in-box client
>Applies to Windows 10, version 1607.
>Applies to: Windows 10, version 1607
The App-V client is the component that runs virtualized applications on user devices. Once you enable the client, users can interact with icons and file names to start virtualized applications. The client can also get virtual application content from the management server.

8
windows/application-management/app-v/revision-heidi/appv-getting-started.md
View File

@ -8,10 +8,9 @@ ms.sitesec: library
ms.prod: w10
ms.date: 04/16/2018
---
# Getting started with App-V for Windows 10
>Applies to Windows 10, version 1607.
>Applies to: Windows 10, version 1607
Microsoft Application Virtualization (App-V) for Windows 10 delivers Win32 applications to users as virtual applications. Virtual applications are installed on centrally managed servers and delivered to users as a service in real time and on an as-needed basis. Users launch virtual applications from familiar access points and interact with them as if they were installed locally.
@ -51,13 +50,8 @@ If you're new to App-V, it's a good idea to read the documentation thoroughly. B
## Other resources for this product
* [Application Virtualization (App-V) overview](appv-for-windows.md)
* [Planning for App-V](appv-planning-for-appv.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)

2
windows/application-management/app-v/revision-heidi/appv-high-level-architecture.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# High-level architecture for App-V
>Applies to Windows 10, version 1607.
>Applies to: Windows 10, version 1607
Use the following information to simplify your Microsoft Application Virtualization (App-V) deployment.

2
windows/application-management/app-v/revision-heidi/appv-install-the-management-and-reporting-databases-on-separate-computers.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services
>Applies to Windows Server 2016.
>Applies to: Windows Server 2016
Use the following procedure to install the database server and management server on different computers. The computer you plan to install the database server on must be running a supported version of Microsoft SQL or the installation will fail.

2
windows/application-management/app-v/revision-heidi/appv-install-the-management-server-on-a-standalone-computer.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# How to install the Management Server on a Standalone Computer and Connect it to the Database
>Applies to Windows Server 2016
>Applies to: Windows Server 2016
To install the management server on a standalone computer and connect it to the database, follow these steps.

2
windows/application-management/app-v/revision-heidi/appv-install-the-publishing-server-on-a-remote-computer.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# How to Install the Publishing Server on a Remote Computer
>Applies to Windows Server 2016.
>Applies to: Windows Server 2016
Use the following procedure to install the publishing server on a separate computer. Before you perform the following procedure, ensure the database and management server are available.

2
windows/application-management/app-v/revision-heidi/appv-install-the-reporting-server-on-a-standalone-computer.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# How to install the reporting server on a standalone computer and connect it to the database
>Applies to Windows Server 2016.
>Applies to: Windows Server 2016
Use the following procedure to install the reporting server on a standalone computer and connect it to the database.

4
windows/application-management/app-v/revision-heidi/appv-install-the-sequencer.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# Install the App-V Sequencer
>Applies to Windows 10, version 1607.
>Applies to: Windows 10, version 1607
Use the App-V Sequencer to convert Win32 applications into virtual packages for deployment to user devices. Those devices must be running the App-V client to allow users to interact with virtual applications.
@ -19,7 +19,7 @@ The App-V Sequencer is included in the Windows 10 Assessment and Deployment Kit
>[!NOTE]
>The computer that will run the sequencer must not have the App-V client enabled. As a best practice, choose a computer with the same hardware and software configurations as the computers that will run the virtual applications. The sequencing process is resource-intensive, so make sure the computer that will run the Sequencer has plenty of memory, a fast processor, and a fast hard drive.
To install the App-V Sequencer:
### How to install the App-V Sequencer
1. Go to [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit).
2. Select the **Get Windows ADK for Windows 10** button on the page to start the ADK installer. Make sure that **Microsoft Application Virtualization (App-V) Sequencer** is selected during the installation.

58
windows/application-management/app-v/revision-heidi/appv-planning-checklist.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# App-V Planning Checklist
>Applies to Windows 10, version 1607.
>Applies to: Windows 10, version 1607
This checklist can be used to help you plan for preparing your organization for an App-V deployment.
@ -22,64 +22,10 @@ This checklist can be used to help you plan for preparing your organization for
|![Checklist box](../images/checklistbox.gif)|Review the getting started information about App-V to gain a basic understanding of the product before beginning deployment planning.|[Getting started with App-V](appv-getting-started.md)||
|![Checklist box](../images/checklistbox.gif)|Plan for App-V deployment prerequisites and prepare your computing environment.|[App-V prerequisites](appv-prerequisites.md)||
|![Checklist box](../images/checklistbox.gif)|If you plan to use the App-V management server, plan for the required roles.|[Planning for the App-V server deployment](appv-planning-for-appv-server-deployment.md)||
|![Checklist box](../images/checklistbox.gif)|Plan for the App-V sequencer and client to create and run virtualized applications.|[Planning for the App-V Sequencer and client deployment](appv-planning-for-sequencer-and-client-deployment.md)||
|![Checklist box](../images/checklistbox.gif)|If applicable, review the options and steps for migrating from a previous version of App-V.|[Migrating to App-V from a previous version](appv-migrating-to-appv-from-a-previous-version.md)||
|![Checklist box](../images/checklistbox.gif)|Decide whether to configure App-V clients in Shared Content Store mode.|[Deploying the App-V Sequencer and configuring the client](appv-deploying-the-appv-sequencer-and-client.md)||
<table>
<colgroup>
<col width="25%" />
<col width="25%" />
<col width="25%" />
<col width="25%" />
</colgroup>
<thead>
<tr class="header">
<th align="left"></th>
<th align="left">Task</th>
<th align="left">References</th>
<th align="left">Notes</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
<td align="left"><p>Review the getting started information about App-V to gain a basic understanding of the product before beginning deployment planning.</p></td>
<td align="left"><p>[Getting started with App-V](appv-getting-started.md)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
<td align="left"><p>Plan for App-V deployment prerequisites and prepare your computing environment.</p></td>
<td align="left"><p>[App-V prerequisites](appv-prerequisites.md)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
<td align="left"><p>If you plan to use the App-V management server, plan for the required roles.</p></td>
<td align="left"><p>[Planning for the App-V server deployment](appv-planning-for-appv-server-deployment.md)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
<td align="left"><p>Plan for the App-V sequencer and client to create and run virtualized applications.</p></td>
<td align="left"><p>[Planning for the App-V Sequencer and client deployment](appv-planning-for-sequencer-and-client-deployment.md)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
<td align="left"><p>If applicable, review the options and steps for migrating from a previous version of App-V.</p></td>
<td align="left"><p>[Migrating to App-V from a previous version](appv-migrating-to-appv-from-a-previous-version.md)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
<td align="left"><p>Decide whether to configure App-V clients in Shared Content Store mode.</p></td>
<td align="left"><p>[Deploying the App-V Sequencer and configuring the client](appv-deploying-the-appv-sequencer-and-client.md)</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).

2
windows/application-management/app-v/revision-heidi/appv-planning-folder-redirection-with-appv.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# Planning to Use Folder Redirection with App-V
>Applies to Windows 10, version 1607.
>Applies to: Windows 10, version 1607
Microsoft Application Virtualization (App-V) supports the use of folder redirection, a feature that enables users and administrators to redirect the path of a folder to a new location.

2
windows/application-management/app-v/revision-heidi/appv-planning-for-appv-server-deployment.md
View File

@ -10,7 +10,7 @@ ms.date: 04/19/2017
---
# Planning for the App-V server deployment
>Applies to Windows Server 2016.
>Applies to: Windows Server 2016
The Microsoft Application Virtualization (App-V) server infrastructure consists of a set of specialized features that can be installed on one or more server computers, based on the requirements of the enterprise.

2
windows/application-management/app-v/revision-heidi/appv-planning-for-appv.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# Planning for App-V
>Applies to Windows 10, version 1607.
>Applies to: Windows 10, version 1607
Use the following information to plan to deploy App-V without disrupting your existing network or user experience.

2
windows/application-management/app-v/revision-heidi/appv-planning-for-high-availability-with-appv.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# Planning for high availability with App-V Server
>Applies to Windows 10, version 1607.
>Applies to: Windows 10, version 1607
Microsoft Application Virtualization (App-V) system configurations can take advantage of options that maintain a high available service level.

2
windows/application-management/app-v/revision-heidi/appv-planning-for-sequencer-and-client-deployment.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# Planning for the App-V Sequencer and Client Deployment
>Applies to Windows 10, version 1607.
>Applies to: Windows 10, version 1607
Before you can use App-V, you must install the App-V Sequencer and enable the App-V client. You can also the App-V shared content store, although it isn't required. The following sections will tell you how to set these up.

29
windows/application-management/app-v/revision-heidi/appv-planning-for-using-appv-with-office.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# Planning for deploying App-V with Office
>Applies to Windows 10, version 1607.
>Applies to: Windows 10, version 1607
Use the following information to plan how to deploy Office within Microsoft Application Virtualization (App-V).
@ -44,33 +44,6 @@ Before implementing Office coexistence, review the information in the following
|Office 2013|[How to use Office 2013 suites and programs (MSI deployment) on a computer running another version of Office](http://support.microsoft.com/kb/2784668)|
|Office 2010|How to use Office 2010 suites and programs on a computer running another version of Office](http://support.microsoft.com/kb/2121447)|
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Office version</th>
<th align="left">Relevant guide links</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Office 2016</p></td>
<td align="left"><p>[How to use Outlook 2016 or 2013 and an earlier version of Outlook installed on the same computer](https://support.microsoft.com/kb/2782408)</p></td>
</tr>
<tr class="even">
<td align="left"><p>Office 2013</p></td>
<td align="left"><p>[How to use Office 2013 suites and programs (MSI deployment) on a computer running another version of Office](http://support.microsoft.com/kb/2784668)</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Office 2010</p></td>
<td align="left"><p>[How to use Office 2010 suites and programs on a computer running another version of Office](http://support.microsoft.com/kb/2121447)</p></td>
</tr>
</tbody>
</table>
Once you've reviewed the relevant guide, this topic will supplement what you've learned with information about Office coexistence that's more specific to App-V deployments.
### Supported Office coexistence scenarios

2
windows/application-management/app-v/revision-heidi/appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md
View File

@ -10,7 +10,7 @@ ms.date: 04/16/2018
---
# Planning to Deploy App-V with an electronic software distribution system
>Applies to Windows 10, version 1607.
>Applies to: Windows 10, version 1607
If you are using an electronic software distribution (ESD) system to deploy App-V packages, review the following planning considerations. For information about deploying App-V with System Center Configuration Manager, see [Introduction to application management in Configuration Manager](https://technet.microsoft.com/en-us/library/gg682125.aspx#BKMK_Appv).

417
windows/application-management/app-v/revision-heidi/appv-prerequisites.md
View File

@ -72,104 +72,13 @@ The following deployment scenarios are not supported:
|64-bit ASP.NET registration||
|Windows Server Web Server Role|This role must be added to a server operating system that is supported for the Management server.|
|Web Server (IIS) Management Tools|Select **IIS Management Scripts and Tools**.|
|Web Server Role Services|Common HTTP features:<br>Static content<br>Default document<br><br>Application development:<br>ASP.NET<br>.NET Extensibility<br>ISAPI Extensions<br>ISAPI Filters<br><br>Security:<br>Windows Authentication<br>Request Filtering<br><br>Management Tools:<br>IIS Management Console|
|Web Server Role Services|Common HTTP features:<br>- Static content<br>- Default document<br><br>Application development:<br>- ASP<span></span>.NET<br>- .NET Extensibility<br>- ISAPI Extensions<br>- ISAPI Filters<br><br>Security:<br>- Windows Authentication<br>- Request Filtering<br><br>Management Tools:<br>- IIS Management Console|
|Default installation location|%PROGRAMFILES%\Microsoft Application Virtualization Server|
|Location of the Management database|SQL Server database name, SQL Server database instance name, and database name.|
|Management console and Management database permissions|A user or group that can access the Management console and database after the deployment is complete. Only these users or groups will have access to the Management console and database unless additional administrators are added by using the Management console.|
|Management console and Management database permissions|A user or group that can access the Management console and database after the deployment is complete. Only these users or groups can access the Management console and database unless the Management console is used to add additional administrators.|
|Management service website name|Name for the Management console website.|
|Management service port binding|Unique port number for the Management service. This port cannot be used by another process on the computer.|
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Prerequisites and required settings</th>
<th align="left">Details</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Supported version of SQL Server</p></td>
<td align="left"><p>For supported versions, see [App-V supported configurations](appv-supported-configurations.md).</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Windows PowerShell 3.0](http://www.microsoft.com/download/details.aspx?id=34595)</p></td>
<td align="left"><p>Installing Windows PowerShell 3.0 requires a restart.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Download and install [KB2533623](http://support.microsoft.com/kb/2533623)</p></td>
<td align="left"><p>Applies to Windows 7 only.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><p>64-bit ASP.NET registration</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><p>Windows Server Web Server Role</p></td>
<td align="left"><p>This role must be added to a server operating system that is supported for the Management server.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Web Server (IIS) Management Tools</p></td>
<td align="left"><p>Click <strong>IIS Management Scripts and Tools</strong>.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Web Server Role Services</p></td>
<td align="left"><p><strong>Common HTTP features:</strong></p>
<ul>
<li><p>Static content</p></li>
<li><p>Default document</p></li>
</ul>
<p><strong>Application development:</strong></p>
<ul>
<li><p>ASP.NET</p></li>
<li><p>.NET extensibility</p></li>
<li><p>ISAPI extensions</p></li>
<li><p>ISAPI filters</p></li>
</ul>
<p><strong>Security:</strong></p>
<ul>
<li><p>Windows authentication</p></li>
<li><p>Request filtering</p></li>
</ul>
<p><strong>Management tools:</strong></p>
<ul>
<li><p>IIS Management Console</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>Default installation location</p></td>
<td align="left"><p>%PROGRAMFILES%\Microsoft Application Virtualization Server</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Location of the Management database</p></td>
<td align="left"><p>SQL Server database name, SQL Server database instance name, and database name.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Management console and Management database permissions</p></td>
<td align="left"><p>A user or group that can access the Management console and database after the deployment is complete. Only these users or groups will have access to the Management console and database unless additional administrators are added by using the Management console.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Management service website name</p></td>
<td align="left"><p>Name for the Management console website.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Management service port binding</p></td>
<td align="left"><p>Unique port number for the Management service. This port cannot be used by another process on the computer.</p></td>
</tr>
</tbody>
</table>
>[!IMPORTANT]
>JavaScript must be enabled on the browser that opens the Web Management Console.
@ -184,63 +93,10 @@ The Management database is only required if you use the App-V Management server.
|Default installation location|%PROGRAMFILES%\Microsoft Application Virtualization Server|
|Custom SQL Server instance name (if applicable)|Format to use: **INSTANCENAME**<br>This format assumes that the installation is on the local computer.<br>If you specify the name with the format **SVR\INSTANCE**, the installation will fail.|
|Custom database name (if applicable)|Unique database name.<br>Default: AppVManagement|
|Management server location|Machine account on which the Management server is deployed.<br>Format to use: Domain\MachineAccount|
|Management server installation administrator|Account used to install the Management server.<br>Format to use: Domain\AdministratorLoginName|
|Management server location|Machine account on which the Management server is deployed.<br>Format to use: **Domain\MachineAccount**|
|Management server installation administrator|Account used to install the Management server.<br>Format to use: **Domain\AdministratorLoginName**|
|Microsoft SQL Server Service Agent|Configure the Management database computer so that the Microsoft SQL Server Agent service is restarted automatically. For instructions, see [Configure SQL Server Agent to restart services automatically](http://technet.microsoft.com/magazine/gg313742.aspx).|
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Prerequisites and required settings</th>
<th align="left">Details</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><p>[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><p>Default installation location</p></td>
<td align="left"><p>%PROGRAMFILES%\Microsoft Application Virtualization Server</p></td>
</tr>
<tr class="even">
<td align="left"><p>Custom SQL Server instance name (if applicable)</p></td>
<td align="left"><p>Format to use: <strong>INSTANCENAME</strong></p>
<p>This format assumes that the installation is on the local computer.</p>
<p>If you specify the name with the format <strong>SVR\INSTANCE</strong>, the installation will fail.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Custom database name (if applicable)</p></td>
<td align="left"><p>Unique database name.</p>
<p>Default: AppVManagement</p></td>
</tr>
<tr class="even">
<td align="left"><p>Management server location</p></td>
<td align="left"><p>Machine account on which the Management server is deployed.</p>
<p>Format to use: Domain\MachineAccount</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Management server installation administrator</p></td>
<td align="left"><p>Account used to install the Management server.</p>
<p>Format to use: Domain\AdministratorLoginName</p></td>
</tr>
<tr class="even">
<td align="left"><p>Microsoft SQL Server Service Agent</p></td>
<td align="left"><p>Configure the Management database computer so that the Microsoft SQL Server Agent service is restarted automatically. For instructions, see [Configure SQL Server Agent to restart services automatically](http://technet.microsoft.com/magazine/gg313742.aspx).</p></td>
</tr>
</tbody>
</table>
### Publishing server prerequisite software
|Prerequisites and required settings|Details|
@ -250,111 +106,12 @@ The Management database is only required if you use the App-V Management server.
|64-bit ASP.NET registration||
|Web Server role|This role must be added to a server operating system that is supported for the Management server.|
|Web Server (IIS) Management Tools|Select **IIS Management Scripts and Tools**.|
|Web Server Role Services|Common HTTP features:<br>Static content<br>Default document<br><br>Application development:<br>ASP.NET<br>.NET Extensibility<br>ISAPI Extensions<br>ISAPI Filters<br><br>Security:<br>Windows Authentication<br>Request Filtering<br><br>Management Tools:<br>IIS Management Console|
|Web Server Role Services|Common HTTP features:<br>- Static content<br>- Default document<br><br>Application development:<br>- ASP<span></span>.NET<br>- .NET Extensibility<br>- ISAPI Extensions<br>- ISAPI Filters<br><br>Security:<br>- Windows Authentication<br>- Request Filtering<br><br>Management Tools:<br>- IIS Management Console|
|Default installation location|%PROGRAMFILES%\Microsoft Application Virtualization Server|
|Management service URL|URL of the App-V Management service. This is the port with which the Publishing server communicates.<br>Management server and Publishing server are installed on the same server, use the format http://localhost:12345.<br>If the Management server and Publishing server are installed on different servers, use the format http://MyAppvServer.MyDomain.com.|
|Management service URL|URL of the App-V Management service. This is the port with which the Publishing server communicates.<br>Management server and Publishing server are installed on the same server, use the format **http://<span></span>localhost:12345**.<br>If the Management server and Publishing server are installed on different servers, use the format **http:<span></span>//MyAppvServer<span></span>.MyDomain<span></span>.com**.|
|Publishing service website name|Name for the Publishing website.|
|Publishing service port binding|Unique port number for the Publishing service. This port cannot be used by another process on the computer.|
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Prerequisites and required settings</th>
<th align="left">Details</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><p>[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><p>64-bit ASP.NET registration</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><p>Web Server role</p></td>
<td align="left"><p>This role must be added to a server operating system that is supported for the Management server.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Web Server (IIS) Management Tools</p></td>
<td align="left"><p>Click <strong>IIS Management Scripts and Tools</strong>.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Web Server Role Services</p></td>
<td align="left"><p><strong>Common HTTP reatures:</strong></p>
<ul>
<li><p>Static content</p></li>
<li><p>Default document</p></li>
</ul>
<p><strong>Application development:</strong></p>
<ul>
<li><p>ASP.NET</p></li>
<li><p>.NET extensibility</p></li>
<li><p>ISAPI extensions</p></li>
<li><p>ISAPI filters</p></li>
</ul>
<p><strong>Security:</strong></p>
<ul>
<li><p>Windows authentication</p></li>
<li><p>Request filtering</p></li>
</ul>
<p><strong>Management Tools:</strong></p>
<ul>
<li><p>IIS Management Console</p></li>
</ul></td>
</tr>
<tr class="odd">
<td align="left"><p>Default installation location</p></td>
<td align="left"><p>%PROGRAMFILES%\Microsoft Application Virtualization Server</p></td>
</tr>
<tr class="even">
<td align="left"><p>Management service URL</p></td>
<td align="left"><p>URL of the App-V Management service. This is the port with which the Publishing server communicates.</p>
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Installation architecture</th>
<th align="left">URL format</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Management server and Publishing server are installed on the same server</p></td>
<td align="left"><p>http://localhost:12345</p></td>
</tr>
<tr class="even">
<td align="left"><p>Management server and Publishing server are installed on different servers</p></td>
<td align="left"><p>http://MyAppvServer.MyDomain.com</p></td>
</tr>
</tbody>
</table>
<p> </p>
<p></p></td>
</tr>
<tr class="odd">
<td align="left"><p>Publishing service website name</p></td>
<td align="left"><p>Name for the Publishing website</p></td>
</tr>
<tr class="even">
<td align="left"><p>Publishing service port binding</p></td>
<td align="left"><p>Unique port number for the Publishing service. This port cannot be used by another process on the computer.</p></td>
</tr>
</tbody>
</table>
### Reporting server prerequisite software
|Prerequisites and required settings|Details|
@ -365,87 +122,11 @@ The Management database is only required if you use the App-V Management server.
|64-bit ASP.NET registration||
|Windows Server Web Server role|This role must be added to a server operating system that is supported for the Management server.|
|Web Server (IIS) Management Tools|Select **IIS Management Scripts and Tools**.|
|Web Server Role Services|To reduce the risk of unwanted or malicious data being sent to the Reporting server, you should restrict access to the Reporting Web Service per your corporate security policy.<br>Common HTTP features:<br>Static content<br>Default document<br><br>Application development:<br>ASP.NET<br>.NET Extensibility<br>ISAPI Extensions<br>ISAPI Filters<br><br>Security:<br>Windows Authentication<br>Request Filtering<br><br>Management Tools:<br>IIS Management Console|
|Web Server Role Services|To reduce the risk of unwanted or malicious data being sent to the Reporting server, you should restrict access to the Reporting Web Service per your corporate security policy.<br><br>Common HTTP features:<br>- Static content<br>- Default document<br><br>Application development:<br>- ASP<span></span>.NET<br>- .NET Extensibility<br>- ISAPI Extensions<br>- ISAPI Filters<br><br>Security:<br>- Windows Authentication<br>- Request Filtering<br><br>- Management Tools:<br>- IIS Management Console|
|Default installation location|%PROGRAMFILES%\Microsoft Application Virtualization Server|
|Reporting service website name|Name for the Reporting website.|
|Reporting service port binding|Unique port number for the Reporting service. This port cannot be used by another process on the computer.|
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Prerequisites and required settings</th>
<th align="left">Details</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Supported version of SQL Server</p></td>
<td align="left"><p>For supported versions, see [App-V supported configurations](appv-supported-configurations.md).</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><p>64-bit ASP.NET registration</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><p>Windows Server Web Server role</p></td>
<td align="left"><p>This role must be added to a server operating system that is supported for the Management server.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Web Server (IIS) Management Tools</p></td>
<td align="left"><p>Click <strong>IIS Management Scripts and Tools</strong>.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Web Server role services</p></td>
<td align="left"><p>To reduce the risk of unwanted or malicious data being sent to the Reporting server, you should restrict access to the Reporting Web Service per your corporate security policy.</p>
<p><strong>Common HTTP features:</strong></p>
<ul>
<li><p>Static content</p></li>
<li><p>Default document</p></li>
</ul>
<p><strong>Application development:</strong></p>
<ul>
<li><p>ASP.NET</p></li>
<li><p>.NET extensibility</p></li>
<li><p>ISAPI extensions</p></li>
<li><p>ISAPI filters</p></li>
</ul>
<p><strong>Security:</strong></p>
<ul>
<li><p>Windows authentication</p></li>
<li><p>Request filtering</p></li>
</ul>
<p><strong>Management tools:</strong></p>
<ul>
<li><p>IIS Management Console</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>Default installation location</p></td>
<td align="left"><p>%PROGRAMFILES%\Microsoft Application Virtualization Server</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Reporting service website name</p></td>
<td align="left"><p>Name for the Reporting website.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Reporting service port binding</p></td>
<td align="left"><p>Unique port number for the Reporting service. This port cannot be used by another process on the computer.</p></td>
</tr>
</tbody>
</table>
### Reporting database prerequisite software
You only require the Reporting database if you're using the App-V Reporting server.
@ -457,62 +138,10 @@ You only require the Reporting database if you're using the App-V Reporting serv
|Default installation location|%PROGRAMFILES%\Microsoft Application Virtualization Server|
|Custom SQL Server instance name (if applicable)|Format to use: **INSTANCENAME**<br>his format assumes that the installation is on the local computer.<br>If you specify the name with the format **SVR\INSTANCE**, the installation will fail.|
|Custom database name (if applicable)|Unique database name.<br>Default: AppVReporting|
|Reporting server location|The Reporting server will be deployed on this machine account.<br>Format to use: Domain\MachineAccount|
|Reporting server installation administrator|Account used to install the Reporting server.<br>Format to use: Domain\AdministratorLoginName|
|Reporting server location|The Reporting server will be deployed on this machine account.<br>Format to use: **Domain\MachineAccount**|
|Reporting server installation administrator|Account used to install the Reporting server.<br>Format to use: **Domain\AdministratorLoginName**|
|Microsoft SQL Server Service and Microsoft SQL Server Service Agent|Configure these services to be associated with user accounts that have access to query AD DS.|
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Prerequisites and required settings</th>
<th align="left">Details</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><p>[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><p>Default installation location</p></td>
<td align="left"><p>%PROGRAMFILES%\Microsoft Application Virtualization Server</p></td>
</tr>
<tr class="even">
<td align="left"><p>Custom SQL Server instance name (if applicable)</p></td>
<td align="left"><p>Format to use: <strong>INSTANCENAME</strong></p>
<p>This format assumes that the installation is on the local computer.</p>
<p>If you specify the name with the format <strong>SVR\INSTANCE</strong>, the installation will fail.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Custom database name (if applicable)</p></td>
<td align="left"><p>Unique database name.</p>
<p>Default: AppVReporting</p></td>
</tr>
<tr class="even">
<td align="left"><p>Reporting server location</p></td>
<td align="left"><p>The Reporting server will be deployed on this machine account.</p>
<p>Format to use: Domain\MachineAccount</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Reporting server installation administrator</p></td>
<td align="left"><p>Account used to install the Reporting server.</p>
<p>Format to use: Domain\AdministratorLoginName</p></td>
</tr>
<tr class="even">
<td align="left"><p>Microsoft SQL Server Service and Microsoft SQL Server Service Agent</p></td>
<td align="left"><p>Configure these services to be associated with user accounts that have access to query AD DS.</p></td>
</tr>
</tbody>
</table>
## Sequencer prerequisite software
What to know before installing the prerequisites:
@ -527,34 +156,6 @@ What to know before installing the prerequisites:
|[Windows PowerShell 3.0](http://www.microsoft.com/download/details.aspx?id=34595)|Installing Windows PowerShell 3.0 requires a restart.|
|[KB2533623](http://support.microsoft.com/kb/2533623)|Applies to Windows 7 only: download and install the KB.|
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Prerequisite</th>
<th align="left">Details</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><p>[Windows PowerShell 3.0](http://www.microsoft.com/download/details.aspx?id=34595)</p>
<p></p></td>
<td align="left"><p>Installing Windows PowerShell 3.0 requires a restart.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[KB2533623](http://support.microsoft.com/kb/2533623)</p></td>
<td align="left"><p>Applies to Windows 7 only: download and install the KB.</p></td>
</tr>
</tbody>
</table>
## Related topics
* [Planning for App-V](appv-planning-for-appv.md)

32
windows/application-management/app-v/revision-heidi/appv-reporting.md
View File

@ -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
---
# About App-V reporting
>Applies to Windows 10, version 1607.
>Applies to: Windows 10, version 1607
Application Virtualization (App-V) includes a built-in reporting feature that collects information about computers running the App-V client and virtual application package usage. You can generate reports from a centralized database with this information.
@ -238,34 +238,6 @@ You can also use the **Send-AppVClientReport** cmdlet to manually collect data.
>[!NOTE]
>If a location other than the Reporting Server is specified, the data is sent in **.xml** format with no additional processing.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">With a reporting server</th>
<th align="left">Without a reporting server</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>If you have an existing App-V reporting server, create a customized scheduled task or script. Specify that the client sends the data to the specified location at the desired frequency.</p></td>
<td align="left"><p>If you do not have an existing App-V reporting Server, use the <strong>–URL</strong> parameter to send the data to a specified share. For example:</p>
<p><code>Send-AppVClientReport –URL \\Myshare\MyData\ -DeleteOnSuccess</code></p>
<p>The previous example will send the reporting data to <strong>\\MyShare\MyData\</strong> location indicated by the <strong>-URL</strong> parameter. After the data has been sent, the cache is cleared.</p>
<div class="alert">
<strong>Note</strong>
<p>If a location other than the Reporting Server is specified, the data is sent using <strong>.xml</strong> format with no additional processing.</p>
</div>
<div>
 
</div></td>
</tr>
</tbody>
</table>
### Creating reports
To retrieve report information and create reports using App-V you must use one of the following methods:

58
windows/application-management/app-v/revision-heidi/appv-security-considerations.md
View File

@ -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 security considerations
>Applies to Windows 10, version 1607.
>Applies to: Windows 10, version 1607
This topic contains a brief overview of the accounts and groups, log files, and other security-related considerations for Microsoft Application Virtualization (App-V).
@ -43,64 +43,12 @@ A best practice for user account management is to create domain global groups an
No groups are created automatically during App-V setup. You should create the following Active Directory Domain Services global groups to manage App-V server operations.
|Group name|Details|Important notes|
|---|---|
|---|---|---|
|App-V Management Admin group|Used to manage the App-V management server. This group is created during the App-V Management Server installation.|The management console can't create a new group after installation is complete.|
|Database read/write for Management Service account|Provides read/write access to the management database. This account should be created during App-V management database installation.||
|App-V Management Service install admin account|Provides public access to schema-version table in management database. This account should be created during App-V management database installation.|This is only required if the management database is being installed separately from the service.|
|App-V Reporting Service install admin account|Public access to schema-version table in reporting database. This account should be created during the App-V reporting database installation.|This is only required if reporting database is being installed separately from the service.|
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Group name</th>
<th align="left">Details</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>App-V Management Admin group</p></td>
<td align="left"><p>Used to manage the App-V management server. This group is created during the App-V Management Server installation.</p>
<div class="alert">
<strong>Important</strong>
<p>The management console can't create a new group after installation is complete.</p>
</div>
<div>
 
</div></td>
</tr>
<tr class="even">
<td align="left"><p>Database read/write for Management Service account</p></td>
<td align="left"><p>Provides read/write access to the management database. This account should be created during App-V management database installation.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>App-V Management Service install admin account</p>
<div class="alert">
<strong>Note</strong>
<p>This is only required if the management database is being installed separately from the service.</p>
</div>
<div>
 
</div></td>
<td align="left"><p>Provides public access to schema-version table in management database. This account should be created during App-V management database installation.</p></td>
</tr>
<tr class="even">
<td align="left"><p>App-V Reporting Service install admin account</p>
<div class="alert">
<strong>Note</strong>
<p>This is only required if reporting database is being installed separately from the service.</p>
</div>
<div>
 
</div></td>
<td align="left"><p>Public access to schema-version table in reporting database. This account should be created during the App-V reporting database installation.</p></td>
</tr>
</tbody>
</table>
Consider the following additional information:
* Access to the package shares: If a share exists on the same computer as the management Server, the **Network** service requires read access to the share. In addition, each App-V client computer must have read access to the package share.

2
windows/application-management/app-v/revision-heidi/appv-sequence-a-new-application.md
View File

@ -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
---
# Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)

120
windows/application-management/app-v/revision-heidi/appv-supported-configurations.md
View File

@ -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 Supported Configurations
>Applies to Windows 10, version 1607; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; and Windows Server 2008 R2.
>Applies to: Windows 10, version 1607; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2
This topic specifies the requirements to install and run App-V in your Windows 10 environment. For information about prerequisite software such as the .NET Framework, see [App-V prerequisites](appv-prerequisites.md).
@ -58,38 +58,6 @@ The following table lists the SQL Server versions that the App-V Management data
|Microsoft SQL Server 2008 R2|SP3|32-bit or 64-bit|
<table>
<colgroup>
<col width="33%" />
<col width="33%" />
<col width="33%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">SQL Server version</th>
<th align="left">Service pack</th>
<th align="left">System architecture</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Microsoft SQL Server 2014</p></td>
<td align="left"><p></p></td>
<td align="left"><p>32-bit or 64-bit</p></td>
</tr>
<tr class="even">
<td align="left"><p>Microsoft SQL Server 2012</p></td>
<td align="left"><p>SP2</p></td>
<td align="left"><p>32-bit or 64-bit</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Microsoft SQL Server 2008 R2</p></td>
<td align="left"><p>SP3</p></td>
<td align="left"><p>32-bit or 64-bit</p></td>
</tr>
</tbody>
</table>
### Publishing server operating system requirements
The App-V Publishing server can be installed on a server that runs Windows Server 2008 R2 with SP1 or later.
@ -128,38 +96,6 @@ The following table lists the SQL Server versions that are supported for the App
|Microsoft SQL Server 2012|SP2|32-bit or 64-bit|
|Microsoft SQL Server 2008 R2|SP3|32-bit or 64-bit|
<table>
<colgroup>
<col width="33%" />
<col width="33%" />
<col width="33%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">SQL Server version</th>
<th align="left">Service pack</th>
<th align="left">System architecture</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Microsoft SQL Server 2014</p></td>
<td align="left"><p></p></td>
<td align="left"><p>32-bit or 64-bit</p></td>
</tr>
<tr class="even">
<td align="left"><p>Microsoft SQL Server 2012</p></td>
<td align="left"><p>SP2</p></td>
<td align="left"><p>32-bit or 64-bit</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Microsoft SQL Server 2008 R2</p></td>
<td align="left"><p>SP3</p></td>
<td align="left"><p>32-bit or 64-bit</p></td>
</tr>
</tbody>
</table>
## App-V client and Remote Desktop Services client requirements
With Windows 10, version 1607 and later releases, the App-V client is included with Windows 10 Enterprise and Windows 10 Education. The App-V client is no longer part of the Microsoft Desktop Optimization Pack. Before you can use the App-V client, it must be enabled, as described in [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
@ -180,58 +116,6 @@ The following table lists the operating systems that the App-V Sequencer install
|Microsoft Windows 8||32-bit and 64-bit|
|Microsoft Windows 7|SP1|32-bit and 64-bit|
<table>
<colgroup>
<col width="33%" />
<col width="33%" />
<col width="33%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Operating system</th>
<th align="left">Service pack</th>
<th align="left">System architecture</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Microsoft Windows Server 2012 R2</p></td>
<td align="left"></td>
<td align="left"><p>64-bit</p></td>
</tr>
<tr class="even">
<td align="left"><p>Microsoft Windows Server 2012</p></td>
<td align="left"><p></p></td>
<td align="left"><p>64-bit</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Microsoft Windows Server 2008 R2</p></td>
<td align="left"><p>SP1</p></td>
<td align="left"><p>64-bit</p></td>
</tr>
<tr class="even">
<td align="left"><p>Microsoft Windows 10</p></td>
<td align="left"><p></p></td>
<td align="left"><p>32-bit and 64-bit</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Microsoft Windows 8.1</p></td>
<td align="left"><p></p></td>
<td align="left"><p>32-bit and 64-bit</p></td>
</tr>
<tr class="even">
<td align="left"><p>Microsoft Windows 8</p></td>
<td align="left"><p></p></td>
<td align="left"><p>32-bit and 64-bit</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Microsoft Windows 7</p></td>
<td align="left"><p>SP1</p></td>
<td align="left"><p>32-bit and 64-bit</p></td>
</tr>
</tbody>
</table>
### Sequencer hardware requirements
See the Windows or Windows Server documentation for the hardware requirements.