mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 10:23:37 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into jd-sandbox
This commit is contained in:
jdeckerMS
@ -36,6 +36,131 @@
|
||||
## [Configure devices without MDM](configure-devices-without-mdm.md)
|
||||
## [Windows 10 servicing options](introduction-to-windows-10-servicing.md)
|
||||
## [Application development for Windows as a service](application-development-for-windows-as-a-service.md)
|
||||
## [Application Virtualization for Windows (App-V)](appv-for-windows.md)
|
||||
### [Getting Started with App-V](appv-getting-started.md)
|
||||
#### [About App-V](appv-about-appv.md)
|
||||
##### [Release Notes for App-V](appv-release-notes-for-appv-for-windows.md)
|
||||
#### [Evaluating App-V](appv-evaluating-appv.md)
|
||||
#### [High Level Architecture for App-V](appv-high-level-architecture.md)
|
||||
#### [Accessibility for App-V](appv-accessibility.md)
|
||||
### [Planning for App-V](appv-planning-for-appv.md)
|
||||
#### [Preparing Your Environment for App-V](appv-preparing-your-environment.md)
|
||||
##### [App-V Prerequisites](appv-prerequisites.md)
|
||||
##### [App-V Security Considerations](appv-security-considerations.md)
|
||||
#### [Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
##### [App-V Supported Configurations](appv-supported-configurations.md)
|
||||
##### [App-V Capacity Planning](appv-capacity-planning.md)
|
||||
##### [Planning for High Availability with App-V](appv-planning-for-high-availability-with-appv.md)
|
||||
##### [Planning to Deploy App-V with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md)
|
||||
##### [Planning for the App-V Server Deployment](appv-planning-for-appv-server-deployment.md)
|
||||
##### [Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md)
|
||||
##### [Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md)
|
||||
##### [Planning for Using App-V with Office](appv-planning-for-using-appv-with-office.md)
|
||||
##### [Planning to Use Folder Redirection with App-V](appv-planning-folder-redirection-with-appv.md)
|
||||
#### [App-V Planning Checklist](appv-planning-checklist.md)
|
||||
### [Deploying App-V](appv-deploying-appv.md)
|
||||
#### [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
##### [About Client Configuration Settings](appv-client-configuration-settings.md)
|
||||
##### [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)
|
||||
##### [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)
|
||||
##### [How to Install the Sequencer](appv-install-the-sequencer.md)
|
||||
##### [How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md)
|
||||
#### [Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
##### [How to Deploy the App-V Server](appv-deploy-the-appv-server.md)
|
||||
##### [How to Deploy the App-V Server Using a Script](appv-deploy-the-appv-server-with-a-script.md)
|
||||
##### [How to Deploy the App-V Databases by Using SQL Scripts](appv-deploy-appv-databases-with-sql-scripts.md)
|
||||
##### [How to Install the Publishing Server on a Remote Computer](appv-install-the-publishing-server-on-a-remote-computer.md)
|
||||
##### [How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services](appv-install-the-management-and-reporting-databases-on-separate-computers.md)
|
||||
##### [How to install the Management Server on a Standalone Computer and Connect it to the Database ](appv-install-the-management-server-on-a-standalone-computer.md)
|
||||
##### [About App-V Reporting](appv-reporting.md)
|
||||
##### [How to install the Reporting Server on a Standalone Computer and Connect it to the Database](appv-install-the-reporting-server-on-a-standalone-computer.md)
|
||||
#### [App-V Deployment Checklist](appv-deployment-checklist.md)
|
||||
#### [Deploying Microsoft Office 2013 by Using App-V](appv-deploying-microsoft-office-2013-with-appv.md)
|
||||
#### [Deploying Microsoft Office 2010 by Using App-V](appv-deploying-microsoft-office-2010-wth-appv.md)
|
||||
### [Operations for App-V](appv-operations.md)
|
||||
#### [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md)
|
||||
##### [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md)
|
||||
##### [How to Modify an Existing Virtual Application Package](appv-modify-an-existing-virtual-application-package.md)
|
||||
##### [How to Create and Use a Project Template](appv-create-and-use-a-project-template.md)
|
||||
##### [How to Create a Package Accelerator](appv-create-a-package-accelerator.md)
|
||||
##### [How to Create a Virtual Application Package Using an App-V Package Accelerator](appv-create-a-virtual-application-package-package-accelerator.md)
|
||||
#### [Administering App-V Virtual Applications by Using the Management Console](appv-administering-virtual-applications-with-the-management-console.md)
|
||||
##### [About App-V Dynamic Configuration](appv-dynamic-configuration.md)
|
||||
##### [How to Connect to the Management Console ](appv-connect-to-the-management-console.md)
|
||||
##### [How to Add or Upgrade Packages by Using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md)
|
||||
##### [How to Configure Access to Packages by Using the Management Console ](appv-configure-access-to-packages-with-the-management-console.md)
|
||||
##### [How to Publish a Package by Using the Management Console ](appv-publish-a-packages-with-the-management-console.md)
|
||||
##### [How to Delete a Package in the Management Console ](appv-delete-a-package-with-the-management-console.md)
|
||||
##### [How to Add or Remove an Administrator by Using the Management Console](appv-add-or-remove-an-administrator-with-the-management-console.md)
|
||||
##### [How to Register and Unregister a Publishing Server by Using the Management Console](appv-register-and-unregister-a-publishing-server-with-the-management-console.md)
|
||||
##### [How to Create a Custom Configuration File by Using the App-V Management Console](appv-create-a-custom-configuration-file-with-the-management-console.md)
|
||||
##### [How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console](appv-transfer-access-and-configurations-to-another-version-of-a-package-with-the-management-console.md)
|
||||
##### [How to Customize Virtual Applications Extensions for a Specific AD Group by Using the Management Console](appv-customize-virtual-application-extensions-with-the-management-console.md)
|
||||
##### [How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console ](appv-view-and-configure-applications-and-default-virtual-application-extensions-with-the-management-console.md)
|
||||
#### [Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
##### [About the Connection Group Virtual Environment](appv-connection-group-virtual-environment.md)
|
||||
##### [About the Connection Group File](appv-connection-group-file.md)
|
||||
##### [How to Create a Connection Group](appv-create-a-connection-group.md)
|
||||
##### [How to Create a Connection Group with User-Published and Globally Published Packages](appv-create-a-connection-group-with-user-published-and-globally-published-packages.md)
|
||||
##### [How to Delete a Connection Group](appv-delete-a-connection-group.md)
|
||||
##### [How to Publish a Connection Group](appv-publish-a-connection-group.md)
|
||||
##### [How to Make a Connection Group Ignore the Package Version](appv-configure-connection-groups-to-ignore-the-package-version.md)
|
||||
##### [How to Allow Only Administrators to Enable Connection Groups](appv-allow-administrators-to-enable-connection-groups.md)
|
||||
#### [Deploying App-V Packages by Using Electronic Software Distribution (ESD)](appv-deploying-packages-with-electronic-software-distribution-solutions.md)
|
||||
##### [How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md)
|
||||
##### [How to Enable Only Administrators to Publish Packages by Using an ESD](appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md)
|
||||
#### [Using the App-V Client Management Console](appv-using-the-client-management-console.md)
|
||||
##### [How to Access the Client Management Console](appv-accessing-the-client-management-console.md)
|
||||
##### [How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server ](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md)
|
||||
#### [Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)
|
||||
##### [How to Convert a Package Created in a Previous Version of App-V](appv-convert-a-package-created-in-a-previous-version-of-appv.md)
|
||||
#### [Maintaining App-V](appv-maintaining-appv.md)
|
||||
##### [How to Move the App-V Server to Another Computer](appv-move-the-appv-server-to-another-computer.md)
|
||||
#### [Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
|
||||
##### [How to Load the PowerShell Cmdlets and Get Cmdlet Help ](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md)
|
||||
##### [How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md)
|
||||
##### [How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md)
|
||||
##### [How to Modify Client Configuration by Using PowerShell](appv-modify-client-configuration-with-powershell.md)
|
||||
##### [How to Apply the User Configuration File by Using PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)
|
||||
##### [How to Apply the Deployment Configuration File by Using PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)
|
||||
##### [How to Sequence a Package by Using PowerShell ](appv-sequence-a-package-with-powershell.md)
|
||||
##### [How to Create a Package Accelerator by Using PowerShell](appv-create-a-package-accelerator-with-powershell.md)
|
||||
##### [How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)
|
||||
##### [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md)
|
||||
### [Troubleshooting App-V](appv-troubleshooting.md)
|
||||
### [Technical Reference for App-V](appv-technical-reference.md)
|
||||
#### [Performance Guidance for Application Virtualization](appv-performance-guidance.md)
|
||||
#### [Application Publishing and Client Interaction](appv-application-publishing-and-client-interaction.md)
|
||||
#### [Viewing App-V Server Publishing Metadata](appv-viewing-appv-server-publishing-metadata.md)
|
||||
#### [Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md)
|
||||
## [User Experience Virtualization (UE-V)](uev-for-windows.md)
|
||||
### [Get Started with UE-V](uev-getting-started.md)
|
||||
#### [What's New in UE-V for Windows 10, version 1607](uev-whats-new-in-uev-for-windows.md)
|
||||
#### [User Experience Virtualization Release Notes](uev-release-notes-1607.md)
|
||||
#### [Upgrade to UE-V for Windows 10](uev-upgrade-uev-from-previous-releases.md)
|
||||
### [Prepare a UE-V Deployment](uev-prepare-for-deployment.md)
|
||||
#### [Deploy Required UE-V Features](uev-deploy-required-features.md)
|
||||
#### [Deploy UE-V for use with Custom Applications](uev-deploy-uev-for-custom-applications.md)
|
||||
### [Administering UE-V](uev-administering-uev.md)
|
||||
#### [Manage Configurations for UE-V](uev-manage-configurations.md)
|
||||
##### [Configuring UE-V with Group Policy Objects](uev-configuring-uev-with-group-policy-objects.md)
|
||||
##### [Configuring UE-V with System Center Configuration Manager](uev-configuring-uev-with-system-center-configuration-manager.md)
|
||||
##### [Administering UE-V with Windows PowerShell and WMI](uev-administering-uev-with-windows-powershell-and-wmi.md)
|
||||
###### [Managing the UE-V Service and Packages with Windows PowerShell and WMI](uev-managing-uev-agent-and-packages-with-windows-powershell-and-wmi.md)
|
||||
###### [Managing UE-V Settings Location Templates Using Windows PowerShell and WMI](uev-managing-settings-location-templates-using-windows-powershell-and-wmi.md)
|
||||
#### [Working with Custom UE-V Templates and the UE-V Template Generator](uev-working-with-custom-templates-and-the-uev-generator.md)
|
||||
#### [Manage Administrative Backup and Restore in UE-V](uev-manage-administrative-backup-and-restore.md)
|
||||
#### [Changing the Frequency of UE-V Scheduled Tasks](uev-changing-the-frequency-of-scheduled-tasks.md)
|
||||
#### [Migrating UE-V Settings Packages](uev-migrating-settings-packages.md)
|
||||
#### [Using UE-V with Application Virtualization Applications](uev-using-uev-with-application-virtualization-applications.md)
|
||||
### [Troubleshooting UE-V](uev-troubleshooting.md)
|
||||
### [Technical Reference for UE-V](uev-technical-reference.md)
|
||||
#### [Sync Methods for UE-V](uev-sync-methods.md)
|
||||
#### [Sync Trigger Events for UE-V](uev-sync-trigger-events.md)
|
||||
#### [Synchronizing Microsoft Office with UE-V](uev-synchronizing-microsoft-office-with-uev.md)
|
||||
#### [Application Template Schema Reference for UE-V](uev-application-template-schema-reference.md)
|
||||
#### [Accessibility for UE-V](uev-accessibility.md)
|
||||
#### [Security Considerations for UE-V](uev-security-considerations.md)
|
||||
## [Windows Store for Business](windows-store-for-business.md)
|
||||
### [Sign up and get started](sign-up-windows-store-for-business-overview.md)
|
||||
####[Windows Store for Business overview](windows-store-for-business-overview.md)
|
||||
|
||||
524
windows/manage/appv-about-appv.md
Normal file
524
windows/manage/appv-about-appv.md
Normal file
@ -0,0 +1,524 @@
|
||||
---
|
||||
title: About App-V (Windows 10)
|
||||
description: About App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# About App-V
|
||||
|
||||
|
||||
Use the following sections to review information about significant changes that apply to Application Virtualization (App-V):
|
||||
|
||||
[App-V software prerequisites and supported configurations](#bkmk-51-prereq-configs)
|
||||
|
||||
[Migrating to App-V](#bkmk-migrate-to-51)
|
||||
|
||||
[What’s New in App-V](#bkmk-whatsnew)
|
||||
|
||||
[App-V support for Windows 10](#bkmk-win10support)
|
||||
|
||||
[App-V Management Console Changes](#bkmk-mgmtconsole)
|
||||
|
||||
[Sequencer Improvements](#bkmk-seqimprove)
|
||||
|
||||
[Improvements to Package Converter](#bkmk-pkgconvimprove)
|
||||
|
||||
[Support for multiple scripts on a single event trigger](#bkmk-supmultscripts)
|
||||
|
||||
[Hardcoded path to installation folder is redirected to virtual file system root](#bkmk-hardcodepath)
|
||||
|
||||
## <a href="" id="bkmk-51-prereq-configs"></a>App-V software prerequisites and supported configurations
|
||||
|
||||
|
||||
See the following links for the App-V software prerequisites and supported configurations.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Links to prerequisites and supported configurations</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[App-V Prerequisites](appv-prerequisites.md)</p></td>
|
||||
<td align="left"><p>Prerequisite software that you must install before starting the App-V installation</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[App-V Supported Configurations](appv-supported-configurations.md)</p></td>
|
||||
<td align="left"><p>Supported operating systems and hardware requirements for the App-V Server, Sequencer, and Client components</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Support for using Configuration Manager with App-V:** App-V supports System Center 2012 R2 Configuration Manager SP1. See [Planning for App-V Integration with Configuration Manager](https://technet.microsoft.com/library/jj822982.aspx) for information about integrating your App-V environment with Configuration Manager and Configuration Manager.
|
||||
|
||||
## <a href="" id="bkmk-migrate-to-51"></a>Migrating to App-V
|
||||
|
||||
|
||||
Use the following information to upgrade to App-V from earlier versions. See [Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md) for more information.
|
||||
|
||||
### Before you start the upgrade
|
||||
|
||||
Review the following information before you start the upgrade:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Items to review before upgrading</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Components to upgrade, in any order</p></td>
|
||||
<td align="left"><ol>
|
||||
<li><p>App-V Server</p></li>
|
||||
<li><p>Sequencer</p></li>
|
||||
<li><p>App-V Client or App-V Remote Desktop Services (RDS) Client</p></li>
|
||||
</ol>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>Prior to App-V 5.0 SP2, the Client Management User Interface (UI) was provided with the App-V Client installation. For App-V 5.0 SP2 installations (or later), you can use the Client Management UI by downloading from [Application Virtualization 5.0 Client UI Application](http://www.microsoft.com/download/details.aspx?id=41186).</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Upgrading from App-V 4.x</p></td>
|
||||
<td align="left"><p>You must first upgrade to App-V 5.0. You cannot upgrade directly from App-V 4.x to App-V. For more information, see:</p>
|
||||
<ul>
|
||||
<li><p>“Differences between App-V 4.6 and App-V 5.0” in [About App-V 5.0](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/about-app-v-50.md)</p></li>
|
||||
<li><p>[Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md)</p></li>
|
||||
</ul>
|
||||
<p></p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Upgrading from App-V 5.0 or later</p></td>
|
||||
<td align="left"><p>You can upgrade to App-V directly from any of the following versions:</p>
|
||||
<ul>
|
||||
<li><p>App-V 5.0</p></li>
|
||||
<li><p>App-V 5.0 SP1</p></li>
|
||||
<li><p>App-V 5.0 SP2</p></li>
|
||||
<li><p>App-V 5.0 SP3</p></li>
|
||||
</ul>
|
||||
<p>To upgrade to App-V, follow the steps in the remaining sections of this topic.</p>
|
||||
<p>Packages and connection groups will continue to work with App-V as they currently do.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### <a href="" id="bkmk-steps-upgrd-infrastruc"></a>Steps to upgrade the App-V infrastructure
|
||||
|
||||
Complete the following steps to upgrade each component of the App-V infrastructure to App-V. The following order is only a suggestion; you may upgrade components in any order.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Step</th>
|
||||
<th align="left">For more information</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Step 1: Upgrade the App-V Server.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>If you are not using the App-V Server, skip this step and go to the next step.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
</div></td>
|
||||
<td align="left"><p>Follow these steps:</p>
|
||||
<ol>
|
||||
<li><p>Do one of the following, depending on the method you are using to upgrade the Management database and/or Reporting database:</p>
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Database upgrade method</th>
|
||||
<th align="left">Step</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows Installer</p></td>
|
||||
<td align="left"><p>Skip this step and go to step 2, “If you are upgrading the App-V Server...”</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>SQL scripts</p></td>
|
||||
<td align="left"><p>Follow the steps in [How to Deploy the App-V Databases by Using SQL Scripts](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/how-to-deploy-the-app-v-databases-by-using-sql-scripts).</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<li><p>If you are upgrading the App-V Server from App-V 5.0 SP1 Hotfix Package 3 or later, complete the steps in section [Check registry keys after installing the App-V 5.0 SP3 Server](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/check-reg-key-svr).</p></li>
|
||||
<li><p>Follow the steps in [How to Deploy the App-V Server](appv-deploy-the-appv-server.md)</p></li>
|
||||
<p> </p></li>
|
||||
</ol></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Step 2: Upgrade the App-V Sequencer.</p></td>
|
||||
<td align="left"><p>See [How to Install the Sequencer](appv-install-the-sequencer.md).</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Step 3: Enabled the App-V Client.</p></td>
|
||||
<td align="left"><p>See [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Converting packages created using a prior version of App-V
|
||||
|
||||
Use the package converter utility to upgrade virtual application packages created using versions of App-V prior to App-V 5.0. The package converter uses PowerShell to convert packages and can help automate the process if you have many packages that require conversion.
|
||||
|
||||
**Note**
|
||||
App-V packages are exactly the same as App-V 5.0 packages. There has been no change in the package format between the versions and so there is no need to convert App-V 5.0 packages to App-V packages.
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-whatsnew"></a>What’s New in App-V
|
||||
|
||||
|
||||
These sections are for users who are already familiar with App-V and want to know what has changed in App-V. If you are not already familiar with App-V, you should start by reading [Planning for App-V](appv-planning-for-appv.md).
|
||||
|
||||
### <a href="" id="bkmk-win10support"></a>App-V support for Windows 10
|
||||
|
||||
The following table lists the Windows 10 support for App-V. Windows 10 is not supported in versions of App-V prior to App-V.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Component</th>
|
||||
<th align="left">App-V</th>
|
||||
<th align="left">App-V 5.0</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V Client</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V RDS Client</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V Sequencer</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### <a href="" id="bkmk-mgmtconsole"></a>App-V Management Console Changes
|
||||
|
||||
This section compares the App-V Management Console’s current and previous functionality.
|
||||
|
||||
### Silverlight is no longer required
|
||||
|
||||
The Management Console UI no longer requires Silverlight. The 5.1 Management Console is built on HTML5 and Javascript.
|
||||
|
||||
### Notifications and messages are displayed individually in a dialog box
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">New in App-V</th>
|
||||
<th align="left">Prior to App-V</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Number of messages indicator:</strong></p>
|
||||
<p>On the title bar of the App-V Management Console, a number is now displayed next to a flag icon to indicate the number of messages that are waiting to be read.</p></td>
|
||||
<td align="left"><p>You could see only one message or error at a time, and you were unable to determine how many messages there were.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Message appearance:</strong></p>
|
||||
<ul>
|
||||
<li><p>Messages that require user input appear in a separate dialog box that displays on top of the current page that you were viewing, and require a response before you can dismiss them.</p></li>
|
||||
<li><p>Messages and errors appear in a list, with one beneath the other.</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p>You could see only one message or error at a time.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Dismissing messages:</strong></p>
|
||||
<p>Use the <strong>Dismiss All</strong> link to dismiss all messages and errors at one time, or dismiss them one at a time.</p></td>
|
||||
<td align="left"><p>You could dismiss messages and errors only one at a time.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Console pages are now separate URLs
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">New in App-V</th>
|
||||
<th align="left">Prior to App-V</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Each page in the console has a different URL, which enables you to bookmark specific pages for quick access in the future.</p>
|
||||
<p>The number that appears in some URLs indicates the specific package. These numbers are unique.</p></td>
|
||||
<td align="left"><p>All console pages are accessed through the same URL.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### New, separate CONNECTION GROUPS page and menu option
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">New in App-V</th>
|
||||
<th align="left">Prior to App-V</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>The CONNECTION GROUPS page is now part of the main menu, at the same level as the PACKAGES page.</p></td>
|
||||
<td align="left"><p>To open the CONNECTION GROUPS page, you navigate through the PACKAGES page.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Menu options for packages have changed
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">New in App-V</th>
|
||||
<th align="left">Prior to App-V</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>The following options are now buttons that appear at the bottom of the PACKAGES page:</p>
|
||||
<ul>
|
||||
<li><p>Add or Upgrade</p></li>
|
||||
<li><p>Publish</p></li>
|
||||
<li><p>Unpublish</p></li>
|
||||
<li><p>Delete</p></li>
|
||||
</ul>
|
||||
<p>The following options will still appear when you right-click a package to open the drop-down context menu:</p>
|
||||
<ul>
|
||||
<li><p>Publish</p></li>
|
||||
<li><p>Unpublish</p></li>
|
||||
<li><p>Edit AD Access</p></li>
|
||||
<li><p>Edit Deployment Config</p></li>
|
||||
<li><p>Transfer deployment configuration from…</p></li>
|
||||
<li><p>Transfer access and configuration from…</p></li>
|
||||
<li><p>Delete</p></li>
|
||||
</ul>
|
||||
<p>When you click <strong>Delete</strong> to remove a package, a dialog box opens and asks you to confirm that you want to delete the package.</p></td>
|
||||
<td align="left"><p>The <strong>Add or Upgrade</strong> option was a button at the top right of the PACKAGES page.</p>
|
||||
<p>The <strong>Publish</strong>, <strong>Unpublish</strong>, and <strong>Delete</strong> options were available only if you right-clicked a package name in the packages list.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>The following package operations are now buttons on the package details page for each package:</p>
|
||||
<ul>
|
||||
<li><p>Transfer (drop-down menu with the following options):</p>
|
||||
<ul>
|
||||
<li><p>Transfer deployment configuration from…</p></li>
|
||||
<li><p>Transfer access and configuration from…</p></li>
|
||||
</ul></li>
|
||||
<li><p>Edit (connection groups and AD Access)</p></li>
|
||||
<li><p>Unpublish</p></li>
|
||||
<li><p>Delete</p></li>
|
||||
<li><p>Edit Default Configuration</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p>These package options were available only if you right-clicked a package name in the packages list.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Icons in left pane have new colors and text
|
||||
|
||||
The colors of the icons in the left pane have been changed, and text added, to make the icons consistent with other Microsoft products.
|
||||
|
||||
### Overview page has been removed
|
||||
|
||||
In the left pane of the Management Console, the OVERVIEW menu option and its associated OVERVIEW page have been removed.
|
||||
|
||||
### <a href="" id="bkmk-seqimprove"></a>Sequencer Improvements
|
||||
|
||||
The following improvements have been made to the package editor in the App-V Sequencer.
|
||||
|
||||
### Import and export the manifest file
|
||||
|
||||
You can import and export the AppxManifest.xml file. To export the manifest file, select the **Advanced** tab and in the Manifest File box, click **Export...**. You can make changes to the manifest file, such as removing shell extensions or editing file type associations.
|
||||
|
||||
After you make your changes, click **Import...** and select the file you edited. After you successfully import it back in, the manifest file is immediately updated within the package editor.
|
||||
|
||||
**Caution**
|
||||
When you import the file, your changes are validated against the XML schema. If the file is not valid, you will receive an error. Be aware that it is possible to import a file that is validated against the XML schema, but that might still fail to run for other reasons.
|
||||
|
||||
|
||||
|
||||
### Addition of Windows 10 to operating systems list
|
||||
|
||||
In the Deployment tab, Windows 10 32-bit and Windows 10-64 bit have been added to the list of operating systems for which you can sequence a package. If you select **Any Operating System**, Windows 10 is automatically included among the operating systems that the sequenced package will support.
|
||||
|
||||
### Current path displays at bottom of virtual registry editor
|
||||
|
||||
In the Virtual Registry tab, the path now displays at the bottom of the virtual registry editor, which enables you to determine the currently selected key. Previously, you had to scroll through the registry tree to find the currently selected key.
|
||||
|
||||
### <a href="" id="combined--find-and-replace--dialog-box-and-shortcut-keys-added-in-virtual-registry-editor"></a>Combined “find and replace” dialog box and shortcut keys added in virtual registry editor
|
||||
|
||||
In the virtual registry editor, shortcut keys have been added for the Find option (Ctrl+F), and a dialog box that combines the “find” and “replace” tasks has been added to enable you to find and replace values and data. To access this combined dialog box, select a key and do one of the following:
|
||||
|
||||
- Press **Ctrl+H**
|
||||
|
||||
- Right-click a key and select **Replace**.
|
||||
|
||||
- Select **View** > **Virtual Registry** > **Replace**.
|
||||
|
||||
Previously, the “Replace” dialog box did not exist, and you had to make changes manually.
|
||||
|
||||
### Rename registry keys and package files successfully
|
||||
|
||||
You can rename virtual registry keys and files without experiencing Sequencer issues. Previously, the Sequencer stopped working if you tried to rename a key.
|
||||
|
||||
### Import and export virtual registry keys
|
||||
|
||||
You can import and export virtual registry keys. To import a key, right-click the node under which to import the key, navigate to the key you want to import, and then click **Import**. To export a key, right-click the key and select **Export**.
|
||||
|
||||
### Import a directory into the virtual file system
|
||||
|
||||
You can import a directory into the VFS. To import a directory, click the **Package Files** tab, and then click **View** > **Virtual File System** > **Import Directory**. If you try to import a directory that contains files that are already in the VFS, the import fails, and an explanatory message is displayed. Prior to App-V, you could not import directories.
|
||||
|
||||
### Import or export a VFS file without having to delete and then add it back to the package
|
||||
|
||||
You can import files to or export files from the VFS without having to delete the file and then add it back to the package. For example, you might use this feature to export a change log to a local drive, edit the file using an external editor, and then re-import the file into the VFS.
|
||||
|
||||
To export a file, select the **Package Files** tab, right-click the file in the VFS, click **Export**, and choose an export location from which you can make your edits.
|
||||
|
||||
To import a file, select the **Package Files** tab and right-click the file that you had exported. Browse to the file that you edited, and then click **Import**. The imported file will overwrite the existing file.
|
||||
|
||||
After you import a file, you must save the package by clicking **File** > **Save**.
|
||||
|
||||
### Menu for adding a package file has moved
|
||||
|
||||
The menu option for adding a package file has been moved. To find the Add option, select the **Package Files** tab, then click **View** > **Virtual File System** > **Add File**. Previously, you right-clicked a folder under the VFS node, and chose **Add File**.
|
||||
|
||||
### Virtual registry node expands MACHINE and USER hives by default
|
||||
|
||||
When you open the virtual registry, the MACHINE and USER hives are shown below the top-level REGISTRY node. Previously, you had to expand the REGISTRY node to show the hives beneath.
|
||||
|
||||
### Enable or disable Browser Helper Objects
|
||||
|
||||
You can enable or disable Browser Helper Objects by selecting a new check box, Enable Browser Helper Objects, on the Advanced tab of the Sequencer user interface. If Browser Helper Objects:
|
||||
|
||||
- Exist in the package and are enabled, the check box is selected by default.
|
||||
|
||||
- Exist in the package and are disabled, the check box is clear by default.
|
||||
|
||||
- Exist in the package, with one or more enabled and one or more disabled, the check box is set to indeterminate by default.
|
||||
|
||||
- Do not exist in the package, the check box is disabled.
|
||||
|
||||
### <a href="" id="bkmk-pkgconvimprove"></a>Improvements to Package Converter
|
||||
|
||||
You can now use the package converter to convert App-V 4.6 packages that contain scripts, and registry information and scripts from source .osd files are now included in package converter output.
|
||||
|
||||
For more information including examples, see [Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md).
|
||||
|
||||
### <a href="" id="bkmk-supmultscripts"></a>Support for multiple scripts on a single event trigger
|
||||
|
||||
App-V supports the use of multiple scripts on a single event trigger for App-V packages, including packages that you are converting from App-V 4.6 to App-V 5.0 or later. To enable the use of multiple scripts, App-V uses a script launcher application, named ScriptRunner.exe, which is installed as part of the App-V client installation.
|
||||
|
||||
For more information, including a list of event triggers and the context under which scripts can be run, see the Scripts section in [About App-V Dynamic Configuration](appv-dynamic-configuration.md).
|
||||
|
||||
### <a href="" id="bkmk-hardcodepath"></a>Hardcoded path to installation folder is redirected to virtual file system root
|
||||
|
||||
When you convert packages from App-V 4.6 to 5.1, the App-V package can access the hardcoded drive that you were required to use when you created 4.6 packages. The drive letter will be the drive you selected as the installation drive on the 4.6 sequencing machine. (The default drive letter is Q:\\.)
|
||||
|
||||
Previously, the 4.6 root folder was not recognized and could not be accessed by App-V 5.0 packages. App-V packages can access hardcoded files by their full path or can programmatically enumerate files under the App-V 4.6 installation root.
|
||||
|
||||
**Technical Details:** The App-V package converter will save the App-V 4.6 installation root folder and short folder names in the FilesystemMetadata.xml file in the Filesystem element. When the App-V client creates the virtual process, it will map requests from the App-V 4.6 installation root to the virtual file system root.
|
||||
|
||||
## How to Get MDOP Technologies
|
||||
|
||||
|
||||
App-V is a part of the Microsoft Desktop Optimization Pack (MDOP). MDOP is part of Microsoft Software Assurance. For more information about Microsoft Software Assurance and acquiring MDOP, see [How Do I Get MDOP](http://go.microsoft.com/fwlink/?LinkId=322049).
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Release Notes for App-V](appv-release-notes-for-appv-for-windows.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
169
windows/manage/appv-accessibility.md
Normal file
169
windows/manage/appv-accessibility.md
Normal file
@ -0,0 +1,169 @@
|
||||
---
|
||||
title: Accessibility for App-V (Windows 10)
|
||||
description: Accessibility for App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Accessibility for App-V
|
||||
|
||||
|
||||
Microsoft is committed to making its products and services easier for everyone to use. This section provides information about features and services that make this product and its corresponding documentation more accessible for people with disabilities.
|
||||
|
||||
## Keyboard Shortcuts for the App-V Management Server
|
||||
|
||||
|
||||
Following are the keyboard Shortcuts for the App-V Management Server:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">To do this</th>
|
||||
<th align="left">Press</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Close a dialog box.</p></td>
|
||||
<td align="left"><p>Esc</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Perform the default action of a dialog box.</p></td>
|
||||
<td align="left"><p>Enter</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Refresh the current page of the App-V client console.</p></td>
|
||||
<td align="left"><p>F5</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Keyboard Shortcuts for the App-V Sequencer
|
||||
|
||||
|
||||
Following are the keyboard shortcuts for the Virtual Registry tab in the package editor in the App-V Sequencer:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">To do this</th>
|
||||
<th align="left">Press</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Open the Find dialog box.</p></td>
|
||||
<td align="left"><p>CTRL + F</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Open the Replace dialog box.</p></td>
|
||||
<td align="left"><p>CTRL + H</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Access Any Command with a Few Keystrokes
|
||||
|
||||
**Important**
|
||||
The information in this section only applies to the App-V sequencer. For specific information about the App-V server, see the Keyboard Shortcuts for the App-V Management Server section of this document.
|
||||
|
||||
|
||||
|
||||
Access keys let you quickly use a command by pressing a few keys. You can get to most commands by using two keystrokes. To use an access key:
|
||||
|
||||
1. Press ALT.
|
||||
|
||||
An underline appears beneath the keyboard shortcut for each feature that is available in the current view.
|
||||
|
||||
2. Press the letter underlined in the keyboard shortcut for the feature that you want to use.
|
||||
|
||||
**Note**
|
||||
To cancel the action that you are taking and hide the keyboard shortcuts, press ALT.
|
||||
|
||||
|
||||
|
||||
## Documentation in Alternative Formats
|
||||
|
||||
|
||||
If you have difficulty reading or handling printed materials, you can obtain the documentation for many Microsoft products in more accessible formats. You can view an index of accessible product documentation on the Microsoft Accessibility website. In addition, you can obtain additional Microsoft publications from Learning Ally (formerly Recording for the Blind & Dyslexic, Inc.). Learning Ally distributes these documents to registered, eligible members of their distribution service.
|
||||
|
||||
For information about the availability of Microsoft product documentation and books from Microsoft Press, contact:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Learning Ally (formerly Recording for the Blind & Dyslexic, Inc.)</strong></p>
|
||||
<p>20 Roszel Road</p>
|
||||
<p>Princeton, NJ 08540</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Telephone number from within the United States:</p></td>
|
||||
<td align="left"><p>(800) 221-4792</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Telephone number from outside the United States and Canada:</p></td>
|
||||
<td align="left"><p>(609) 452-0606</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Fax:</p></td>
|
||||
<td align="left"><p>(609) 987-8116</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[http://www.learningally.org/](http://go.microsoft.com/fwlink/?linkid=239)</p></td>
|
||||
<td align="left"><p>Web addresses can change, so you might be unable to connect to the website or sites mentioned here.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Customer Service for People with Hearing Impairments
|
||||
|
||||
|
||||
If you are deaf or hard-of-hearing, complete access to Microsoft product and customer services is available through a text telephone (TTY/TDD) service:
|
||||
|
||||
- For customer service, contact Microsoft Sales Information Center at (800) 892-5234 between 6:30 AM and 5:30 PM Pacific Time, Monday through Friday, excluding holidays.
|
||||
|
||||
- For technical assistance in the United States, contact Microsoft Product Support Services at (800) 892-5234 between 6:00 AM and 6:00 PM Pacific Time, Monday through Friday, excluding holidays. In Canada, dial (905) 568-9641 between 8:00 AM and 8:00 PM Eastern Time, Monday through Friday, excluding holidays.
|
||||
|
||||
Microsoft Support Services are subject to the prices, terms, and conditions in place at the time the service is used.
|
||||
|
||||
## For More Information
|
||||
|
||||
|
||||
For more information about how accessible technology for computers helps to improve the lives of people with disabilities, see the [Microsoft Accessibility website](http://go.microsoft.com/fwlink/?linkid=8431).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Getting Started with App-V](appv-getting-started.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,26 @@
|
||||
---
|
||||
title: How to access the client management console (Windows 10)
|
||||
description: How to access the client management console
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to access the client management console
|
||||
|
||||
Use the App-V client management console to manage packages on the computer running the App-V client.
|
||||
|
||||
> [!NOTE]
|
||||
To perform all of the actions available using the client management console, you must have administrative access on the computer running the App-V client.
|
||||
|
||||
The client management console is available from the [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=41186).
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
@ -0,0 +1,45 @@
|
||||
---
|
||||
title: How to Add or Remove an Administrator by Using the Management Console (Windows 10)
|
||||
description: How to Add or Remove an Administrator by Using the Management Console
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Add or Remove an Administrator by Using the Management Console
|
||||
|
||||
|
||||
Use the following procedures to add or remove an administrator on the Microsoft Application Virtualization (App-V) server.
|
||||
|
||||
**To add an administrator using the Management Console**
|
||||
|
||||
1. Open the Microsoft Application Virtualization (App-V) Management Console and click **Administrators** in the navigation pane. The navigation pane displays a list of Access Directory (AD) users and groups that currently have administrative access to the Microsoft Application Virtualization (App-V) server.
|
||||
|
||||
2. To add a new administrator, click **Add Administrator** Type the name of the administrator that you want to add in the **Active Directory Name** field. Ensure you provide the associated user account domain name. For example, **Domain** \\ **UserName**.
|
||||
|
||||
3. Select the account that you want to add and click **Add**. The new account is displayed in the list of server administrators.
|
||||
|
||||
**To remove an administrator using the Management Console**
|
||||
|
||||
1. Open the Microsoft Application Virtualization (App-V) Management Console and click **Administrators** in the navigation pane. The navigation pane displays a list of AD users and groups that currently have administrative access to the Microsoft Application Virtualization (App-V) server.
|
||||
|
||||
2. Right-click the account to be removed from the list of administrators and select **Remove**.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,54 @@
|
||||
---
|
||||
title: How to Add or Upgrade Packages by Using the Management Console (Windows 10)
|
||||
description: How to Add or Upgrade Packages by Using the Management Console
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Add or Upgrade Packages by Using the Management Console
|
||||
|
||||
|
||||
You can the following procedure to add or upgrade a package to the App-V Management Console. To upgrade a package that already exists in the Management Console, use the following steps and import the upgraded package using the same package **Name**.
|
||||
|
||||
**To add a package to the Management Console**
|
||||
|
||||
1. Click the **Packages** tab in the navigation pane of the Management Console display.
|
||||
|
||||
The console displays the list of packages that have been added to the server along with status information about each package. When a package is selected, detailed information about the package is displayed in the **PACKAGES** pane.
|
||||
|
||||
Click the **Ungrouped** drop-down list box and specify how the packages are to be displayed in the console. You can also click the associated column header to sort the packages.
|
||||
|
||||
2. To specify the package you want to add, click **Add or Upgrade Packages**.
|
||||
|
||||
3. Type the full path to the package that you want to add. Use the UNC or HTTP path format, for example **\\\\servername\\sharename\\foldername\\packagename.appv** or **http://server.1234/file.appv**, and then click **Add**.
|
||||
|
||||
**Important**
|
||||
You must select a package with the **.appv** file name extension.
|
||||
|
||||
|
||||
|
||||
4. The page displays the status message **Adding <Packagename>**. Click **IMPORT STATUS** to check the status of a package that you have imported.
|
||||
|
||||
Click **OK** to add the package and close the **Add Package** page. If there was an error during the import, click **Detail** on the **Package Import** page for more information. The newly added package is now available in the **PACKAGES** pane.
|
||||
|
||||
5. Click **Close** to close the **Add or Upgrade Packages** page.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
138
windows/manage/appv-administering-appv-with-powershell.md
Normal file
138
windows/manage/appv-administering-appv-with-powershell.md
Normal file
@ -0,0 +1,138 @@
|
||||
---
|
||||
title: Administering App-V by Using PowerShell (Windows 10)
|
||||
description: Administering App-V by Using PowerShell
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Administering App-V by Using PowerShell
|
||||
|
||||
|
||||
Microsoft Application Virtualization (App-V) provides Windows PowerShell cmdlets, which can help administrators perform various App-V tasks. The following sections provide more information about using PowerShell with App-V.
|
||||
|
||||
## How to administer App-V by using PowerShell
|
||||
|
||||
|
||||
Use the following PowerShell procedures to perform various App-V tasks.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Name</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[How to Load the PowerShell Cmdlets and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md)</p></td>
|
||||
<td align="left"><p>Describes how to install the PowerShell cmdlets and find cmdlet help and examples.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to manage the client package lifecycle on a stand-alone computer using PowerShell.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to manage connection groups using PowerShell.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[How to Modify Client Configuration by Using PowerShell](appv-modify-client-configuration-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to modify the client using PowerShell.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[How to Apply the User Configuration File by Using PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to apply a user configuration file using PowerShell.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[How to Apply the Deployment Configuration File by Using PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to apply a deployment configuration file using PowerShell.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[How to Sequence a Package by Using PowerShell](appv-sequence-a-package-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to create a new package using PowerShell.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[How to Create a Package Accelerator by Using PowerShell](appv-create-a-package-accelerator-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to create a package accelerator using PowerShell. You can use package accelerators automatically sequence large, complex applications.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to enable the computer running the App-V to send reporting information.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to take an array of account names and to convert each of them to the corresponding SID in standard and hexadecimal formats.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Important**
|
||||
Make sure that any script you execute with your App-V packages matches the execution policy that you have configured for PowerShell.
|
||||
|
||||
|
||||
|
||||
## PowerShell Error Handling
|
||||
|
||||
|
||||
Use the following table for information about App-V PowerShell error handling.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Event</th>
|
||||
<th align="left">Action</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Using the RollbackOnError attribute with embedded scripts</p></td>
|
||||
<td align="left"><p>When you use the <strong>RollbackOnError</strong> attribute with embedded scripts, the attribute is ignored for the following events:</p>
|
||||
<ul>
|
||||
<li><p>Removing a package</p></li>
|
||||
<li><p>Unpublishing a package</p></li>
|
||||
<li><p>Terminating a virtual environment</p></li>
|
||||
<li><p>Terminating a process</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Package name contains <strong>$</strong></p></td>
|
||||
<td align="left"><p>If a package name contains the character ( <strong>$</strong> ), you must use a single-quote ( <strong>‘</strong> ), for example,</p>
|
||||
<p><strong>Add-AppvClientPackage ‘Contoso$App.appv’</strong></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,113 @@
|
||||
---
|
||||
title: Administering App-V Virtual Applications by Using the Management Console (Windows 10)
|
||||
description: Administering App-V Virtual Applications by Using the Management Console
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Administering App-V Virtual Applications by Using the Management Console
|
||||
|
||||
|
||||
Use the Microsoft Application Virtualization (App-V) management server to manage packages, connection groups, and package access in your environment. The server publishes application icons, shortcuts, and file type associations to authorized computers that run the App-V client. One or more management servers typically share a common data store for configuration and package information.
|
||||
|
||||
The management server uses Active Directory Domain Services (AD DS) groups to manage user authorization and has SQL Server installed to manage the database and data store.
|
||||
|
||||
Because the management servers stream applications to end users on demand, these servers are ideally suited for system configurations that have reliable, high-bandwidth LANs. The management server consists of the following components:
|
||||
|
||||
- Management Server – Use the management server to manage packages and connection groups.
|
||||
|
||||
- Publishing Server – Use the publishing server to deploy packages to computers that run the App-V client.
|
||||
|
||||
- Management Database - Use the management database to manage the package access and to publish the server’s synchronization with the management server.
|
||||
|
||||
## Management Console tasks
|
||||
|
||||
|
||||
The most common tasks that you can perform with the App-V Management console are:
|
||||
|
||||
- [How to Connect to the Management Console](appv-connect-to-the-management-console.md)
|
||||
|
||||
- [How to Add or Upgrade Packages by Using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md)
|
||||
|
||||
- [How to Configure Access to Packages by Using the Management Console](appv-configure-access-to-packages-with-the-management-console.md)
|
||||
|
||||
- [How to Publish a Package by Using the Management Console](appv-publish-a-packages-with-the-management-console.md)
|
||||
|
||||
- [How to Delete a Package in the Management Console](appv-delete-a-package-with-the-management-console.md)
|
||||
|
||||
- [How to Add or Remove an Administrator by Using the Management Console](appv-add-or-remove-an-administrator-with-the-management-console.md)
|
||||
|
||||
- [How to Register and Unregister a Publishing Server by Using the Management Console](appv-register-and-unregister-a-publishing-server-with-the-management-console.md)
|
||||
|
||||
- [How to Create a Custom Configuration File by Using the App-V Management Console](appv-create-a-custom-configuration-file-with-the-management-console.md)
|
||||
|
||||
- [How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console](appv-transfer-access-and-configurations-to-another-version-of-a-package-with-the-management-console.md)
|
||||
|
||||
- [How to Customize Virtual Applications Extensions for a Specific AD Group by Using the Management Console](appv-customize-virtual-application-extensions-with-the-management-console.md)
|
||||
|
||||
- [How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console](appv-view-and-configure-applications-and-default-virtual-application-extensions-with-the-management-console.md)
|
||||
|
||||
The main elements of the App-V Management Console are:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Management Console tab</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Packages tab</p></td>
|
||||
<td align="left"><p>Use the <strong>PACKAGES</strong> tab to add or upgrade packages.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Connection Groups tab</p></td>
|
||||
<td align="left"><p>Use the <strong>CONNECTION GROUPS</strong> tab to manage connection groups.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Servers tab</p></td>
|
||||
<td align="left"><p>Use the <strong>SERVERS</strong> tab to register a new server.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Administrators tab</p></td>
|
||||
<td align="left"><p>Use the <strong>ADMINISTRATORS</strong> tab to register, add, or remove administrators in your App-V environment.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Important**
|
||||
JavaScript must be enabled on the browser that opens the Web Management Console.
|
||||
|
||||
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## <a href="" id="other-resources-for-this-app-v-5-1-deployment-"></a>Other resources for this App-V deployment
|
||||
|
||||
|
||||
- [Application Virtualization (App-V) overview](appv-for-windows.md)
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,70 @@
|
||||
---
|
||||
title: How to Allow Only Administrators to Enable Connection Groups (Windows 10)
|
||||
description: How to Allow Only Administrators to Enable Connection Groups
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Allow Only Administrators to Enable Connection Groups
|
||||
|
||||
|
||||
You can configure the App-V client so that only administrators (not end users) can enable or disable connection groups. In earlier versions of App-V, you could not prevent end users from performing these tasks.
|
||||
|
||||
**Note**
|
||||
**This feature is supported starting in App-V 5.0 SP3.**
|
||||
|
||||
|
||||
|
||||
Use one of the following methods to allow only administrators to enable or disable connection groups.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Method</th>
|
||||
<th align="left">Steps</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Group Policy setting</p></td>
|
||||
<td align="left"><p>Enable the “Require publish as administrator” Group Policy setting, which is located in the following Group Policy Object node:</p>
|
||||
<p><strong>Computer Configuration > Policies > Administrative Templates > System > App-V > Publishing</strong></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>PowerShell cmdlet</p></td>
|
||||
<td align="left"><p>Run the <strong>Set-AppvClientConfiguration</strong> cmdlet with the <strong>–RequirePublishAsAdmin</strong> parameter.</p>
|
||||
<p>Parameter values:</p>
|
||||
<ul>
|
||||
<li><p>0 - False</p></li>
|
||||
<li><p>1 - True</p></li>
|
||||
</ul>
|
||||
<p><strong>Example:</strong>: Set-AppvClientConfiguration –RequirePublishAsAdmin1</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
1291
windows/manage/appv-application-publishing-and-client-interaction.md
Normal file
1291
windows/manage/appv-application-publishing-and-client-interaction.md
Normal file
File diff suppressed because it is too large
Load Diff
@ -0,0 +1,48 @@
|
||||
---
|
||||
title: How to Apply the Deployment Configuration File by Using PowerShell (Windows 10)
|
||||
description: How to Apply the Deployment Configuration File by Using PowerShell
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Apply the Deployment Configuration File by Using PowerShell
|
||||
|
||||
|
||||
The dynamic deployment configuration file is applied when a package is added or set to a computer running the App-V client before the package has been published. The file configures the default settings for package for all users on the computer running the App-V client. This section describes the steps used to use a deployment configuration file. The procedure is based on the following example and assumes the following package and configuration files exist on a computer:
|
||||
|
||||
**c:\\Packages\\Contoso\\MyApp.appv**
|
||||
|
||||
**c:\\Packages\\Contoso\\DynamicConfigurations\\deploymentconfig.xml**
|
||||
|
||||
**To Apply the Deployment Configuration File Using PowerShell**
|
||||
|
||||
- To specify a new default set of configurations for all users who will run the package on a specific computer, using a PowerShell console type the following:
|
||||
|
||||
**Add-AppVClientPackage –Path c:\\Packages\\Contoso\\MyApp.appv -DynamicDeploymentConfiguration c:\\Packages\\Contoso\\DynamicConfigurations\\deploymentconfig.xml**
|
||||
|
||||
**Note**
|
||||
This command captures the resulting object into $pkg. If the package is already present on the computer, the **Set-AppVclientPackage** cmdlet can be used to apply the deployment configuration document:
|
||||
|
||||
**Set-AppVClientPackage –Name Myapp –Path c:\\Packages\\Contoso\\MyApp.appv -DynamicDeploymentConfiguration c:\\Packages\\Contoso\\DynamicConfigurations\\deploymentconfig.xml**
|
||||
|
||||
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,45 @@
|
||||
---
|
||||
title: How to Apply the User Configuration File by Using PowerShell (Windows 10)
|
||||
description: How to Apply the User Configuration File by Using PowerShell
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Apply the User Configuration File by Using PowerShell
|
||||
|
||||
|
||||
The dynamic user configuration file is applied when a package is published to a specific user and determines how the package will run.
|
||||
|
||||
Use the following procedure to specify a user-specific configuration file. The following procedure is based on the example:
|
||||
|
||||
**c:\\Packages\\Contoso\\MyApp.appv**
|
||||
|
||||
**To apply a user Configuration file**
|
||||
|
||||
1. To add the package to the computer using the PowerShell console type the following command:
|
||||
|
||||
**Add-AppVClientPackage c:\\Packages\\Contoso\\MyApp.appv**.
|
||||
|
||||
2. Use the following command to publish the package to the user and specify the updated the dynamic user configuration file:
|
||||
|
||||
**Publish-AppVClientPackage $pkg –DynamicUserConfigurationPath c:\\Packages\\Contoso\\config.xml**
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
958
windows/manage/appv-capacity-planning.md
Normal file
958
windows/manage/appv-capacity-planning.md
Normal file
@ -0,0 +1,958 @@
|
||||
---
|
||||
title: App-V Capacity Planning (Windows 10)
|
||||
description: App-V Capacity Planning
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# App-V Capacity Planning
|
||||
|
||||
|
||||
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.
|
||||
|
||||
**Important**
|
||||
Use the information in this section only as a general guide for planning your App-V deployment. Your system capacity requirements will depend on the specific details of your hardware and application environment. Additionally, the performance numbers displayed in this document are examples and your results may vary.
|
||||
|
||||
|
||||
|
||||
## Determine the Project Scope
|
||||
|
||||
|
||||
Before you design the App-V infrastructure, you must determine the project’s scope. The scope consists of determining which applications will be available virtually and to also identify the target users, and their locations. This information will help determine what type of App-V infrastructure should be implemented. Decisions about the scope of the project must be based on the specific needs of your organization.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Task</th>
|
||||
<th align="left">More Information</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Determine Application Scope</p></td>
|
||||
<td align="left"><p>Depending on the applications to be virtualized, the App-V infrastructure can be set up in different ways. The first task is to define what applications you want to virtualize.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Determine Location Scope</p></td>
|
||||
<td align="left"><p>Location scope refers to the physical locations (for example, enterprise-wide or a specific geographic location) where you plan to run the virtualized applications. It can also refer to the user population (for example, a single department) who will run the virtual applications. You should obtain a network map that includes the connection paths as well as available bandwidth to each location and the number of users using virtualized applications and the WAN link speed.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Determine Which App-V Infrastructure is Required
|
||||
|
||||
|
||||
**Important**
|
||||
Both of the following models require the App-V client to be installed on the computer where you plan to run virtual applications.
|
||||
|
||||
You can also manage your App-V environment using an Electronic Software Distribution (ESD) solution such as Microsoft Systems Center Configuration Manager. For more information see [How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md).
|
||||
|
||||
|
||||
|
||||
- **Standalone Model** - The standalone model allows virtual applications to be Windows Installer-enabled for distribution without streaming. App-V in Standalone Mode consists of the sequencer and the client; no additional components are required. Applications are prepared for virtualization using a process called sequencing. For more information see, [Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md). The stand-alone model is recommended for the following scenarios:
|
||||
|
||||
- With disconnected remote users who cannot connect to the App-V infrastructure.
|
||||
|
||||
- When you are running a software management system, such as Configuration Manager 2012.
|
||||
|
||||
- When network bandwidth limitations inhibit electronic software distribution.
|
||||
|
||||
- **Full Infrastructure Model** - The full infrastructure model provides for software distribution, management, and reporting capabilities; it also includes the streaming of applications across the network. The App-V Full Infrastructure Model consists of one or more App-V management servers. The Management Server can be used to publish applications to all clients. The publishing process places the virtual application icons and shortcuts on the target computer. It can also stream applications to local users. For more information about installing the management server see, [Planning for the App-V Server Deployment](appv-planning-for-appv-server-deployment.md). The full infrastructure model is recommended for the following scenarios:
|
||||
|
||||
**Important**
|
||||
The App-V full infrastructure model requires Microsoft SQL Server to store configuration data. For more information see [App-V Supported Configurations](appv-supported-configurations.md).
|
||||
|
||||
|
||||
|
||||
- When you want to use the Management Server to publish the application to target computers.
|
||||
|
||||
- For rapid provisioning of applications to target computers.
|
||||
|
||||
- When you want to use App-V reporting.
|
||||
|
||||
## End-to-end Server Sizing Guidance
|
||||
|
||||
|
||||
The following section provides information about end-to-end App-V sizing and planning. For more specific information, refer to the subsequent sections.
|
||||
|
||||
**Note**
|
||||
Round trip response time on the client is the time taken by the computer running the App-V client to receive a successful notification from the publishing server. Round trip response time on the publishing server is the time taken by the computer running the publishing server to receive a successful package metadata update from the management server.
|
||||
|
||||
|
||||
|
||||
- 20,000 clients can target a single publishing server to obtain the package refreshes in an acceptable round trip time. (<3 seconds)
|
||||
|
||||
- A single management server can support up to 50 publishing servers for package metadata refreshes in an acceptable round trip time. (<5 seconds)
|
||||
|
||||
## <a href="" id="---------app-v-5-1-management-server-capacity-planning-recommendations"></a> App-V Management Server Capacity Planning Recommendations
|
||||
|
||||
|
||||
The App-V publishing servers require the management server for package refresh requests and package refresh responses. The management server then sends the information to the management database to retrieve information. For more information about App-V management server supported configurations see [App-V Supported Configurations](appv-supported-configurations.md).
|
||||
|
||||
**Note**
|
||||
The default refresh time on the App-V publishing server is ten minutes.
|
||||
|
||||
|
||||
|
||||
When multiple simultaneous publishing servers contact a single management server for package metadata refreshes, the following three factors influence the round trip response time on the publishing server:
|
||||
|
||||
1. Number of publishing servers making simultaneous requests.
|
||||
|
||||
2. Number of connection groups configured on the management server.
|
||||
|
||||
3. Number of access groups configured on the management server.
|
||||
|
||||
The following table displays more information about each factor that impacts round trip time.
|
||||
|
||||
**Note**
|
||||
Round trip response time is the time taken by the computer running the App-V publishing server to receive a successful package metadata update from the management server.
|
||||
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Factors impacting round trip response time</th>
|
||||
<th align="left">More Information</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>The number of publishing servers simultaneously requesting package metadata refreshes.</p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>A single management server can respond to up to 320 publishing servers requesting publishing metadata simultaneously.</p></li>
|
||||
<li><p>Round trip response time for 320 pub servers is ~40 seconds.</p></li>
|
||||
<li><p>For <50 publishing servers requesting metadata simultaneously, the round trip response time is <5 seconds.</p></li>
|
||||
<li><p>From 50 to 320 publishing servers, the response time increases linearly (approximately 2x).</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>The number of connection groups configured on the management server.</p>
|
||||
<p></p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>For up to 100 connection groups, there is no significant change in the round trip response time on the publishing server.</p></li>
|
||||
<li><p>For 100 - 400 connection groups, there is a minor linear increase in the round trip response time.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>The number of access groups configured on the management server.</p>
|
||||
<p></p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>For up to 40 access groups, there is a linear (approximately 3x) increase in the round trip response time on the publishing server.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
The following table displays sample values for each of the previous factors. In each variation, 120 packages are refreshed from the App-Vmanagement server.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Scenario</th>
|
||||
<th align="left">Variation</th>
|
||||
<th align="left">Number of connection groups</th>
|
||||
<th align="left">Number of access groups</th>
|
||||
<th align="left">Number of publishing servers</th>
|
||||
<th align="left">Network connection type publishing server / management server</th>
|
||||
<th align="left">Round trip response time on the publishing server (in seconds)</th>
|
||||
<th align="left">CPU utilization on management server</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Publishing servers simultaneously contacting management server for publishing metadata.</p></td>
|
||||
<td align="left"><p>Number of publishing servers</p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>0</p></li>
|
||||
<li><p>0</p></li>
|
||||
<li><p>0</p></li>
|
||||
<li><p>0</p></li>
|
||||
<li><p>0</p></li>
|
||||
<li><p>0</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>1</p></li>
|
||||
<li><p>1</p></li>
|
||||
<li><p>1</p></li>
|
||||
<li><p>1</p></li>
|
||||
<li><p>1</p></li>
|
||||
<li><p>1</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>50</p></li>
|
||||
<li><p>100</p></li>
|
||||
<li><p>200</p></li>
|
||||
<li><p>300</p></li>
|
||||
<li><p>315</p></li>
|
||||
<li><p>320</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>5</p></li>
|
||||
<li><p>10</p></li>
|
||||
<li><p>19</p></li>
|
||||
<li><p>32</p></li>
|
||||
<li><p>30</p></li>
|
||||
<li><p>37</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>17</p></li>
|
||||
<li><p>17</p></li>
|
||||
<li><p>17</p></li>
|
||||
<li><p>15</p></li>
|
||||
<li><p>17</p></li>
|
||||
<li><p>15</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Publishing metadata contains connection groups</p></td>
|
||||
<td align="left"><p>Number of connection groups</p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>10</p></li>
|
||||
<li><p>50</p></li>
|
||||
<li><p>100</p></li>
|
||||
<li><p>150</p></li>
|
||||
<li><p>300</p></li>
|
||||
<li><p>400</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>1</p></li>
|
||||
<li><p>1</p></li>
|
||||
<li><p>1</p></li>
|
||||
<li><p>1</p></li>
|
||||
<li><p>1</p></li>
|
||||
<li><p>1</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>100</p></li>
|
||||
<li><p>100</p></li>
|
||||
<li><p>100</p></li>
|
||||
<li><p>100</p></li>
|
||||
<li><p>100</p></li>
|
||||
<li><p>100</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>10</p></li>
|
||||
<li><p>11</p></li>
|
||||
<li><p>11</p></li>
|
||||
<li><p>16</p></li>
|
||||
<li><p>22</p></li>
|
||||
<li><p>25</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>17</p></li>
|
||||
<li><p>19</p></li>
|
||||
<li><p>22</p></li>
|
||||
<li><p>19</p></li>
|
||||
<li><p>20</p></li>
|
||||
<li><p>20</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Publishing metadata contains access groups</p></td>
|
||||
<td align="left"><p>Number of access groups</p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>0</p></li>
|
||||
<li><p>0</p></li>
|
||||
<li><p>0</p></li>
|
||||
<li><p>0</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>1</p></li>
|
||||
<li><p>10</p></li>
|
||||
<li><p>20</p></li>
|
||||
<li><p>40</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>100</p></li>
|
||||
<li><p>100</p></li>
|
||||
<li><p>100</p></li>
|
||||
<li><p>100</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>10</p></li>
|
||||
<li><p>43</p></li>
|
||||
<li><p>153</p></li>
|
||||
<li><p>535</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>17</p></li>
|
||||
<li><p>26</p></li>
|
||||
<li><p>24</p></li>
|
||||
<li><p>24</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
The CPU utilization of the computer running the management server is around 25% irrespective of the number of publishing servers targeting it. The Microsoft SQL Server database transactions/sec, batch requests/sec and user connections are identical irrespective of the number of publishing servers. For example: Transactions/sec is ~30, batch requests ~200, and user connects ~6.
|
||||
|
||||
Using a geographically distributed deployment, where the management server & publishing servers utilize a slow link network between them, the round trip response time on the publishing servers is within acceptable time limits (<5 seconds), even for 100 simultaneous requests on a single management server.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Scenario</th>
|
||||
<th align="left">Variation</th>
|
||||
<th align="left">Number of connection groups</th>
|
||||
<th align="left">Number of access groups</th>
|
||||
<th align="left">Number of publishing servers</th>
|
||||
<th align="left">Network connection type publishing server / management server</th>
|
||||
<th align="left">Round trip response time on the publishing server (in seconds)</th>
|
||||
<th align="left">CPU utilization on management server</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Network connection between the publishing server and management server</p></td>
|
||||
<td align="left"><p>1.5 Mbps Slow link Network</p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>0</p></li>
|
||||
<li><p>0</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>1</p></li>
|
||||
<li><p>1</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>50</p></li>
|
||||
<li><p>100</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>1.5Mbps Cable DSL</p></li>
|
||||
<li><p>1.5Mbps Cable DSL</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>4</p></li>
|
||||
<li><p>5</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>1</p></li>
|
||||
<li><p>2</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Network connection between the publishing server and management server</p></td>
|
||||
<td align="left"><p>LAN / WIFI Network</p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>0</p></li>
|
||||
<li><p>0</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>1</p></li>
|
||||
<li><p>1</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>100</p></li>
|
||||
<li><p>200</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>Wifi</p></li>
|
||||
<li><p>Wifi</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>11</p></li>
|
||||
<li><p>20</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>15</p></li>
|
||||
<li><p>17</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
Whether the management server and publishing servers are connected over a slow link network, or a high speed network, the management server can handle approximately 15,000 package refresh requests in 30 minutes.
|
||||
|
||||
## <a href="" id="---------app-v-5-1-reporting-server-capacity-planning-recommendations"></a> App-V Reporting Server Capacity Planning Recommendations
|
||||
|
||||
|
||||
App-V clients send reporting data to the reporting server. The reporting server then records the information in the Microsoft SQL Server database and returns a successful notification back to the computer running App-V client. For more information about App-V Reporting Server supported configurations see [App-V Supported Configurations](appv-supported-configurations.md).
|
||||
|
||||
**Note**
|
||||
Round trip response time is the time taken by the computer running the App-V client to send the reporting information to the reporting server and receive a successful notification from the reporting server.
|
||||
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Scenario</th>
|
||||
<th align="left">Summary</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Multiple App-V clients send reporting information to the reporting server simultaneously.</p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>Round trip response time from the reporting server is 2.6 seconds for 500 clients.</p></li>
|
||||
<li><p>Round trip response time from the reporting server is 5.65 seconds for 1000 clients.</p></li>
|
||||
<li><p>Round trip response time increases linearly depending on number of clients.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Requests per second processed by the reporting server.</p>
|
||||
<p></p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>A single reporting server and a single database, can process a maximum of 139 requests per second. The average is 121 requests/second.</p></li>
|
||||
<li><p>Using two reporting servers reporting to the same Microsoft SQL Server database, the average requests/second is similar to a single reporting server = ~127, with a max of 278 requests/second.</p></li>
|
||||
<li><p>A single reporting server can process 500 concurrent/active connections.</p></li>
|
||||
<li><p>A single reporting server can process a maximum 1500 concurrent connections.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Reporting Database.</p>
|
||||
<p></p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>Lock contention on the computer running Microsoft SQL Server is the limiting factor for requests/second.</p></li>
|
||||
<li><p>Throughput and response time are independent of database size.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Calculating random delay**:
|
||||
|
||||
The random delay specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between **0** and **ReportingRandomDelay** and will wait the specified duration before sending data.
|
||||
|
||||
Random delay = 4 \* number of clients / average requests per second.
|
||||
|
||||
Example: For 500 clients, with 120 requests per second, the Random delay is, 4 \* 500 / 120 = ~17 minutes.
|
||||
|
||||
## <a href="" id="---------app-v-5-1-publishing-server-capacity-planning-recommendations"></a> App-V Publishing Server Capacity Planning Recommendations
|
||||
|
||||
|
||||
Computers running the App-V client connect to the App-V publishing server to send a publishing refresh request and to receive a response. Round trip response time is measured on the computer running the App-V client. Processor time is measured on the publishing server. For more information about App-V Publishing Server supported configurations see [App-V Supported Configurations](appv-supported-configurations.md).
|
||||
|
||||
**Important**
|
||||
The following list displays the main factors to consider when setting up the App-V publishing server:
|
||||
|
||||
- The number of clients connecting simultaneously to a single publishing server.
|
||||
|
||||
- The number of packages in each refresh.
|
||||
|
||||
- The available network bandwidth in your environment between the client and the App-V publishing server.
|
||||
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Scenario</th>
|
||||
<th align="left">Summary</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Multiple App-V clients connect to a single publishing server simultaneously.</p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>A publishing server running dual core processors can respond to at most 5000 clients requesting a refresh simultaneously.</p></li>
|
||||
<li><p>For 5000-10000 clients, the publishing server requires a minimum quad core.</p></li>
|
||||
<li><p>For 10000-20000 clients, the publishing server should have dual quad cores for more efficient response times.</p></li>
|
||||
<li><p>A publishing server with a quad core can refresh up to 10000 packages within 3 seconds. (Supporting 10000 simultaneous clients)</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Number of packages in each refresh.</p>
|
||||
<p></p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>Increasing number of packages will increase response time by ~40% (up to 1000 packages).</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Network between the App-V client and the publishing server.</p>
|
||||
<p></p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>Across a slow network (1.5 Mbps bandwidth), there is a 97% increase in response time compared to LAN (up to 1000 users).</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Note**
|
||||
The publishing server CPU usage is always high during the time interval when it has to process simultaneous requests (>90% in most cases). The publishing server can handle ~1500 client requests in 1 second.
|
||||
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Scenario</th>
|
||||
<th align="left">Variation</th>
|
||||
<th align="left">Number of App-V clients</th>
|
||||
<th align="left">Number of packages</th>
|
||||
<th align="left">Processor configuration on the publishing server</th>
|
||||
<th align="left">Network connection type publishing server / App-V client</th>
|
||||
<th align="left">Round trip time on the App-V client (in seconds)</th>
|
||||
<th align="left">CPU utilization on publishing server (in %)</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V client sends publishing refresh request & receives response, each request containing 120 packages</p></td>
|
||||
<td align="left"><p>Number of clients</p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>100</p></li>
|
||||
<li><p>1000</p></li>
|
||||
<li><p>5000</p></li>
|
||||
<li><p>10000</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>120</p></li>
|
||||
<li><p>120</p></li>
|
||||
<li><p>120</p></li>
|
||||
<li><p>120</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>Dual Core</p></li>
|
||||
<li><p>Dual Core</p></li>
|
||||
<li><p>Quad Core</p></li>
|
||||
<li><p>Quad Core</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>1</p></li>
|
||||
<li><p>2</p></li>
|
||||
<li><p>2</p></li>
|
||||
<li><p>3</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>100</p></li>
|
||||
<li><p>99</p></li>
|
||||
<li><p>89</p></li>
|
||||
<li><p>77</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Multiple packages in each refresh</p></td>
|
||||
<td align="left"><p>Number of packages</p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>1000</p></li>
|
||||
<li><p>1000</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>500</p></li>
|
||||
<li><p>1000</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>Quad Core</p></li>
|
||||
<li><p>Quad Core</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>2</p></li>
|
||||
<li><p>3</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>92</p></li>
|
||||
<li><p>91</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Network between client and publishing server</p></td>
|
||||
<td align="left"><p>1.5 Mbps Slow link network</p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>100</p></li>
|
||||
<li><p>500</p></li>
|
||||
<li><p>1000</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>120</p></li>
|
||||
<li><p>120</p></li>
|
||||
<li><p>120</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>Quad Core</p></li>
|
||||
<li><p>Quad Core</p></li>
|
||||
<li><p>Quad Core</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>1.5 Mbps Intra-Continental Network</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>3</p></li>
|
||||
<li><p>10 (with 0.2% failure rate)</p></li>
|
||||
<li><p>17 (with 1% failure rate)</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## <a href="" id="---------app-v-5-1-streaming-capacity-planning-recommendations"></a> App-V Streaming Capacity Planning Recommendations
|
||||
|
||||
|
||||
Computers running the App-V client stream the virtual application package from the streaming server. Round trip response time is measured on the computer running the App-V client, and is the time taken to stream the entire package.
|
||||
|
||||
**Important**
|
||||
The following list identifies the main factors to consider when setting up the App-V streaming server:
|
||||
|
||||
- The number of clients streaming application packages simultaneously from a single streaming server.
|
||||
|
||||
- The size of the package being streamed.
|
||||
|
||||
- The available network bandwidth in your environment between the client and the streaming server.
|
||||
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Scenario</th>
|
||||
<th align="left">Summary</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Multiple App-V clients stream applications from a single streaming server simultaneously.</p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>If the number of clients simultaneously streaming from the same server increases, there is a linear relationship with the package download/streaming time.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Size of the package being streamed.</p>
|
||||
<p></p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>The package size has a significant impact on the streaming/download time only for larger packages with a size ~ 1GB. For package sizes ranging from 3 MB to 100 MB, the streaming time ranges from 20 seconds to 100 seconds, with 100 simultaneous clients.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Network between the App-V client and the streaming server.</p>
|
||||
<p></p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>Across a slow network (1.5 Mbps bandwidth), there is a 70-80% increase in response time compared to LAN (up to 100 users).</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
The following table displays sample values for each of the factors in the previous list:
|
||||
|
||||
<table style="width:100%;">
|
||||
<colgroup>
|
||||
<col width="16%" />
|
||||
<col width="16%" />
|
||||
<col width="16%" />
|
||||
<col width="16%" />
|
||||
<col width="16%" />
|
||||
<col width="16%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Scenario</th>
|
||||
<th align="left">Variation</th>
|
||||
<th align="left">Number of App-V clients</th>
|
||||
<th align="left">Size of each package</th>
|
||||
<th align="left">Network connection type streaming server / App-V client</th>
|
||||
<th align="left">Round trip time on the App-V client (in seconds)</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Multiple App-V clients streaming virtual application packages from a streaming server.</p></td>
|
||||
<td align="left"><p>Number of clients.</p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>100</p></li>
|
||||
<li><p>200</p></li>
|
||||
<li><p>1000</p></li>
|
||||
<li><p></p></li>
|
||||
<li><p>100</p></li>
|
||||
<li><p>200</p></li>
|
||||
<li><p>1000</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>3.5 MB</p></li>
|
||||
<li><p>3.5 MB</p></li>
|
||||
<li><p>3.5 MB</p></li>
|
||||
<li><p></p></li>
|
||||
<li><p>5 MB</p></li>
|
||||
<li><p>5 MB</p></li>
|
||||
<li><p>5 MB</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p></p></li>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>29</p></li>
|
||||
<li><p>39</p></li>
|
||||
<li><p>391</p></li>
|
||||
<li><p></p></li>
|
||||
<li><p>35</p></li>
|
||||
<li><p>68</p></li>
|
||||
<li><p>461</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Size of each package being streamed.</p></td>
|
||||
<td align="left"><p>Size of each package.</p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>100</p></li>
|
||||
<li><p>200</p></li>
|
||||
<li><p></p></li>
|
||||
<li><p>100</p></li>
|
||||
<li><p>200</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>21 MB</p></li>
|
||||
<li><p>21 MB</p></li>
|
||||
<li><p></p></li>
|
||||
<li><p>109</p></li>
|
||||
<li><p>109</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p></p></li>
|
||||
<li><p>LAN</p></li>
|
||||
<li><p>LAN</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<p>33</p>
|
||||
<p>83</p>
|
||||
<p></p>
|
||||
<p>100</p>
|
||||
<p>160</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Network connection between client and App-V streaming server.</p></td>
|
||||
<td align="left"><p>1.5 Mbps Slow link network.</p></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>100</p></li>
|
||||
<li><p></p></li>
|
||||
<li><p>100</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>3.5 MB</p></li>
|
||||
<li><p></p></li>
|
||||
<li><p>5 MB</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>1.5 Mbps Intra-Continental Network</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<p>102</p>
|
||||
<p></p>
|
||||
<p>121</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
Each App-V streaming server should be able to handle a minimum of 200 clients concurrently streaming virtualized applications.
|
||||
|
||||
**Note**
|
||||
The actual time to it will take to stream is determined primarily by the number of clients streaming simultaneously, number of packages, package size, the server’s network activity, and network conditions.
|
||||
|
||||
|
||||
|
||||
For example, an average user can stream a 100 MB package in less than 2 minutes, when 100 simultaneous clients are streaming from the server. However, a package of size 1 GB could take up to 30 minutes. In most real world environments streaming demand is not uniformly distributed, you will need to understand the approximate peak streaming requirements present in your environment in order to properly size the number of required streaming servers.
|
||||
|
||||
The number of clients a streaming server can support can be significantly increased and the peak streaming requirements reduced if you pre-cache your applications. You can also increase the number of clients a streaming server can support by using on-demand streaming delivery and stream optimized packages.
|
||||
|
||||
## Combining App-V Server Roles
|
||||
|
||||
|
||||
Discounting scaling and fault-tolerance requirements, the minimum number of servers needed for a location with connectivity to Active Directory is one. This server will host the management server, management server service, and Microsoft SQL Server roles. Server roles, therefore, can be arranged in any desired combination since they do not conflict with one another.
|
||||
|
||||
Ignoring scaling requirements, the minimum number of servers necessary to provide a fault-tolerant implementation is four. The management server, and Microsoft SQL Server roles support being placed in fault-tolerant configurations. The management server service can be combined with any of the roles, but remains a single point of failure.
|
||||
|
||||
Although there are a number of fault-tolerance strategies and technologies available, not all are applicable to a given service. Additionally, if App-V roles are combined, certain fault-tolerance options may no longer apply due to incompatibilities.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[App-V Supported Configurations](appv-supported-configurations.md)
|
||||
|
||||
[Planning for High Availability with App-V](appv-planning-for-high-availability-with-appv.md)
|
||||
|
||||
[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
113
windows/manage/appv-client-configuration-settings.md
Normal file
113
windows/manage/appv-client-configuration-settings.md
Normal file
@ -0,0 +1,113 @@
|
||||
---
|
||||
title: About Client Configuration Settings (Windows 10)
|
||||
description: About Client Configuration Settings
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# About Client Configuration Settings
|
||||
|
||||
The Microsoft Application Virtualization (App-V) client stores its configuration in the registry. You can gather some useful information about the client if you understand the format of data in the registry. You can also configure many client actions by changing registry entries. This topic lists the App-V Client configuration settings and explains their uses. You can use PowerShell to modify the client configuration settings. For more information about using PowerShell and App-V see [Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md).
|
||||
|
||||
|
||||
|
||||
## App-V Client Configuration Settings: Windows PowerShell
|
||||
|
||||
The following table provides information about App-V client configuration settings that can be configured through Windows PowerShell cmdlets:
|
||||
|
||||
| **Name of option in Windows PowerShell**<br>Type | Description | Cmdlet or cmdlets for setting | Disabled Policy State Keys and Values |
|
||||
|------------|------------|------------|------------|
|
||||
| **PackageInstallationRoot**<br>String | Specifies directory where all new applications and updates will be installed. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | Policy value not written (same as Not Configured) |
|
||||
| **PackageSourceRoot**<br>String | Overrides source location for downloading package content. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | Policy value not written (same as Not Configured) |
|
||||
| **AllowHighCostLaunch**<br>True (enabled); False (Disabled state) | This setting controls whether virtualized applications are launched on Windows 10 machines connected via a metered network connection (For example, 4G). | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | 0 |
|
||||
| **ReestablishmentRetries**<br>Integer (0-99) | Specifies the number of times to retry a dropped session. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | Policy value not written (same as Not Configured) |
|
||||
| **ReestablishmentInterval**<br>Integer (0-3600) | Specifies the number of seconds between attempts to reestablish a dropped session. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | Policy value not written (same as Not Configured) |
|
||||
| **LocationProvider**<br>String | Specifies the CLSID for a compatible implementation of the IAppvPackageLocationProvider interface. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | Policy value not written (same as Not Configured) |
|
||||
| **CertFilterForClientSsl**<br>String | Specifies the path to a valid certificate in the certificate store. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | Policy value not written (same as Not Configured) |
|
||||
| **VerifyCertificateRevocationList**<br>True(enabled); False(Disabled state) | Verifies Server certificate revocation status before steaming using HTTPS. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | 0 |
|
||||
| **SharedContentStoreMode**<br>True(enabled); False(Disabled state) | Specifies that streamed package contents will be not be saved to the local hard disk. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | 0 |
|
||||
| **Name**<br>String | Displays the name of publishing server. | Set-AppvPublishingServer | Policy value not written (same as Not Configured) |
|
||||
| **URL**<br>String | Displays the URL of publishing server. | Set-AppvPublishingServer | Policy value not written (same as Not Configured) |
|
||||
| **GlobalRefreshEnabled**<br>True(enabled); False(Disabled state) | Enables global publishing refresh (Boolean) | Set-AppvPublishingServer | False |
|
||||
| **GlobalRefreshOnLogon**<br>True(enabled); False(Disabled state) | Triggers a global publishing refresh on logon. ( Boolean) | Set-AppvPublishingServer | False |
|
||||
| **GlobalRefreshInterval**<br>Integer (0-744) | Specifies the publishing refresh interval using the GlobalRefreshIntervalUnit. To disable package refresh, select 0. | Set-AppvPublishingServer | 0 |
|
||||
| **GlobalRefreshIntervalUnit** <br>0 for hour, 1 for day | Specifies the interval unit (Hour 0-23, Day 0-31). | Set-AppvPublishingServer | 1 |
|
||||
| **UserRefreshEnabled**<br>True(enabled); False(Disabled state) | Enables user publishing refresh (Boolean) | Set-AppvPublishingServer | False |
|
||||
| **UserRefreshOnLogon**<br>True(enabled); False(Disabled state) | Triggers a user publishing refresh onlogon. ( Boolean)Word count (with spaces): 60 | Set-AppvPublishingServer | False |
|
||||
| **UserRefreshInterval**<br>Word count (with spaces): 85Integer (0-744 Hours) | Specifies the publishing refresh interval using the UserRefreshIntervalUnit. To disable package refresh, select 0. | Set-AppvPublishingServer | 0 |
|
||||
| **UserRefreshIntervalUnit**<br>0 for hour, 1 for day | Specifies the interval unit (Hour 0-23, Day 0-31). | Set-AppvPublishingServer | 1 |
|
||||
| **MigrationMode**<br>True(enabled state); False (disabled state) | Migration mode allows the App-V client to modify shortcuts and FTA’s for packages created using a previous version of App-V. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | |
|
||||
| **EnablePackageScripts**<br>True(enabled); False(Disabled state) | Enables scripts defined in the package manifest of configuration files that should run. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | |
|
||||
| **RoamingFileExclusions**<br>String | Specifies the file paths relative to %userprofile% that do not roam with a user's profile. Example usage: /ROAMINGFILEEXCLUSIONS='desktop;my pictures' | Set-AppvClientConfiguration | |
|
||||
| **RoamingRegistryExclusions**<br>String | Specifies the registry paths that do not roam with a user profile. Example usage: /ROAMINGREGISTRYEXCLUSIONS=software\\classes;software\\clients | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | Policy value not written (same as Not Configured) |
|
||||
| **IntegrationRootUser**<br>String | Specifies the location to create symbolic links associated with the current version of a per-user published package. all virtual application extensions, for example shortcuts and file type associations, will point to this path. If you do not specify a path, symbolic links will not be used when you publish the package. For example: %localappdata%\\Microsoft\\AppV\\Client\\Integration. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | Policy value not written (same as Not Configured) |
|
||||
| **IntegrationRootGlobal**<br>String | Specifies the location to create symbolic links associated with the current version of a globally published package. all virtual application extensions, for example shortcuts and file type associations, will point to this path. If you do not specify a path, symbolic links will not be used when you publish the package. For example: %allusersprofile%\\Microsoft\\AppV\\Client\\Integration | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | Policy value not written (same as Not Configured) |
|
||||
| **VirtualizableExtensions**<br>String | A comma -delineated list of file name extensions that can be used to determine if a locally installed application can be run in the virtual environment. When shortcuts, FTAs, and other extension points are created during publishing, App-V will compare the file name extension to the list if the application that is associated with the extension point is locally installed. If the extension is located, the **RunVirtual** command line parameter will be added, and the application will run virtually. For more information about the **RunVirtual** parameter, see [Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](https://microsoft.sharepoint.com/teams/osg_core_dcp/cpub/partner/Shared%20Documents/APPV&UEV-for-Windows-RS1/App-V/App-V%20updated%20topics%20from%20JAN%20-%20PM%20reviews/appv-running-locally-installed-applications-inside-a-virtual-environment.md). | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | Policy value not written |
|
||||
| **ReportingEnabled**<br>True (enabled); False (Disabled state) | Enables the client to return information to a reporting server. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | False |
|
||||
| **ReportingServerURL**<br>String | Specifies the location on the reporting server where client information is saved. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | Policy value not written (same as Not Configured) |
|
||||
| **ReportingDataCacheLimit**<br>Integer \[0-1024\] | Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over. Set between 0 and 1024. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | Policy value not written (same as Not Configured) |
|
||||
| **ReportingDataBlockSize**<br>Integer \[1024 - Unlimited\] | Specifies the maximum size in bytes to transmit to the server for reporting upload requests. This can help avoid permanent transmission failures when the log has reached a significant size. Set between 1024 and unlimited. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | Policy value not written (same as Not Configured) |
|
||||
| **ReportingStartTime**<br>Integer (0 – 23) | Specifies the time to initiate the client to send data to the reporting server. You must specify a valid integer between 0-23 corresponding to the hour of the day. By default the **ReportingStartTime** will start on the current day at 10 P.M.or 22.<br>**Note** You should configure this setting to a time when computers running the App-V client are least likely to be offline. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | Policy value not written (same as Not Configured) |
|
||||
| **ReportingInterval**<br>Integer | Specifies the retry interval that the client will use to resend data to the reporting server. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | Policy value not written (same as Not Configured) |
|
||||
| **ReportingRandomDelay**<br>Integer \[0 - ReportingRandomDelay\] | Specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between 0 and **ReportingRandomDelay** and will wait the specified duration before sending data. This can help to prevent collisions on the server. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | Policy value not written (same as Not Configured) |
|
||||
| **EnableDynamicVirtualization<br>**1 (Enabled), 0 (Disabled) | Enables supported Shell Extensions, Browser Helper Objects, and Active X controls to be virtualized and run with virtual applications. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | |
|
||||
| **EnablePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | Enables the publishing refresh progress bar for the computer running the App-V Client. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | |
|
||||
| **HidePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | Hides the publishing refresh progress bar. | Sync-AppvPublishingServer | |
|
||||
| **ProcessesUsingVirtualComponents**<br>String | Specifies a list of process paths (that may contain wildcards), which are candidates for using dynamic virtualization (supported shell extensions, browser helper objects, and ActiveX controls). Only processes whose full path matches one of these items can use dynamic virtualization. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | Empty string. |
|
||||
|
||||
## App-V Client Configuration Settings: Setup Flags and Registry Keys
|
||||
|
||||
The following table provides information about App-V client configuration settings that can be configured through setup flags or in the registry:
|
||||
|
||||
| **Setting name**<br>Type | Setup Flag | Registry Key Value | Disabled Policy State Keys and Values |
|
||||
|--------------------------------------------------------------------------------|---------------------------|-------------------------------------------------------------------------|---------------------------------------------------|
|
||||
| **PackageInstallationRoot**<br>String | PACKAGEINSTALLATIONROOT | Streaming\\PackageInstallationRoot | Policy value not written (same as Not Configured) |
|
||||
| **PackageSourceRoot**<br>String | PACKAGESOURCEROOT | Streaming\\PackageSourceRoot | Policy value not written (same as Not Configured) |
|
||||
| **AllowHighCostLaunch**<br>True (enabled); False (Disabled state) | Not available. | Streaming\\AllowHighCostLaunch | 0 |
|
||||
| **ReestablishmentRetries**<br>Integer (0-99) | Not available. | Streaming\\ReestablishmentRetries | Policy value not written (same as Not Configured) |
|
||||
| **ReestablishmentInterval**<br>Integer (0-3600) | Not available. | Streaming\\ReestablishmentInterval | Policy value not written (same as Not Configured) |
|
||||
| **LocationProvider**<br>String | Not available. | Streaming\\LocationProvider | Policy value not written (same as Not Configured) |
|
||||
| **CertFilterForClientSsl**<br>String | Not available. | Streaming\\CertFilterForClientSsl | Policy value not written (same as Not Configured) |
|
||||
| **VerifyCertificateRevocationList**<br>True(enabled); False(Disabled state) | Not available. | Streaming\\VerifyCertificateRevocationList | 0 |
|
||||
| **SharedContentStoreMode**<br>True(enabled); False(Disabled state) | SHAREDCONTENTSTOREMODE | Streaming\\SharedContentStoreMode | 0 |
|
||||
| **Name**<br>String | PUBLISHINGSERVERNAME | Publishing\\Servers{serverId}\\FriendlyName | Policy value not written (same as Not Configured) |
|
||||
| **URL**<br>String | PUBLISHINGSERVERURL | Publishing\\Servers{serverId}\\URL | Policy value not written (same as Not Configured) |
|
||||
| **GlobalRefreshEnabled**<br>True(enabled); False(Disabled state) | GLOBALREFRESHENABLED | Publishing\\Servers{serverId}\\GlobalEnabled | False |
|
||||
| **GlobalRefreshOnLogon**<br>True(enabled); False(Disabled state) | GLOBALREFRESHONLOGON | Publishing\\Servers{serverId}\\GlobalLogonRefresh | False |
|
||||
| **GlobalRefreshInterval**<br>Integer (0-744) | GLOBALREFRESHINTERVAL | Publishing\\Servers{serverId}\\GlobalPeriodicRefreshInterval | 0 |
|
||||
| **GlobalRefreshIntervalUnit** <br>0 for hour, 1 for day | GLOBALREFRESHINTERVALUNI | Publishing\\Servers{serverId}\\GlobalPeriodicRefreshIntervalUnit | 1 |
|
||||
| **UserRefreshEnabled**<br>True(enabled); False(Disabled state) | USERREFRESHENABLED | Publishing\\Servers{serverId}\\UserEnabled | False |
|
||||
| **UserRefreshOnLogon**<br>True(enabled); False(Disabled state) | USERREFRESHONLOGON | Publishing\\Servers{serverId}\\UserLogonRefresh | False |
|
||||
| **UserRefreshInterval**<br>Word count (with spaces): 85Integer (0-744 Hours) | USERREFRESHINTERVAL | Publishing\\Servers{serverId}\\UserPeriodicRefreshInterval | 0 |
|
||||
| **UserRefreshIntervalUnit**<br>0 for hour, 1 for day | USERREFRESHINTERVALUNIT | Publishing\\Servers{serverId}\\UserPeriodicRefreshIntervalUnit | 1 |
|
||||
| **MigrationMode**<br>True(enabled state); False (disabled state) | MIGRATIONMODE | Coexistence\\MigrationMode | |
|
||||
| **EnablePackageScripts**<br>True(enabled); False(Disabled state) | ENABLEPACKAGESCRIPTS | \\Scripting\\EnablePackageScripts | |
|
||||
| **RoamingFileExclusions**<br>String | ROAMINGFILEEXCLUSIONS | | |
|
||||
| **RoamingRegistryExclusions**<br>String | ROAMINGREGISTRYEXCLUSIONS | Integration\\RoamingReglstryExclusions | Policy value not written (same as Not Configured) |
|
||||
| **IntegrationRootUser**<br>String | Not available. | Integration\\IntegrationRootUser | Policy value not written (same as Not Configured) |
|
||||
| **IntegrationRootGlobal**<br>String | Not available. | Integration\\IntegrationRootGlobal | Policy value not written (same as Not Configured) |
|
||||
| **VirtualizableExtensions**<br>String | Not available. | Integration\\VirtualizableExtensions | Policy value not written |
|
||||
| **ReportingEnabled**<br>True (enabled); False (Disabled state) | Not available. | Reporting\\EnableReporting | False |
|
||||
| **ReportingServerURL**<br>String | Not available. | Reporting\\ReportingServer | Policy value not written (same as Not Configured) |
|
||||
| **ReportingDataCacheLimit**<br>Integer \[0-1024\] | Not available. | Reporting\\DataCacheLimit | Policy value not written (same as Not Configured) |
|
||||
| **ReportingDataBlockSize**<br>Integer \[1024 - Unlimited\] | Not available. | Reporting\\DataBlockSize | Policy value not written (same as Not Configured) |
|
||||
| **ReportingStartTime**<br>Integer (0 – 23) | Not available. | Reporting\\ StartTime | Policy value not written (same as Not Configured) |
|
||||
| **ReportingInterval**<br>Integer | Not available. | Reporting\\RetryInterval | Policy value not written (same as Not Configured) |
|
||||
| **ReportingRandomDelay**<br>Integer \[0 - ReportingRandomDelay\] | Not available. | Reporting\\RandomDelay | Policy value not written (same as Not Configured) |
|
||||
| **EnableDynamicVirtualization<br>**1 (Enabled), 0 (Disabled) | Not available. | HKEY\_LOCAL\_MACHINE\\Software\\Microsoft\\AppV\\Client\\Virtualization | |
|
||||
| **EnablePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | Not available. | HKEY\_LOCAL\_MACHINE\\Software\\Microsoft\\AppV\\Client\\Publishing | |
|
||||
| **HidePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | Not available. | | |
|
||||
| **ProcessesUsingVirtualComponents**<br>String | Not available. | Virtualization\\ProcessesUsingVirtualComponents | Empty string. |
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
[Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
|
||||
[How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md)
|
||||
@ -0,0 +1,72 @@
|
||||
---
|
||||
title: How to Configure Access to Packages by Using the Management Console (Windows 10)
|
||||
description: How to Configure Access to Packages by Using the Management Console
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Configure Access to Packages by Using the Management Console
|
||||
|
||||
|
||||
Before you deploy an App-V virtualized package, you must configure the Active Directory Domain Services (AD DS) security groups that will be allowed to access and run the applications. The security groups may contain computers or users. Entitling a package to a computer group publishes the package globally to all computers in the group.
|
||||
|
||||
Use the following procedure to configure access to virtualized packages.
|
||||
|
||||
**To grant access to an App-V package**
|
||||
|
||||
1. Find the package you want to configure:
|
||||
|
||||
1. Open the App-V Management console.
|
||||
|
||||
2. To display the **AD ACCESS** page, right-click the package to be configured, and select **Edit active directory access**. Alternatively, select the package and click **EDIT** in the **AD ACCESS** pane.
|
||||
|
||||
2. Provision a security group for the package:
|
||||
|
||||
1. Go to the **FIND VALID ACTIVE DIRECTORY NAMES AND GRANT ACCESS** page.
|
||||
|
||||
2. Using the format **mydomain** \\ **groupname**, type the name or part of the name of an Active Directory group object, and click **Check**.
|
||||
|
||||
**Note**
|
||||
Ensure that you provide an associated domain name for the group that you are searching for.
|
||||
|
||||
|
||||
|
||||
3. To grant access to the package, select the desired group and click **Grant Access**. The newly added group is displayed in the **AD ENTITIES WITH ACCESS** pane.
|
||||
|
||||
4.
|
||||
|
||||
To accept the default configuration settings and close the **AD ACCESS** page, click **Close**.
|
||||
|
||||
To customize configurations for a specific group, click the **ASSIGNED CONFIGURATIONS** drop-down and select **Custom**. To configure the custom configurations, click **EDIT**. After you grant access, click **Close**.
|
||||
|
||||
**To remove access to an App-V package**
|
||||
|
||||
1. Find the package you want to configure:
|
||||
|
||||
1. Open the App-V Management console.
|
||||
|
||||
2. To display the **AD ACCESS** page, right-click the package to be configured, and select **Edit active directory access**. Alternatively, select the package and click **EDIT** in the **AD ACCESS** pane.
|
||||
|
||||
2. Select the group you want to remove, and click **DELETE**.
|
||||
|
||||
3. To close the **AD ACCESS** page, click **Close**.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,104 @@
|
||||
---
|
||||
title: How to Make a Connection Group Ignore the Package Version (Windows 10)
|
||||
description: How to Make a Connection Group Ignore the Package Version
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Make a Connection Group Ignore the Package Version
|
||||
|
||||
|
||||
Microsoft Application Virtualization (App-V) lets you configure a connection group to use any version of a package, which simplifies package upgrades and reduces the number of connection groups you need to create.
|
||||
|
||||
To upgrade a package in some earlier versions of App-V, you had to perform several steps, including disabling the connection group and modifying the connection group’s XML definition file.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Task description with App-V</th>
|
||||
<th align="left">How to perform the task with App-V</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>You can configure a connection group to accept any version of a package, which enables you to upgrade the package without having to disable the connection group.</p>
|
||||
<p><strong>How the feature works:</strong></p>
|
||||
<ul>
|
||||
<li><p>If the connection group has access to multiple versions of a package, the latest version is used.</p></li>
|
||||
<li><p>If the connection group contains an optional package that has an incorrect version, the package is ignored and won’t block the connection group’s virtual environment from being created.</p></li>
|
||||
<li><p>If the connection group contains a non-optional package that has an incorrect version, the connection group’s virtual environment cannot be created.</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Method</th>
|
||||
<th align="left">Steps</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V Server – Management Console</p></td>
|
||||
<td align="left"><ol>
|
||||
<li><p>In the Management Console, select <strong>CONNECTION GROUPS</strong>.</p></li>
|
||||
<li><p>Select the correct connection group from the Connection Groups library.</p></li>
|
||||
<li><p>Click <strong>EDIT</strong> in the CONNECTED PACKAGES pane.</p></li>
|
||||
<li><p>Select <strong>Use Any Version</strong> check box next to the package name, and click <strong>Apply</strong>.</p></li>
|
||||
</ol>
|
||||
<p>For more about adding or upgrading packages, see [How to Add or Upgrade Packages by Using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md).</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V Client on a Stand-alone computer</p></td>
|
||||
<td align="left"><ol>
|
||||
<li><p>Create the connection group XML document.</p></li>
|
||||
<li><p>For the package to be upgraded, set the <strong>Package</strong> tag attribute <strong>VersionID</strong> to an asterisk (<strong>*</strong>).</p></li>
|
||||
<li><p>Use the following cmdlet to add the connection group, and include the path to the connection group XML document:</p>
|
||||
<p><strong>Add-AppvClientConnectionGroup</strong></p></li>
|
||||
<li><p>When you upgrade a package, use the following cmdlets to remove the old package, add the upgraded package, and publish the upgraded package:</p>
|
||||
<ul>
|
||||
<li><p>RemoveAppvClientPackage</p></li>
|
||||
<li><p>Add-AppvClientPackage</p></li>
|
||||
<li><p>Publish-AppvClientPackage</p></li>
|
||||
</ul></li>
|
||||
</ol>
|
||||
<p>For more information, see [How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md).</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p> </p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,82 @@
|
||||
---
|
||||
title: How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server (Windows 10)
|
||||
description: How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server
|
||||
|
||||
|
||||
Deploying packages and connection groups using the App-V publishing server is helpful because it offers single-point management and high scalability.
|
||||
|
||||
Use the following steps to configure the App-V client to receive updates from the publishing server.
|
||||
|
||||
**Note**
|
||||
For the following procedures the management server was installed on a computer named **MyMgmtSrv**, and the publishing server was installed on a computer named **MyPubSrv**.
|
||||
|
||||
|
||||
|
||||
**To configure the App-V client to receive updates from the publishing server**
|
||||
|
||||
1. Deploy the App-V management and publishing servers, and add the required packages and connection groups. For more information about adding packages and connection groups, see [How to Add or Upgrade Packages by Using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md) and [How to Create a Connection Group](appv-create-a-connection-group.md).
|
||||
|
||||
2. To open the management console click the following link, open a browser and type the following: http://MyMgmtSrv/AppvManagement/Console.html in a web browser, and import, publish, and entitle all the packages and connection groups which will be necessary for a particular set of users.
|
||||
|
||||
3. On the computer running the App-V client, open an elevated PowerShell command prompt, run the following command:
|
||||
|
||||
**Add-AppvPublishingServer -Name ABC -URL http:// MyPubSrv/AppvPublishing**
|
||||
|
||||
This command will configure the specified publishing server. You should see output similar to the following:
|
||||
|
||||
Id : 1
|
||||
|
||||
SetByGroupPolicy : False
|
||||
|
||||
Name : ABC
|
||||
|
||||
URL : http:// MyPubSrv/AppvPublishing
|
||||
|
||||
GlobalRefreshEnabled : False
|
||||
|
||||
GlobalRefreshOnLogon : False
|
||||
|
||||
GlobalRefreshInterval : 0
|
||||
|
||||
GlobalRefreshIntervalUnit : Day
|
||||
|
||||
UserRefreshEnabled : True
|
||||
|
||||
UserRefreshOnLogon : True
|
||||
|
||||
UserRefreshInterval : 0
|
||||
|
||||
UserRefreshIntervalUnit : Day
|
||||
|
||||
The returned Id – in this case 1
|
||||
|
||||
4. On the computer running the App-V client, open a PowerShell command prompt, and type the following command:
|
||||
|
||||
**Sync-AppvPublishingServer -ServerId 1**
|
||||
|
||||
The command will query the publishing server for the packages and connection groups that need to be added or removed for this particular client based on the entitlements for the packages and connection groups as configured on the management server.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
27
windows/manage/appv-connect-to-the-management-console.md
Normal file
27
windows/manage/appv-connect-to-the-management-console.md
Normal file
@ -0,0 +1,27 @@
|
||||
---
|
||||
title: How to Connect to the Management Console (Windows 10)
|
||||
description: How to Connect to the Management Console
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Connect to the Management Console
|
||||
|
||||
Use the following procedure to connect to the App-V Management Console.
|
||||
|
||||
**To connect to the App-V Management Console**
|
||||
|
||||
1. Open Internet Explorer browser and type the address for the App-V. For example, **http://\<_management server name_\>:\<_management service port number_\>/console.html**.
|
||||
|
||||
2. To view different sections of the console, click the desired section in the navigation pane.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
292
windows/manage/appv-connection-group-file.md
Normal file
292
windows/manage/appv-connection-group-file.md
Normal file
@ -0,0 +1,292 @@
|
||||
---
|
||||
title: About the Connection Group File (Windows 10)
|
||||
description: About the Connection Group File
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# About the Connection Group File
|
||||
|
||||
|
||||
**In this topic:**
|
||||
|
||||
- [Connection group file purpose and location](#bkmk-cg-purpose-loc)
|
||||
|
||||
- [Structure of the connection group XML file](#bkmk-define-cg-5-0sp3)
|
||||
|
||||
- [Configuring the priority of packages in a connection group](#bkmk-config-pkg-priority-incg)
|
||||
|
||||
- [Supported virtual application connection configurations](#bkmk-va-conn-configs)
|
||||
|
||||
## <a href="" id="bkmk-cg-purpose-loc"></a>Connection group file purpose and location
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Connection group purpose</p></td>
|
||||
<td align="left"><p>A connection group is an App-V feature that enables you to group packages together to create a virtual environment in which the applications in those packages can interact with each other.</p>
|
||||
<p>Example: You want to use plug-ins with Microsoft Office. You can create a package that contains the plug-ins, and create another package that contains Office, and then add both packages to a connection group to enable Office to use those plug-ins.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>How the connection group file works</p></td>
|
||||
<td align="left"><p>When you apply an App-V connection group file, the packages that are enumerated in the file will be combined at runtime into a single virtual environment. Use the Microsoft Application Virtualization (App-V) connection group file to configure existing App-V connection groups.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Example file path</p></td>
|
||||
<td align="left"><p>%APPDATA%\Microsoft\AppV\Client\Catalog\PackageGroups\{6CCC7575-162E-4152-9407-ED411DA138F4}\{4D1E16E1-8EF8-41ED-92D5-8910A8527F96}.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-define-cg-5-0sp3"></a>Structure of the connection group XML file
|
||||
|
||||
|
||||
**In this section:**
|
||||
|
||||
- [Parameters that define the connection group](#bkmk-params-define-cg)
|
||||
|
||||
- [Parameters that define the packages in the connection group](#bkmk-params-define-pkgs-incg)
|
||||
|
||||
- [App-V example connection group XML file](#bkmk-50sp3-exp-cg-xml)
|
||||
|
||||
### <a href="" id="bkmk-params-define-cg"></a>Parameters that define the connection group
|
||||
|
||||
The following table describes the parameters in the XML file that define the connection group itself, not the packages.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Field</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Schema name</p></td>
|
||||
<td align="left"><p>Name of the schema.</p>
|
||||
<p>If you want to use the “optional packages” and “use any version” features that are described in this table, you must specify the following schema in the XML file:</p>
|
||||
<p><code>xmlns="http://schemas.microsoft.com/appv/2014/virtualapplicationconnectiongroup"</code></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>AppConnectionGroupId</p></td>
|
||||
<td align="left"><p>Unique GUID identifier for this connection group. The connection group state is associated with this identifier. Specify this identifier only when you create the connection group.</p>
|
||||
<p>You can create a new GUID by typing: <strong>[Guid]::NewGuid()</strong>.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>VersionId</p></td>
|
||||
<td align="left"><p>Version GUID identifier for this version of the connection group.</p>
|
||||
<p>When you update a connection group (for example, by adding or updating a new package), you must update the version GUID to reflect the new version.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>DisplayName</p></td>
|
||||
<td align="left"><p>Display name of the connection group.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Priority</p></td>
|
||||
<td align="left"><p>Optional priority field for the connection group.</p>
|
||||
<p><strong>“0”</strong> - indicates the highest priority.</p>
|
||||
<p>If a priority is required, but has not been configured, the package will fail because the correct connection group to use cannot be determined.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### <a href="" id="bkmk-params-define-pkgs-incg"></a>Parameters that define the packages in the connection group
|
||||
|
||||
In the <Packages> section of the connection group XML file, you list the member packages in the connection group by specifying each package’s unique package identifier and version identifier, as described in the following table. The first package in the list has the highest precedence.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Field</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>PackageId</p></td>
|
||||
<td align="left"><p>Unique GUID identifier for this package. This GUID doesn’t change when newer versions of the package are published.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>VersionId</p></td>
|
||||
<td align="left"><p>Unique GUID identifier for the version of the package.</p>
|
||||
<p>If you specify <strong>“*”</strong> for the package version, the GUID of the latest available package version is dynamically inserted.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>IsOptional</p></td>
|
||||
<td align="left"><p>Parameter that enables you to make a package optional within the connection group. Valid entries are:</p>
|
||||
<ul>
|
||||
<li><p><strong>“true”</strong> – package is optional in the connection group</p></li>
|
||||
<li><p><strong>“false”</strong> – package is required in the connection group</p></li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### <a href="" id="bkmk-50sp3-exp-cg-xml"></a>App-V example connection group XML file
|
||||
|
||||
The following example connection group XML file shows examples of the fields in the previous tables.
|
||||
|
||||
```
|
||||
<?xml version="1.0" encoding="UTF-16"?>
|
||||
<appv:AppConnectionGroup
|
||||
xmlns="http://schemas.microsoft.com/appv/2014/virtualapplicationconnectiongroup"
|
||||
xmlns:appv="http://schemas.microsoft.com/appv/2014/virtualapplicationconnectiongroup"
|
||||
AppConnectionGroupId="61BE9B14-D2B4-41CE-A6E3-A1B658DE7000"
|
||||
VersionId="E6B6AA57-F2A7-49C9-ADF8-F2B5B3C8A42F"
|
||||
Priority="0"
|
||||
DisplayName="Sample Connection Group">
|
||||
<appv:Packages>
|
||||
<appv:Package
|
||||
PackageId="1DC709C8-309F-4AB4-BD47-F75926D04276"
|
||||
VersionId="*"
|
||||
IsOptional=”true”
|
||||
/>
|
||||
<appv:Package
|
||||
PackageId="04220DCA-EE77-42BE-A9F5-96FD8E8593F2"
|
||||
VersionId="E15EFFE9-043D-4C01-BC52-AD2BD1E8BAFA"
|
||||
IsOptional=”false”
|
||||
/>
|
||||
</appv:Packages>
|
||||
```
|
||||
|
||||
## <a href="" id="bkmk-config-pkg-priority-incg"></a>Configuring the priority of packages in a connection group
|
||||
|
||||
|
||||
Package precedence is configured using the package list order. The first package in the document has the highest precedence. Subsequent packages in the list have descending priority.
|
||||
|
||||
Package precedence is the resolution for otherwise inevitable resource collisions during virtual environment initialization. For example, if two packages that are opening in the same virtual environment define the same registry DWORD value, the package with the highest precedence determines the value that is set.
|
||||
|
||||
You can use the connection group file to configure each connection group by using the following methods:
|
||||
|
||||
- Specify runtime priorities for connection groups. To edit priority by using the App-V Management Console, click the connection group and then click **Edit**.
|
||||
|
||||
**Note**
|
||||
Priority is required only if the package is associated with more than one connection group.
|
||||
|
||||
|
||||
|
||||
- Specify package precedence within the connection group.
|
||||
|
||||
The priority field is required when a running virtual application initiates from a native application request, for example, Microsoft Windows Explorer. The App-V client uses the priority to determine which connection group virtual environment the application should run in. This situation occurs if a virtual application is part of multiple connection groups.
|
||||
|
||||
If a virtual application is opened using another virtual application the virtual environment of the original virtual application will be used. The priority field is not used in this case.
|
||||
|
||||
**Example:**
|
||||
|
||||
The virtual application Microsoft Outlook is running in virtual environment **XYZ**. When you open an attached Microsoft Word document, a virtualized version Microsoft Word opens in the virtual environment **XYZ**, regardless of the virtualized Microsoft Word’s associated connection groups or runtime priorities.
|
||||
|
||||
## <a href="" id="bkmk-va-conn-configs"></a>Supported virtual application connection configurations
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Configuration</th>
|
||||
<th align="left">Example scenario</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>An. exe file and plug-in (.dll)</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>You want to distribute Microsoft Office to all users, but distribute a Microsoft Excel plug-in to only a subset of users.</p></li>
|
||||
<li><p>Enable the connection group for the appropriate users.</p></li>
|
||||
<li><p>Update each package individually as required.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>An. exe file and a middleware application</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>You have an application requires a middleware application, or several applications that all depend on the same middleware runtime version.</p></li>
|
||||
<li><p>All computers that require one or more of the applications receive the connection groups with the application and middleware application runtime.</p></li>
|
||||
<li><p>You can optionally combine multiple middleware applications into a single connection group.</p>
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Example</th>
|
||||
<th align="left">Example description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Virtual application connection group for the financial division</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Middleware application 1</p></li>
|
||||
<li><p>Middleware application 2</p></li>
|
||||
<li><p>Middleware application 3</p></li>
|
||||
<li><p>Middleware application runtime</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Virtual application connection group for HR division</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Middleware application 5</p></li>
|
||||
<li><p>Middleware application 6</p></li>
|
||||
<li><p>Middleware application runtime</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p> </p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>An. exe file and an .exe file</p></td>
|
||||
<td align="left"><p>You have an application that relies on another application, and you want to keep the packages separate for operational efficiencies, licensing restrictions, or rollout timelines.</p>
|
||||
<p><strong>Example:</strong></p>
|
||||
<p>If you are deploying Microsoft Lync 2010, you can use three packages:</p>
|
||||
<ul>
|
||||
<li><p>Microsoft Office 2010</p></li>
|
||||
<li><p>Microsoft Communicator 2007</p></li>
|
||||
<li><p>Microsoft Lync 2010</p></li>
|
||||
</ul>
|
||||
<p>You can manage the deployment using the following connection groups:</p>
|
||||
<ul>
|
||||
<li><p>Microsoft Office 2010 and Microsoft Communicator 2007</p></li>
|
||||
<li><p>Microsoft Office 2010 and Microsoft Lync 2010</p></li>
|
||||
</ul>
|
||||
<p>When the deployment has completed, you can either create a single new Microsoft Office 2010 + Microsoft Lync 2010 package, or keep and maintain them as separate packages and deploy them by using a connection group.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
[Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
109
windows/manage/appv-connection-group-virtual-environment.md
Normal file
109
windows/manage/appv-connection-group-virtual-environment.md
Normal file
@ -0,0 +1,109 @@
|
||||
---
|
||||
title: About the Connection Group Virtual Environment (Windows 10)
|
||||
description: About the Connection Group Virtual Environment
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# About the Connection Group Virtual Environment
|
||||
|
||||
|
||||
**In this topic:**
|
||||
|
||||
- [How package priority is determined](#bkmk-pkg-priority-deter)
|
||||
|
||||
- [Merging identical package paths into one virtual directory in connection groups](#bkmk-merged-root-ve-exp)
|
||||
|
||||
## <a href="" id="bkmk-pkg-priority-deter"></a>How package priority is determined
|
||||
|
||||
|
||||
The virtual environment and its current state are associated with the connection group, not with the individual packages. If an App-V package is removed from the connection group, the state that existed as part of the connection group will not migrate with the package.
|
||||
|
||||
If the same package is a part of two different connection groups, you have to indicate which connection group App-V should use. For example, you might have two packages in a connection group that each define the same registry DWORD value.
|
||||
|
||||
The connection group that is used is based on the order in which a package appears inside the **AppConnectionGroup** XML document:
|
||||
|
||||
- The first package has the highest precedence.
|
||||
|
||||
- The second package has the second highest precedence.
|
||||
|
||||
Consider the following example section:
|
||||
|
||||
``` syntax
|
||||
<appv:Packages><appv:PackagePackageId="A8731008-4523-4713-83A4-CD1363907160"VersionId="E889951B-7F30-418B-A69C-B37283BC0DB9"/><appv:PackagePackageId="1DC709C8-309F-4AB4-BD47-F75926D04276"VersionId="01F1943B-C778-40AD-BFAD-AC34A695DF3C"/><appv:PackagePackageId="04220DCA-EE77-42BE-A9F5-96FD8E8593F2"VersionId="E15EFFE9-043D-4C01-BC52-AD2BD1E8BAFA"/></appv:Packages>
|
||||
```
|
||||
|
||||
Assume that same DWORD value ABC (HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region) is defined in the first and third package, such as:
|
||||
|
||||
- Package 1 (A8731008-4523-4713-83A4-CD1363907160): HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=5
|
||||
|
||||
- Package 3 (04220DCA-EE77-42BE-A9F5-96FD8E8593F2): HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=10
|
||||
|
||||
Since Package 1 appears first, the AppConnectionGroup's virtual environment will have the single DWORD value of 5 (HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=5). This means that the virtual applications in Package 1, Package 2, and Package 3 will all see the value 5 when they query for HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region.
|
||||
|
||||
Other virtual environment resources are resolved similarly, but the usual case is that the collisions occur in the registry.
|
||||
|
||||
## <a href="" id="bkmk-merged-root-ve-exp"></a>Merging identical package paths into one virtual directory in connection groups
|
||||
|
||||
|
||||
If two or more packages in a connection group contain identical directory paths, the paths are merged into a single virtual directory inside the connection group virtual environment. This merging of paths allows an application in one package to access files that are in a different package.
|
||||
|
||||
When you remove a package from a connection group, the applications in that removed package are no longer able to access files in the remaining packages in the connection group.
|
||||
|
||||
The order in which App-V looks up a file’s name in the connection group is specified by the order in which the App-V packages are listed in the connection group manifest file.
|
||||
|
||||
The following example shows the order and relationship of a file name lookup in a connection group for **Package A** and **Package B**.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Package A</th>
|
||||
<th align="left">Package B</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>C:\Windows\System32</p></td>
|
||||
<td align="left"><p>C:\Windows\System32</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>C:\AppTest</p></td>
|
||||
<td align="left"><p>C:\AppTest</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
In the example above, when a virtualized application tries to find a specific file, Package A is searched first for a matching file path. If a matching path is not found, Package B is searched, using the following mapping rules:
|
||||
|
||||
- If a file named **test.txt** exists in the same virtual folder hierarchy in both application packages, the first matching file is used.
|
||||
|
||||
- If a file named **bar.txt** exists in the virtual folder hierarchy of one application package, but not in the other, the first matching file is used.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,61 @@
|
||||
---
|
||||
title: How to Convert a Package Created in a Previous Version of App-V (Windows 10)
|
||||
description: How to Convert a Package Created in a Previous Version of App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Convert a Package Created in a Previous Version of App-V
|
||||
|
||||
You can use the package converter utility to upgrade virtual application packages that have been created with previous versions of App-V.
|
||||
|
||||
> [!NOTE]
|
||||
> If you are running a computer with a 64-bit architecture, you must use the x86 version of Windows PowerShell.
|
||||
|
||||
The package converter can only directly convert packages that were created by using the App-V 4.5 sequencer or later. Packages that were created using a version prior to App-V 4.5 must be upgraded to at least App-V 4.5 before conversion.
|
||||
|
||||
The following information provides direction for converting existing virtual application packages.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> You must configure the package converter to always save the package ingredients file to a secure location and directory. A secure location is accessible only by an administrator. Additionally, when you deploy the package, you should save the package to a location that is secure, or make sure that no other user is allowed to be logged in during the conversion process.
|
||||
|
||||
## App-V 4.6 installation folder is redirected to virtual file system root
|
||||
|
||||
When you convert packages from App-V 4.6 to App-V for Windows 10, the App-V for Windows 10 package can access the hardcoded drive that you were required to use when you created 4.6 packages. The drive letter will be the drive you selected as the installation drive on the 4.6 sequencing machine. (The default drive letter is Q:\\.)
|
||||
|
||||
**Technical Details:** The App-V package converter will save the App-V 4.6 installation root folder and short folder names in the FilesystemMetadata.xml file in the Filesystem element. When the App-V for Windows 10 client creates the virtual process, it will map requests from the App-V 4.6 installation root to the virtual file system root.
|
||||
|
||||
## Getting started
|
||||
|
||||
1. Install the App-V Sequencer on a computer in your environment. For information about how to install the Sequencer, see [How to Install the Sequencer](appv-install-the-sequencer.md).
|
||||
|
||||
2. The following cmdlets are available:
|
||||
|
||||
- **Test-AppvLegacyPackage** – This cmdlet is designed to check packages. It will return information about any failures with the package such as missing **.sft** files, an invalid source, **.osd** file errors, or invalid package version. This cmdlet will not parse the **.sft** file or do any in depth validation. For information about options and basic functionality for this cmdlet, using Windows PowerShell, type `Test-AppvLegacyPackage -?`.
|
||||
|
||||
- **ConvertFrom-AppvLegacyPackage** – To convert an existing package, type `ConvertFrom-AppvLegacyPackage c:\contentStore c:\convertedPackages`. In this command, `c:\contentStore` represents the location of the existing package and `c:\convertedPackages` is the output directory to which the resulting App-V for Windows 10 virtual application package file will be saved. By default, if you do not specify a new name, the old package name will be used.
|
||||
|
||||
Additionally, the package converter optimizes performance of packages in App-V for Windows 10 by setting the package to stream fault the App-V package. This is more performant than the primary feature block and fully downloading the package. The flag **DownloadFullPackageOnFirstLaunch** allows you to convert the package and set the package to be fully downloaded by default.
|
||||
|
||||
> [!NOTE]
|
||||
> Before you specify the output directory, you must create the output directory.
|
||||
|
||||
### Advanced Conversion Tips
|
||||
|
||||
- Piping - Windows PowerShell supports piping. Piping allows you to call `dir c:\contentStore\myPackage | Test-AppvLegacyPackage`. In this example, the directory object that represents `myPackage` will be given as input to the `Test-AppvLegacyPackage` command and bound to the `-Source` parameter. Piping like this is especially useful when you want to batch commands together; for example, `dir .\ | Test-AppvLegacyPackage | ConvertFrom-AppvLegacyAppvPackage -Target .\ConvertedPackages`. This piped command would test the packages and then pass those objects on to actually be converted. You can also apply a filter on packages without errors or only specify a directory which contains an **.sprj** file or pipe them to another cmdlet that adds the filtered package to the server or publishes them to the App-V client.
|
||||
|
||||
- Batching - The Windows PowerShell command enables batching. More specifically, the cmdlets support taking a string\[\] object for the `-Source` parameter which represents a list of directory paths. This allows you to enter `$packages = dir c:\contentStore` and then call `ConvertFrom-AppvLegacyAppvPackage-Source $packages -Target c:\ConvertedPackages` or to use piping and call `dir c:\ContentStore | ConvertFrom-AppvLegacyAppvPackage -Target C:\ConvertedPackages`.
|
||||
|
||||
- Other functionality - Windows PowerShell has other built-in functionality for features such as aliases, piping, lazy-binding, .NET object, and many others. All of these are usable in Windows PowerShell and can help you create advanced scenarios for the Package Converter.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
@ -0,0 +1,82 @@
|
||||
---
|
||||
title: How to Create a Connection Group with User-Published and Globally Published Packages (Windows 10)
|
||||
description: How to Create a Connection Group with User-Published and Globally Published Packages
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Create a Connection Group with User-Published and Globally Published Packages
|
||||
|
||||
|
||||
You can create user-entitled connection groups that contain both user-published and globally published packages, using either of the following methods:
|
||||
|
||||
- [How to use PowerShell cmdlets to create the user-entitled connection groups](#bkmk-posh-userentitled-cg)
|
||||
|
||||
- [How to use the App-V Server to create the user-entitled connection groups](#bkmk-appvserver-userentitled-cg)
|
||||
|
||||
**What to know before you start:**
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Unsupported scenarios and potential issues</th>
|
||||
<th align="left">Result</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>You cannot include user-published packages in globally entitled connection groups.</p></td>
|
||||
<td align="left"><p>The connection group will fail.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>If you publish a package globally and then create a user-published connection group in which you’ve made that package non-optional, you can still run <strong>Unpublish-AppvClientPackage <package> -global</strong> to unpublish the package, even when that package is being used in another connection group.</p></td>
|
||||
<td align="left"><p>If any other connection groups are using that package, the package will fail in those connection groups.</p>
|
||||
<p>To avoid inadvertently unpublishing a non-optional package that is being used in another connection group, we recommend that you track the connection groups in which you’ve used a non-optional package.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**How to use PowerShell cmdlets to create user-entitled connection groups**
|
||||
|
||||
1. Add and publish packages by using the following commands:
|
||||
|
||||
**Add-AppvClientPackage Pacakage1\_AppV\_file\_Path**
|
||||
|
||||
**Add-AppvClientPackage Pacakage2\_AppV\_file\_Path**
|
||||
|
||||
**Publish-AppvClientPackage -PackageId Package1\_ID -VersionId Package1\_Version ID -Global**
|
||||
|
||||
**Publish-AppvClientPackage -PackageId Package2\_ID -VersionId Package2\_ID**
|
||||
|
||||
2. Create the connection group XML file. For more information, see [About the Connection Group File](appv-connection-group-file.md).
|
||||
|
||||
3. Add and publish the connection group by using the following commands:
|
||||
|
||||
**Add-AppvClientConnectionGroup Connection\_Group\_XML\_file\_Path**
|
||||
|
||||
**Enable-AppvClientConnectionGroup -GroupId CG\_Group\_ID -VersionId CG\_Version\_ID**
|
||||
|
||||
**How to use the App-V Server to create user-entitled connection groups**
|
||||
|
||||
1. Open the App-V Management Console.
|
||||
|
||||
2. Follow the instructions in [How to Publish a Package by Using the Management Console](appv-publish-a-packages-with-the-management-console.md) to publish packages globally and to the user.
|
||||
|
||||
3. Follow the instructions in [How to Create a Connection Group](appv-create-a-connection-group.md) to create the connection group, and add the user-published and globally published packages.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
58
windows/manage/appv-create-a-connection-group.md
Normal file
58
windows/manage/appv-create-a-connection-group.md
Normal file
@ -0,0 +1,58 @@
|
||||
---
|
||||
title: How to Create a Connection Group (Windows 10)
|
||||
description: How to Create a Connection Group
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Create a Connection Group
|
||||
|
||||
|
||||
Use these steps to create a connection group by using the App-V Management Console. To use PowerShell to create connection groups, see [How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md).
|
||||
|
||||
When you place packages in a connection group, their package root paths are merged. If you remove packages, only the remaining packages maintain the merged root.
|
||||
|
||||
**To create a connection group**
|
||||
|
||||
1. In the App-V Management Console, select **CONNECTION GROUPS** to display the Connection Groups library.
|
||||
|
||||
2. Select **ADD CONNECTION GROUP** to create a new connection group.
|
||||
|
||||
3. In the **New Connection Group** pane, type a description for the group.
|
||||
|
||||
4. Click **EDIT** in the **CONNECTED PACKAGES** pane to add a new application to the connection group.
|
||||
|
||||
5. In the **PACKAGES Entire Library** pane, select the application to be added, and click the arrow to add the application.
|
||||
|
||||
To remove an application, select the application to be removed in the **PACKAGES IN** pane and click the arrow.
|
||||
|
||||
To reprioritize the applications in your connection group, use the arrows in the **PACKAGES IN** pane.
|
||||
|
||||
**Important**
|
||||
By default, the Active Directory Domain Services access configurations that are associated with a specific application are not added to the connection group. To transfer the Active Directory access configuration, select **ADD PACKAGE ACCESS TO GROUP ACCESS**, which is located in the **PACKAGES IN** pane.
|
||||
|
||||
|
||||
|
||||
6. After adding all the applications and configuring Active Directory access, click **Apply**.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
[Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,48 @@
|
||||
---
|
||||
title: How to Create a Custom Configuration File by Using the App-V Management Console (Windows 10)
|
||||
description: How to Create a Custom Configuration File by Using the App-V Management Console
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Create a Custom Configuration File by Using the App-V Management Console
|
||||
|
||||
|
||||
You can use a dynamic configuration to customize an App-V package for a specific user. However, you must first create the dynamic user configuration (.xml) file or the dynamic deployment configuration file before you can use the files. Creation of the file is an advanced manual operation. For general information about dynamic user configuration files, see, [About App-V Dynamic Configuration](appv-dynamic-configuration.md).
|
||||
|
||||
Use the following procedure to create a Dynamic User Configuration file by using the App-V Management console.
|
||||
|
||||
**To create a Dynamic User Configuration file**
|
||||
|
||||
1. Right-click the name of the package that you want to view and select **Edit active directory access** to view the configuration that is assigned to a given user group. Alternatively, select the package, and click **Edit**.
|
||||
|
||||
2. Using the list of **AD Entities with Access**, select the AD group that you want to customize. Select **Custom** from the drop-down list, if it is not already selected. A link named **Edit** will be displayed.
|
||||
|
||||
3. Click **Edit**. The Dynamic User Configuration that is assigned to the AD Group will be displayed.
|
||||
|
||||
4. Click **Advanced**, and then click **Export Configuration**. Type in a filename and click **Save**. Now you can edit the file to configure a package for a user.
|
||||
|
||||
**Note**
|
||||
To export a configuration while running on Windows Server, you must disable "IE Enhanced Security Configuration". If this is enabled and set to block downloads, you cannot download anything from the App-V Server.
|
||||
|
||||
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,55 @@
|
||||
---
|
||||
title: How to Create a Package Accelerator by Using PowerShell (Windows 10)
|
||||
description: How to Create a Package Accelerator by Using PowerShell
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Create a Package Accelerator by Using PowerShell
|
||||
|
||||
|
||||
App-V package accelerators automatically sequence large, complex applications. Additionally, when you apply an App-V package accelerator, you are not always required to manually install an application to create the virtualized package.
|
||||
|
||||
**To create a package accelerator**
|
||||
|
||||
1. Install the App-V sequencer. For more information about installing the sequencer see [How to Install the Sequencer](appv-install-the-sequencer.md).
|
||||
|
||||
2. To open a PowerShell console click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**. Use the **New-AppvPackageAccelerator** cmdlet.
|
||||
|
||||
3. To create a package accelerator, make sure that you have the .appv package to create an accelerator from, the installation media or installation files, and optionally a read me file for consumers of the accelerator to use. The following parameters are required to use the package accelerator cmdlet:
|
||||
|
||||
- **InstalledFilesPath** - specifies the application installation path.
|
||||
|
||||
- **Installer** – specifies the path to the application installer media
|
||||
|
||||
- **InputPackagePath** – specifies the path to the .appv package
|
||||
|
||||
- **Path** – specifies the output directory for the package.
|
||||
|
||||
The following example displays how you can create a package accelerator with an .appv package and the installation media:
|
||||
|
||||
**New-AppvPackageAccelerator -InputPackagePath <path to the .appv file> -Installer <path to the installer executable> -Path <directory of the output path>**
|
||||
|
||||
Additional optional parameters that can be used with the **New-AppvPackageAccelerator** cmdlet are displayed in the following list:
|
||||
|
||||
- **AcceleratorDescriptionFile** - specifies the path to user created package accelerator instructions. The package accelerator instructions are **.txt** or **.rtf** description files that will be packaged with the package created using the package accelerator.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
107
windows/manage/appv-create-a-package-accelerator.md
Normal file
107
windows/manage/appv-create-a-package-accelerator.md
Normal file
@ -0,0 +1,107 @@
|
||||
---
|
||||
title: How to Create a Package Accelerator (Windows 10)
|
||||
description: How to Create a Package Accelerator
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Create a Package Accelerator
|
||||
|
||||
|
||||
App-V package accelerators automatically generate new virtual application packages.
|
||||
|
||||
**Note**
|
||||
You can use PowerShell to create a package accelerator. For more information see [How to Create a Package Accelerator by Using PowerShell](appv-create-a-package-accelerator-with-powershell.md).
|
||||
|
||||
|
||||
|
||||
Use the following procedure to create a package accelerator.
|
||||
|
||||
**Important**
|
||||
Package Accelerators can contain password and user-specific information. Therefore you must save Package Accelerators and the associated installation media in a secure location, and you should digitally sign the Package Accelerator after you create it so that the publisher can be verified when the App-V Package Accelerator is applied.
|
||||
|
||||
|
||||
|
||||
**Important**
|
||||
Before you begin the following procedure, you should perform the following:
|
||||
|
||||
- Copy the virtual application package that you will use to create the package accelerator locally to the computer running the sequencer.
|
||||
|
||||
- Copy all required installation files associated with the virtual application package to the computer running the sequencer.
|
||||
|
||||
|
||||
|
||||
**To create a package accelerator**
|
||||
|
||||
1. **Important**
|
||||
The App-V Sequencer does not grant any license rights to the software application you are using to create the Package Accelerator. You must abide by all end user license terms for the application you are using. It is your responsibility to make sure the software application’s license terms allow you to create a Package Accelerator using App-V Sequencer.
|
||||
|
||||
|
||||
|
||||
To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. To start the App-V **Create Package Accelerator** wizard, in the App-V sequencer console, click **Tools** / **Create Accelerator**.
|
||||
|
||||
3. On the **Select Package** page, to specify an existing virtual application package to use to create the Package Accelerator, click **Browse**, and locate the existing virtual application package (.appv file).
|
||||
|
||||
**Tip**
|
||||
Copy the files associated with the virtual application package you plan to use locally to the computer running the Sequencer.
|
||||
|
||||
|
||||
|
||||
Click **Next**.
|
||||
|
||||
4. On the **Installation Files** page, to specify the folder that contains the installation files that you used to create the original virtual application package, click **Browse**, and then select the directory that contains the installation files.
|
||||
|
||||
**Tip**
|
||||
Copy the folder that contains the required installation files to the computer running the Sequencer.
|
||||
|
||||
|
||||
|
||||
5. If the application is already installed on the computer running the sequencer, to specify the installation file, select **Files installed on local system**. To use this option, the application must already be installed in the default installation location.
|
||||
|
||||
6. On the **Gathering Information** page, review the files that were not found in the location specified on the **Installation Files** page of this wizard. If the files displayed are not required, select **Remove these files**, and then click **Next**. If the files are required, click **Previous** and copy the required files to the directory specified on the **Installation Files** page.
|
||||
|
||||
**Note**
|
||||
You must either remove the unrequired files, or click **Previous** and locate the required files to advance to the next page of this wizard.
|
||||
|
||||
|
||||
|
||||
7. On the **Select Files** page, carefully review the files that were detected, and clear any file that should be removed from the package accelerator. Select only files that are required for the application to run successfully, and then click **Next**.
|
||||
|
||||
8. On the **Verify Applications** page, confirm that all installation files that are required to build the package are displayed. When the Package Accelerator is used to create a new package, all installation files displayed in the **Applications** pane are required to create the package.
|
||||
|
||||
If necessary, to add additional Installer files, click **Add**. To remove unnecessary installation files, select the Installer file, and then click **Delete**. To edit the properties associated with an installer, click **Edit**. The installation files specified in this step will be required when the Package Accelerator is used to create a new virtual application package. After you have confirmed the information displayed, click **Next**.
|
||||
|
||||
9. On the **Select Guidance** page, to specify a file that contains information about how the Package Accelerator, click **Browse**. For example, this file can contain information about how the computer running the Sequencer should be configured, application prerequisite information for target computers, and general notes. You should provide all required information for the Package Accelerator to be successfully applied. The file you select must be in rich text (.rtf) or text file (.txt) format. Click **Next**.
|
||||
|
||||
10. On the **Create Package Accelerator** page, to specify where to save the Package Accelerator, click **Browse** and select the directory.
|
||||
|
||||
11. On the **Completion** page, to close the **Create Package Accelerator** wizard, click **Close**.
|
||||
|
||||
**Important**
|
||||
To help ensure that the package accelerator is as secure as possible, and so that the publisher can be verified when the package accelerator is applied, you should always digitally sign the package accelerator.
|
||||
|
||||
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
[How to Create a Virtual Application Package Using an App-V Package Accelerator](appv-create-a-virtual-application-package-package-accelerator.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,101 @@
|
||||
---
|
||||
title: How to Create a Virtual Application Package Using an App-V Package Accelerator (Windows 10)
|
||||
description: How to Create a Virtual Application Package Using an App-V Package Accelerator
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Create a Virtual Application Package Using an App-V Package Accelerator
|
||||
|
||||
|
||||
**Important**
|
||||
The App-V Sequencer does not grant any license rights to the software application that you use to create the Package Accelerator. You must abide by all end user license terms for the application that you use. It is your responsibility to make sure that the software application’s license terms allow you to create a Package Accelerator with the App-V Sequencer.
|
||||
|
||||
|
||||
|
||||
Use the following procedure to create a virtual application package with the App-V Package Accelerator.
|
||||
|
||||
**Note**
|
||||
Before you start this procedure, copy the required Package Accelerator locally to the computer that runs the App-V Sequencer. You should also copy all required installation files for the package to a local directory on the computer that runs the Sequencer. This is the directory that you have to specify in step 5 of this procedure.
|
||||
|
||||
|
||||
|
||||
**To create a virtual application package with an App-V Package Accelerator**
|
||||
|
||||
1. To start the App-V Sequencer, on the computer that runs the App-V Sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. To start the **Create New Package Wizard**, click **Create a New Virtual Application Package**. To create the package, select the **Create Package using a Package Accelerator** check box, and then click **Next**.
|
||||
|
||||
3. To specify the package accelerator that will be used to create the new virtual application package, click **Browse** on the **Select Package Accelerator** page. Click **Next**.
|
||||
|
||||
**Important**
|
||||
If the publisher of the package accelerator cannot be verified and does not contain a valid digital signature, then before you click **Run**, you must confirm that you trust the source of the package accelerator. Confirm your choice in the **Security Warning** dialog box.
|
||||
|
||||
|
||||
|
||||
4. On the **Guidance** page, review the publishing guidance information that is displayed in the information pane. This information was added when the Package Accelerator was created and it contains guidance about how to create and publish the package. To export the guidance information to a text (.txt) file, click **Export** and specify the location where the file should be saved, and then click **Next**.
|
||||
|
||||
5. On the **Select Installation Files** page, click **Make New Folder** to create a local folder that contains all required installation files for the package, and specify where the folder should be saved. You must also specify a name to be assigned to the folder. You must then copy all required installation files to the location that you specified. If the folder that contains the installation files already exists on the computer that runs the Sequencer, click **Browse** to select the folder.
|
||||
|
||||
Alternatively, if you have already copied the installation files to a directory on this computer, click **Make New Folder**, browse to the folder that contains the installation files, and then click **Next**.
|
||||
|
||||
**Note**
|
||||
You can specify the following types of supported installation files:
|
||||
|
||||
- Windows Installer files (**.msi**)
|
||||
|
||||
- Cabinet files (.cab)
|
||||
|
||||
- Compressed files with a .zip file name extension
|
||||
|
||||
- The actual application files
|
||||
|
||||
The following file types are not supported: **.msp** and **.exe** files. If you specify an **.exe** file, you must extract the installation files manually.
|
||||
|
||||
|
||||
|
||||
If the package accelerator requires an application to be installed before you apply the Package Accelerator, and if you have already installed the required application, select **I have installed all applications**, and then click **Next** on the **Local Installation** page.
|
||||
|
||||
6. On the **Package Name** page, specify a name that will be associated with the package. The name that you specify identifies the package in the App-V Management Console. Click **Next**.
|
||||
|
||||
7. On the **Create Package** page, provide comments that will be associated with the package. The comments should contain identifying information about the package that you are creating. To confirm the location where the package is created, review the information that is displayed in **Save Location**. To compress the package, select **Compress Package**. Select the **Compress Package** check box if the package will be streamed across the network, or when the package size exceeds 4 GB.
|
||||
|
||||
To create the package, click **Create**. After the package is created, click **Next**.
|
||||
|
||||
8. On the **Configure Software** page, to enable the Sequencer to configure the applications that are contained in the package, select **Configure Software**. In this step you can configure any associated tasks that must be completed in order to run the application on the target computers. For example, you can configure any associated license agreements.
|
||||
|
||||
If you select **Configure Software**, the following items can be configured using the Sequencer as part of this step:
|
||||
|
||||
- **Load Package**. The Sequencer loads the files that are associated with the package. It can take several seconds to an hour to decode the package.
|
||||
|
||||
- **Run Each Program**. Optionally run the programs that are contained in the package. This step is helpful to complete any associated license or configuration tasks that are required to run the application before you deploy and run the package on target computers. To run all the programs at once, select at least one program, and then click **Run All**. To run specific programs, select the program or programs that you want to run, and then click **Run Selected**. Complete the required configuration tasks, and then close the applications. It can take several minutes for all programs to run. Click **Next**.
|
||||
|
||||
- **Save Package**. The Sequencer saves the package.
|
||||
|
||||
- **Primary Feature Block**. The Sequencer optimizes the package for streaming by rebuilding the primary feature block.
|
||||
|
||||
If you do not want to configure the applications, click **Skip this step**, and to go to step 9 of this procedure, and then click **Next**.
|
||||
|
||||
9. On the **Completion** page, after you review the information that is displayed in the **Virtual Application Package Report** pane, click **Close**.
|
||||
|
||||
The package is now available in the Sequencer. To edit the package properties, click **Edit \[Package Name\]**. For more information about how to modify a package, see [How to Modify an Existing Virtual Application Package](appv-modify-an-existing-virtual-application-package.md).
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
70
windows/manage/appv-create-and-use-a-project-template.md
Normal file
70
windows/manage/appv-create-and-use-a-project-template.md
Normal file
@ -0,0 +1,70 @@
|
||||
---
|
||||
title: How to Create and Use a Project Template (Windows 10)
|
||||
description: How to Create and Use a Project Template
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Create and Use a Project Template
|
||||
|
||||
|
||||
You can use an App-V project template to save commonly applied settings associated with an existing virtual application package. These settings can then be applied when you create new virtual application packages in your environment. Using a project template can streamline the process of creating virtual application packages.
|
||||
|
||||
**Note**
|
||||
You can, and often should apply an App-V project template during a package upgrade. For example, if you sequenced an application with a custom exclusion list, it is recommended that an associated template is created and saved for later use while upgrading the sequenced application.
|
||||
|
||||
|
||||
|
||||
App-V project templates differ from App-V Application Accelerators because App-V Application Accelerators are application-specific, and App-V project templates can be applied to multiple applications.
|
||||
|
||||
Use the following procedures to create and apply a new template.
|
||||
|
||||
**To create a project template**
|
||||
|
||||
1. To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. **Note**
|
||||
If the virtual application package is currently open in the App-V Sequencer console, skip to step 3 of this procedure.
|
||||
|
||||
|
||||
|
||||
To open the existing virtual application package that contains the settings you want to save with the App-V project template, click **File** / **Open**, and then click **Edit Package**. On the **Select Package** page, click **Browse** and locate the virtual application package that you want to open. Click **Edit**.
|
||||
|
||||
3. In the App-V Sequencer console, to save the template file, click **File** / **Save As Template**. After you have reviewed the settings that will be saved with the new template, click **OK**. Specify a name that will be associated with the new App-V project template. Click Save.
|
||||
|
||||
The new App-V project template is saved in the directory specified in step 3 of this procedure.
|
||||
|
||||
**To apply a project template**
|
||||
|
||||
1. **Important**
|
||||
Creating a virtual application package using a project template in conjunction with a Package Accelerator is not supported.
|
||||
|
||||
|
||||
|
||||
To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. To create or upgrade a new virtual application package by using an App-V project template, click **File** / **New From Template**.
|
||||
|
||||
3. To select the project template that you want to use, browse to the directory where the project template is saved, select the project template, and then click **Open**.
|
||||
|
||||
Create the new virtual application package. The settings saved with the specified template will be applied to the new virtual application package that you are creating.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,211 @@
|
||||
---
|
||||
title: Creating and Managing App-V Virtualized Applications (Windows 10)
|
||||
description: Creating and Managing App-V Virtualized Applications
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Creating and Managing App-V Virtualized Applications
|
||||
|
||||
|
||||
After you have properly deployed the Microsoft Application Virtualization (App-V) sequencer, you can use it to monitor and record the installation and setup process for an application to be run as a virtualized application.
|
||||
|
||||
**Note**
|
||||
For more information about configuring the App-V sequencer, sequencing best practices, and an example of creating and updating a virtual application, see the [Microsoft Application Virtualization 5.0 Sequencing Guide](http://download.microsoft.com/download/F/7/8/F784A197-73BE-48FF-83DA-4102C05A6D44/App-V 5.0 Sequencing Guide.docx).
|
||||
|
||||
**Note**
|
||||
The App-V Sequencer cannot sequence applications with filenames matching "CO_<x>" where x is any numeral. Error 0x8007139F will be generated.
|
||||
|
||||
## Sequencing an application
|
||||
|
||||
|
||||
You can use the App-V Sequencer to perform the following tasks:
|
||||
|
||||
- Create virtual packages that can be deployed to computers running the App-V client.
|
||||
|
||||
- Upgrade existing packages. You can expand an existing package onto the computer running the sequencer and then upgrade the application to create a newer version.
|
||||
|
||||
- Edit configuration information associated with an existing package. For example, you can add a shortcut or modify a file type association.
|
||||
|
||||
**Note**
|
||||
You must create shortcuts and save them to an available network location to allow roaming. If a shortcut is created and saved in a private location, the package must be published locally to the computer running the App-V client.
|
||||
|
||||
- Convert existing virtual packages.
|
||||
|
||||
The sequencer uses the **%TMP% \\ Scratch** or **%TEMP% \\ Scratch** directory and the **Temp** directory to store temporary files during sequencing. On the computer that runs the sequencer, you should configure these directories with free disk space equivalent to the estimated application installation requirements. Configuring the temp directories and the Temp directory on different hard drive partitions can help improve performance during sequencing.
|
||||
|
||||
When you use the sequencer to create a new virtual application, the following listed files are created. These files comprise the App-V package.
|
||||
|
||||
- .msi file. This Windows Installer (.msi) file is created by the sequencer and is used to install the virtual package on target computers.
|
||||
|
||||
- Report.xml file. In this file, the sequencer saves all issues, warnings, and errors that were discovered during sequencing. It displays the information after the package has been created. You can us this report for diagnosing and troubleshooting.
|
||||
|
||||
- .appv file. This is the virtual application file.
|
||||
|
||||
- Deployment configuration file. The deployment configuration file determines how the virtual application will be deployed to target computers.
|
||||
|
||||
- User configuration file. The user configuration file determines how the virtual application will run on target computers.
|
||||
|
||||
**Important**
|
||||
You must configure the %TMP% and %TEMP% folders that the package converter uses to be a secure location and directory. A secure location is only accessible by an administrator. Additionally, when you sequence the package you should save the package to a location that is secure, or make sure that no other user is allowed to be logged in during the conversion and monitoring process.
|
||||
|
||||
The **Options** dialog box in the sequencer console contains the following tabs:
|
||||
|
||||
- **General**. Use this tab to enable Microsoft Updates to run during sequencing. Select **Append Package Version to Filename** to configure the sequence to add a version number to the virtualized package that is being sequenced. Select **Always trust the source of Package Accelerators** to create virtualized packages using a package accelerator without being prompted for authorization.
|
||||
|
||||
**Important**
|
||||
Package Accelerators created using App-V 4.6 are not supported by App-V.
|
||||
|
||||
- **Parse Items**. This tab displays the associated file path locations that will be parsed or tokenized into in the virtual environment. Tokens are useful for adding files using the **Package Files** tab in **Advanced Editing**.
|
||||
|
||||
- **Exclusion Items**. Use this tab to specify which folders and directories should not be monitored during sequencing. To add local application data that is saved in the Local App Data folder in the package, click **New** and specify the location and the associated **Mapping Type**. This option is required for some packages.
|
||||
|
||||
App-V supports applications that include Microsoft Windows Services. If an application includes a Windows service, the Service will be included in the sequenced virtual package as long as it is installed while being monitored by the sequencer. If a virtual application creates a Windows service when it initially runs, then later, after installation, the application must be run while the sequencer is monitoring so that the Windows Service will be added to the package. Only Services that run under the Local System account are supported. Services that are configured for AutoStart or Delayed AutoStart are started before the first virtual application in a package runs inside the package’s Virtual Environment. Windows Services that are configured to be started on demand by an application are started when the virtual application inside the package starts the Service via API call.
|
||||
|
||||
[How to Sequence a New Application with App-V](appv-sequence-a-new-application.md)
|
||||
|
||||
## <a href="" id="---------app-v-5-1-shell-extension-support"></a> App-V shell extension support
|
||||
|
||||
|
||||
App-V supports shell extensions. Shell extensions will be detected and embedded in the package during sequencing.
|
||||
|
||||
Shell extensions are embedded in the package automatically during the sequencing process. When the package is published, the shell extension gives users the same functionality as if the application were locally installed.
|
||||
|
||||
**Requirements for using shell extensions:**
|
||||
|
||||
- Packages that contain embedded shell extensions must be published globally. The application requires no additional setup or configuration on the client to enable the shell extension functionality.
|
||||
|
||||
- The “bitness” of the application, Sequencer, and App-V client must match, or the shell extensions won’t work. For example:
|
||||
|
||||
- The version of the application is 64-bit.
|
||||
|
||||
- The Sequencer is running on a 64-bit computer.
|
||||
|
||||
- The package is being delivered to a 64-bit App-V client computer.
|
||||
|
||||
The following table lists the supported shell extensions:
|
||||
|
||||
<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.
|
||||
|
||||
The following table displays the file types that can exist in a virtual package under the VFS directory, but cannot be updated on the computer running the App-V client. All other files and directories can be modified.
|
||||
|
||||
| File Type | | | | | |
|
||||
|------------ |------------- |------------- |------------ |------------ |------------ |
|
||||
| .acm | .asa | .asp | .aspx | .ax | .bat |
|
||||
| .cer | .chm | .clb | .cmd | .cnt | .cnv |
|
||||
| .com | .cpl | .cpx | .crt | .dll | .drv |
|
||||
| .esc | .exe | .fon | .grp | .hlp | .hta |
|
||||
| .ime | .inf | .ins | .isp | .its | .js |
|
||||
| .jse | .lnk | .msc | .msi | .msp | .mst |
|
||||
| .mui | .nls | .ocx | .pal | .pcd | .pif |
|
||||
| .reg | .scf | .scr | .sct | .shb | .shs |
|
||||
| .sys | .tlb | .tsp | .url | .vb | .vbe |
|
||||
| .vbs | .vsmacros | .ws | .wsf | .wsh | |
|
||||
|
||||
|
||||
## Modifying an existing virtual application package
|
||||
|
||||
|
||||
You can use the sequencer to modify an existing package. The computer on which you do this should match the chip architecture of the computer you used to create the application. For example, if you initially sequenced a package using a computer running a 64-bit operating system, you should modify the package using a computer running a 64-bit operating system.
|
||||
|
||||
[How to Modify an Existing Virtual Application Package](appv-modify-an-existing-virtual-application-package.md)
|
||||
|
||||
## Creating a project template
|
||||
|
||||
|
||||
A .appvt file is a project template that can be used to save commonly applied, customized settings. You can then more easily use these settings for future sequencings.
|
||||
|
||||
App-V project templates differ from App-V Application Accelerators because App-V Application Accelerators are application-specific, and App-V project templates can be applied to multiple applications. Additionally, you cannot use a project template when you use a Package Accelerator to create a virtual application package. The following general settings are saved with an App-V project template:
|
||||
|
||||
A template can specify and store multiple settings as follows:
|
||||
|
||||
- **Advanced Monitoring Options**. Enables Microsoft Update to run during monitoring. Saves allow local interaction option settings
|
||||
|
||||
- **General Options**. Enables the use of **Windows Installer**, **Append Package Version to Filename**.
|
||||
|
||||
- **Exclusion Items.** Contains the Exclusion pattern list.
|
||||
|
||||
[How to Create and Use a Project Template](appv-create-and-use-a-project-template.md)
|
||||
|
||||
## Creating a package accelerator
|
||||
|
||||
|
||||
**Note**
|
||||
Package accelerators created using a previous version of App-V must be recreated using App-V.
|
||||
|
||||
You can use App-V package accelerators to automatically generate a new virtual application packages. After you have successfully created a package accelerator, you can reuse and share the package accelerator.
|
||||
|
||||
In some situations, to create the package accelerator, you might have to install the application locally on the computer that runs the sequencer. In such cases, you should first try to create the package accelerator with the installation media. If multiple missing files are required, you should install the application locally to the computer that runs the sequencer, and then create the package accelerator.
|
||||
|
||||
After you have successfully created a Package Accelerator, you can reuse and share the Package Accelerator. Creating App-V Package Accelerators is an advanced task. Package Accelerators can contain password and user-specific information. Therefore you must save Package Accelerators and the associated installation media in a secure location, and you should digitally sign the Package Accelerator after you create it so that the publisher can be verified when the App-V Package Accelerator is applied.
|
||||
|
||||
[How to Create a Package Accelerator](appv-create-a-package-accelerator.md)
|
||||
|
||||
[How to Create a Virtual Application Package Using an App-V Package Accelerator](appv-create-a-virtual-application-package-package-accelerator.md)
|
||||
|
||||
## Sequencer error reporting
|
||||
|
||||
|
||||
The App-V Sequencer can detect common sequencing issues during sequencing. The **Installation Report** page at the end of the sequencing wizard displays diagnostic messages categorized into **Errors**, **Warnings**, and **Info** depending on the severity of the issue.
|
||||
|
||||
You can also find additional information about sequencing errors using the Windows Event Viewer.
|
||||
|
||||
|
||||
## <a href="" id="other-resources-for-the-app-v-5-1-sequencer-"></a>Other resources for the App-V sequencer
|
||||
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
|
||||
@ -0,0 +1,45 @@
|
||||
---
|
||||
title: How to Customize Virtual Applications Extensions for a Specific AD Group by Using the Management Console (Windows 10)
|
||||
description: How to Customize Virtual Applications Extensions for a Specific AD Group by Using the Management Console
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Customize Virtual Applications Extensions for a Specific AD Group by Using the Management Console
|
||||
|
||||
|
||||
Use the following procedure to customize the virtual application extensions for an Active Directory (AD) group.
|
||||
|
||||
**To customize virtual applications extensions for an AD group**
|
||||
|
||||
1. To view the package that you want to configure, open the App-V Management Console. To view the configuration that is assigned to a given user group, select the package, and right-click the package name and select **Edit active directory access**. Alternatively, select the package and click **EDIT** in the **AD ACCESS** pane.
|
||||
|
||||
2. To customize an AD group, you can find the group from the list of **AD Entities with Access**. Then, using the drop-down box in the **Assigned Configuration** pane, select **Custom**, and then click **EDIT**.
|
||||
|
||||
3. To disable all extensions for a given application, clear **ENABLE**.
|
||||
|
||||
To add a new shortcut for the selected application, right-click the application in the **SHORTCUTS** pane, and select **Add new shortcut**. To remove a shortcut, right-click the application in the **SHORTCUTS** pane, and select **Remove Shortcut**. To edit an existing shortcut, right-click the application, and select **Edit Shortcut**.
|
||||
|
||||
4. To view any other application extensions, click **Advanced**, and click **Export Configuration**. Type in a filename and click **Save**. You can view all application extensions that are associated with the package using the configuration file.
|
||||
|
||||
5. To edit additional application extensions, modify the configuration file and click **Import and Overwrite this Configuration**. Select the modified file and click **Open**. In the dialog, click **Overwrite** to complete the process.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
39
windows/manage/appv-delete-a-connection-group.md
Normal file
39
windows/manage/appv-delete-a-connection-group.md
Normal file
@ -0,0 +1,39 @@
|
||||
---
|
||||
title: How to Delete a Connection Group (Windows 10)
|
||||
description: How to Delete a Connection Group
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Delete a Connection Group
|
||||
|
||||
|
||||
Use the following procedure to delete an existing App-V connection group.
|
||||
|
||||
**To delete a connection group**
|
||||
|
||||
1. Open the App-V Management Console and select **CONNECTION GROUPS**.
|
||||
|
||||
2. Right-click the connection group to be removed, and select **delete**.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
[Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,37 @@
|
||||
---
|
||||
title: How to Delete a Package in the Management Console (Windows 10)
|
||||
description: How to Delete a Package in the Management Console
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Delete a Package in the Management Console
|
||||
|
||||
|
||||
Use the following procedure to delete an App-V package.
|
||||
|
||||
**To delete a package in the Management Console**
|
||||
|
||||
1. To view the package you want to delete, open the App-V Management Console and select **Packages**. Select the package to be removed.
|
||||
|
||||
2. Click or right-click the package. Select **Delete** to remove the package.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
183
windows/manage/appv-deploy-appv-databases-with-sql-scripts.md
Normal file
183
windows/manage/appv-deploy-appv-databases-with-sql-scripts.md
Normal file
@ -0,0 +1,183 @@
|
||||
---
|
||||
title: How to Deploy the App-V Databases by Using SQL Scripts (Windows 10)
|
||||
description: How to Deploy the App-V Databases by Using SQL Scripts
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Deploy the App-V Databases by Using SQL Scripts
|
||||
|
||||
Use the following instructions to use SQL scripts, rather than the Windows Installer, to:
|
||||
|
||||
- Install the App-V databases
|
||||
|
||||
- Upgrade the App-V databases to a later version
|
||||
|
||||
> [!NOTE]
|
||||
> If you have already deployed an App-V 5.0 SP3 database or later, the SQL scripts are not required to upgrade to App-V.
|
||||
|
||||
## How to install the App-V databases by using SQL scripts
|
||||
|
||||
1. Before you install the database scripts, review and keep a copy of the App-V license terms. By running the database scripts, you are agreeing to the license terms. If you do not accept them, you should not use this software.
|
||||
|
||||
2. Copy the **appv\_server\_setup.exe** from the App-V release media to a temporary location.
|
||||
|
||||
3. From a command prompt, run **appv\_server\_setup.exe** and specify a temporary location for extracting the database scripts.
|
||||
|
||||
Example: appv\_server\_setup.exe /layout c:\\_<temporary location path>_
|
||||
|
||||
4. Browse to the temporary location that you created, open the extracted **DatabaseScripts** folder, and review the appropriate readme.txt file for instructions:
|
||||
|
||||
| Database | Location of readme.txt file to use
|
||||
| - | - |
|
||||
| Management database | ManagementDatabase subfolder |
|
||||
| Reporting database | ReportingDatabase subfolder |
|
||||
|
||||
> [!CAUTION]
|
||||
> The readme.txt file in the ManagementDatabase subfolder is out of date. The information in the updated readme files below is the most current and should supersede the readme information provided in the **DatabaseScripts** folders.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The InsertVersionInfo.sql script is not required for versions of the App-V management database later than App-V 5.0 SP3.
|
||||
> The Permissions.sql script should be updated according to **Step 2** in [KB article 3031340](https://support.microsoft.com/kb/3031340). **Step 1** is not required for versions of App-V later than App-V 5.0 SP3.
|
||||
|
||||
### Updated management database README file content
|
||||
|
||||
``` syntax
|
||||
***********************************************************************************************************
|
||||
Before you install and use the Application Virtualization Database Scripts, you must:
|
||||
|
||||
- Review the license terms.
|
||||
- Print and retain a copy of the license terms for your records.
|
||||
|
||||
By running the App-V you agree to such license terms. If you do not accept them, do not use the software.
|
||||
***********************************************************************************************************
|
||||
|
||||
Steps to install "AppVManagement" schema in SQL SERVER.
|
||||
|
||||
## PREREQUISITES:
|
||||
|
||||
1. Review the installation package. The following files MUST exist:
|
||||
|
||||
SQL files
|
||||
---------
|
||||
Database.sql
|
||||
CreateTables.sql
|
||||
CreateStoredProcs.sql
|
||||
UpdateTables.sql
|
||||
Permissions.sql
|
||||
|
||||
2. Ensure the target SQL Server instance and SQL Server Agent service are running.
|
||||
|
||||
3. If you are not running the scripts directly on the server, ensure the
|
||||
necessary SQL Server client software is installed and available from
|
||||
the specified location. Specifically, the "osql" command must be supported for these scripts to run.
|
||||
|
||||
## PREPARATION:
|
||||
|
||||
1. Review the database.sql file and modify as necessary. Although the
|
||||
defaults are likely sufficient, it is suggested that the following
|
||||
settings be reviewed:
|
||||
|
||||
DATABASE - ensure name is satisfactory - default is "AppVManagement".
|
||||
|
||||
2. Review the Permissions.sql file and provide all the necessary account information
|
||||
for setting up read and write access on the database. Note: Default settings in the file will not work.
|
||||
|
||||
## INSTALLATION:
|
||||
|
||||
1. Run the database.sql against the "master" database. Your user
|
||||
credential must have the ability to create databases.
|
||||
This script will create the database.
|
||||
|
||||
2. Run the following scripts against the "AppVManagement" database using the
|
||||
same account as above in order.
|
||||
|
||||
CreateTables.sql
|
||||
CreateStoredProcs.sql
|
||||
UpdateTables.sql
|
||||
Permissions.sql
|
||||
|
||||
```
|
||||
|
||||
### Updated reporting database README file content
|
||||
|
||||
``` syntax
|
||||
***********************************************************************************************************
|
||||
Before you install and use the Application Virtualization Database Scripts, you must:
|
||||
|
||||
- Review the license terms.
|
||||
- Print and retain a copy of the license terms for your records.
|
||||
|
||||
By running the App-V you agree to such license terms. If you do not accept them, do not use the software.
|
||||
***********************************************************************************************************
|
||||
|
||||
Steps to install "AppVReporting" schema in SQL SERVER.
|
||||
|
||||
## PREREQUISITES:
|
||||
|
||||
1. Review the installation package. The following files MUST exist:
|
||||
|
||||
SQL files
|
||||
---------
|
||||
Database.sql
|
||||
UpgradeDatabase.sql
|
||||
CreateTables.sql
|
||||
CreateReportingStoredProcs.sql
|
||||
CreateStoredProcs.sql
|
||||
CreateViews.sql
|
||||
Permissions.sql
|
||||
ScheduleReportingJob.sql
|
||||
|
||||
2. Ensure the target SQL Server instance and SQL Server Agent service are running.
|
||||
|
||||
3. If you are not running the scripts directly on the server, ensure the
|
||||
necessary SQL Server client software is installed and executable from
|
||||
the location you have chosen. Specifically, the "osql" command must be supported for these scripts to run.
|
||||
|
||||
## PREPARATION:
|
||||
|
||||
1. Review the database.sql file and modify as necessary. Although the
|
||||
defaults are likely sufficient, it is suggested that the following
|
||||
settings be reviewed:
|
||||
|
||||
DATABASE - ensure name is satisfactory - default is "AppVReporting".
|
||||
|
||||
2. Review the Permissions.sql file and provide all the necessary account information
|
||||
for setting up read and write access on the database. Note: Default settings
|
||||
in the file will not work.
|
||||
|
||||
3. Review the ScheduleReportingJob.sql file and make sure that the stored proc schedule
|
||||
time is acceptable. The default stored proc schedule time is at 12.01 AM (line 84).
|
||||
If this time is not suitable, you can change this to a more suitable time. The time is in the format HHMMSS.
|
||||
|
||||
## INSTALLATION:
|
||||
|
||||
1. Run the database.sql against the "master" database. Your user
|
||||
credential must have the ability to create databases.
|
||||
This script will create the database.
|
||||
|
||||
2. If upgrading the database, run UpgradeDatabase.sql This will upgrade database schema.
|
||||
|
||||
2. Run the following scripts against the "AppVReporting" database using the
|
||||
same account as above in order.
|
||||
|
||||
CreateTables.sql
|
||||
CreateReportingStoredProcs.sql
|
||||
CreateStoredProcs.sql
|
||||
CreateViews.sql
|
||||
Permissions.sql
|
||||
ScheduleReportingJob.sql
|
||||
```
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
- [How to Deploy the App-V Server](appv-deploy-the-appv-server.md)
|
||||
@ -0,0 +1,41 @@
|
||||
---
|
||||
title: How to deploy App-V Packages Using Electronic Software Distribution (Windows 10)
|
||||
description: How to deploy App-V Packages Using Electronic Software Distribution
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to deploy App-V packages using electronic software distribution
|
||||
|
||||
You can use an electronic software distribution (ESD) system to deploy App-V virtual applications to App-V clients.
|
||||
|
||||
For component requirements and options for using an ESD to deploy App-V packages, see [Planning to Deploy App-V with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md).
|
||||
|
||||
Use one of the following methods to publish packages to App-V client computers with an ESD:
|
||||
|
||||
| Method | Description |
|
||||
| - | - |
|
||||
| Functionality provided by a third-party ESD | Use the functionality in a third-party ESD.|
|
||||
| Stand-alone Windows Installer | Install the application on the target client computer by using the associated Windows Installer (.msi) file that is created when you initially sequence an application. The Windows Installer file contains the associated App-V package file information used to configure a package and copies the required package files to the client. |
|
||||
| Windows PowerShell | Use Windows PowerShell cmdlets to deploy virtualized applications. For more information about using PowerShell and App-V, see [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md).|
|
||||
|
||||
|
||||
|
||||
**To deploy App-V packages by using an ESD**
|
||||
|
||||
1. Install the App-V Sequencer on a computer in your environment. For more information about installing the sequencer, see [How to Install the Sequencer](appv-install-the-sequencer.md).
|
||||
|
||||
2. Use the App-V Sequencer to create virtual application. For information about creating a virtual application, see [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md).
|
||||
|
||||
3. After you create the virtual application, deploy the package by using your ESD solution.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
789
windows/manage/appv-deploy-the-appv-server-with-a-script.md
Normal file
789
windows/manage/appv-deploy-the-appv-server-with-a-script.md
Normal file
@ -0,0 +1,789 @@
|
||||
---
|
||||
title: How to Deploy the App-V Server Using a Script (Windows 10)
|
||||
description: How to Deploy the App-V Server Using a Script
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Deploy the App-V Server Using a Script
|
||||
|
||||
|
||||
In order to complete the **appv\_server\_setup.exe** Server setup successfully using the command line, you must specify and combine multiple parameters.
|
||||
|
||||
**To Install the App-V server using a script**
|
||||
|
||||
- Use the following tables for more information about installing the App-V server using the command line.
|
||||
|
||||
**Note**
|
||||
The information in the following tables can also be accessed using the command line by typing the following command: **appv\_server\_setup.exe /?**.
|
||||
|
||||
|
||||
|
||||
**Common parameters and Examples**
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>To Install the Management server and Management database on a local machine.</p></td>
|
||||
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
|
||||
<ul>
|
||||
<li><p>/MANAGEMENT_SERVER</p></li>
|
||||
<li><p>/MANAGEMENT_ADMINACCOUNT</p></li>
|
||||
<li><p>/MANAGEMENT_WEBSITE_NAME</p></li>
|
||||
<li><p>/MANAGEMENT_WEBSITE_PORT</p></li>
|
||||
<li><p>/DB_PREDEPLOY_MANAGEMENT</p></li>
|
||||
<li><p>/MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT</p></li>
|
||||
<li><p>/MANAGEMENT_DB_NAME</p></li>
|
||||
</ul>
|
||||
<p>To use a custom instance of Microsoft SQL Server, use the following parameters:</p>
|
||||
<ul>
|
||||
<li><p>/MANAGEMENT_SERVER</p></li>
|
||||
<li><p>/MANAGEMENT_ADMINACCOUNT</p></li>
|
||||
<li><p>/MANAGEMENT_WEBSITE_NAME</p></li>
|
||||
<li><p>/MANAGEMENT_WEBSITE_PORT</p></li>
|
||||
<li><p>/DB_PREDEPLOY_MANAGEMENT</p></li>
|
||||
<li><p>/MANAGEMENT_DB_CUSTOM_SQLINSTANCE</p></li>
|
||||
<li><p>/MANAGEMENT_DB_NAME</p></li>
|
||||
</ul>
|
||||
<p>Using a custom instance of Microsoft SQL Server example:</p>
|
||||
<p>/appv_server_setup.exe /QUIET</p>
|
||||
<p>/MANAGEMENT_SERVER</p>
|
||||
<p>/MANAGEMENT_ADMINACCOUNT=”Domain\AdminGroup”</p>
|
||||
<p>/MANAGEMENT_WEBSITE_NAME=”Microsoft AppV Management Service”</p>
|
||||
<p>/MANAGEMENT_WEBSITE_PORT=”8080”</p>
|
||||
<p>/DB_PREDEPLOY_MANAGEMENT</p>
|
||||
<p>/MANAGEMENT_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”</p>
|
||||
<p>/MANAGEMENT_DB_NAME=”AppVManagement”</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>To Install the Management server using an existing Management database on a local machine.</p></td>
|
||||
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
|
||||
<ul>
|
||||
<li><p>/MANAGEMENT_SERVER</p></li>
|
||||
<li><p>/MANAGEMENT_ADMINACCOUNT</p></li>
|
||||
<li><p>/MANAGEMENT_WEBSITE_NAME</p></li>
|
||||
<li><p>/MANAGEMENT_WEBSITE_PORT</p></li>
|
||||
<li><p>/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL</p></li>
|
||||
<li><p>/EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT</p></li>
|
||||
<li><p>/EXISTING_MANAGEMENT_DB_NAME</p></li>
|
||||
</ul>
|
||||
<p>To use a custom instance of Microsoft SQL Server, use these parameters:</p>
|
||||
<ul>
|
||||
<li><p>/MANAGEMENT_SERVER</p></li>
|
||||
<li><p>/MANAGEMENT_ADMINACCOUNT</p></li>
|
||||
<li><p>/MANAGEMENT_WEBSITE_NAME</p></li>
|
||||
<li><p>/MANAGEMENT_WEBSITE_PORT</p></li>
|
||||
<li><p>/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL</p></li>
|
||||
<li><p>/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE</p></li>
|
||||
<li><p>/EXISTING_MANAGEMENT_DB_NAME</p></li>
|
||||
</ul>
|
||||
<p>Using a custom instance of Microsoft SQL Server example:</p>
|
||||
<p>/appv_server_setup.exe /QUIET</p>
|
||||
<p>/MANAGEMENT_SERVER</p>
|
||||
<p>/MANAGEMENT_ADMINACCOUNT=”Domain\AdminGroup”</p>
|
||||
<p>/MANAGEMENT_WEBSITE_NAME=”Microsoft AppV Management Service”</p>
|
||||
<p>/MANAGEMENT_WEBSITE_PORT=”8080”</p>
|
||||
<p>/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL</p>
|
||||
<p>/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE =”SqlInstanceName”</p>
|
||||
<p>/EXISTING_MANAGEMENT_DB_NAME =”AppVManagement”</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>To install the Management server using an existing Management database on a remote machine.</p></td>
|
||||
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
|
||||
<ul>
|
||||
<li><p>/MANAGEMENT_SERVER</p></li>
|
||||
<li><p>/MANAGEMENT_ADMINACCOUNT</p></li>
|
||||
<li><p>/MANAGEMENT_WEBSITE_NAME</p></li>
|
||||
<li><p>/MANAGEMENT_WEBSITE_PORT</p></li>
|
||||
<li><p>/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME</p></li>
|
||||
<li><p>/EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT</p></li>
|
||||
<li><p>/EXISTING_MANAGEMENT_DB_NAME</p></li>
|
||||
</ul>
|
||||
<p>To use a custom instance of Microsoft SQL Server, use these parameters:</p>
|
||||
<ul>
|
||||
<li><p>/MANAGEMENT_SERVER</p></li>
|
||||
<li><p>/MANAGEMENT_ADMINACCOUNT</p></li>
|
||||
<li><p>/MANAGEMENT_WEBSITE_NAME</p></li>
|
||||
<li><p>/MANAGEMENT_WEBSITE_PORT</p></li>
|
||||
<li><p>/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME</p></li>
|
||||
<li><p>/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE</p></li>
|
||||
<li><p>/EXISTING_MANAGEMENT_DB_NAME</p></li>
|
||||
</ul>
|
||||
<p>Using a custom instance of Microsoft SQL Server example:</p>
|
||||
<p>/appv_server_setup.exe /QUIET</p>
|
||||
<p>/MANAGEMENT_SERVER</p>
|
||||
<p>/MANAGEMENT_ADMINACCOUNT=”Domain\AdminGroup”</p>
|
||||
<p>/MANAGEMENT_WEBSITE_NAME=”Microsoft AppV Management Service”</p>
|
||||
<p>/MANAGEMENT_WEBSITE_PORT=”8080”</p>
|
||||
<p>/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME=”SqlServermachine.domainName”</p>
|
||||
<p>/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE =”SqlInstanceName”</p>
|
||||
<p>/EXISTING_MANAGEMENT_DB_NAME =”AppVManagement”</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>To Install the Management database and the Management Server on the same computer.</p></td>
|
||||
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
|
||||
<ul>
|
||||
<li><p>/DB_PREDEPLOY_MANAGEMENT</p></li>
|
||||
<li><p>/MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT</p></li>
|
||||
<li><p>/MANAGEMENT_DB_NAME</p></li>
|
||||
<li><p>/MANAGEMENT_SERVER_MACHINE_USE_LOCAL</p></li>
|
||||
<li><p>/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT</p></li>
|
||||
</ul>
|
||||
<p>To use a custom instance of Microsoft SQL Server, use these parameters:</p>
|
||||
<ul>
|
||||
<li><p>/DB_PREDEPLOY_MANAGEMENT</p></li>
|
||||
<li><p>/MANAGEMENT_DB_CUSTOM_SQLINSTANCE</p></li>
|
||||
<li><p>/MANAGEMENT_DB_NAME</p></li>
|
||||
<li><p>/MANAGEMENT_SERVER_MACHINE_USE_LOCAL</p></li>
|
||||
<li><p>/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT</p></li>
|
||||
</ul>
|
||||
<p>Using a custom instance of Microsoft SQL Server example:</p>
|
||||
<p>/appv_server_setup.exe /QUIET</p>
|
||||
<p>/DB_PREDEPLOY_MANAGEMENT</p>
|
||||
<p>/MANAGEMENT_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”</p>
|
||||
<p>/MANAGEMENT_DB_NAME=”AppVManagement”</p>
|
||||
<p>/MANAGEMENT_SERVER_MACHINE_USE_LOCAL</p>
|
||||
<p>/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>To install the Management database on a different computer than the Management server.</p></td>
|
||||
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
|
||||
<ul>
|
||||
<li><p>/DB_PREDEPLOY_MANAGEMENT</p></li>
|
||||
<li><p>/MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT</p></li>
|
||||
<li><p>/MANAGEMENT_DB_NAME</p></li>
|
||||
<li><p>/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT</p></li>
|
||||
<li><p>/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT</p></li>
|
||||
</ul>
|
||||
<p>To use a custom instance of Microsoft SQL Server, use these parameters:</p>
|
||||
<ul>
|
||||
<li><p>/DB_PREDEPLOY_MANAGEMENT</p></li>
|
||||
<li><p>/MANAGEMENT_DB_CUSTOM_SQLINSTANCE</p></li>
|
||||
<li><p>/MANAGEMENT_DB_NAME</p></li>
|
||||
<li><p>/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT</p></li>
|
||||
<li><p>/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT</p></li>
|
||||
</ul>
|
||||
<p>Using a custom instance of Microsoft SQL Server example:</p>
|
||||
<p>/appv_server_setup.exe /QUIET</p>
|
||||
<p>/DB_PREDEPLOY_MANAGEMENT</p>
|
||||
<p>/MANAGEMENT_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”</p>
|
||||
<p>/MANAGEMENT_DB_NAME=”AppVManagement”</p>
|
||||
<p>/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT=”Domain\MachineAccount”</p>
|
||||
<p>/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>To Install the publishing server.</p></td>
|
||||
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
|
||||
<ul>
|
||||
<li><p>/PUBLISHING_SERVER</p></li>
|
||||
<li><p>/PUBLISHING_MGT_SERVER</p></li>
|
||||
<li><p>/PUBLISHING_WEBSITE_NAME</p></li>
|
||||
<li><p>/PUBLISHING_WEBSITE_PORT</p></li>
|
||||
</ul>
|
||||
<p>Using a custom instance of Microsoft SQL Server example:</p>
|
||||
<p>/appv_server_setup.exe /QUIET</p>
|
||||
<p>/PUBLISHING_SERVER</p>
|
||||
<p>/PUBLISHING_MGT_SERVER=”http://ManagementServerName:ManagementPort”</p>
|
||||
<p>/PUBLISHING_WEBSITE_NAME=”Microsoft AppV Publishing Service”</p>
|
||||
<p>/PUBLISHING_WEBSITE_PORT=”8081”</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>To Install the Reporting server and Reporting database on a local machine.</p></td>
|
||||
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
|
||||
<ul>
|
||||
<li><p>/REPORTING _SERVER</p></li>
|
||||
<li><p>/REPORTING _WEBSITE_NAME</p></li>
|
||||
<li><p>/REPORTING _WEBSITE_PORT</p></li>
|
||||
<li><p>/DB_PREDEPLOY_REPORTING</p></li>
|
||||
<li><p>/REPORTING _DB_SQLINSTANCE_USE_DEFAULT</p></li>
|
||||
<li><p>/REPORTING _DB_NAME</p></li>
|
||||
</ul>
|
||||
<p>To use a custom instance of Microsoft SQL Server, use these parameters:</p>
|
||||
<ul>
|
||||
<li><p>/REPORTING _SERVER</p></li>
|
||||
<li><p>/REPORTING _ADMINACCOUNT</p></li>
|
||||
<li><p>/REPORTING _WEBSITE_NAME</p></li>
|
||||
<li><p>/REPORTING _WEBSITE_PORT</p></li>
|
||||
<li><p>/DB_PREDEPLOY_REPORTING</p></li>
|
||||
<li><p>/REPORTING _DB_CUSTOM_SQLINSTANCE</p></li>
|
||||
<li><p>/REPORTING _DB_NAME</p></li>
|
||||
</ul>
|
||||
<p>Using a custom instance of Microsoft SQL Server example:</p>
|
||||
<ul>
|
||||
<li><p>/appv_server_setup.exe /QUIET</p></li>
|
||||
<li><p>/REPORTING_SERVER</p></li>
|
||||
<li><p>/REPORTING_WEBSITE_NAME=”Microsoft AppV Reporting Service”</p></li>
|
||||
<li><p>/REPORTING_WEBSITE_PORT=”8082”</p></li>
|
||||
<li><p>/DB_PREDEPLOY_REPORTING</p></li>
|
||||
<li><p>/REPORTING_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”</p></li>
|
||||
<li><p>/REPORTING_DB_NAME=”AppVReporting”</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>To Install the Reporting server and using an existing Reporting database on a local machine.</p></td>
|
||||
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
|
||||
<ul>
|
||||
<li><p>/REPORTING _SERVER</p></li>
|
||||
<li><p>/REPORTING _WEBSITE_NAME</p></li>
|
||||
<li><p>/REPORTING _WEBSITE_PORT</p></li>
|
||||
<li><p>/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL</p></li>
|
||||
<li><p>/EXISTING_REPORTING _DB_SQLINSTANCE_USE_DEFAULT</p></li>
|
||||
<li><p>/EXISTING_REPORTING _DB_NAME</p></li>
|
||||
</ul>
|
||||
<p>To use a custom instance of Microsoft SQL Server, use these parameters:</p>
|
||||
<ul>
|
||||
<li><p>/REPORTING _SERVER</p></li>
|
||||
<li><p>/REPORTING _ADMINACCOUNT</p></li>
|
||||
<li><p>/REPORTING _WEBSITE_NAME</p></li>
|
||||
<li><p>/REPORTING _WEBSITE_PORT</p></li>
|
||||
<li><p>/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL</p></li>
|
||||
<li><p>/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE</p></li>
|
||||
<li><p>/EXISTING_REPORTING _DB_NAME</p></li>
|
||||
</ul>
|
||||
<p>Using a custom instance of Microsoft SQL Server example:</p>
|
||||
<p>/appv_server_setup.exe /QUIET</p>
|
||||
<p>/REPORTING_SERVER</p>
|
||||
<p>/REPORTING_WEBSITE_NAME=”Microsoft AppV Reporting Service”</p>
|
||||
<p>/REPORTING_WEBSITE_PORT=”8082”</p>
|
||||
<p>/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL</p>
|
||||
<p>/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”</p>
|
||||
<p>/EXITING_REPORTING_DB_NAME=”AppVReporting”</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>To Install the Reporting server using an existing Reporting database on a remote machine.</p></td>
|
||||
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
|
||||
<ul>
|
||||
<li><p>/REPORTING _SERVER</p></li>
|
||||
<li><p>/REPORTING _WEBSITE_NAME</p></li>
|
||||
<li><p>/REPORTING _WEBSITE_PORT</p></li>
|
||||
<li><p>/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME</p></li>
|
||||
<li><p>/EXISTING_REPORTING _DB_SQLINSTANCE_USE_DEFAULT</p></li>
|
||||
<li><p>/EXISTING_REPORTING _DB_NAME</p></li>
|
||||
</ul>
|
||||
<p>To use a custom instance of Microsoft SQL Server, use these parameters:</p>
|
||||
<ul>
|
||||
<li><p>/REPORTING _SERVER</p></li>
|
||||
<li><p>/REPORTING _ADMINACCOUNT</p></li>
|
||||
<li><p>/REPORTING _WEBSITE_NAME</p></li>
|
||||
<li><p>/REPORTING _WEBSITE_PORT</p></li>
|
||||
<li><p>/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME</p></li>
|
||||
<li><p>/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE</p></li>
|
||||
<li><p>/EXISTING_REPORTING _DB_NAME</p></li>
|
||||
</ul>
|
||||
<p>Using a custom instance of Microsoft SQL Server example:</p>
|
||||
<p>/appv_server_setup.exe /QUIET</p>
|
||||
<p>/REPORTING_SERVER</p>
|
||||
<p>/REPORTING_WEBSITE_NAME=”Microsoft AppV Reporting Service”</p>
|
||||
<p>/REPORTING_WEBSITE_PORT=”8082”</p>
|
||||
<p>/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME=”SqlServerMachine.DomainName”</p>
|
||||
<p>/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”</p>
|
||||
<p>/EXITING_REPORTING_DB_NAME=”AppVReporting”</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>To install the Reporting database on the same computer as the Reporting server.</p></td>
|
||||
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
|
||||
<ul>
|
||||
<li><p>/DB_PREDEPLOY_REPORTING</p></li>
|
||||
<li><p>/REPORTING _DB_SQLINSTANCE_USE_DEFAULT</p></li>
|
||||
<li><p>/REPORTING _DB_NAME</p></li>
|
||||
<li><p>/REPORTING_SERVER_MACHINE_USE_LOCAL</p></li>
|
||||
<li><p>/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT</p></li>
|
||||
</ul>
|
||||
<p>To use a custom instance of Microsoft SQL Server, use these parameters:</p>
|
||||
<ul>
|
||||
<li><p>/DB_PREDEPLOY_REPORTING</p></li>
|
||||
<li><p>/REPORTING _DB_CUSTOM_SQLINSTANCE</p></li>
|
||||
<li><p>/REPORTING _DB_NAME</p></li>
|
||||
<li><p>/REPORTING_SERVER_MACHINE_USE_LOCAL</p></li>
|
||||
<li><p>/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT</p></li>
|
||||
</ul>
|
||||
<p>Using a custom instance of Microsoft SQL Server example:</p>
|
||||
<p>/appv_server_setup.exe /QUIET</p>
|
||||
<p>/DB_PREDEPLOY_REPORTING</p>
|
||||
<p>/REPORTING_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”</p>
|
||||
<p>/REPORTING_DB_NAME=”AppVReporting”</p>
|
||||
<p>/REPORTING_SERVER_MACHINE_USE_LOCAL</p>
|
||||
<p>/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>To install the Reporting database on a different computer than the Reporting server.</p></td>
|
||||
<td align="left"><p>To use the default instance of Microsoft SQL Server, use the following parameters:</p>
|
||||
<ul>
|
||||
<li><p>/DB_PREDEPLOY_REPORTING</p></li>
|
||||
<li><p>/REPORTING _DB_SQLINSTANCE_USE_DEFAULT</p></li>
|
||||
<li><p>/REPORTING _DB_NAME</p></li>
|
||||
<li><p>/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT</p></li>
|
||||
<li><p>/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT</p></li>
|
||||
</ul>
|
||||
<p>To use a custom instance of Microsoft SQL Server, use these parameters:</p>
|
||||
<ul>
|
||||
<li><p>/DB_PREDEPLOY_REPORTING</p></li>
|
||||
<li><p>/REPORTING _DB_CUSTOM_SQLINSTANCE</p></li>
|
||||
<li><p>/REPORTING _DB_NAME</p></li>
|
||||
<li><p>/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT</p></li>
|
||||
<li><p>/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT</p></li>
|
||||
</ul>
|
||||
<p>Using a custom instance of Microsoft SQL Server example:</p>
|
||||
<p>/appv_server_setup.exe /QUIET</p>
|
||||
<p>/DB_PREDEPLOY_REPORTING</p>
|
||||
<p>/REPORTING_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”</p>
|
||||
<p>/REPORTING_DB_NAME=”AppVReporting”</p>
|
||||
<p>/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT=”Domain\MachineAccount”</p>
|
||||
<p>/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Parameter Definitions**
|
||||
|
||||
**General Parameters**
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Parameter</th>
|
||||
<th align="left">Information</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/QUIET</p></td>
|
||||
<td align="left"><p>Specifies silent install.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/UNINSTALL</p></td>
|
||||
<td align="left"><p>Specifies an uninstall.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/LAYOUT</p></td>
|
||||
<td align="left"><p>Specifies layout action. This extracts the MSIs and script files to a folder without actually installing the product. No value is expected.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/LAYOUTDIR</p></td>
|
||||
<td align="left"><p>Specifies the layout directory. Takes a string. For example, /LAYOUTDIR=”C:\Application Virtualization Server”</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/INSTALLDIR</p></td>
|
||||
<td align="left"><p>Specifies the installation directory. Takes a string. E.g. /INSTALLDIR=”C:\Program Files\Application Virtualization\Server”</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/MUOPTIN</p></td>
|
||||
<td align="left"><p>Enables Microsoft Update. No value is expected</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/ACCEPTEULA</p></td>
|
||||
<td align="left"><p>Accepts the license agreement. This is required for an unattended installation. Example usage: <strong>/ACCEPTEULA</strong> or <strong>/ACCEPTEULA=1</strong>.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Management Server Installation Parameters**
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Parameter</th>
|
||||
<th align="left">Information</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/MANAGEMENT_SERVER</p></td>
|
||||
<td align="left"><p>Specifies that the management server will be installed. No value is expected</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/MANAGEMENT_ADMINACCOUNT</p></td>
|
||||
<td align="left"><p>Specifies the account that will be allowed to Administrator access to the management server This account can be an individual user account or a group. Example usage: <strong>/MANAGEMENT_ADMINACCOUNT=”mydomain\admin”</strong>. If <strong>/MANAGEMENT_SERVER</strong> is not specified, this will be ignored. Specifies the account that will be allowed to Administrator access to the management server. This can be a user account or a group. For example, <strong>/MANAGEMENT_ADMINACCOUNT="mydomain\admin"</strong>.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/MANAGEMENT_WEBSITE_NAME</p></td>
|
||||
<td align="left"><p>Specifies name of the website that will be created for the management service. For example, /MANAGEMENT_WEBSITE_NAME=”Microsoft App-V Management Service”</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>MANAGEMENT_WEBSITE_PORT</p></td>
|
||||
<td align="left"><p>Specifies the port number that will be used by the management service will use. For example, /MANAGEMENT_WEBSITE_PORT=82.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Parameters for the Management Server Database**
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Parameter</th>
|
||||
<th align="left">Information</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/DB_PREDEPLOY_MANAGEMENT</p></td>
|
||||
<td align="left"><p>Specifies that the management database will be installed. You must have sufficient database permissions to complete this installation. No value is expected</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT</p></td>
|
||||
<td align="left"><p>Indicates that the default SQL instance should be used. No value is expected.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/MANAGEMENT_DB_ CUSTOM_SQLINSTANCE</p></td>
|
||||
<td align="left"><p>Specifies the name of the custom SQL instance that should be used to create a new database. Example usage: <strong>/MANAGEMENT_DB_ CUSTOM_SQLINSTANCE=”MYSQLSERVER”</strong>. If /DB_PREDEPLOY_MANAGEMENT is not specified, this will be ignored.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/MANAGEMENT_DB_NAME</p></td>
|
||||
<td align="left"><p>Specifies the name of the new management database that should be created. Example usage: <strong>/MANAGEMENT_DB_NAME=”AppVMgmtDB”</strong>. If /DB_PREDEPLOY_MANAGEMENT is not specified, this will be ignored.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/MANAGEMENT_SERVER_MACHINE_USE_LOCAL</p></td>
|
||||
<td align="left"><p>Indicates if the management server that will be accessing the database is installed on the local server. Switch parameter so no value is expected.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT</p></td>
|
||||
<td align="left"><p>Specifies the machine account of the remote machine that the management server will be installed on. Example usage: <strong>/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT=”domain\computername”</strong></p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT</p></td>
|
||||
<td align="left"><p>Indicates the Administrator account that will be used to install the management server. Example usage: <strong>/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT =”domain\alias”</strong></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Parameters for Installing Publishing Server**
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Parameter</th>
|
||||
<th align="left">Information</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/PUBLISHING_SERVER</p></td>
|
||||
<td align="left"><p>Specifies that the Publishing Server will be installed. No value is expected</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/PUBLISHING_MGT_SERVER</p></td>
|
||||
<td align="left"><p>Specifies the URL to Management Service the Publishing server will connect to. Example usage: <strong>http://<management server name>:<Management server port number></strong>. If /PUBLISHING_SERVER is not used, this parameter will be ignored</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/PUBLISHING_WEBSITE_NAME</p></td>
|
||||
<td align="left"><p>Specifies name of the website that will be created for the publishing service. For example, /PUBLISHING_WEBSITE_NAME=”Microsoft App-V Publishing Service”</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/PUBLISHING_WEBSITE_PORT</p></td>
|
||||
<td align="left"><p>Specifies the port number used by the publishing service. For example, /PUBLISHING_WEBSITE_PORT=83</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Parameters for Reporting Server**
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Parameter</th>
|
||||
<th align="left">Information</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/REPORTING_SERVER</p></td>
|
||||
<td align="left"><p>Specifies that the Reporting Server will be installed. No value is expected</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/REPORTING_WEBSITE_NAME</p></td>
|
||||
<td align="left"><p>Specifies name of the website that will be created for the Reporting Service. E.g. /REPORTING_WEBSITE_NAME="Microsoft App-V ReportingService"</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/REPORTING_WEBSITE_PORT</p></td>
|
||||
<td align="left"><p>Specifies the port number that the Reporting Service will use. E.g. /REPORTING_WEBSITE_PORT=82</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Parameters for using an Existing Reporting Server Database**
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Parameter</th>
|
||||
<th align="left">Information</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL</p></td>
|
||||
<td align="left"><p>Indicates that the Microsoft SQL Server is installed on the local server. Switch parameter so no value is expected.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME</p></td>
|
||||
<td align="left"><p>Specifies the name of the remote computer that SQL Server is installed on. Takes a string. E.g. /EXISTING_REPORTING_DB_ REMOTE_SQL_SERVER_NAME="mycomputer1"</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/EXISTING_ REPORTING _DB_SQLINSTANCE_USE_DEFAULT</p></td>
|
||||
<td align="left"><p>Indicates that the default SQL instance is to be used. Switch parameter so no value is expected.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/EXISTING_ REPORTING_DB_CUSTOM_SQLINSTANCE</p></td>
|
||||
<td align="left"><p>Specifies the name of the custom SQL instance that should be used. Takes a string. E.g. /EXISTING_REPORTING_DB_ CUSTOM_SQLINSTANCE="MYSQLSERVER"</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/EXISTING_ REPORTING _DB_NAME</p></td>
|
||||
<td align="left"><p>Specifies the name of the existing Reporting database that should be used. Takes a string. E.g. /EXISITING_REPORTING_DB_NAME="AppVReporting"</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Parameters for installing Reporting Server Database**
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Parameter</th>
|
||||
<th align="left">Information</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/DB_PREDEPLOY_REPORTING</p></td>
|
||||
<td align="left"><p>Specifies that the Reporting Database will be installed. DBA permissions are required for this installation. No value is expected</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/REPORTING_DB_SQLINSTANCE_USE_DEFAULT</p></td>
|
||||
<td align="left"><p>Specifies the name of the custom SQL instance that should be used. Takes a string. E.g. /REPORTING_DB_ CUSTOM_SQLINSTANCE="MYSQLSERVER"</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/REPORTING_DB_NAME</p></td>
|
||||
<td align="left"><p>Specifies the name of the new Reporting database that should be created. Takes a string. E.g. /REPORTING_DB_NAME="AppVMgmtDB"</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/REPORTING_SERVER_MACHINE_USE_LOCAL</p></td>
|
||||
<td align="left"><p>Indicates that the Reporting server that will be accessing the database is installed on the local server. Switch parameter so no value is expected.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT</p></td>
|
||||
<td align="left"><p>Specifies the machine account of the remote machine that the Reporting server will be installed on. Takes a string. E.g. /REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT = "domain\computername"</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT</p></td>
|
||||
<td align="left"><p>Indicates the Administrator account that will be used to install the App-V Reporting Server. Takes a string. E.g. /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT = "domain\alias"</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Parameters for using an existing Management Server Database**
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Parameter</th>
|
||||
<th align="left">Information</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL</p></td>
|
||||
<td align="left"><p>Indicates that the SQL Server is installed on the local server. Switch parameter so no value is expected.If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME</p></td>
|
||||
<td align="left"><p>Specifies the name of the remote computer that SQL Server is installed on. Takes a string. E.g. /EXISTING_MANAGEMENT_DB_ REMOTE_SQL_SERVER_NAME="mycomputer1"</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/EXISTING_ MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT</p></td>
|
||||
<td align="left"><p>Indicates that the default SQL instance is to be used. Switch parameter so no value is expected. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/EXISTING_MANAGEMENT_DB_ CUSTOM_SQLINSTANCE</p></td>
|
||||
<td align="left"><p>Specifies the name of the custom SQL instance that will be used. Example usage <strong>/EXISTING_MANAGEMENT_DB_ CUSTOM_SQLINSTANCE=”AppVManagement”</strong>. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>/EXISTING_MANAGEMENT_DB_NAME</p></td>
|
||||
<td align="left"><p>Specifies the name of the existing management database that should be used. Example usage: <strong>/EXISITING_MANAGEMENT_DB_NAME=”AppVMgmtDB”</strong>. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.</p>
|
||||
<p></p>
|
||||
<p><strong>Have a suggestion for App-V</strong>? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). <strong>Got an App-V issue?</strong> Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
116
windows/manage/appv-deploy-the-appv-server.md
Normal file
116
windows/manage/appv-deploy-the-appv-server.md
Normal file
@ -0,0 +1,116 @@
|
||||
---
|
||||
title: How to Deploy the App-V Server (Windows 10)
|
||||
description: How to Deploy the App-V Server
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Deploy the App-V server
|
||||
|
||||
Use the following procedure to install the App-V server..
|
||||
|
||||
**Before you start:**
|
||||
|
||||
- Ensure that you’ve installed prerequisite software. See [App-V Prerequisites](appv-prerequisites.md).
|
||||
|
||||
- Review the server section of [App-V security considerations](appv-security-considerations.md).
|
||||
|
||||
- Specify a port where each component will be hosted.
|
||||
|
||||
- Add firewall rules to allow incoming requests to access the specified ports.
|
||||
|
||||
- If you use SQL scripts, instead of the Windows Installer, to set up the Management database or Reporting database, you must run the SQL scripts before installing the Management Server or Reporting Server. See [How to Deploy the App-V Databases by Using SQL Scripts](appv-deploy-appv-databases-with-sql-scripts.md).
|
||||
|
||||
**To install the App-V server**
|
||||
|
||||
1. Copy the App-V server installation files to the computer on which you want to install it.
|
||||
|
||||
2. Start the App-V server installation by right-clicking and running **appv\_server\_setup.exe** as an administrator, and then click **Install**.
|
||||
|
||||
3. Review and accept the license terms, and choose whether to enable Microsoft updates.
|
||||
|
||||
4. On the **Feature Selection** page, select all of the following components.
|
||||
|
||||
| Component | Description |
|
||||
| - | - |
|
||||
| Management server | Provides overall management functionality for the App-V infrastructure. |
|
||||
| Management database | Facilitates database predeployments for App-V management. |
|
||||
| Publishing server | Provides hosting and streaming functionality for virtual applications. |
|
||||
| Reporting server | Provides App-V reporting services. |
|
||||
| Reporting database | Facilitates database predeployments for App-V reporting. |
|
||||
|
||||
5. On the **Installation Location** page, accept the default location where the selected components will be installed, or change the location by typing a new path on the **Installation Location** line.
|
||||
|
||||
6. On the initial **Create New Management Database** page, configure the **Microsoft SQL Server instance** and **Management Server database** by selecting the appropriate option below.
|
||||
|
||||
| Method | What you need to do |
|
||||
| - | - |
|
||||
| You are using a custom Microsoft SQL Server instance. | Select **Use the custom instance**, and type the name of the instance.<br/>Use the format **INSTANCENAME**. The assumed installation location is the local computer.<br/>Not supported: A server name using the format **ServerName**\\**INSTANCE**.|
|
||||
| You are using a custom database name. | Select **Custom configuration** and type the database name.<br/>The database name must be unique, or the installation will fail.|
|
||||
|
||||
7. On the **Configure** page, accept the default value **Use this local computer**.
|
||||
|
||||
> [!NOTE]
|
||||
> If you are installing the Management server and Management database side by side, some options on this page are not available. In this case, the appropriate options are selected by default and cannot be changed.
|
||||
|
||||
8. On the initial **Create New Reporting Database** page, configure the **Microsoft SQL Server instance** and **Reporting Server database** by selecting the appropriate option below.
|
||||
|
||||
| Method | What you need to do |
|
||||
| - | - |
|
||||
| You are using a custom Microsoft SQL Server instance. | Select **Use the custom instance**, and type the name of the instance.<br/>Use the format **INSTANCENAME**. The assumed installation location is the local computer.<br/>Not supported: A server name using the format **ServerName**\\**INSTANCE**.|
|
||||
| You are using a custom database name. | Select **Custom configuration** and type the database name.<br/>The database name must be unique, or the installation will fail.|
|
||||
|
||||
|
||||
9. On the **Configure** page, accept the default value: **Use this local computer**.
|
||||
|
||||
> [!NOTE]
|
||||
> If you are installing the Management server and Management database side by side, some options on this page are not available. In this case, the appropriate options are selected by default and cannot be changed.
|
||||
|
||||
|
||||
10. On the **Configure** (Management Server Configuration) page, specify the following:
|
||||
|
||||
| Item to configure | Description and examples |
|
||||
| - | - |
|
||||
Type the AD group with sufficient permissions to manage the App-V environment. | Example: MyDomain\MyUser<br/>After installation, you can add additional users or groups by using the Management console. However, global security groups and Active Directory Domain Services (AD DS) distribution groups are not supported. You must use <strong>Domain local</strong> or <strong>Universal</strong> groups are required to perform this action.|
|
||||
| **Website name**: Specify the custom name that will be used to run the publishing service.<br/>If you do not have a custom name, do not make any changes.|
|
||||
|**Port binding**: Specify a unique port number that will be used by App-V. | Example: **12345**<br/>Ensure that the port specified is not being used by another website. |
|
||||
|
||||
11. On the **Configure Publishing Server Configuration** page, specify the following:
|
||||
|
||||
| Item to configure | Description and examples |
|
||||
| - | - |
|
||||
| Specify the URL for the management service. | Example: http://localhost:12345 |
|
||||
| **Website name**: Specify the custom name that will be used to run the publishing service.| If you do not have a custom name, do not make any changes. |
|
||||
| **Port binding**: Specify a unique port number that will be used by App-V. | Example: 54321<br/>Ensure that the port specified is not being used by another website. |
|
||||
|
||||
12. On the **Reporting Server** page, specify the following:
|
||||
|
||||
| Item to configure | Description and examples |
|
||||
| - | - |
|
||||
| **Website name**: Specify the custom name that will be used to run the Reporting Service. | If you do not have a custom name, do not make any changes. |
|
||||
| **Port binding**: Specify a unique port number that will be used by App-V. | Example: 55555<br/>Ensure that the port specified is not being used by another website. |
|
||||
|
||||
13. To start the installation, click **Install** on the **Ready** page, and then click **Close** on the **Finished** page.
|
||||
|
||||
14. To verify that the setup completed successfully, open a web browser, and type the following URL:
|
||||
|
||||
**http://\<_Management server machine name_\>:\<_Management service port number_\>/console.html**.
|
||||
|
||||
Example: **http://localhost:12345/console.html**. If the installation succeeded, the App-V Management console is displayed with no errors.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
- [How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services](appv-install-the-management-and-reporting-databases-on-separate-computers.md)
|
||||
|
||||
- [How to Install the Publishing Server on a Remote Computer](appv-install-the-publishing-server-on-a-remote-computer.md)
|
||||
|
||||
- [How to Deploy the App-V Server Using a Script](appv-deploy-the-appv-server-with-a-script.md)
|
||||
47
windows/manage/appv-deploying-appv.md
Normal file
47
windows/manage/appv-deploying-appv.md
Normal file
@ -0,0 +1,47 @@
|
||||
---
|
||||
title: Deploying App-V (Windows 10)
|
||||
description: Deploying App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# Deploying App-V
|
||||
|
||||
App-V supports a number of different deployment options. This section of the App-V Administrator’s Guide includes information you should consider about the deployment of App-V and step-by-step procedures to help you successfully perform the tasks that you must complete at different stages of your deployment.
|
||||
|
||||
## App-V Deployment Information
|
||||
|
||||
|
||||
- [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
|
||||
This section describes how to install the App-V sequencer which is used to virtualize applications, and the App-V client which runs on target computers to facilitate virtualized packages.
|
||||
|
||||
- [Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
|
||||
This section provides information about installing the App-V management, publishing, database and reporting severs.
|
||||
|
||||
- [App-V Deployment Checklist](appv-deployment-checklist.md)
|
||||
|
||||
This section provides a deployment checklist that can be used to assist with installing App-V.
|
||||
|
||||
## Other Resources for Deploying App-V
|
||||
|
||||
|
||||
- [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?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
293
windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md
Normal file
293
windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md
Normal file
@ -0,0 +1,293 @@
|
||||
---
|
||||
title: Deploying Microsoft Office 2010 by Using App-V (Windows 10)
|
||||
description: Deploying Microsoft Office 2010 by Using App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Deploying Microsoft Office 2010 by Using App-V
|
||||
|
||||
|
||||
You can create Office 2010 packages for Microsoft Application Virtualization (App-V) using one of the following methods:
|
||||
|
||||
- Application Virtualization (App-V) Sequencer
|
||||
|
||||
- Application Virtualization (App-V) Package Accelerator
|
||||
|
||||
## App-V support for Office 2010
|
||||
|
||||
|
||||
The following table shows the App-V versions, methods of Office package creation, supported licensing, and supported deployments for Office 2010.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Supported item</th>
|
||||
<th align="left">Level of support</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Package creation</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Sequencing</p></li>
|
||||
<li><p>Package Accelerator</p></li>
|
||||
<li><p>Office Deployment Kit</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Supported licensing</p></td>
|
||||
<td align="left"><p>Volume Licensing</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Supported deployments</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Desktop</p></li>
|
||||
<li><p>Personal VDI</p></li>
|
||||
<li><p>RDS</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Creating Office 2010 App-V using the sequencer
|
||||
|
||||
|
||||
Sequencing Office 2010 is one of the main methods for creating an Office 2010 package on App-V. Microsoft has provided a detailed recipe through a Knowledge Base article. To create an Office 2010 package on App-V, refer to the following link for detailed instructions:
|
||||
|
||||
[How To Sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0](http://go.microsoft.com/fwlink/p/?LinkId=330676)
|
||||
|
||||
## Creating Office 2010 App-V packages using package accelerators
|
||||
|
||||
|
||||
Office 2010 App-V packages can be created through package accelerators. Microsoft has provided package accelerators for creating Office 2010 on Windows 10, Windows 8 and Windows 7. To create Office 2010 packages on App-V using Package accelerators, refer to the following pages to access the appropriate package accelerator:
|
||||
|
||||
- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 8](http://go.microsoft.com/fwlink/p/?LinkId=330677)
|
||||
|
||||
- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 7](http://go.microsoft.com/fwlink/p/?LinkId=330678)
|
||||
|
||||
For detailed instructions on how to create virtual application packages using App-V package accelerators, see [How to Create a Virtual Application Package Using an App-V Package Accelerator](appv-create-a-virtual-application-package-package-accelerator.md).
|
||||
|
||||
## Deploying the Microsoft Office package for App-V
|
||||
|
||||
|
||||
You can deploy Office 2010 packages by using any of the following App-V deployment methods:
|
||||
|
||||
- System Center Configuration Manager
|
||||
|
||||
- App-V server
|
||||
|
||||
- Stand-alone through PowerShell commands
|
||||
|
||||
## Office App-V package management and customization
|
||||
|
||||
|
||||
Office 2010 packages can be managed like any other App-V packages through known package management mechanisms. No special instructions are needed, for example, to add, publish, unpublish, or remove Office packages.
|
||||
|
||||
## Microsoft Office integration with Windows
|
||||
|
||||
|
||||
The following table provides a full list of supported integration points for Office 2010.
|
||||
|
||||
<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](http://go.microsoft.com/fwlink/p/?LinkId=331361).</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**
|
||||
|
||||
[Supported scenarios for deploying Microsoft Office as a sequenced App-V Package](http://go.microsoft.com/fwlink/p/?LinkId=330680)
|
||||
|
||||
**Office 2010 App-V Packages**
|
||||
|
||||
[Microsoft Office 2010 Sequencing Kit for Microsoft Application Virtualization 5.0](http://go.microsoft.com/fwlink/p/?LinkId=330681)
|
||||
|
||||
[Known issues when you create or use an App-V 5.0 Office 2010 package](http://go.microsoft.com/fwlink/p/?LinkId=330682)
|
||||
|
||||
[How to sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0](http://go.microsoft.com/fwlink/p/?LinkId=330676)
|
||||
|
||||
**Connection Groups**
|
||||
|
||||
[Deploying Connection Groups in Microsoft App-V v5](http://go.microsoft.com/fwlink/p/?LinkId=330683)
|
||||
|
||||
[Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
|
||||
**Dynamic Configuration**
|
||||
|
||||
[About App-V Dynamic Configuration](appv-dynamic-configuration.md)
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
895
windows/manage/appv-deploying-microsoft-office-2013-with-appv.md
Normal file
895
windows/manage/appv-deploying-microsoft-office-2013-with-appv.md
Normal file
@ -0,0 +1,895 @@
|
||||
---
|
||||
title: Deploying Microsoft Office 2013 by Using App-V (Windows 10)
|
||||
description: Deploying Microsoft Office 2013 by Using App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Deploying Microsoft Office 2013 by Using App-V
|
||||
|
||||
|
||||
Use the information in this article to use Microsoft Application Virtualization (App-V), or later versions, to deliver Microsoft Office 2013 as a virtualized application to computers in your organization. For information about using App-V to deliver Office 2010, see [Deploying Microsoft Office 2010 by Using App-V](appv-deploying-microsoft-office-2010-wth-appv.md). To successfully deploy Office 2013 with App-V, you need to be familiar with Office 2013 and App-V.
|
||||
|
||||
This topic contains the following sections:
|
||||
|
||||
- [What to know before you start](#bkmk-before-you-start)
|
||||
|
||||
- [Creating an Office 2013 package for App-V with the Office Deployment Tool](#bkmk-create-office-pkg)
|
||||
|
||||
- [Publishing the Office package for App-V](#bkmk-pub-pkg-office)
|
||||
|
||||
- [Customizing and managing Office App-V packages](#bkmk-custmz-manage-office-pkgs)
|
||||
|
||||
## <a href="" id="bkmk-before-you-start"></a>What to know before you start
|
||||
|
||||
|
||||
Before you deploy Office 2013 by using App-V, review the following planning information.
|
||||
|
||||
### <a href="" id="bkmk-supp-vers-coexist"></a>Supported Office versions and Office coexistence
|
||||
|
||||
Use the following table to get information about supported versions of Office and about running coexisting versions of Office.
|
||||
|
||||
<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>[Planning for Using App-V with 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 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>
|
||||
|
||||
|
||||
|
||||
### <a href="" id="bkmk-pkg-pub-reqs"></a>Packaging, publishing, and deployment requirements
|
||||
|
||||
Before you deploy Office by using App-V, review the following requirements.
|
||||
|
||||
<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 of the Office applications that you want 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. You cannot use the Sequencer.</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 publish only one Office package to each client computer.</p></li>
|
||||
<li><p>You must publish the Office package globally. You cannot publish 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](http://technet.microsoft.com/library/dn782860.aspx).</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>
|
||||
|
||||
|
||||
|
||||
### Excluding Office applications from a package
|
||||
|
||||
The following table describes the recommended methods for excluding specific Office applications from a package.
|
||||
|
||||
<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](http://technet.microsoft.com/library/jj219426.aspx#bkmk-excludeappelement).</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 the package has been created. This file contains the default package settings for all users on a computer that is 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>
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-create-office-pkg"></a>Creating an Office 2013 package for App-V with the Office Deployment Tool
|
||||
|
||||
|
||||
Complete the following steps to create an Office 2013 package for App-V or later.
|
||||
|
||||
**Important**
|
||||
In App-V and later, you must the Office Deployment Tool to create a package. You cannot use the Sequencer to create packages.
|
||||
|
||||
|
||||
|
||||
### Review prerequisites for using the Office Deployment Tool
|
||||
|
||||
The computer on which you are installing the Office Deployment Tool must have:
|
||||
|
||||
<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.
|
||||
|
||||
|
||||
|
||||
### Create Office 2013 App-V Packages Using Office Deployment Tool
|
||||
|
||||
You create Office 2013 App-V packages by using the Office Deployment Tool. The following instructions explain how to create an Office 2013 App-V package with Volume Licensing or Subscription Licensing.
|
||||
|
||||
Create Office 2013 App-V packages on 64-bit Windows computers. Once created, the Office 2013 App-V package will run on 32-bit and 64-bit Windows 7, Windows 8.1, and Windows 10 computers.
|
||||
|
||||
### Download the Office Deployment Tool
|
||||
|
||||
Office 2013 App-V Packages are created using the Office Deployment Tool, which generates an Office 2013 App-V Package. The package cannot be created or modified through the App-V sequencer. To begin package creation:
|
||||
|
||||
1. Download the [Office Deployment Tool for Click-to-Run](http://www.microsoft.com/download/details.aspx?id=36778).
|
||||
|
||||
2. Run the .exe file and extract its features into the desired location. To make this process easier, you can create a shared network folder where the features will be saved.
|
||||
|
||||
Example: \\\\Server\\Office2013
|
||||
|
||||
3. Check that a setup.exe and a configuration.xml file exist and are in the location you specified.
|
||||
|
||||
### Download Office 2013 applications
|
||||
|
||||
After you download the Office Deployment Tool, you can use it to get the latest Office 2013 applications. After getting the Office applications, you create the Office 2013 App-V package.
|
||||
|
||||
The XML file that is included in the Office Deployment Tool specifies the product details, such as the languages and Office applications included.
|
||||
|
||||
1. **Customize the sample XML configuration file:** Use the sample XML configuration file that you downloaded with the Office Deployment Tool to customize the Office applications:
|
||||
|
||||
1. Open the sample XML file in Notepad or your favorite text editor.
|
||||
|
||||
2. With the sample configuration.xml file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2013 applications. The following is a basic example of the configuration.xml file:
|
||||
|
||||
``` syntax
|
||||
<Configuration>
|
||||
<Add SourcePath= ”\\Server\Office2013” OfficeClientEdition="32" >
|
||||
<Product ID="O365ProPlusRetail ">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
<Product ID="VisioProRetail">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
</Add>
|
||||
</Configuration>
|
||||
```
|
||||
|
||||
**Note**
|
||||
The configuration XML is a sample XML file. The file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file.
|
||||
|
||||
|
||||
|
||||
The above XML configuration file specifies that Office 2013 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office 2013, which is the location where Office applications will be saved to. Note that the Product ID of the applications will not affect the final licensing of Office. Office 2013 App-V packages with various licensing can be created from the same applications through specifying licensing in a later stage. The table below summarizes the customizable attributes and elements of XML file:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Input</th>
|
||||
<th align="left">Description</th>
|
||||
<th align="left">Example</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Add element</p></td>
|
||||
<td align="left"><p>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)</p></td>
|
||||
<td align="left"><p>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><strong>OfficeClientEdition</strong>="32"</p>
|
||||
<p><strong>OfficeClientEdition</strong>="64"</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Product element</p></td>
|
||||
<td align="left"><p>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 ="O365ProPlusRetail "</code></p>
|
||||
<p><code>Product ID ="VisioProRetail"</code></p>
|
||||
<p><code>Product ID ="ProjectProRetail"</code></p>
|
||||
<p><code>Product ID ="ProPlusVolume"</code></p>
|
||||
<p><code>Product ID ="VisioProVolume"</code></p>
|
||||
<p><code>Product ID = "ProjectProVolume"</code></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Language element</p></td>
|
||||
<td align="left"><p>Specifies the language supported in the applications</p></td>
|
||||
<td align="left"><p><code>Language ID="en-us"</code></p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Version (attribute of Add element)</p></td>
|
||||
<td align="left"><p>Optional. Specifies a build to use for the package</p>
|
||||
<p>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)</p></td>
|
||||
<td align="left"><p>Specifies the location in which the applications will be saved to.</p></td>
|
||||
<td align="left"><p><code>Sourcepath = "\\Server\Office2013”</code></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
After editing the configuration.xml file to specify the desired product, languages, and also the location which the Office 2013 applications will be saved onto, you can save the configuration file, for example, as Customconfig.xml.
|
||||
|
||||
2. **Download the applications into the specified location:** Use an elevated command prompt and a 64 bit operating system to download the Office 2013 applications that will later be converted into an App-V package. Below is an example command with description of details:
|
||||
|
||||
``` syntax
|
||||
\\server\Office2013\setup.exe /download \\server\Office2013\Customconfig.xml
|
||||
```
|
||||
|
||||
In the example:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>\\server\Office2013</strong></p></td>
|
||||
<td align="left"><p>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><strong>Setup.exe</strong></p></td>
|
||||
<td align="left"><p>is the Office Deployment Tool.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>/download</strong></p></td>
|
||||
<td align="left"><p>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.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>\\server\Office2013\Customconfig.xml</strong></p></td>
|
||||
<td align="left"><p>passes the XML configuration file required to complete the download process, in this example, customconfig.xml. 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>
|
||||
|
||||
|
||||
|
||||
### 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. Complete the steps that correspond to your licensing model.
|
||||
|
||||
**Summary of what you’ll need to do:**
|
||||
|
||||
- Create the Office 2013 App-V packages on 64-bit Windows computers. However, the package will run on 32-bit and 64-bit Windows 7, Windows 8, and Windows 10 computers.
|
||||
|
||||
- Create an Office App-V package for either Subscription Licensing package or Volume Licensing by using the Office Deployment Tool, and then modify the CustomConfig.xml configuration file.
|
||||
|
||||
The following table summarizes the values you need to enter in the CustomConfig.xml file for the licensing model you’re using. The steps in the sections that follow the table will specify the exact entries you need to make.
|
||||
|
||||
<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:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Parameter</th>
|
||||
<th align="left">What to change the value to</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>SourcePath</p></td>
|
||||
<td align="left"><p>Point to the Office applications downloaded earlier.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>ProductID</p></td>
|
||||
<td align="left"><p>Specify the type of licensing, as shown in the following examples:</p>
|
||||
<ul>
|
||||
<li><p>Subscription Licensing</p>
|
||||
<pre class="syntax" space="preserve"><code><Configuration>
|
||||
<Add SourcePath= "\\server\Office 2013" OfficeClientEdition="32" >
|
||||
<Product ID="O365ProPlusRetail">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
<Product ID="VisioProRetail">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
</Add>
|
||||
</Configuration> </code></pre>
|
||||
<p>In this example, the following changes were made to create a package with Subscription licensing:</p>
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>SourcePath</strong></p></td>
|
||||
<td align="left"><p>is the path, which was changed to point to the Office applications that were downloaded earlier.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Product ID</strong></p></td>
|
||||
<td align="left"><p>for Office was changed to <code>O365ProPlusRetail</code>.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Product ID</strong></p></td>
|
||||
<td align="left"><p>for Visio was changed to <code>VisioProRetail</code>.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p> </p>
|
||||
<p></p></li>
|
||||
<li><p>Volume Licensing</p>
|
||||
<pre class="syntax" space="preserve"><code><Configuration>
|
||||
<Add SourcePath= "\\Server\Office2013" OfficeClientEdition="32" >
|
||||
<Product ID="ProPlusVolume">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
<Product ID="VisioProVolume">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
</Add>
|
||||
</Configuration></code></pre>
|
||||
<p>In this example, the following changes were made to create a package with Volume licensing:</p>
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>SourcePath</strong></p></td>
|
||||
<td align="left"><p>is the path, which was changed to point to the Office applications that were downloaded earlier.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Product ID</strong></p></td>
|
||||
<td align="left"><p>for Office was changed to <code>ProPlusVolume</code>.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Product ID</strong></p></td>
|
||||
<td align="left"><p>for Visio was changed to <code>VisioProVolume</code>.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p> </p>
|
||||
<p></p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>ExcludeApp (optional)</p></td>
|
||||
<td align="left"><p>Lets you specify Office programs that you don’t want included in the App-V package that the Office Deployment Tool creates. For example, you can exclude Access and InfoPath.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>PACKAGEGUID (optional)</p></td>
|
||||
<td align="left"><p>By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use PACKAGEGUID to specify a different package ID for each package, which allows you to publish multiple App-V packages, created by the Office Deployment Tool, and manage them by using the App-V Server.</p>
|
||||
<p>An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2013 for some users, and create another package with Office 2013 and Visio 2013 for another set of users.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>Even if you use unique package IDs, you can still deploy only one App-V package to a single device.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
2. Use the /packager command to convert the Office applications to an Office 2013 App-V package.
|
||||
|
||||
For example:
|
||||
|
||||
``` syntax
|
||||
\\server\Office2013\setup.exe /packager \\server\Office2013\Customconfig.xml \\server\share\Office2013AppV
|
||||
```
|
||||
|
||||
In the example:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>\\server\Office2013</strong></p></td>
|
||||
<td align="left"><p>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><strong>Setup.exe</strong></p></td>
|
||||
<td align="left"><p>is the Office Deployment Tool.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>/packager</strong></p></td>
|
||||
<td align="left"><p>creates the Office 2013 App-V package with Volume Licensing as specified in the customConfig.xml file.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>\\server\Office2013\Customconfig.xml</strong></p></td>
|
||||
<td align="left"><p>passes the configuration XML file (in this case customConfig) that has been prepared for the packaging stage.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>\\server\share\Office 2013AppV</strong></p></td>
|
||||
<td align="left"><p>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 appear up in the directory where you specified the package should be saved:
|
||||
|
||||
- **App-V Packages** – contains an Office 2013 App-V package and two deployment configuration files.
|
||||
|
||||
- **WorkingDir**
|
||||
|
||||
**Note**
|
||||
To troubleshoot any issues, see the log files in the %temp% directory (default).
|
||||
|
||||
|
||||
|
||||
3. Verify that the Office 2013 App-V package works correctly:
|
||||
|
||||
1. Publish the Office 2013 App-V package, which you created globally, to a test computer, and verify that the Office 2013 shortcuts appear.
|
||||
|
||||
2. Start a few Office 2013 applications, such as Excel or Word, to ensure that your package is working as expected.
|
||||
|
||||
## <a href="" id="bkmk-pub-pkg-office"></a>Publishing the Office package for App-V
|
||||
|
||||
|
||||
Use the following information to publish an Office package.
|
||||
|
||||
### Methods for publishing Office App-V packages
|
||||
|
||||
Deploy the App-V package for Office 2013 by using the same methods you use for any other package:
|
||||
|
||||
- System Center Configuration Manager
|
||||
|
||||
- App-V Server
|
||||
|
||||
- Stand-alone through PowerShell commands
|
||||
|
||||
### Publishing prerequisites and requirements
|
||||
|
||||
<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 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 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:
|
||||
|
||||
- `Add-AppvClientPackage <Path_to_AppV_Package> | Publish-AppvClientPackage –global`
|
||||
|
||||
- From the Web Management Console on the App-V Server, you can add permissions to a group of computers instead of to a user group to enable packages to be published globally to the computers in the corresponding group.
|
||||
|
||||
## <a href="" id="bkmk-custmz-manage-office-pkgs"></a>Customizing and managing Office App-V packages
|
||||
|
||||
|
||||
To manage your Office App-V packages, use the same operations as you would for any other package, but there are a few exceptions, as outlined in the following sections.
|
||||
|
||||
- [Enabling Office plug-ins by using connection groups](#bkmk-enable-office-plugins)
|
||||
|
||||
- [Disabling Office 2013 applications](#bkmk-disable-office-apps)
|
||||
|
||||
- [Disabling Office 2013 shortcuts](#bkmk-disable-shortcuts)
|
||||
|
||||
- [Managing Office 2013 package upgrades](#bkmk-manage-office-pkg-upgrd)
|
||||
|
||||
- [Managing Office 2013 licensing upgrades](#bkmk-manage-office-lic-upgrd)
|
||||
|
||||
- [Deploying Visio 2013 and Project 2013 with Office](#bkmk-deploy-visio-project)
|
||||
|
||||
### <a href="" id="bkmk-enable-office-plugins"></a>Enabling Office plug-ins by using connection groups
|
||||
|
||||
Use the steps in this section 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 contains just the plug-ins. You cannot use the Office Deployment Tool to create the plug-ins package. You then create a connection group that contains the Office package and the plug-ins package, as described in the following steps.
|
||||
|
||||
**To enable plug-ins for Office App-V packages**
|
||||
|
||||
1. Add a Connection Group through App-V Server, System Center Configuration Manager, or a PowerShell cmdlet.
|
||||
|
||||
2. Sequence your plug-ins using the App-V Sequencer. Ensure that Office 2013 is installed on the computer being used to sequence the plug-in. It is recommended you use Office 365 ProPlus(non-virtual) on the sequencing computer when you sequence Office 2013 plug-ins.
|
||||
|
||||
3. Create an App-V package that includes the desired plug-ins.
|
||||
|
||||
4. Add a Connection Group through App-V server, System Center Configuration Manager, or a PowerShell cmdlet.
|
||||
|
||||
5. Add the Office 2013 App-V package and the plug-ins package you sequenced to the Connection Group you created.
|
||||
|
||||
**Important**
|
||||
The order of the packages in the Connection Group determines the order in which the package contents are merged. In your Connection group descriptor file, add the Office 2013 App-V package first, and then add the plug-in App-V package.
|
||||
|
||||
|
||||
|
||||
6. Ensure that both packages are published to the target computer and that the plug-in package is published globally to match the global settings of the published Office 2013 App-V package.
|
||||
|
||||
7. Verify that the Deployment Configuration File of the plug-in package has the same settings that the Office 2013 App-V package has.
|
||||
|
||||
Since the Office 2013 App-V package is integrated with the operating system, the plug-in package settings should match. You can search the Deployment Configuration File for “COM Mode” and ensure that your plug-ins package has that value set as “Integrated” and that both "InProcessEnabled" and "OutOfProcessEnabled" match the settings of the Office 2013 App-V package you published.
|
||||
|
||||
8. Open the Deployment Configuration File and set the value for **Objects Enabled** to **false**.
|
||||
|
||||
9. If you made any changes to the Deployment Configuration file after sequencing, ensure that the plug-in package is published with the file.
|
||||
|
||||
10. Ensure that the Connection Group you created is enabled onto your desired computer. The Connection Group created will likely “pend” if the Office 2013 App-V package is in use when the Connection Group is enabled. If that happens, you have to reboot to successfully enable the Connection Group.
|
||||
|
||||
11. After you successfully publish both packages and enable the Connection Group, start the target Office 2013 application and verify that the plug-in you published and added to the connection group works as expected.
|
||||
|
||||
### <a href="" id="bkmk-disable-office-apps"></a>Disabling Office 2013 applications
|
||||
|
||||
You may want to disable specific applications in your Office App-V package. For instance, you can disable Access, but leave all other Office application main available. When you disable an application, the end user will no longer see the shortcut for that application. You do not have to re-sequence the application. When you change the Deployment Configuration File after the Office 2013 App-V package has been published, you will save the changes, add the Office 2013 App-V package, and then republish it with the new Deployment Configuration File to apply the new settings to Office 2013 App-V Package applications.
|
||||
|
||||
**Note**
|
||||
To exclude specific Office applications (for example, Access and InfoPath) when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting. For more information, see [Reference for Click-to-Run configuration.xml file](http://technet.microsoft.com/library/jj219426.aspx).
|
||||
|
||||
|
||||
|
||||
**To disable an Office 2013 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 2013.
|
||||
|
||||
3. Change the value of "Enabled" from "true" to "false."
|
||||
|
||||
4. Save the Deployment Configuration File.
|
||||
|
||||
5. Add the Office 2013 App-V Package with the new Deployment Configuration File.
|
||||
|
||||
``` syntax
|
||||
<Application Id="[{AppVPackageRoot)]\officefl5\INFOPATH.EXE" Enabled="true">
|
||||
<VisualElements>
|
||||
<Name>InfoPath Filler 2013</Name>
|
||||
<Icon />
|
||||
<Description />
|
||||
</VisualElements>
|
||||
</Application>
|
||||
<Application Id="[{AppVPackageRoot}]\officel5\lync.exe" Enabled="true">
|
||||
<VisualElements>
|
||||
<Name>Lync 2013</Name>
|
||||
<Icon />
|
||||
<Description />
|
||||
</VisualElements>
|
||||
</Application>
|
||||
<Application Id="[(AppVPackageRoot}]\office15\MSACCESS.EXE" Enabled="true">
|
||||
<VisualElements>
|
||||
<Name>Access 2013</Name>
|
||||
<Icon />
|
||||
<Description />
|
||||
</VisualElements>
|
||||
</Application>
|
||||
```
|
||||
|
||||
6. Re-add the Office 2013 App-V package, and then republish it with the new Deployment Configuration File to apply the new settings to Office 2013 App-V Package applications.
|
||||
|
||||
### <a href="" id="bkmk-disable-shortcuts"></a>Disabling Office 2013 shortcuts
|
||||
|
||||
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 <shortcut> </shortcut> intact to disable the Microsoft Access shortcut.
|
||||
|
||||
``` syntax
|
||||
Shortcuts
|
||||
|
||||
-->
|
||||
<Shortcuts Enabled="true">
|
||||
<Extensions>
|
||||
<Extension Category="AppV.Shortcut">
|
||||
<Shortcut>
|
||||
<File>[{Common Programs}]\Microsoft Office 2013\Access 2013.lnk</File>
|
||||
<Target>[{AppvPackageRoot}])office15\MSACCESS.EXE</Target>
|
||||
<Icon>[{Windows}]\Installer\{90150000-000F-0000-0000-000000FF1CE)\accicons.exe.Ø.ico</Icon>
|
||||
<Arguments />
|
||||
<WorkingDirectory />
|
||||
<AppuserModelId>Microsoft.Office.MSACCESS.EXE.15</AppUserModelId>
|
||||
<AppUsermodelExcludeFroeShowInNewInstall>true</AppUsermodelExcludeFroeShowInNewInstall>
|
||||
<Description>Build a professional app quickly to manage data.</Description>
|
||||
<ShowCommand>l</ShowCommand>
|
||||
<ApplicationId>[{AppVPackageRoot}]\officel5\MSACCESS.EXE</ApplicationId>
|
||||
</Shortcut>
|
||||
```
|
||||
|
||||
3. Save the Deployment Configuration File.
|
||||
|
||||
4. Republish Office 2013 App-V Package with new Deployment Configuration File.
|
||||
|
||||
Many additional settings can be changed through modifying the Deployment Configuration for App-V packages, for example, file type associations, Virtual File System, and more. For additional information on how to use Deployment Configuration Files to change App-V package settings, refer to the additional resources section at the end of this document.
|
||||
|
||||
### <a href="" id="bkmk-manage-office-pkg-upgrd"></a>Managing Office 2013 package upgrades
|
||||
|
||||
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**
|
||||
|
||||
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.
|
||||
|
||||
**Note**
|
||||
Office App-V packages have two Version IDs:
|
||||
|
||||
- An Office 2013 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.
|
||||
|
||||
- A second App-V Package Version ID, x.x.x.x for example, in the AppX manifest that will only change if there is a new version of Office itself. For example, if a new Office 2013 release with upgrades is available, and a package is created through the Office Deployment Tool to incorporate these upgrades, the X.X.X.X version ID will change to reflect that the Office version itself has changed. The App-V server will use the X.X.X.X version ID to differentiate this package and recognize that it contains new upgrades to the previously published package, and as a result, publish it as an upgrade to the existing Office 2013 package.
|
||||
|
||||
|
||||
|
||||
2. Globally publish the newly created Office 2013 App-V Packages onto computers where you would like to apply the new updates. Since the new package has the same lineage of the older Office 2013 App-V Package, publishing the new package with the updates will only apply the new changes to the old package, and thus will be fast.
|
||||
|
||||
3. Upgrades will be applied in the same manner of any globally published App-V Packages. Because applications will probably be in use, upgrades might be delayed until the computer is rebooted.
|
||||
|
||||
### <a href="" id="bkmk-manage-office-lic-upgrd"></a>Managing Office 2013 licensing upgrades
|
||||
|
||||
If a new Office 2013 App-V Package has a different license than the Office 2013 App-V Package currently deployed. For instance, the Office 2013 package deployed is a subscription based Office 2013 and the new Office 2013 package is Volume Licensing based, the following instructions must be followed to ensure smooth licensing upgrade:
|
||||
|
||||
**How to upgrade an Office 2013 License**
|
||||
|
||||
1. Unpublish the already deployed Office 2013 Subscription Licensing App-V package.
|
||||
|
||||
2. Remove the unpublished Office 2013 Subscription Licensing App-V package.
|
||||
|
||||
3. Restart the computer.
|
||||
|
||||
4. Add the new Office 2013 App-V Package Volume Licensing.
|
||||
|
||||
5. Publish the added Office 2013 App-V Package with Volume Licensing.
|
||||
|
||||
An Office 2013 App-V Package with your chosen licensing will be successfully deployed.
|
||||
|
||||
### <a href="" id="bkmk-deploy-visio-project"></a>Deploying Visio 2013 and Project 2013 with Office
|
||||
|
||||
The following table describes the requirements and options for deploying Visio 2013 and Project 2013 with Office.
|
||||
|
||||
<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>How do I package and publish Visio 2013 and Project 2013 with Office?</p></td>
|
||||
<td align="left"><p>You must include Visio 2013 and Project 2013 in the same package with Office.</p>
|
||||
<p>If you aren’t deploying Office, you can create a package that contains Visio and/or Project, as long as you follow the [Virtualizing Microsoft Office 2013 for Application Virtualization (App-V) 5.0](https://technet.microsoft.com/en-us/itpro/mdop/solutions/virtualizing-microsoft-office-2013-for-application-virtualization--app-v--50-solutions#bkmk-pkg-pub-reqs).</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>How can I deploy Visio 2013 and Project 2013 to specific users?</p></td>
|
||||
<td align="left"><p>Use one of the following methods:</p>
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">If you want to...</th>
|
||||
<th align="left">...then use this 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 [Microsoft AppLocker](http://technet.microsoft.com/library/dd723678.aspx) to prevent specific users from using Visio and Project.</p></li>
|
||||
</ol></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p> </p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Additional resources
|
||||
|
||||
|
||||
**Office 2013 App-V Packages Additional Resources**
|
||||
|
||||
[Office Deployment Tool for Click-to-Run](http://go.microsoft.com/fwlink/p/?LinkID=330672)
|
||||
|
||||
[Supported scenarios for deploying Microsoft Office as a sequenced App-V Package](http://go.microsoft.com/fwlink/p/?LinkId=330680)
|
||||
|
||||
**Office 2010 App-V Packages**
|
||||
|
||||
[Microsoft Office 2010 Sequencing Kit for Microsoft Application Virtualization 5.0](http://go.microsoft.com/fwlink/p/?LinkId=330681)
|
||||
|
||||
[Known issues when you create or use an App-V 5.0 Office 2010 package](http://go.microsoft.com/fwlink/p/?LinkId=330682)
|
||||
|
||||
[How to sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0](http://go.microsoft.com/fwlink/p/?LinkId=330676)
|
||||
|
||||
**Connection Groups**
|
||||
|
||||
[Deploying Connection Groups in Microsoft App-V v5](http://go.microsoft.com/fwlink/p/?LinkId=330683)
|
||||
|
||||
[Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
|
||||
**Dynamic Configuration**
|
||||
|
||||
[About App-V Dynamic Configuration](appv-dynamic-configuration.md)
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,52 @@
|
||||
---
|
||||
title: Deploying App-V Packages by Using Electronic Software Distribution (ESD)
|
||||
description: Deploying App-V Packages by Using Electronic Software Distribution (ESD)
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Deploying App-V Packages by Using Electronic Software Distribution (ESD)
|
||||
|
||||
|
||||
You can deploy App-V packages using an Electronic Software Distribution (ESD) solution. For information about planning to deploy App-V packages with an ESD, see [Planning to Deploy App-V with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md).
|
||||
|
||||
To deploy App-V packages with Microsoft System Center 2012 Configuration Manager, see [Introduction to Application Management in Configuration Manager](http://go.microsoft.com/fwlink/?LinkId=281816)
|
||||
|
||||
## How to deploy virtualized packages using an ESD
|
||||
|
||||
|
||||
Describes the methods you can use to deploy App-V packages by using an ESD
|
||||
|
||||
[How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md)
|
||||
|
||||
## How to Enable Only Administrators to Publish Packages by Using an ESD
|
||||
|
||||
|
||||
Explains how to configure the App-V client to enable only administrators to publish and unpublish packages when you’re using an ESD.
|
||||
|
||||
[How to Enable Only Administrators to Publish Packages by Using an ESD](appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md)
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Other resources for using an ESD and App-V
|
||||
|
||||
|
||||
Use the following link for more information about [App-V and Citrix Integration](http://go.microsoft.com/fwlink/?LinkId=330294 ) (http://go.microsoft.com/fwlink/?LinkId=330294).
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,97 @@
|
||||
---
|
||||
title: Deploy the App-V Sequencer and Client (Windows 10)
|
||||
description: Deploying the App-V Sequencer and Client
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Deploying the App-V Sequencer and Client
|
||||
|
||||
The App-V Sequencer and client enable administrators to virtualize and run virtualized applications.
|
||||
|
||||
## Enable the client
|
||||
|
||||
|
||||
The App-V client is the component that runs a virtualized application on a target computer. The client enables users to interact with icons and to double-click file types, so that they can start a virtualized application. The client can also obtain the virtual application content from the management server.
|
||||
|
||||
> [!NOTE]
|
||||
> In Windows 10, version 1607, App-V is included with the OS. You only need to enable it.
|
||||
|
||||
[Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)
|
||||
|
||||
## Client Configuration Settings
|
||||
|
||||
|
||||
The App-V client stores its configuration in the registry. You can gather some useful information about the client if you understand the format of data in the registry. You can also configure many client actions by changing registry entries.
|
||||
|
||||
[About Client Configuration Settings](appv-client-configuration-settings.md)
|
||||
|
||||
## Configure the client by using the ADMX template and Group Policy
|
||||
|
||||
You can use Group Policy to configure the client settings for the App-V client and the Remote Desktop Services client.
|
||||
|
||||
|
||||
Perform the following steps on the computer that you will use to manage Group Policy. This is typically the Domain Controller.
|
||||
|
||||
1. Save the **.admx** file to the following directory: **Windows \\ PolicyDefinitions**
|
||||
|
||||
2. Save the **.adml** file to the following directory: **Windows \\ PolicyDefinitions \\ <Language Directory>**
|
||||
|
||||
After you have completed the preceding steps, you can manage the App-V client configuration settings with the **Group Policy Management** console.
|
||||
|
||||
The App-V client also stores its configuration in the registry. You can gather some useful information about the client if you understand the format of the data in the registry. You can also configure many client actions by changing registry entries.
|
||||
|
||||
[How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md)
|
||||
|
||||
## Deploy the client by using the Shared Content Store mode
|
||||
|
||||
The App-V Shared Content Store (SCS) mode enables the SCS App-V clients to run virtualized applications without saving any of the associated package data locally. All required virtualized package data is transmitted across the network; therefore, you should only use the SCS mode in environments with a fast connection. Both the Remote Desktop Services (RDS) and the standard version of the App-V client are supported with SCS mode.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If the App-V client is configured to run in the SCS mode, the location where the App-V packages are streamed from must be available, otherwise, the virtualized package will fail. Additionally, we do not recommend deployment of virtualized applications to computers that run the App-V client in the SCS mode across the internet.
|
||||
|
||||
Additionally, the SCS is not a physical location that contains virtualized packages. It is a mode that allows the App-V client to stream the required virtualized package data across the network.
|
||||
|
||||
The SCS mode is helpful in the following scenarios:
|
||||
|
||||
- Virtual desktop infrastructure (VDI) deployments
|
||||
|
||||
- Remote Desktop Services deployments
|
||||
|
||||
To use SCS in your environment, you must enable the App-V client to run in SCS mode. This setting should be specified during installation. By default, the client is not configured to use SCS mode. You should install the client by using the suggested procedure if you plan to use SCS. However, you can configure an existing App-V client to run in SCS mode by entering the following Windows PowerShell command on the computer that runs the App-V client:
|
||||
|
||||
```
|
||||
set-AppvClientConfiguration -SharedContentStoreMode 1
|
||||
```
|
||||
|
||||
There might be cases when the administrator pre-loads some virtual applications on the computer that runs the App-V client in SCS mode. This can be accomplished with Windows PowerShell commands to add, publish, and mount the package. For example, if a package is pre-loaded on all computers, the administrator could add, publish, and mount the package by using Windows PowerShell commands. The package would not stream across the network because it would be locally stored.
|
||||
|
||||
[How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)
|
||||
|
||||
## Deploy the Sequencer
|
||||
|
||||
The Sequencer is a tool that is used to convert standard applications into virtual packages for deployment to computers that run the App-V client. The Sequencer helps provide a simple and predictable conversion process with minimal changes to prior sequencing workflows. In addition, the Sequencer allows users to more easily configure applications to enable connections of virtualized applications.
|
||||
|
||||
For a list of changes in the App-V Sequencer, see [About App-V](appv-about-appv.md).
|
||||
|
||||
[How to Install the Sequencer](appv-install-the-sequencer.md)
|
||||
|
||||
## App-V Client and Sequencer logs
|
||||
|
||||
|
||||
You can use the App-V Sequencer log information to help troubleshoot the Sequencer installation and operational events while using App-V. The Sequencer-related log information can be reviewed with the **Event Viewer**. The following line displays the specific path for Sequencer-related events:
|
||||
|
||||
**Event Viewer \\ Applications and Services Logs \\ Microsoft \\ App V**. Sequencer-related events are prepended with **AppV\_Sequencer**. Client-related events are prepended with **AppV\_Client**.
|
||||
|
||||
## Other resources for deploying the Sequencer and client
|
||||
|
||||
- [Deploying App-V](appv-deploying-appv.md)
|
||||
- [Planning for App-V](appv-planning-for-appv.md)
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
104
windows/manage/appv-deploying-the-appv-server.md
Normal file
104
windows/manage/appv-deploying-the-appv-server.md
Normal file
@ -0,0 +1,104 @@
|
||||
---
|
||||
title: Deploying the App-V Server (Windows 10)
|
||||
description: Deploying the App-V Server
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# Deploying the App-V Server
|
||||
|
||||
You can install the App-V server features by 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).
|
||||
|
||||
For information about deploying the App-V Server, see [About App-V](appv-about-appv.md).
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Before you install and configure the App-V servers, you must specify a port where each component will be hosted. You must also add the associated firewall rules to allow incoming requests to access the specified ports. The installer does not modify firewall settings.
|
||||
|
||||
## Download and install App-V Server components
|
||||
|
||||
App-V offers the following five server components, each of which serves a specific purpose in an App-V environment. All five server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from the [Microsoft Developer Network (MSDN) subscription site](https://msdn.microsoft.com/en-us/subscriptions/downloads/default.aspx#FileId=65215). You must have a MSDN subscription to download MDOP.
|
||||
|
||||
- **Management server**. Use the App-V management server and console to manage your App-V infrastructure. See [Administering App-V with the management console](appv-administering-virtual-applications-with-the-management-console.md) for more information about the management server.
|
||||
|
||||
**Note**: If you are using App-V with your electronic software distribution solution, you don’t need to use the management server and console. However, you can still take advantage of the reporting and streaming capabilities in App-V.
|
||||
|
||||
- **Management database**. Use the App-V management database to facilitate database pre-deployments for App-V management. See [How to deploy the App-V server components](appv-deploy-the-appv-server.md) for more information about the management database.
|
||||
|
||||
- **Publishing server**. Use the App-V publishing server to host and stream virtual applications. The publishing server supports the HTTP and HTTPS protocols and does not require a database connection. See [How to install the App-V publishing server](appv-install-the-publishing-server-on-a-remote-computer.md) for more information about configuring the publishing server.
|
||||
|
||||
- **Reporting server**. Use the App-V reporting server to generate reports that help you manage your App-V infrastructure. The reporting server requires a connection to the reporting database. See [About App-V reporting](appv-reporting.md) for more information about the reporting capabilities in App-V.
|
||||
|
||||
- **Reporting database**. Use the App-V reporting database to facilitate database pre-deployments for App-V reporting. See [How to deploy the App-V server](appv-deploy-the-appv-server.md) for more information about the reporting database.
|
||||
|
||||
In large organizations, you might want to install more than one instance of the server components to get:
|
||||
|
||||
- Fault tolerance for situations when one of the servers is unavailable.
|
||||
|
||||
- High availability to balance server requests. We recommend using a network load balancer to achieve this.
|
||||
|
||||
- Scalability to support a high load. For example, you can install additional servers behind a network load balancer.
|
||||
|
||||
## App-V standalone deployment
|
||||
|
||||
|
||||
The App-V standalone deployment provides a good topology for a small deployment or a test environment. When you use this type of implementation, all server components are deployed to a single computer. The services and associated databases will compete for the resources on the computer that runs the App-V components. Therefore, you should not use this topology for larger deployments.
|
||||
|
||||
- [How to Deploy the App-V Server](appv-deploy-the-appv-server.md)
|
||||
- [How to Deploy the App-V Server Using a Script](appv-deploy-the-appv-server-with-a-script.md)
|
||||
|
||||
## App-V Server distributed deployment
|
||||
|
||||
The distributed deployment topology can support a large App-V client base and it allows you to more easily manage and scale your environment. When you use this type of deployment, the App-V Server components are deployed across multiple computers, based on the structure and requirements of the organization.
|
||||
|
||||
- [How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services](appv-install-the-management-and-reporting-databases-on-separate-computers.md)
|
||||
- [How to install the Management Server on a Standalone Computer and Connect it to the Database](appv-install-the-management-server-on-a-standalone-computer.md)
|
||||
- [How to Deploy the App-V Server Using a Script](appv-deploy-the-appv-server-with-a-script.md)
|
||||
- [How to Install the Publishing Server on a Remote Computer](appv-install-the-publishing-server-on-a-remote-computer.md)
|
||||
- [How to install the Management Server on a Standalone Computer and Connect it to the Database](appv-install-the-management-server-on-a-standalone-computer.md)
|
||||
|
||||
## Using an Enterprise Software Distribution (ESD) solution and App-V
|
||||
|
||||
You can also deploy the App-V clients and packages by using an ESD without having to deploy App-V. The full capabilities for integration will vary depending on the ESD that you use.
|
||||
|
||||
> [!NOTE]
|
||||
> The App-V reporting server and reporting database can still be deployed alongside the ESD to collect the reporting data from the App-V clients. However, the other three server components should not be deployed, because they will conflict with the ESD functionality.
|
||||
|
||||
[Deploying App-V Packages by Using Electronic Software Distribution (ESD)](appv-deploying-packages-with-electronic-software-distribution-solutions.md)
|
||||
|
||||
## App-V Server logs
|
||||
|
||||
You can use App-V server log information to help troubleshoot the server installation and operational events while using App-V. The server-related log information can be reviewed with the **Event Viewer**. The following line displays the specific path for Server-related events:
|
||||
|
||||
**Event Viewer \\ Applications and Services Logs \\ Microsoft \\ App V**
|
||||
|
||||
Associated setup logs are saved in the following directory:
|
||||
|
||||
**%temp%**
|
||||
|
||||
## App-V reporting
|
||||
|
||||
App-V reporting allows App-V clients to collect data and then send it back to be stored in a central repository. You can use this information to get a better view of the virtual application usage within your organization. The following list displays some of the types of information the App-V client collects:
|
||||
|
||||
- Information about the computer that runs the App-V client.
|
||||
|
||||
- Information about virtualized packages on a specific computer that runs the App-V client.
|
||||
|
||||
- Information about package open and shutdown for a specific user.
|
||||
|
||||
The reporting information will be maintained until it is successfully sent to the reporting server database. After the data is in the database, you can use Microsoft SQL Server Reporting Services to generate any necessary reports.
|
||||
|
||||
If you want to retrieve report information, you must use Microsoft SQL Server Reporting Services (SSRS) which is available with Microsoft SQL. SSRS is not installed when you install the App-V reporting server and it must be deployed separately to generate the associated reports.
|
||||
|
||||
|
||||
For more information, see [About App-V Reporting](appv-reporting.md) and [How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md).
|
||||
|
||||
## Other resources for the App-V server
|
||||
|
||||
- [Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
76
windows/manage/appv-deployment-checklist.md
Normal file
76
windows/manage/appv-deployment-checklist.md
Normal file
@ -0,0 +1,76 @@
|
||||
---
|
||||
title: App-V Deployment Checklist (Windows 10)
|
||||
description: App-V Deployment Checklist
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# App-V Deployment Checklist
|
||||
|
||||
|
||||
This checklist can be used to help you during an App-V deployment.
|
||||
|
||||
> [!NOTE]
|
||||
> This checklist outlines the recommended steps and a high-level list of items to consider when deploying App-V features. It is recommended that you copy this checklist into a spreadsheet program and customize it for your use.
|
||||
|
||||
<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>Complete the planning phase to prepare the computing environment for App-V deployment.</p></td>
|
||||
<td align="left"><p>[App-V Planning Checklist](appv-planning-checklist.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>Review the App-V supported configurations information to make sure selected client and server computers are supported for App-V feature installation.</p></td>
|
||||
<td align="left"><p>[App-V Supported Configurations](appv-supported-configurations.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>Run App-V Setup to deploy the required App-V features for your environment.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>Keep track of the names of the servers and associated URLs created during installation. This information will be used throughout the installation process.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
</div></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>[How to Install the Sequencer](appv-install-the-sequencer.md)</p></li>
|
||||
<li><p>[Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)</p></li>
|
||||
<li><p>[How to Deploy the App-V Server](appv-deploy-the-appv-server.md)</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
[Deploying App-V](appv-deploying-appv.md)
|
||||
742
windows/manage/appv-dynamic-configuration.md
Normal file
742
windows/manage/appv-dynamic-configuration.md
Normal file
@ -0,0 +1,742 @@
|
||||
---
|
||||
title: About App-V Dynamic Configuration (Windows 10)
|
||||
description: About App-V Dynamic Configuration
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# About App-V Dynamic Configuration
|
||||
|
||||
You can use the dynamic configuration to customize an App-V package for a user. Use the following information to create or edit an existing dynamic configuration file.
|
||||
|
||||
When you edit the dynamic configuration file it customizes how an App-V package will run for a user or group. This helps to provide a more convenient method for package customization by removing the need to re-sequence packages using the desired settings, and provides a way to keep package content and custom settings independent.
|
||||
|
||||
## Advanced: Dynamic Configuration
|
||||
|
||||
|
||||
Virtual application packages contain a manifest that provides all the core information for the package. This information includes the defaults for the package settings and determines settings in the most basic form (with no additional customization). If you want to adjust these defaults for a particular user or group, you can create and edit the following files:
|
||||
|
||||
- User Configuration file
|
||||
|
||||
- Deployment configuration file
|
||||
|
||||
The previous .xml files specify package settings and allow for packages to be customized without directly affecting the packages. When a package is created, the sequencer automatically generates default deployment and user configuration .xml files using the package manifest data. Therefore, these automatically generated configuration files simply reflect the default settings that the package innately as from how things were configured during sequencing. If you apply these configuration files to a package in the form generated by the sequencer, the packages will have the same default settings that came from their manifest. This provides you with a package-specific template to get started if any of the defaults must be changed.
|
||||
|
||||
**Note**
|
||||
The following information can only be used to modify sequencer generated configuration files to customize packages to meet specific user or group requirements.
|
||||
|
||||
|
||||
|
||||
### Dynamic Configuration file contents
|
||||
|
||||
All of the additions, deletions, and updates in the configuration files need to be made in relation to the default values specified by the package's manifest information. Review the following table:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="100%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>User Configuration .xml file</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Deployment Configuration .xml file</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Package Manifest</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
The previous table represents how the files will be read. The first entry represents what will be read last, therefore, its content takes precedence. Therefore, all packages inherently contain and provide default settings from the package manifest. If a deployment configuration .xml file with customized settings is applied, it will override the package manifest defaults. If a user configuration .xml file with customized settings is applied prior to that, it will override both the deployment configuration and the package manifest defaults.
|
||||
|
||||
The following list displays more information about the two file types:
|
||||
|
||||
- **User Configuration File (UserConfig)** – Allows you to specify or modify custom settings for a package. These settings will be applied for a specific user when the package is deployed to a computer running the App-V client.
|
||||
|
||||
- **Deployment Configuration File (DeploymentConfig)** – Allows you to specify or modify the default settings for a package. These settings will be applied for all users when a package is deployed to a computer running the App-V client.
|
||||
|
||||
To customize the settings for a package for a specific set of users on a computer or to make changes that will be applied to local user locations such as HKCU, the UserConfig file should be used. To modify the default settings of a package for all users on a machine or to make changes that will be applied to global locations such as HKEY\_LOCAL\_MACHINE and the all users folder, the DeploymentConfig file should be used.
|
||||
|
||||
The UserConfig file provides configuration settings that can be applied to a single user without affecting any other users on a client:
|
||||
|
||||
- Extensions that will be integrated into the native system per user:- shortcuts, File-Type associations, URL Protocols, AppPaths, Software Clients and COM
|
||||
|
||||
- Virtual Subsystems:- Application Objects, Environment variables, Registry modifications, Services and Fonts
|
||||
|
||||
- Scripts (User context only)
|
||||
|
||||
The DeploymentConfig file provides configuration settings in two sections, one relative to the machine context and one relative to the user context providing the same capabilities listed in the UserConfig list above:
|
||||
|
||||
- All UserConfig settings above
|
||||
|
||||
- Extensions that can only be applied globally for all users
|
||||
|
||||
- Virtual Subsystems that can be configured for global machine locations e.g. registry
|
||||
|
||||
- Product Source URL
|
||||
|
||||
- Scripts (Machine context only)
|
||||
|
||||
- Controls to Terminate Child Processes
|
||||
|
||||
### File structure
|
||||
|
||||
The structure of the App-V Dynamic Configuration file is explained in the following section.
|
||||
|
||||
### Dynamic User Configuration file
|
||||
|
||||
**Header** - the header of a dynamic user configuration file is as follows:
|
||||
|
||||
```
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<UserConfiguration PackageId="1f8488bf-2257-46b4-b27f-09c9dbaae707" DisplayName="Reserved" xmlns="http://schemas.microsoft.com/appv/2010/userconfiguration">
|
||||
```
|
||||
|
||||
The **PackageId** is the same value as exists in the Manifest file.
|
||||
|
||||
**Body** - the body of the Dynamic User Configuration file can include all the app extension points that are defined in the Manifest file, as well as information to configure virtual applications. There are four subsections allowed in the body:
|
||||
|
||||
**Applications** - All app-extensions that are contained in the Manifest file within a package are assigned with an Application ID, which is also defined in the manifest file. This allows you to enable or disable all the extensions for a given application within a package. The **Application ID** must exist in the Manifest file or it will be ignored.
|
||||
|
||||
```
|
||||
<UserConfiguration PackageId="1f8488bf-2257-46b4-b27f-09c9dbaae707" DisplayName="Reserved" xmlns="http://schemas.microsoft.com/appv/2010/userconfiguration">
|
||||
<Applications>
|
||||
<!-- No new application can be defined in policy. AppV Client will ignore any application ID that is not also in the Manifest file -->
|
||||
<Application Id="{a56fa627-c35f-4a01-9e79-7d36aed8225a}" Enabled="false">
|
||||
</Application>
|
||||
</Applications>
|
||||
…
|
||||
</UserConfiguration>
|
||||
```
|
||||
|
||||
**Subsystems** - AppExtensions and other subsystems are arranged as subnodes under the <Subsystems>:
|
||||
|
||||
```
|
||||
<UserConfiguration **PackageId**="1f8488bf-2257-46b4-b27f-09c9dbaae707" DisplayName="Reserved" xmlns="http://schemas.microsoft.com/appv/2010/userconfiguration">
|
||||
<Subsystems>
|
||||
..
|
||||
</Subsystems>
|
||||
..
|
||||
</UserConfiguration>
|
||||
```
|
||||
|
||||
Each subsystem can be enabled/disabled using the “**Enabled**” attribute. Below are the various subsystems and usage samples.
|
||||
|
||||
**Extensions:**
|
||||
|
||||
Some subsystems (Extension Subsystems) control Extensions. Those subsystems are:- shortcuts, File-Type associations, URL Protocols, AppPaths, Software Clients and COM
|
||||
|
||||
Extension Subsystems can be enabled and disabled independently of the content. Thus if Shortcuts are enabled, The client will use the shortcuts contained within the manifest by default. Each Extension Subsystem can contain an <Extensions> node. If this child element is present, the client will ignore the content in the Manifest file for that subsystem and only use the content in the configuration file.
|
||||
|
||||
Example using the shortcuts subsystem:
|
||||
|
||||
**Example 1**<br>If the user defined this in either the dynamic or deployment config file:
|
||||
|
||||
```
|
||||
<Shortcuts Enabled="true">
|
||||
<Extensions
|
||||
...
|
||||
</Extensions>
|
||||
</Shortcuts>
|
||||
```
|
||||
|
||||
Content in the manifest will be ignored.
|
||||
|
||||
**Example 2**<br>If the user defined only the following:
|
||||
|
||||
`<Shortcuts Enabled="true"/>`
|
||||
|
||||
Then the content in the Manifest will be integrated during publishing.
|
||||
|
||||
**Example 3**<br>If the user defines the following
|
||||
|
||||
```
|
||||
<Shortcuts Enabled="true">
|
||||
<Extensions/>
|
||||
</Shortcuts>
|
||||
```
|
||||
|
||||
Then all the shortcuts within the manifest will still be ignored. There will be no shortcuts integrated.
|
||||
|
||||
The supported Extension Subsystems are:
|
||||
|
||||
**Shortcuts:** This controls shortcuts that will be integrated into the local system. Below is a sample with 2 shortcuts:
|
||||
|
||||
```
|
||||
<Subsystems>
|
||||
<Shortcuts Enabled="true">
|
||||
<Extensions>
|
||||
<Extension Category="AppV.Shortcut">
|
||||
<Shortcut>
|
||||
<File>\[{Common Programs}\]\\Microsoft Contoso\\Microsoft ContosoApp Filler 2010.lnk</File>
|
||||
<Target>\[{PackageRoot}\]\\Contoso\\ContosoApp.EXE</Target>
|
||||
<Icon>\[{Windows}\]\\Installer\\{90140000-0011-0000-0000-0000000FF1CE}\\inficon.exe</Icon>
|
||||
<Arguments />
|
||||
<WorkingDirectory />
|
||||
<AppUserModelId>ContosoApp.Filler.3</AppUserModelId>
|
||||
<Description>Fill out dynamic forms to gather and reuse information throughout the organization using Microsoft ContosoApp.</Description>
|
||||
<Hotkey>0</Hotkey>
|
||||
<ShowCommand>1</ShowCommand>
|
||||
<ApplicationId>\[{PackageRoot}\]\\Contoso\\ContosoApp.EXE</ApplicationId>
|
||||
</Shortcut>
|
||||
</Extension>
|
||||
<Extension Category="AppV.Shortcut">
|
||||
<Shortcut>
|
||||
<File>\[{AppData}\]\\Microsoft\\Contoso\\Recent\\Templates.LNK</File>
|
||||
<Target>\[{AppData}\]\\Microsoft\\Templates</Target>
|
||||
<Icon />
|
||||
<Arguments />
|
||||
<WorkingDirectory />
|
||||
<AppUserModelId />
|
||||
<Description />
|
||||
<Hotkey>0</Hotkey>
|
||||
<ShowCommand>1</ShowCommand>
|
||||
<!-- Note the ApplicationId is optional -->
|
||||
</Shortcut>
|
||||
</Extension>
|
||||
</Extensions>
|
||||
</Shortcuts>
|
||||
```
|
||||
|
||||
**File-Type Associations:** Associates File-types with programs to open by default as well as setup the context menu. (MIME types can also be setup using this susbsystem). Sample File-type Association is below:
|
||||
|
||||
```
|
||||
<FileTypeAssociations Enabled="true">
|
||||
<Extensions>
|
||||
<Extension Category="AppV.FileTypeAssociation">
|
||||
<FileTypeAssociation>
|
||||
<FileExtension MimeAssociation="true">
|
||||
<Name>.docm</Name>
|
||||
<ProgId>contosowordpad.DocumentMacroEnabled.12</ProgId>
|
||||
<PerceivedType>document</PerceivedType>
|
||||
<ContentType>application/vnd.ms-contosowordpad.document.macroEnabled.12</ContentType>
|
||||
<OpenWithList>
|
||||
<ApplicationName>wincontosowordpad.exe</ApplicationName>
|
||||
</OpenWithList>
|
||||
<OpenWithProgIds>
|
||||
<ProgId>contosowordpad.8</ProgId>
|
||||
</OpenWithProgIds>
|
||||
<ShellNew>
|
||||
<Command />
|
||||
<DataBinary />
|
||||
<DataText />
|
||||
<FileName />
|
||||
<NullFile>true</NullFile>
|
||||
<ItemName />
|
||||
<IconPath />
|
||||
<MenuText />
|
||||
<Handler />
|
||||
</ShellNew>
|
||||
</FileExtension>
|
||||
<ProgId>
|
||||
<Name>contosowordpad.DocumentMacroEnabled.12</Name>
|
||||
<DefaultIcon>\[{Windows}\]\\Installer\\{90140000-0011-0000-0000-0000000FF1CE}\\contosowordpadicon.exe,15</DefaultIcon>
|
||||
<Description>Blah Blah Blah</Description>
|
||||
<FriendlyTypeName>\[{FOLDERID\_ProgramFilesX86}\]\\Microsoft Contoso 14\\res.dll,9182</FriendlyTypeName>
|
||||
<InfoTip>\[{FOLDERID\_ProgramFilesX86}\]\\Microsoft Contoso 14\\res.dll,1424</InfoTip>
|
||||
<EditFlags>0</EditFlags>
|
||||
<ShellCommands>
|
||||
<DefaultCommand>Open</DefaultCommand>
|
||||
<ShellCommand>
|
||||
<ApplicationId>{e56fa627-c35f-4a01-9e79-7d36aed8225a}</ApplicationId>
|
||||
<Name>Edit</Name>
|
||||
<FriendlyName>&Edit</FriendlyName>
|
||||
<CommandLine>"\[{PackageRoot}\]\\Contoso\\WINcontosowordpad.EXE" /vu "%1"</CommandLine>
|
||||
</ShellCommand>
|
||||
</ShellCommand>
|
||||
<ApplicationId>{e56fa627-c35f-4a01-9e79-7d36aed8225a}</ApplicationId>
|
||||
<Name>Open</Name>
|
||||
<FriendlyName>&Open</FriendlyName>
|
||||
<CommandLine>"\[{PackageRoot}\]\\Contoso\\WINcontosowordpad.EXE" /n "%1"</CommandLine>
|
||||
<DropTargetClassId />
|
||||
<DdeExec>
|
||||
<Application>mscontosowordpad</Application>
|
||||
<Topic>ShellSystem</Topic>
|
||||
<IfExec>\[SHELLNOOP\]</IfExec>
|
||||
<DdeCommand>\[SetForeground\]\[ShellNewDatabase "%1"\]</DdeCommand>
|
||||
</DdeExec>
|
||||
</ShellCommand>
|
||||
</ShellCommands>
|
||||
</ProgId>
|
||||
</FileTypeAssociation>
|
||||
</Extension>
|
||||
</Extensions>
|
||||
</FileTypeAssociations>
|
||||
```
|
||||
|
||||
**URL Protocols**: This controls the URL Protocols that are integrated into the local registry of the client machine e.g. “mailto:”.
|
||||
|
||||
```
|
||||
<URLProtocols Enabled="true">
|
||||
<Extensions>
|
||||
<Extension Category="AppV.URLProtocol">
|
||||
<URLProtocol>
|
||||
<Name>mailto</Name>
|
||||
<ApplicationURLProtocol>
|
||||
<DefaultIcon>\[{ProgramFilesX86}\]\\Microsoft Contoso\\Contoso\\contosomail.EXE,-9403</DefaultIcon>
|
||||
<EditFlags>2</EditFlags>
|
||||
<Description />
|
||||
<AppUserModelId />
|
||||
<FriendlyTypeName />
|
||||
<InfoTip />
|
||||
<SourceFilter />
|
||||
<ShellFolder />
|
||||
<WebNavigableCLSID />
|
||||
<ExplorerFlags>2</ExplorerFlags>
|
||||
<CLSID />
|
||||
<ShellCommands>
|
||||
<DefaultCommand>open</DefaultCommand>
|
||||
<ShellCommand>
|
||||
<ApplicationId>\[{ProgramFilesX86}\]\\Microsoft Contoso\\Contoso\\contosomail.EXE</ApplicationId>
|
||||
<Name>open</Name>
|
||||
<CommandLine>\[{ProgramFilesX86}\\Microsoft Contoso\\Contoso\\contosomail.EXE" -c OEP.Note /m "%1"</CommandLine>
|
||||
<DropTargetClassId />
|
||||
<FriendlyName />
|
||||
<Extended>0</Extended>
|
||||
<LegacyDisable>0</LegacyDisable>
|
||||
<SuppressionPolicy>2</SuppressionPolicy>
|
||||
<DdeExec>
|
||||
<NoActivateHandler />
|
||||
<Application>contosomail</Application>
|
||||
<Topic>ShellSystem</Topic>
|
||||
<IfExec>\[SHELLNOOP\]</IfExec>
|
||||
<DdeCommand>\[SetForeground\]\[ShellNewDatabase "%1"\]</DdeCommand>
|
||||
</DdeExec>
|
||||
</ShellCommand>
|
||||
</ShellCommands>
|
||||
</ApplicationURLProtocol>
|
||||
</URLProtocol>
|
||||
</Extension>
|
||||
</Extension>
|
||||
</URLProtocols>
|
||||
```
|
||||
|
||||
**Software Clients**: Allows the app to register as an Email client, news reader, media player and makes the app visible in the Set Program Access and Computer Defaults UI. In most cases you should only need to enable and disable it. There is also a control to enable and disable the email client specifically if you want the other clients still enabled except for that client.
|
||||
|
||||
```
|
||||
<SoftwareClients Enabled="true">
|
||||
<ClientConfiguration EmailEnabled="false" />
|
||||
</SoftwareClients>
|
||||
```
|
||||
|
||||
**AppPaths**: If an application for example contoso.exe is registered with an apppath name of “myapp”, it allows you type “myapp” under the run menu and it will open contoso.exe.
|
||||
|
||||
```
|
||||
<AppPaths Enabled="true">
|
||||
<Extensions>
|
||||
<Extension Category="AppV.AppPath">
|
||||
<AppPath>
|
||||
<ApplicationId>\[{ProgramFilesX86}\]\\Microsoft Contoso\\Contoso\\contosomail.EXE</ApplicationId>
|
||||
<Name>contosomail.exe</Name>
|
||||
<ApplicationPath>\[{ProgramFilesX86}\]\\Microsoft Contoso\\Contoso\\contosomail.EXE</ApplicationPath>
|
||||
<PATHEnvironmentVariablePrefix />
|
||||
<CanAcceptUrl>false</CanAcceptUrl>
|
||||
<SaveUrl />
|
||||
</AppPath>
|
||||
</Extension>
|
||||
</Extensions>
|
||||
</AppPaths>
|
||||
```
|
||||
|
||||
**COM**: Allows an Application register Local COM servers. Mode can be Integration, Isolated or Off. When Isol.
|
||||
|
||||
` <COM Mode="Isolated"/>`
|
||||
|
||||
**Other Settings**:
|
||||
|
||||
In addition to Extensions, other subsystems can be enabled/disabled and edited:
|
||||
|
||||
**Virtual Kernel Objects**:
|
||||
|
||||
` <Objects Enabled="false" />`
|
||||
|
||||
**Virtual Registry**: Used if you want to set a registry in the Virtual Registry within HKCU
|
||||
|
||||
```
|
||||
<Registry Enabled="true">
|
||||
<Include>
|
||||
<Key Path="\\REGISTRY\\USER\\\[{AppVCurrentUserSID}\]\\Software\\ABC">
|
||||
<Value Type="REG\_SZ" Name="Bar" Data="NewValue" />
|
||||
</Key>
|
||||
<Key Path="\\REGISTRY\\USER\\\[{AppVCurrentUserSID}\]\\Software\\EmptyKey" />
|
||||
</Include>
|
||||
<Delete>
|
||||
</Registry>
|
||||
```
|
||||
|
||||
**Virtual File System**
|
||||
|
||||
` <FileSystem Enabled="true" />`
|
||||
|
||||
**Virtual Fonts**
|
||||
|
||||
` <Fonts Enabled="false" />`
|
||||
|
||||
**Virtual Environment Variables**
|
||||
|
||||
```
|
||||
<EnvironmentVariables Enabled="true">
|
||||
<Include>
|
||||
<Variable Name="UserPath" Value="%path%;%UserProfile%" />
|
||||
<Variable Name="UserLib" Value="%UserProfile%\\ABC" />
|
||||
</Include>
|
||||
<Delete>
|
||||
<Variable Name="lib" />
|
||||
</Delete>
|
||||
</EnvironmentVariables>
|
||||
```
|
||||
|
||||
**Virtual services**
|
||||
|
||||
` <Services Enabled="false" />`
|
||||
|
||||
**UserScripts** – Scripts can be used to setup or alter the virtual environment as well as execute scripts at time of deployment or removal, before an application executes, or they can be used to “clean up” the environment after the application terminates. Please reference a sample User configuration file that is output by the sequencer to see a sample script. The Scripts section below provides more information on the various triggers that can be used.
|
||||
|
||||
### Dynamic Deployment Configuration file
|
||||
|
||||
**Header** - The header of a Deployment Configuration file is as follows:
|
||||
|
||||
```
|
||||
<?xml version="1.0" encoding="utf-8"?><DeploymentConfiguration PackageId="1f8488bf-2257-46b4-b27f-09c9dbaae707" DisplayName="Reserved" xmlns="http://schemas.microsoft.com/appv/2010/deploymentconfiguration">
|
||||
```
|
||||
|
||||
The **PackageId** is the same value as exists in the manifest file.
|
||||
|
||||
**Body** - The body of the deployment configuration file includes two sections:
|
||||
|
||||
- User Configuration section –allows the same content as the User Configuration file described in the previous section. When the package is published to a user, any appextensions configuration settings in this section will override corresponding settings in the Manifest within the package unless a user configuration file is also provided. If a UserConfig file is also provided, it will be used instead of the User settings in the deployment configuration file. If the package is published globally, then only the contents of the deployment configuration file will be used in combination with the manifest.
|
||||
|
||||
- Machine Configuration section–contains information that can be configured only for an entire machine, not for a specific user on the machine. For example, HKEY\_LOCAL\_MACHINE registry keys in the VFS.
|
||||
|
||||
```
|
||||
<DeploymentConfiguration PackageId="1f8488bf-2257-46b4-b27f-09c9dbaae707" DisplayName="Reserved" xmlns="http://schemas.microsoft.com/appv/2010/deploymentconfiguration">
|
||||
<UserConfiguration>
|
||||
..
|
||||
</UserConfiguration>
|
||||
<MachineConfiguration>
|
||||
..
|
||||
</MachineConfiguration>
|
||||
..
|
||||
</MachineConfiguration>
|
||||
</DeploymentConfiguration>
|
||||
```
|
||||
|
||||
**User Configuration** - use the previous **Dynamic User Configuration file** section for information on settings that are provided in the user configuration section of the Deployment Configuration file.
|
||||
|
||||
Machine Configuration - the Machine configuration section of the Deployment Configuration File is used to configure information that can be set only for an entire machine, not for a specific user on the computer. For example, HKEY\_LOCAL\_MACHINE registry keys in the Virtual Registry. There are four subsections allowed in under this element
|
||||
|
||||
1. **Subsystems** - AppExtensions and other subsystems are arranged as subnodes under <Subsystems>:
|
||||
|
||||
```
|
||||
<MachineConfiguration>
|
||||
<Subsystems>
|
||||
..
|
||||
</Subsystems>
|
||||
..
|
||||
</MachineConfiguration>
|
||||
```
|
||||
|
||||
The following section displays the various subsystems and usage samples.
|
||||
|
||||
**Extensions**:
|
||||
|
||||
Some subsystems (Extension Subsystems) control Extensions which can only apply to all users. The subsystem is application capabilities. Because this can only apply to all users, the package must be published globally in order for this type of extension to be integrated into the local system. The same rules for controls and settings that apply to the Extensions in the User Configuration also apply to those in the MachineConfiguration section.
|
||||
|
||||
**Application Capabilities**: Used by default programs in windows operating system Interface. Allows an application to register itself as capable of opening certain file extensions, as a contender for the start menu internet browser slot, as capable of opening certain windows MIME types. This extension also makes the virtual application visible in the Set Default Programs UI.:
|
||||
|
||||
```
|
||||
<ApplicationCapabilities Enabled="true">
|
||||
<Extensions>
|
||||
<Extension Category="AppV.ApplicationCapabilities">
|
||||
<ApplicationCapabilities>
|
||||
<ApplicationId>\[{PackageRoot}\]\\LitView\\LitViewBrowser.exe</ApplicationId>
|
||||
<Reference>
|
||||
<Name>LitView Browser</Name>
|
||||
<Path>SOFTWARE\\LitView\\Browser\\Capabilities</Path>
|
||||
</Reference>
|
||||
<CapabilityGroup>
|
||||
<Capabilities>
|
||||
<Name>@\[{ProgramFilesX86}\]\\LitView\\LitViewBrowser.exe,-12345</Name>
|
||||
<Description>@\[{ProgramFilesX86}\]\\LitView\\LitViewBrowser.exe,-12346</Description>
|
||||
<Hidden>0</Hidden>
|
||||
<EMailSoftwareClient>Lit View E-Mail Client</EMailSoftwareClient>
|
||||
<FileAssociationList>
|
||||
<FileAssociation Extension=".htm" ProgID="LitViewHTML" />
|
||||
<FileAssociation Extension=".html" ProgID="LitViewHTML" />
|
||||
<FileAssociation Extension=".shtml" ProgID="LitViewHTML" />
|
||||
</FileAssociationList>
|
||||
<MIMEAssociationList>
|
||||
<MIMEAssociation Type="audio/mp3" ProgID="LitViewHTML" />
|
||||
<MIMEAssociation Type="audio/mpeg" ProgID="LitViewHTML" />
|
||||
</MIMEAssociationList>
|
||||
<URLAssociationList>
|
||||
<URLAssociation Scheme="http" ProgID="LitViewHTML.URL.http" />
|
||||
</URLAssociationList>
|
||||
</Capabilities>
|
||||
</CapabilityGroup>
|
||||
</ApplicationCapabilities>
|
||||
</Extension>
|
||||
</Extensions>
|
||||
</ApplicationCapabilities>
|
||||
```
|
||||
|
||||
**Other Settings**:
|
||||
|
||||
In addition to Extensions, other subsystems can be edited:
|
||||
|
||||
**Machine Wide Virtual Registry**: Used when you want to set a registry key in the virtual registry within HKEY\_Local\_Machine
|
||||
|
||||
```
|
||||
<Registry>
|
||||
<Include>
|
||||
<Key Path="\\REGISTRY\\Machine\\Software\\ABC">
|
||||
<Value Type="REG\_SZ" Name="Bar" Data="Baz" />
|
||||
</Key>
|
||||
<Key Path="\\REGISTRY\\Machine\\Software\\EmptyKey" />
|
||||
</Include>
|
||||
<Delete>
|
||||
</Registry>
|
||||
```
|
||||
|
||||
**Machine Wide Virtual Kernel Objects**
|
||||
|
||||
```
|
||||
<Objects>
|
||||
<NotIsolate>
|
||||
<Object Name="testObject" />
|
||||
</NotIsolate>
|
||||
</Objects>
|
||||
```
|
||||
|
||||
**ProductSourceURLOptOut**: Indicates whether the URL for the package can be modified globally through PackageSourceRoot (to support branch office scenarios). Default is false and the setting change takes effect on the next launch.
|
||||
|
||||
```
|
||||
<MachineConfiguration>
|
||||
..
|
||||
<ProductSourceURLOptOut Enabled="true" />
|
||||
..
|
||||
</MachineConfiguration>
|
||||
```
|
||||
|
||||
**MachineScripts** – Package can be configured to execute scripts at time of deployment, publishing or removal. Please reference a sample deployment configuration file that is generated by the sequencer to see a sample script. The Scripts section below provides more information on the various triggers that can be used
|
||||
|
||||
**TerminateChildProcess**:- An application executable can be specified, whose child processes will be terminated when the application exe process is terminated.
|
||||
|
||||
```
|
||||
<MachineConfiguration>
|
||||
..
|
||||
<TerminateChildProcesses>
|
||||
<Application Path="\[{PackageRoot}\]\\Contoso\\ContosoApp.EXE" />
|
||||
<Application Path="\[{PackageRoot}\]\\LitView\\LitViewBrowser.exe" />
|
||||
<Application Path="\[{ProgramFilesX86}\]\\Microsoft Contoso\\Contoso\\contosomail.EXE" />
|
||||
</TerminateChildProcesses>
|
||||
..
|
||||
</MachineConfiguration>
|
||||
```
|
||||
|
||||
### Scripts
|
||||
|
||||
The following table describes the various script events and the context under which they can be run.
|
||||
|
||||
<table style="width:100%;">
|
||||
<colgroup>
|
||||
<col width="16%" />
|
||||
<col width="16%" />
|
||||
<col width="16%" />
|
||||
<col width="16%" />
|
||||
<col width="16%" />
|
||||
<col width="16%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Script Execution Time</th>
|
||||
<th align="left">Can be specified in Deployment Configuration</th>
|
||||
<th align="left">Can be specified in User Configuration</th>
|
||||
<th align="left">Can run in the Virtual Environment of the package</th>
|
||||
<th align="left">Can be run in the context of a specific application</th>
|
||||
<th align="left">Runs in system/user context: (Deployment Configuration, User Configuration)</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>AddPackage</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>(SYSTEM, N/A)</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>PublishPackage</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>(SYSTEM, User)</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>UnpublishPackage</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>(SYSTEM, User)</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>RemovePackage</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>(SYSTEM, N/A)</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>StartProcess</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>(User, User)</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>ExitProcess</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>(User, User)</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>StartVirtualEnvironment</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>(User, User)</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>TerminateVirtualEnvironment</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>(User, User)</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Using multiple scripts on a single event trigger
|
||||
|
||||
App-V supports the use of multiple scripts on a single event trigger for App-V packages, including packages that you convert from App-V 4.6 to App-V for Windows 10. To enable the use of multiple scripts, App-V uses a script launcher application, named ScriptRunner.exe, which is installed as part of the App-V client installation.
|
||||
|
||||
**How to use multiple scripts on a single event trigger:**
|
||||
|
||||
For each script that you want to run, pass that script as an argument to the ScriptRunner.exe application. The application then runs each script separately, along with the arguments that you specify for each script. Use only one script (ScriptRunner.exe) per trigger.
|
||||
|
||||
**Note**
|
||||
We recommended that you run the multi-script line from a command prompt first to make sure that all arguments are built correctly before adding them to the deployment configuration file.
|
||||
|
||||
|
||||
|
||||
**Example script and parameter descriptions**
|
||||
|
||||
Using the following example file and table, modify the deployment or user configuration file to add the scripts that you want to run.
|
||||
|
||||
``` syntax
|
||||
<MachineScripts>
|
||||
<AddPackage>
|
||||
<Path>ScriptRunner.exe</Path>
|
||||
<Arguments>
|
||||
-appvscript script1.exe arg1 arg2 –appvscriptrunnerparameters –wait –timeout=10
|
||||
-appvscript script2.vbs arg1 arg2
|
||||
-appvscript script3.bat arg1 arg2 –appvscriptrunnerparameters –wait –timeout=30 –rollbackonerror
|
||||
</Arguments>
|
||||
<Wait timeout=”40” RollbackOnError=”true”/>
|
||||
</AddPackage>
|
||||
</MachineScripts>
|
||||
```
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Parameter in the example file</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><code><AddPackage></code></p></td>
|
||||
<td align="left"><p>Name of the event trigger for which you are running a script, such as adding a package or publishing a package.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><code><Path>ScriptRunner.exe</Path></code></p></td>
|
||||
<td align="left"><p>The script launcher application that is installed as part of the App-V client installation.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>Although ScriptRunner.exe is installed as part of the App-V client, the location of the App-V client must be in %path% or ScriptRunner will not run. ScriptRunner.exe is typically located in the C:\Program Files\Microsoft Application Virtualization\Client folder.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><pre class="syntax" space="preserve"><code><Arguments>
|
||||
-appvscript script1.exe arg1 arg2 –appvscriptrunnerparameters –wait –timeout=10
|
||||
|
||||
-appvscript script2.vbs arg1 arg2
|
||||
|
||||
-appvscript script3.bat arg1 arg2 –appvscriptrunnerparameters –wait –timeout=30 -rollbackonerror
|
||||
</Arguments></code></pre></td>
|
||||
<td align="left"><p><code>-appvscript</code> - Token that represents the actual script that you want to run.</p>
|
||||
<p><code>script1.exe</code> – Name of the script that you want to run.</p>
|
||||
<p><code>arg1 arg2</code> – Arguments for the script that you want to run.</p>
|
||||
<p><code>-appvscriptrunnerparameters</code> – Token that represents the execution options for <code>script1.exe</code></p>
|
||||
<p><code>-wait</code> – Token that informs ScriptRunner to wait for execution of <code>script1.exe</code> to complete before proceeding to the next script.</p>
|
||||
<p><code>-timeout=x</code> – Token that informs ScriptRunner to stop running the current script after <code>x</code> number of seconds. All other specified scripts will still run.</p>
|
||||
<p><code>-rollbackonerror</code> – Token that informs ScriptRunner to stop running all scripts that haven't yet run and to roll back an error to the App-V client.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><code><Wait timeout=”40” RollbackOnError=”true”/></code></p></td>
|
||||
<td align="left"><p>Waits for overall completion of ScriptRunner.exe.</p>
|
||||
<p>Set the timeout value for the overall runner to be greater than or equal to the sum of the timeout values on the individual scripts.</p>
|
||||
<p>If any individual script reported an error and rollbackonerror was set to <code>true</code>, then ScriptRunner would report the error to App-V client.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
ScriptRunner will run any script whose file type is associated with an application installed on the computer. If the associated application is missing, or the script’s file type is not associated with any application on the computer, the script will not run.
|
||||
|
||||
### Create a Dynamic Configuration file using an App-V Manifest file
|
||||
|
||||
You can create the Dynamic Configuration file using one of three methods: either manually, using the App-V Management Console or sequencing a package, which will be generated with 2 sample files.
|
||||
|
||||
For more information about how to create the file using the App-V Management Console see, [How to Create a Custom Configuration File by Using the App-V Management Console](appv-create-a-custom-configuration-file-with-the-management-console.md).
|
||||
|
||||
To create the file manually, the information above in previous sections can be combined into a single file. We recommend you use files generated by the sequencer.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
[How to Apply the Deployment Configuration File by Using PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)
|
||||
|
||||
[How to Apply the User Configuration File by Using PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
@ -0,0 +1,36 @@
|
||||
---
|
||||
title: How to Enable Only Administrators to Publish Packages by Using an ESD (Windows 10)
|
||||
description: How to Enable Only Administrators to Publish Packages by Using an ESD
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Enable Only Administrators to Publish Packages by Using an ESD
|
||||
|
||||
|
||||
Starting in App-V 5.0 SP3, you can configure the App-V client so that only administrators (not end users) can publish or unpublish packages. In earlier versions of App-V, you could not prevent end users from performing these tasks.
|
||||
|
||||
**To enable only administrators to publish or unpublish packages**
|
||||
|
||||
1. Navigate to the following Group Policy Object node:
|
||||
|
||||
**Computer Configuration > Policies > Administrative Templates > System > App-V > Publishing**.
|
||||
|
||||
2. Enable the **Require publish as administrator** Group Policy setting.
|
||||
|
||||
To alternatively use PowerShell to set this item, see [How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs).
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,87 @@
|
||||
---
|
||||
title: How to Enable Reporting on the App-V Client by Using PowerShell (Windows 10)
|
||||
description: How to Enable Reporting on the App-V Client by Using PowerShell
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Enable Reporting on the App-V Client by Using PowerShell
|
||||
|
||||
|
||||
Use the following procedure to configure the App-V for reporting.
|
||||
|
||||
**To configure the computer running the App-V client for reporting**
|
||||
|
||||
1. Enable the App-V client. For more information, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
|
||||
|
||||
2. After you have enabled the App-V client, use the **Set-AppvClientConfiguration** PowerShell to configure appropriate Reporting Configuration settings:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Setting</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>ReportingEnabled</p></td>
|
||||
<td align="left"><p>Enables the client to return information to a reporting server. This setting is required for the client to collect the reporting data on the client.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>ReportingServerURL</p></td>
|
||||
<td align="left"><p>Specifies the location on the reporting server where client information is saved. For example, http://<reportingservername>:<reportingportnumber>.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>This is the port number that was assigned during the Reporting Server setup</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Reporting Start Time</p></td>
|
||||
<td align="left"><p>This is set to schedule the client to automatically send the data to the server. This setting will indicate the hour at which the reporting data will start to send. It is in the 24 hour format and will take a number between 0-23.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>ReportingRandomDelay</p></td>
|
||||
<td align="left"><p>Specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between 0 and ReportingRandomDelay and will wait the specified duration before sending data.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>ReportingInterval</p></td>
|
||||
<td align="left"><p>Specifies the retry interval that the client will use to resend data to the reporting server.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>ReportingDataCacheLimit</p></td>
|
||||
<td align="left"><p>Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>ReportingDataBlockSize</p></td>
|
||||
<td align="left"><p>Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
3. After the appropriate settings have been configured, the computer running the App-V client will automatically collect data and will send the data back to the reporting server.
|
||||
|
||||
Additionally, administrators can manually send the data back in an on-demand manner using the **Send-AppvClientReport** PowerShell cmdlet.
|
||||
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
|
||||
41
windows/manage/appv-enable-the-app-v-desktop-client.md
Normal file
41
windows/manage/appv-enable-the-app-v-desktop-client.md
Normal file
@ -0,0 +1,41 @@
|
||||
---
|
||||
title: Enable the App-V desktop client (Windows 10)
|
||||
description: Enable the App-V desktop client
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# Enable the App-V desktop client
|
||||
|
||||
The App-V client is the component that runs virtualized applications on user devices. The client enables users to interact with icons and file names to start virtualized applications. The client can also get virtual application content from the management server.
|
||||
|
||||
With Windows 10, the App-V client is installed automatically. You need to enable the client to allow user devices to access and run virtual applications. You can enable the client with the Group Policy editor or with Windows PowerShell.
|
||||
|
||||
**To enable the App-V client with Group Policy:**
|
||||
|
||||
1. Open the device’s **Local Group Policy Editor**.
|
||||
|
||||
2. Navigate to **Computer Configuration** > **Administrative Templates** > **System** > **App-V**.
|
||||
|
||||
3. Run **Enables App-V Client** and then select **Enabled** on the screen that appears.
|
||||
|
||||
4. Restart the device.
|
||||
|
||||
**To enable the App-V client with Windows PowerShell:**
|
||||
|
||||
1. Open Windows PowerShell.
|
||||
|
||||
2. Type `Enable-Appv` and press Enter.
|
||||
|
||||
3. Restart the device.
|
||||
|
||||
4. To verify that the App-V client is enabled on the device, enter **AppvClientEnabled** or **Get-AppvStatus** in Windows PowerShell.
|
||||
|
||||
See [Using the client management console](appv-using-the-client-management-console.md) for information about configuring the App-V client.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
51
windows/manage/appv-evaluating-appv.md
Normal file
51
windows/manage/appv-evaluating-appv.md
Normal file
@ -0,0 +1,51 @@
|
||||
---
|
||||
title: Evaluating App-V (Windows 10)
|
||||
description: Evaluating App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Evaluating App-V
|
||||
|
||||
|
||||
Before you deploy pp-V into a production environment, you should evaluate it in a lab environment. You can use the information in this topic to set up App-V in a lab environment for evaluation purposes only.
|
||||
|
||||
## Configure lab computers for App-V Evaluation
|
||||
|
||||
Use the following link for information about setting up the App-V sequencer on a computer in your lab environment.
|
||||
|
||||
### Installing the App-V Sequencer and Creating Packages
|
||||
|
||||
Use the following links for information about setting up the App-V sequencer and creating packages in your lab environment.
|
||||
|
||||
- [How to Install the Sequencer](appv-install-the-sequencer.md)
|
||||
|
||||
- [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md)
|
||||
|
||||
### Configuring the App-V Server
|
||||
|
||||
Use the following links for information about setting up the App-V server in your lab environment.
|
||||
|
||||
- [How to Deploy the App-V Server](appv-deploy-the-appv-server.md)
|
||||
|
||||
- [Administering App-V Virtual Applications by Using the Management Console](appv-administering-virtual-applications-with-the-management-console.md)
|
||||
|
||||
### Installing the App-V Client
|
||||
|
||||
Use the following link for more information about creating and managing virtualized packages in your lab environment.
|
||||
|
||||
- [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)
|
||||
|
||||
- [How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md)
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Getting Started with App-V](appv-getting-started.md)
|
||||
62
windows/manage/appv-for-windows.md
Normal file
62
windows/manage/appv-for-windows.md
Normal file
@ -0,0 +1,62 @@
|
||||
---
|
||||
title: Application Virtualization (App-V) (Windows 10)
|
||||
description: Application Virtualization (App-V)
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Application Virtualization (App-V) overview
|
||||
|
||||
|
||||
The topics in this section provides information and step-by-step procedures to help you administer App-V and its components. This information will be valuable for system administrators who manage large installations with many servers and clients and for support personnel who interact directly with the computers or the end users.
|
||||
|
||||
[Getting Started with App-V](appv-getting-started.md)
|
||||
|
||||
- [About App-V](appv-about-appv.md)
|
||||
- [Evaluating App-V](appv-evaluating-appv.md)
|
||||
- [High Level Architecture for App-V](appv-high-level-architecture.md)
|
||||
- [Accessibility for App-V](appv-accessibility.md)
|
||||
|
||||
[Planning for App-V](appv-planning-for-appv.md)
|
||||
|
||||
- [Preparing Your Environment for App-V](appv-preparing-your-environment.md)
|
||||
- [App-V Prerequisites](appv-prerequisites.md)
|
||||
- [Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
- [App-V Supported Configurations](appv-supported-configurations.md)
|
||||
- [App-V Planning Checklist](appv-planning-checklist.md)
|
||||
|
||||
[Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
- [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
- [Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
- [App-V Deployment Checklist](appv-deployment-checklist.md)
|
||||
- [Deploying Microsoft Office 2013 by Using App-V](appv-deploying-microsoft-office-2013-with-appv.md)
|
||||
- [Deploying Microsoft Office 2010 by Using App-V](appv-deploying-microsoft-office-2010-wth-appv.md)
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
- [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md)
|
||||
- [Administering App-V Virtual Applications by Using the Management Console](appv-administering-virtual-applications-with-the-management-console.md)
|
||||
- [Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
- [Deploying App-V Packages by Using Electronic Software Distribution (ESD)](appv-deploying-packages-with-electronic-software-distribution-solutions.md)
|
||||
- [Using the App-V Client Management Console](appv-using-the-client-management-console.md)
|
||||
- [Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)
|
||||
- [Maintaining App-V](appv-maintaining-appv.md)
|
||||
- [Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
[Troubleshooting App-V](appv-troubleshooting.md)
|
||||
|
||||
[Technical Reference for App-V](appv-technical-reference.md)
|
||||
|
||||
- [Performance Guidance for Application Virtualization](appv-performance-guidance.md)
|
||||
- [Application Publishing and Client Interaction](appv-application-publishing-and-client-interaction.md)
|
||||
- [Viewing App-V Server Publishing Metadata](appv-viewing-appv-server-publishing-metadata.md)
|
||||
- [Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md)
|
||||
|
||||
### Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
78
windows/manage/appv-getting-started.md
Normal file
78
windows/manage/appv-getting-started.md
Normal file
@ -0,0 +1,78 @@
|
||||
---
|
||||
title: Getting Started with App-V (Windows 10)
|
||||
description: Getting Started with App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Getting Started with App-V
|
||||
|
||||
|
||||
Microsoft Application Virtualization (App-V) enables organizations to deliver 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 as as-needed basis. Users launch virtual applications from familiar access points, including the Windows Store, and interact with them as if they were installed locally.
|
||||
|
||||
With the release of Windows 10, version 1607, App-V is included with the [Windows 10 Enterprise edition](https://www.microsoft.com/en-us/WindowsForBusiness/windows-for-enterprise) and is available with Software Assurance. If you are new to Windows 10 and App-V, you’ll need to download, activate, and install server- and client-side components to start delivering virtual applications to users. For information about what you need to know before getting started with App-V, see the [Application Virtualization (App-V) overview](appv-for-windows.md).
|
||||
|
||||
If you’re already using App-V, performing an in-place upgrade to Windows 10 on user devices automatically installs the App-V client and migrates users’ App-V applications and settings. For more information about how to configure an existing App-V installation after upgrading user devices to Windows 10, see [Upgrading to App-V for Windows 10 from an existing installation](appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md).
|
||||
|
||||
Important: You can migrate your existing App-V installation to Windows 10 from App-V versions 5.0 SP2 and higher only. If you are using an earlier version of App-V, you’ll need to upgrade from that version to App-V 5.0 SP2 before you upgrade to Windows 10.
|
||||
|
||||
For information about previous versions of App-V, see [MDOP Information Experience](https://technet.microsoft.com/itpro/mdop/index).
|
||||
|
||||
## Getting started with App-V for Windows 10 (new installations)
|
||||
|
||||
To start using App-V to deliver virtual applications to users, you’ll need to download, enable, and install server- and client-side components. The following table provides information about the App-V for Windows 10 components and where to find them.
|
||||
|
||||
<!--App-V Remote Desktop Services (RDS) client once had its own row in the table below, and could have its own row again. As of 7/29/2016, it's in the same row as App-V client -->
|
||||
|
||||
| Component | What it does | Where to find it |
|
||||
|------------|--|------|
|
||||
| App-V server components | App-V offers five server components that work together to allow you to host and publish virtual applications, generate usage reports, and manage your App-V environment. For information about the server components, see [Deploying the App-V Server](#_Deploying_the_App-V). | The App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from the [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/en-us/subscriptions/downloads/default.aspx#FileId=65215). <br>You must have a MSDN subscription to download the MDOP ISO package.<br>See [Deploying the App-V Server](appv-deploying-the-appv-server.md) for more information about installing and using the server components. |
|
||||
| App-V client and App-V Remote Desktop Services (RDS) client | The App-V client is the component that runs virtualized applications on user devices. The client enables users to interact with icons and file names to start virtualized applications. | The App-V client is automatically installed with Windows 10. <br>For information about enabling the client, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md). |
|
||||
| App-V Sequencer | Use the App-V Sequencer to convert Win32 applications into virtual packages for deployment to user devices. Devices must be running the App-V client to allow users to interact with virtual applications. | Installed with the [Windows 10 Assessment and Deployment Kit](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit) (Windows ADK). |
|
||||
|
||||
For more information about these elements, see [High Level Architecture for App-V](appv-high-level-architecture.md).
|
||||
|
||||
If you are new to this product, we recommend that you read the documentation thoroughly. Before you deploy it to a production environment, we also recommend that you validate your deployment plan in a test network environment. You might also consider taking a class about relevant technologies. For information about Microsoft training opportunities, see the [Microsoft Training Overview](https://www.microsoft.com/en-us/learning/default.aspx).
|
||||
|
||||
## Getting started with App-V
|
||||
|
||||
|
||||
- [About App-V](appv-about-appv.md)
|
||||
|
||||
Provides a high-level overview of App-V and how it can be used in your organization.
|
||||
|
||||
- [Evaluating App-V](appv-evaluating-appv.md)
|
||||
|
||||
Provides information about how you can best evaluate App-V for use in your organization.
|
||||
|
||||
- [High Level Architecture for App-V](appv-high-level-architecture.md)
|
||||
|
||||
Provides a description of the App-V features and how they work together.
|
||||
|
||||
- [Accessibility for App-V](appv-accessibility.md)
|
||||
|
||||
Provides information about features and services that make this product and its corresponding documentation more accessible for people with disabilities.
|
||||
|
||||
## <a href="" id="other-resources-for-this-product-"></a>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)
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
82
windows/manage/appv-high-level-architecture.md
Normal file
82
windows/manage/appv-high-level-architecture.md
Normal file
@ -0,0 +1,82 @@
|
||||
---
|
||||
title: High Level Architecture for App-V (Windows 10)
|
||||
description: High Level Architecture for App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# High Level Architecture for App-V
|
||||
|
||||
|
||||
Use the following information to help you simplify you Microsoft Application Virtualization (App-V) deployment.
|
||||
|
||||
## Architecture Overview
|
||||
|
||||
|
||||
A typical App-V implementation consists of the following elements.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Element</th>
|
||||
<th align="left">More information</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, a network load balancer should also be considered so that server requests are 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. A network load balancer should also be considered so that server requests are 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 enables authorized users to run and view existing App-V reports and ad hoc reports that can help them manage the 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. A network load balancer should also be considered so that server requests are 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 are not required to use the App-V Management server. However, you can still utilize the reporting and streaming functionality of App-V.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Getting Started with App-V](appv-getting-started.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,29 @@
|
||||
---
|
||||
title: How to Install the App-V Client for Shared Content Store Mode (Windows 10)
|
||||
description: How to Install the App-V Client for Shared Content Store Mode
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Install the App-V Client for Shared Content Store Mode
|
||||
|
||||
|
||||
Use the following procedure to install the Microsoft Application Virtualization (App-V) client so that it uses the App-V Shared Content Store (SCS) mode. You should ensure that all required prerequisites are installed on the computer you plan to install to. Use the following link to see [App-V Prerequisites](appv-prerequisites.md).
|
||||
|
||||
**Enable the App-V client for SCS mode**
|
||||
|
||||
1. In the Group Policy Management Console, navigate to **Computer Configuration** > **Administrative Templates** > **System** > **App-V** > **Streaming**.
|
||||
|
||||
2. Enable the **Set the Shared Content Mode (SCS) mode** setting.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
@ -0,0 +1,390 @@
|
||||
---
|
||||
title: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell (Windows 10)
|
||||
description: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell
|
||||
|
||||
|
||||
Use the following PowerShell procedure to convert any number of Active Directory Domain Services (AD DS) user or machine accounts into formatted Security Identifiers (SIDs) both in the standard format and in the hexadecimal format used by Microsoft SQL Server when running SQL scripts.
|
||||
|
||||
Before attempting this procedure, you should read and understand the information and examples displayed in the following list:
|
||||
|
||||
- **.INPUTS** – The account or accounts used to convert to SID format. This can be a single account name or an array of account names.
|
||||
|
||||
- **.OUTPUTS** - A list of account names with the corresponding SID in standard and hexadecimal formats.
|
||||
|
||||
- **Examples** -
|
||||
|
||||
**.\\ConvertToSID.ps1 DOMAIN\\user\_account1 DOMAIN\\machine\_account1$ DOMAIN\\user\_account2 | Format-List**.
|
||||
|
||||
**$accountsArray = @("DOMAIN\\user\_account1", "DOMAIN\\machine\_account1$", "DOMAIN\_user\_account2")**
|
||||
|
||||
**.\\ConvertToSID.ps1 $accountsArray | Write-Output -FilePath .\\SIDs.txt -Width 200**
|
||||
|
||||
\#>
|
||||
|
||||
**To convert any number of Active Directory Domain Services (AD DS) user or machine accounts into formatted Security Identifiers (SIDs)**
|
||||
|
||||
1. Copy the following script into a text editor and save it as a PowerShell script file, for example **ConvertToSIDs.ps1**.
|
||||
|
||||
2. To open a PowerShell console click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**.
|
||||
|
||||
``` syntax
|
||||
<#
|
||||
```
|
||||
|
||||
``` syntax
|
||||
.SYNOPSIS
|
||||
```
|
||||
|
||||
``` syntax
|
||||
This PowerShell script will take an array of account names and try to convert each of them to the corresponding SID in standard and hexadecimal formats.
|
||||
```
|
||||
|
||||
``` syntax
|
||||
.DESCRIPTION
|
||||
```
|
||||
|
||||
``` syntax
|
||||
This is a PowerShell script that converts any number of Active Directory (AD) user or machine accounts into formatted Security Identifiers (SIDs) both in the standard format and in the hexadecimal format used by SQL server when running SQL scripts.
|
||||
```
|
||||
|
||||
``` syntax
|
||||
.INPUTS
|
||||
```
|
||||
|
||||
``` syntax
|
||||
The account(s) to convert to SID format. This can be a single account name or an array of account names. Please see examples below.
|
||||
```
|
||||
|
||||
``` syntax
|
||||
.OUTPUTS
|
||||
```
|
||||
|
||||
``` syntax
|
||||
A list of account names with the corresponding SID in standard and hexadecimal formats
|
||||
```
|
||||
|
||||
``` syntax
|
||||
.EXAMPLE
|
||||
```
|
||||
|
||||
``` syntax
|
||||
.\ConvertToSID.ps1 DOMAIN\user_account1 DOMAIN\machine_account1$ DOMAIN\user_account2 | Format-List
|
||||
```
|
||||
|
||||
``` syntax
|
||||
.EXAMPLE
|
||||
```
|
||||
|
||||
``` syntax
|
||||
$accountsArray = @("DOMAIN\user_account1", "DOMAIN\machine_account1$", "DOMAIN_user_account2")
|
||||
```
|
||||
|
||||
``` syntax
|
||||
.\ConvertToSID.ps1 $accountsArray | Write-Output -FilePath .\SIDs.txt -Width 200
|
||||
```
|
||||
|
||||
``` syntax
|
||||
#>
|
||||
```
|
||||
|
||||
``` syntax
|
||||
```
|
||||
|
||||
[]()
|
||||
|
||||
[]()
|
||||
|
||||
``` syntax
|
||||
function ConvertSIDToHexFormat
|
||||
```
|
||||
|
||||
{
|
||||
|
||||
param(\[System.Security.Principal.SecurityIdentifier\]$sidToConvert)
|
||||
|
||||
``` syntax
|
||||
```
|
||||
|
||||
``` syntax
|
||||
$sb = New-Object System.Text.StringBuilder
|
||||
```
|
||||
|
||||
``` syntax
|
||||
[int] $binLength = $sidToConvert.BinaryLength
|
||||
```
|
||||
|
||||
``` syntax
|
||||
[Byte[]] $byteArray = New-Object Byte[] $binLength
|
||||
```
|
||||
|
||||
``` syntax
|
||||
$sidToConvert.GetBinaryForm($byteArray, 0)
|
||||
```
|
||||
|
||||
``` syntax
|
||||
foreach($byte in $byteArray)
|
||||
```
|
||||
|
||||
``` syntax
|
||||
{
|
||||
```
|
||||
|
||||
``` syntax
|
||||
$sb.Append($byte.ToString("X2")) |Out-Null
|
||||
```
|
||||
|
||||
``` syntax
|
||||
}
|
||||
```
|
||||
|
||||
``` syntax
|
||||
return $sb.ToString()
|
||||
```
|
||||
|
||||
``` syntax
|
||||
}
|
||||
```
|
||||
|
||||
``` syntax
|
||||
[string[]]$myArgs = $args
|
||||
```
|
||||
|
||||
``` syntax
|
||||
if(($myArgs.Length -lt 1) -or ($myArgs[0].CompareTo("/?") -eq 0))
|
||||
```
|
||||
|
||||
{
|
||||
|
||||
``` syntax
|
||||
[string]::Format("{0}====== Description ======{0}{0}" +
|
||||
```
|
||||
|
||||
``` syntax
|
||||
" Converts any number of user or machine account names to string and hexadecimal SIDs.{0}" +
|
||||
```
|
||||
|
||||
``` syntax
|
||||
" Pass the account(s) as space separated command line parameters. (For example 'ConvertToSID.exe DOMAIN\\Account1 DOMAIN\\Account2 ...'){0}" +
|
||||
```
|
||||
|
||||
``` syntax
|
||||
" The output is written to the console in the format 'Account name SID as string SID as hexadecimal'{0}" +
|
||||
```
|
||||
|
||||
``` syntax
|
||||
" And can be written out to a file using standard PowerShell redirection{0}" +
|
||||
```
|
||||
|
||||
``` syntax
|
||||
" Please specify user accounts in the format 'DOMAIN\username'{0}" +
|
||||
```
|
||||
|
||||
``` syntax
|
||||
" Please specify machine accounts in the format 'DOMAIN\machinename$'{0}" +
|
||||
```
|
||||
|
||||
``` syntax
|
||||
" For more help content, please run 'Get-Help ConvertToSID.ps1'{0}" +
|
||||
```
|
||||
|
||||
``` syntax
|
||||
"{0}====== Arguments ======{0}" +
|
||||
```
|
||||
|
||||
``` syntax
|
||||
"{0} /? Show this help message", [Environment]::NewLine)
|
||||
```
|
||||
|
||||
``` syntax
|
||||
{
|
||||
```
|
||||
|
||||
``` syntax
|
||||
else
|
||||
```
|
||||
|
||||
``` syntax
|
||||
{
|
||||
#If an array was passed in, try to split it
|
||||
```
|
||||
|
||||
``` syntax
|
||||
if($myArgs.Length -eq 1)
|
||||
```
|
||||
|
||||
``` syntax
|
||||
{
|
||||
```
|
||||
|
||||
``` syntax
|
||||
$myArgs = $myArgs.Split(' ')
|
||||
```
|
||||
|
||||
``` syntax
|
||||
}
|
||||
```
|
||||
|
||||
``` syntax
|
||||
|
||||
#Parse the arguments for account names
|
||||
```
|
||||
|
||||
``` syntax
|
||||
foreach($accountName in $myArgs)
|
||||
```
|
||||
|
||||
``` syntax
|
||||
{
|
||||
```
|
||||
|
||||
``` syntax
|
||||
[string[]] $splitString = $accountName.Split('\') # We're looking for the format "DOMAIN\Account" so anything that does not match, we reject
|
||||
```
|
||||
|
||||
``` syntax
|
||||
if($splitString.Length -ne 2)
|
||||
```
|
||||
|
||||
``` syntax
|
||||
{
|
||||
```
|
||||
|
||||
``` syntax
|
||||
$message = [string]::Format("{0} is not a valid account name. Expected format 'Domain\username' for user accounts or 'DOMAIN\machinename$' for machine accounts.", $accountName)
|
||||
```
|
||||
|
||||
``` syntax
|
||||
Write-Error -Message $message
|
||||
```
|
||||
|
||||
``` syntax
|
||||
continue
|
||||
```
|
||||
|
||||
``` syntax
|
||||
}
|
||||
```
|
||||
|
||||
``` syntax
|
||||
|
||||
```
|
||||
|
||||
``` syntax
|
||||
#Convert any account names to SIDs
|
||||
```
|
||||
|
||||
``` syntax
|
||||
try
|
||||
```
|
||||
|
||||
``` syntax
|
||||
{
|
||||
```
|
||||
|
||||
``` syntax
|
||||
[System.Security.Principal.NTAccount] $account = New-Object System.Security.Principal.NTAccount($splitString[0], $splitString[1])
|
||||
```
|
||||
|
||||
``` syntax
|
||||
[System.Security.Principal.SecurityIdentifier] $SID = [System.Security.Principal.SecurityIdentifier]($account.Translate([System.Security.Principal.SecurityIdentifier]))
|
||||
```
|
||||
|
||||
``` syntax
|
||||
}
|
||||
```
|
||||
|
||||
``` syntax
|
||||
catch [System.Security.Principal.IdentityNotMappedException]
|
||||
```
|
||||
|
||||
``` syntax
|
||||
{
|
||||
```
|
||||
|
||||
``` syntax
|
||||
$message = [string]::Format("Failed to translate account object '{0}' to a SID. Please verify that this is a valid user or machine account.", $account.ToString())
|
||||
```
|
||||
|
||||
``` syntax
|
||||
Write-Error -Message $message
|
||||
```
|
||||
|
||||
``` syntax
|
||||
continue
|
||||
```
|
||||
|
||||
``` syntax
|
||||
}
|
||||
```
|
||||
|
||||
``` syntax
|
||||
|
||||
#Convert regular SID to binary format used by SQL
|
||||
```
|
||||
|
||||
``` syntax
|
||||
$hexSIDString = ConvertSIDToHexFormat $SID
|
||||
```
|
||||
|
||||
``` syntax
|
||||
|
||||
$SIDs = New-Object PSObject
|
||||
```
|
||||
|
||||
``` syntax
|
||||
$SIDs | Add-Member NoteProperty Account $accountName
|
||||
```
|
||||
|
||||
``` syntax
|
||||
$SIDs | Add-Member NoteProperty SID $SID.ToString()
|
||||
```
|
||||
|
||||
``` syntax
|
||||
$SIDs | Add-Member NoteProperty Hexadecimal $hexSIDString
|
||||
```
|
||||
|
||||
``` syntax
|
||||
|
||||
Write-Output $SIDs
|
||||
```
|
||||
|
||||
``` syntax
|
||||
}
|
||||
```
|
||||
|
||||
``` syntax
|
||||
}
|
||||
```
|
||||
|
||||
3. Run the script you saved in step one of this procedure passing the accounts to convert as arguments.
|
||||
|
||||
For example,
|
||||
|
||||
**.\\ConvertToSID.ps1 DOMAIN\\user\_account1 DOMAIN\\machine\_account1$ DOMAIN\\user\_account2 | Format-List” or “$accountsArray = @("DOMAIN\\user\_account1", "DOMAIN\\machine\_account1$", "DOMAIN\_user\_account2")**
|
||||
|
||||
**.\\ConvertToSID.ps1 $accountsArray | Write-Output -FilePath .\\SIDs.txt -Width 200”**
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,117 @@
|
||||
---
|
||||
title: How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services (Windows 10)
|
||||
description: How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services
|
||||
|
||||
|
||||
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.
|
||||
|
||||
**Note**
|
||||
After you complete the deployment, the **Microsoft SQL Server name**, **instance name** and **database name** will be required by the administrator installing the service to be able to connect to these databases.
|
||||
|
||||
|
||||
|
||||
**To install the management database and the management server on separate computers**
|
||||
|
||||
1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
|
||||
2. On the **Getting Started** page, review and accept the license terms, and click **Next**.
|
||||
|
||||
3. On the **Use Microsoft Update to help keep your computer secure and up-to-date** page, to enable Microsoft updates, select **Use Microsoft Update when I check for updates (recommended).** To disable Microsoft updates, select **I don’t want to use Microsoft Update**. Click **Next**.
|
||||
|
||||
4. On the **Feature Selection** page, select the components you want to install by selecting the **Management Server Database** checkbox and click **Next**.
|
||||
|
||||
5. On the **Installation Location** page, accept the default location and click **Next**.
|
||||
|
||||
6. On the initial **Create New Management Server Database page**, accept the default selections if appropriate, and click **Next**.
|
||||
|
||||
If you are using a custom SQL Server instance, then select **Use a custom instance** and type the name of the instance.
|
||||
|
||||
If you are using a custom database name, then select **Custom configuration** and type the database name.
|
||||
|
||||
7. On the next **Create New Management Server Database** page, select **Use a remote computer**, and type the remote machine account using the following format: **Domain\\MachineAccount**.
|
||||
|
||||
**Note**
|
||||
If you plan to deploy the management server on the same computer you must select **Use this local computer**.
|
||||
|
||||
|
||||
|
||||
Specify the user name for the management server **Install Administrator** using the following format: **Domain\\AdministratorLoginName**. Click **Next**.
|
||||
|
||||
8. To start the installation, click **Install**.
|
||||
|
||||
**To install the reporting database and the reporting server on separate computers**
|
||||
|
||||
1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
|
||||
2. On the **Getting Started** page, review and accept the license terms, and click **Next**.
|
||||
|
||||
3. On the **Use Microsoft Update to help keep your computer secure and up-to-date** page, to enable Microsoft updates, select **Use Microsoft Update when I check for updates (recommended).** To disable Microsoft updates, select **I don’t want to use Microsoft Update**. Click **Next**.
|
||||
|
||||
4. On the **Feature Selection** page, select the components you want to install by selecting the **Reporting Server Database** checkbox and click **Next**.
|
||||
|
||||
5. On the **Installation Location** page, accept the default location and click **Next**.
|
||||
|
||||
6. On the initial **Create New Reporting Server Database** page, accept the default selections if appropriate, and click **Next**.
|
||||
|
||||
If you are using a custom SQL Server instance, then select **Use a custom instance** and type the name of the instance.
|
||||
|
||||
If you are using a custom database name, then select **Custom configuration** and type the database name.
|
||||
|
||||
7. On the next **Create New Reporting Server Database** page, select **Use a remote computer**, and type the remote machine account using the following format: **Domain\\MachineAccount**.
|
||||
|
||||
**Note**
|
||||
If you plan to deploy the reporting server on the same computer you must select **Use this local computer**.
|
||||
|
||||
|
||||
|
||||
Specify the user name for the reporting server **Install Administrator** using the following format: **Domain\\AdministratorLoginName**. Click **Next**.
|
||||
|
||||
8. To start the installation, click **Install**.
|
||||
|
||||
**To install the management and reporting databases using App-V database scripts**
|
||||
|
||||
1. Copy the App-V server installation files to the computer on which you want to install it on.
|
||||
|
||||
2. To extract the App-V database scripts, open a command prompt and specify the location where the installation files are saved and run the following command:
|
||||
|
||||
**appv\_server\_setup.exe** **/LAYOUT** **/LAYOUTDIR=”InstallationExtractionLocation”**.
|
||||
|
||||
3. After the extraction has been completed, to access the App-V database scripts and instructions readme file:
|
||||
|
||||
- The App-V Management Database scripts and instructions readme are located in the following folder: **InstallationExtractionLocation** \\ **Database Scripts** \\ **Management Database**.
|
||||
|
||||
- The App-V Reporting Database scripts and instructions readme are located in the following folder: **InstallationExtractionLocation** \\ **Database Scripts** \\ **Reporting Database**.
|
||||
|
||||
4. For each database, copy the scripts to a share and modify them following the instructions in the readme file.
|
||||
|
||||
**Note**
|
||||
For more information about modifying the required SIDs contained in the scripts see, [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md).
|
||||
|
||||
|
||||
|
||||
5. Run the scripts on the computer running Microsoft SQL Server.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,62 @@
|
||||
---
|
||||
title: How to install the Management Server on a Standalone Computer and Connect it to the Database (Windows 10)
|
||||
description: How to install the Management Server on a Standalone Computer and Connect it to the Database
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to install the Management Server on a Standalone Computer and Connect it to the Database
|
||||
|
||||
|
||||
Use the following procedure to install the management server on a standalone computer and connect it to the database.
|
||||
|
||||
**To install the management server on a standalone computer and connect it to the database**
|
||||
|
||||
1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
|
||||
2. On the **Getting Started** page, review and accept the license terms, and click **Next**.
|
||||
|
||||
3. On the **Use Microsoft Update to help keep your computer secure and up-to-date** page, to enable Microsoft updates, select **Use Microsoft Update when I check for updates (recommended).** To disable Microsoft updates, select **I don’t want to use Microsoft Update**. Click **Next**.
|
||||
|
||||
4. On the **Feature Selection** page, select the **Management Server** checkbox and click **Next**.
|
||||
|
||||
5. On the **Installation Location** page, accept the default location and click **Next**.
|
||||
|
||||
6. On the **Configure Existing Management Database** page, select **Use a remote SQL Server**, and type the machine name of the computer running Microsoft SQL SQL, for example **SqlServerMachine**.
|
||||
|
||||
**Note**
|
||||
If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**.
|
||||
|
||||
|
||||
|
||||
For the SQL Server Instance, select **Use the default instance**. If you are using a custom Microsoft SQL Server instance, you must select **Use a custom instance** and then type the name of the instance.
|
||||
|
||||
Specify the **SQL Server Database name** that this management server will use, for example **AppvManagement**.
|
||||
|
||||
7. On the **Configure Management Server Configuration** page, specify the AD group or account that will connect to the management console for administrative purposes for example **MyDomain\\MyUser** or **MyDomain\\AdminGroup**. The account or AD group you specify will be enabled to manage the server through the management console. You can add additional users or groups using the management console after installation
|
||||
|
||||
Specify the **Website Name** that you want to use for the management service. Accept the default if you do not have a custom name. For the **Port Binding**, specify a unique port number to be used, for example **12345**.
|
||||
|
||||
8. Click **Install**.
|
||||
|
||||
9. To confirm that the setup has completed successfully, open a web browser, and type the following URL: http://managementserver:portnumber/Console. If the installation was successful, you should see the **Management Console** appear without any error messages or warnings being displayed.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,79 @@
|
||||
---
|
||||
title: How to Install the Publishing Server on a Remote Computer (Windows 10)
|
||||
description: How to Install the Publishing Server on a Remote Computer
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Install the Publishing Server on a Remote Computer
|
||||
|
||||
|
||||
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.
|
||||
|
||||
**To install the publishing server on a separate computer**
|
||||
|
||||
1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
|
||||
2. On the **Getting Started** page, review and accept the license terms, and click **Next**.
|
||||
|
||||
3. On the **Use Microsoft Update to help keep your computer secure and up-to-date** page, to enable Microsoft updates, select **Use Microsoft Update when I check for updates (recommended).** To disable Microsoft updates, select **I don’t want to use Microsoft Update**. Click **Next**.
|
||||
|
||||
4. On the **Feature Selection** page, select the **Publishing Server** checkbox and click **Next**.
|
||||
|
||||
5. On the **Installation Location** page, accept the default location and click **Next**.
|
||||
|
||||
6. On the **Configure Publishing Server Configuration** page, specify the following items:
|
||||
|
||||
- The URL for the management service that the publishing server will connect to. For example, **http://ManagementServerName:12345**.
|
||||
|
||||
- Specify the website name that you want to use for the publishing service. Accept the default if you do not have a custom name.
|
||||
|
||||
- For the **Port Binding**, specify a unique port number that will be used by App-V, for example **54321**.
|
||||
|
||||
7. On the **Ready to Install** page, click **Install**.
|
||||
|
||||
8. After the installation is complete, the publishing server must be registered with the management server. In the App-V management console, use the following steps to register the server:
|
||||
|
||||
1. Open the App-V management server console.
|
||||
|
||||
2. In the left pane, select **Servers**, and then select **Register New Server**.
|
||||
|
||||
3. Type the name of this server and a description (if required) and click **Add**.
|
||||
|
||||
9. To verify if the publishing server is running correctly, you should import a package to the management server, entitle the package to an AD group, and publish the package. Using an internet browser, open the following URL: **http://publishingserver:pubport**. If the server is running correctly information similar to the following will be displayed:
|
||||
|
||||
`<Publishing Protocol="1.0">`
|
||||
|
||||
` <Packages>`
|
||||
|
||||
` <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" VersionId="5d03c08f-51dc-4026-8cf9-15ebe3d65a72" PackageUrl="\\server\share\file.appv" />`
|
||||
|
||||
` </Packages>`
|
||||
|
||||
` <NoGroup>`
|
||||
|
||||
` <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" />`
|
||||
|
||||
` </NoGroup>`
|
||||
|
||||
`</Publishing>`
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,71 @@
|
||||
---
|
||||
title: How to install the Reporting Server on a Standalone Computer and Connect it to the Database (Windows 10)
|
||||
description: How to install the Reporting Server on a Standalone Computer and Connect it to the Database
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to install the Reporting Server on a Standalone Computer and Connect it to the Database
|
||||
|
||||
|
||||
Use the following procedure to install the reporting server on a standalone computer and connect it to the database.
|
||||
|
||||
**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**
|
||||
|
||||
1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
|
||||
2. On the **Getting Started** page, review and accept the license terms, and click **Next**.
|
||||
|
||||
3. On the **Use Microsoft Update to help keep your computer secure and up-to-date** page, to enable Microsoft updates, select **Use Microsoft Update when I check for updates (recommended).** To disable Microsoft updates, select **I don’t want to use Microsoft Update**. Click **Next**.
|
||||
|
||||
4. On the **Feature Selection** page, select the **Reporting Server** checkbox and click **Next**.
|
||||
|
||||
5. On the **Installation Location** page, accept the default location and click **Next**.
|
||||
|
||||
6. On the **Configure Existing Reporting Database** page, select **Use a remote SQL Server**, and type the machine name of the computer running Microsoft SQL Server, for example **SqlServerMachine**.
|
||||
|
||||
**Note**
|
||||
If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**.
|
||||
|
||||
|
||||
|
||||
For the SQL Server Instance, select **Use the default instance**. If you are using a custom Microsoft SQL Server instance, you must select **Use a custom instance** and then type the name of the instance.
|
||||
|
||||
Specify the **SQL Server Database name** that this reporting server will use, for example **AppvReporting**.
|
||||
|
||||
7. On the **Configure Reporting Server Configuration** page.
|
||||
|
||||
- Specify the Website Name that you want to use for the Reporting Service. Leave the default unchanged if you do not have a custom name.
|
||||
|
||||
- For the **Port binding**, specify a unique port number that will be used by App-V, for example **55555**. You should also ensure that the port specified is not being used by another website.
|
||||
|
||||
8. Click **Install**.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[About App-V Reporting](appv-reporting.md)
|
||||
|
||||
[Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
[How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
58
windows/manage/appv-install-the-sequencer.md
Normal file
58
windows/manage/appv-install-the-sequencer.md
Normal file
@ -0,0 +1,58 @@
|
||||
---
|
||||
title: Install the App-V Sequencer (Windows 10)
|
||||
description: Install the App-V Sequencer
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Install the App-V Sequencer
|
||||
|
||||
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.
|
||||
|
||||
The App-V Sequencer is included in the Windows 10 Assessment and Deployment Kit (Windows ADK).
|
||||
|
||||
> [!NOTE]
|
||||
> The computer that will run the sequencer must not have the App-V client enabled on it. 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 that the computer that runs the Sequencer has plenty of memory, a fast processor, and a fast hard drive.
|
||||
|
||||
To install the App-V Sequencer:
|
||||
|
||||
1. Go to [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit).
|
||||
|
||||
2. Click or press 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.
|
||||
|
||||
|
||||
|
||||
3. To open the Sequencer, from the **Start** menu, select **Microsoft Application Virtualization (App-V) Sequencer** .
|
||||
|
||||
See [Creating and managing virtual applications](appv-creating-and-managing-virtualized-applications.md) and the [Application Virtualization Sequencing Guide](http://download.microsoft.com/download/F/7/8/F784A197-73BE-48FF-83DA-4102C05A6D44/App-V%205.0%20Sequencing%20Guide.docx) for information about creating virtual applications with the Sequencer.
|
||||
|
||||
## Command-line options for installing the sequencer
|
||||
|
||||
You can also use the command line to install the App-V sequencer. The following list displays information about options for installing the sequencer using the command line and **appv\_sequencer\_setup.exe**:
|
||||
|
||||
| **Command** | **Description** |
|
||||
|-------------------|------------------|
|
||||
| /INSTALLDIR | Specifies the installation directory. |
|
||||
| /Log | Specifies where the installation log will be saved, the default location is **%Temp%**. For example, **C:\\Logs\\ log.log**. |
|
||||
| /q | Specifies a quiet or silent installation. |
|
||||
| /Uninstall | Specifies the removal of the sequencer. |
|
||||
| /ACCEPTEULA | Accepts the license agreement. This is required for an unattended installation. Example usage: **/ACCEPTEULA** or **/ACCEPTEULA=1**. |
|
||||
| /LAYOUT | Specifies the associated layout action. It also extracts the Windows Installer (.msi) and script files to a folder without installing App-V. No value is expected. |
|
||||
| /LAYOUTDIR | Specifies the layout directory. Requires a string value. Example usage:**/LAYOUTDIR=”C:\\Application Virtualization Client”**. |
|
||||
| /? Or /h or /help | Displays associated help. |
|
||||
|
||||
## To troubleshoot the App-V sequencer installation
|
||||
|
||||
For more information regarding the sequencer installation, you can view the error log in the **%temp%** folder. To review the log files, click **Start**, type **%temp%**, and then look for the **appv\_ log**.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
@ -0,0 +1,223 @@
|
||||
---
|
||||
title: How to Load the PowerShell Cmdlets and Get Cmdlet Help (Windows 10)
|
||||
description: How to Load the PowerShell Cmdlets and Get Cmdlet Help
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Load the PowerShell Cmdlets and Get Cmdlet Help
|
||||
|
||||
|
||||
What this topic covers:
|
||||
|
||||
- [Requirements for using PowerShell cmdlets](#bkmk-reqs-using-posh)
|
||||
|
||||
- [Loading the PowerShell cmdlets](#bkmk-load-cmdlets)
|
||||
|
||||
- [Getting help for the PowerShell cmdlets](#bkmk-get-cmdlet-help)
|
||||
|
||||
- [Displaying the help for a PowerShell cmdlet](#bkmk-display-help-cmdlet)
|
||||
|
||||
## <a href="" id="bkmk-reqs-using-posh"></a>Requirements for using PowerShell cmdlets
|
||||
|
||||
|
||||
Review the following requirements for using the App-V PowerShell cmdlets:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Requirement</th>
|
||||
<th align="left">Details</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Users can run App-V Server cmdlets only if you grant them access by using one of the following methods:</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p><strong>When you are deploying and configuring the App-V Server</strong>:</p>
|
||||
<p>Specify an Active Directory group or individual user that has permissions to manage the App-V environment. See [How to Deploy the App-V Server](appv-deploy-the-appv-server.md).</p></li>
|
||||
<li><p><strong>After you’ve deployed the App-V Server</strong>:</p>
|
||||
<p>Use the App-V Management console to add an additional Active Directory group or user. See [How to Add or Remove an Administrator by Using the Management Console](appv-add-or-remove-an-administrator-with-the-management-console.md).</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Cmdlets that require an elevated command prompt</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Add-AppvClientPackage</p></li>
|
||||
<li><p>Remove-AppvClientPackage</p></li>
|
||||
<li><p>Set-AppvClientConfiguration</p></li>
|
||||
<li><p>Add-AppvClientConnectionGroup</p></li>
|
||||
<li><p>Remove-AppvClientConnectionGroup</p></li>
|
||||
<li><p>Add-AppvPublishingServer</p></li>
|
||||
<li><p>Remove-AppvPublishingServer</p></li>
|
||||
<li><p>Send-AppvClientReport</p></li>
|
||||
<li><p>Set-AppvClientMode</p></li>
|
||||
<li><p>Set-AppvClientPackage</p></li>
|
||||
<li><p>Set-AppvPublishingServer</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Cmdlets that end users can run, unless you configure them to require an elevated command prompt</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Publish-AppvClientPackage</p></li>
|
||||
<li><p>Unpublish-AppvClientPackage</p></li>
|
||||
</ul>
|
||||
<p>To configure these cmdlets to require an elevated command prompt, use one of the following methods:</p>
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Method</th>
|
||||
<th align="left">More resources</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Run the <strong>Set-AppvClientConfiguration</strong> cmdlet with the <strong>-RequirePublishAsAdmin</strong> parameter.</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>[How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md#bkmk-admin-only-posh-topic-cg)</p></li>
|
||||
<li><p>[How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs)</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Enable the “Require publish as administrator” Group Policy setting for App-V Clients.</p></td>
|
||||
<td align="left"><p>[How to Publish a Package by Using the Management Console](appv-publish-a-packages-with-the-management-console.md#bkmk-admin-pub-pkg-only-posh)</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p> </p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-load-cmdlets"></a>Loading the PowerShell cmdlets
|
||||
|
||||
|
||||
To load the PowerShell cmdlet modules:
|
||||
|
||||
1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE).
|
||||
|
||||
2. Type one of the following commands to load the cmdlets for the module you want:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">App-V component</th>
|
||||
<th align="left">Command to type</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V Server</p></td>
|
||||
<td align="left"><p>Import-Module AppvServer</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V Sequencer</p></td>
|
||||
<td align="left"><p>Import-Module AppvSequencer</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V Client</p></td>
|
||||
<td align="left"><p>Import-Module AppvClient</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-get-cmdlet-help"></a>Getting help for the PowerShell cmdlets
|
||||
|
||||
|
||||
Starting in App-V 5.0 SP3, cmdlet help is available in two formats:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Format</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>As a downloadable module</p></td>
|
||||
<td align="left"><p>To download the latest help after downloading the cmdlet module:</p>
|
||||
<ol>
|
||||
<li><p>Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE).</p></li>
|
||||
<li><p>Type one of the following commands to load the cmdlets for the module you want:</p></li>
|
||||
</ol>
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">App-V component</th>
|
||||
<th align="left">Command to type</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V Server</p></td>
|
||||
<td align="left"><p>Update-Help -Module AppvServer</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V Sequencer</p></td>
|
||||
<td align="left"><p>Update-Help -Module AppvSequencer</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V Client</p></td>
|
||||
<td align="left"><p>Update-Help -Module AppvClient</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p> </p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>On TechNet as web pages</p></td>
|
||||
<td align="left"><p>See the App-V node under [Microsoft Desktop Optimization Pack Automation with Windows PowerShell](http://technet.microsoft.com/library/dn520245.aspx).</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-display-help-cmdlet"></a>Displaying the help for a PowerShell cmdlet
|
||||
|
||||
|
||||
To display help for a specific PowerShell cmdlet:
|
||||
|
||||
1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE).
|
||||
|
||||
2. Type **Get-Help** <*cmdlet*>, for example, **Get-Help Publish-AppvClientPackage**.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
48
windows/manage/appv-maintaining-appv.md
Normal file
48
windows/manage/appv-maintaining-appv.md
Normal file
@ -0,0 +1,48 @@
|
||||
---
|
||||
title: Maintaining App-V (Windows 10)
|
||||
description: Maintaining App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Maintaining App-V
|
||||
|
||||
|
||||
After you have completed all the necessary planning, and then deployment of App-V, you can use the following information to maintain the App-V infrastructure.
|
||||
|
||||
## <a href="" id="move-the-app-v-5-1-server-"></a>Move the App-V Server
|
||||
|
||||
|
||||
The App-V server connects to the App-V database. Therefore you can install the management component to any computer on the network and then connect it to the App-V database.
|
||||
|
||||
[How to Move the App-V Server to Another Computer](appv-move-the-appv-server-to-another-computer.md)
|
||||
|
||||
## <a href="" id="determine-if-an-app-v-5-1-application-is-running-virtualized-"></a>Determine if an App-V Application is Running Virtualized
|
||||
|
||||
|
||||
Independent software vendors (ISV) who want to determine if an application is running virtualized with App-V or above, should open a named object called **AppVVirtual-<PID>** in the default namespace. For example, Windows API **GetCurrentProcessId()** can be used to obtain the current process's ID, for example 4052, and then if a named Event object called **AppVVirtual-4052** can be successfully opened using **OpenEvent()** in the default namespace for read access, then the application is virtual. If the **OpenEvent()** call fails, the application is not virtual.
|
||||
|
||||
Additionally, ISV’s who want to explicitly virtualize or not virtualize calls on specific API’s with App-V and above, can use the **VirtualizeCurrentThread()** and **CurrentThreadIsVirtualized()** functions implemented in the AppEntSubsystems32.dll module. These provide a way of hinting at a downstream component that the call should or should not be virtualized.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Other resources for maintaining App-V
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,294 @@
|
||||
---
|
||||
title: How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell (Windows 10)
|
||||
description: How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell
|
||||
|
||||
|
||||
The following sections explain how to perform various management tasks on a stand-alone client computer by using PowerShell:
|
||||
|
||||
- [To return a list of packages](#bkmk-return-pkgs-standalone-posh)
|
||||
|
||||
- [To add a package](#bkmk-add-pkgs-standalone-posh)
|
||||
|
||||
- [To publish a package](#bkmk-pub-pkg-standalone-posh)
|
||||
|
||||
- [To publish a package to a specific user](#bkmk-pub-pkg-a-user-standalone-posh)
|
||||
|
||||
- [To add and publish a package](#bkmk-add-pub-pkg-standalone-posh)
|
||||
|
||||
- [To unpublish an existing package](#bkmk-unpub-pkg-standalone-posh)
|
||||
|
||||
- [To unpublish a package for a specific user](#bkmk-unpub-pkg-specfc-use)
|
||||
|
||||
- [To remove an existing package](#bkmk-remove-pkg-standalone-posh)
|
||||
|
||||
- [To enable only administrators to publish or unpublish packages](#bkmk-admins-pub-pkgs)
|
||||
|
||||
- [Understanding pending packages (UserPending and GlobalPending)](#bkmk-understd-pend-pkgs)
|
||||
|
||||
## <a href="" id="bkmk-return-pkgs-standalone-posh"></a>To return a list of packages
|
||||
|
||||
|
||||
Use the following information to return a list of packages that are entitled to a specific user:
|
||||
|
||||
**Cmdlet**: Get-AppvClientPackage
|
||||
|
||||
**Parameters**: -Name -Version -PackageID -VersionID
|
||||
|
||||
**Example**: Get-AppvClientPackage –Name “ContosoApplication” -Version 2
|
||||
|
||||
## <a href="" id="bkmk-add-pkgs-standalone-posh"></a>To add a package
|
||||
|
||||
|
||||
Use the following information to add a package to a computer.
|
||||
|
||||
**Important**
|
||||
This example only adds a package. It does not publish the package to the user or the computer.
|
||||
|
||||
|
||||
|
||||
**Cmdlet**: Add-AppvClientPackage
|
||||
|
||||
**Example**: $Contoso = Add-AppvClientPackage \\\\path\\to\\appv\\package.appv
|
||||
|
||||
## <a href="" id="bkmk-pub-pkg-standalone-posh"></a>To publish a package
|
||||
|
||||
|
||||
Use the following information to publish a package that has been added to a specific user or globally to any user on the computer.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Publishing method</th>
|
||||
<th align="left">Cmdlet and example</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Publishing to the user</p></td>
|
||||
<td align="left"><p><strong>Cmdlet</strong>: Publish-AppvClientPackage</p>
|
||||
<p><strong>Example</strong>: Publish-AppvClientPackage “ContosoApplication”</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Publishing globally</p></td>
|
||||
<td align="left"><p><strong>Cmdlet</strong>: Publish-AppvClientPackage</p>
|
||||
<p><strong>Example</strong>: Publish-AppvClientPackage “ContosoApplication” -Global</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-pub-pkg-a-user-standalone-posh"></a>To publish a package to a specific user
|
||||
|
||||
|
||||
**Note**
|
||||
You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter.
|
||||
|
||||
|
||||
|
||||
An administrator can publish a package to a specific user by specifying the optional **–UserSID** parameter with the **Publish-AppvClientPackage** cmdlet, where **-UserSID** represents the end user’s security identifier (SID).
|
||||
|
||||
To use this parameter:
|
||||
|
||||
- You can run this cmdlet from the user or administrator session.
|
||||
|
||||
- You must be logged in with administrative credentials to use the parameter.
|
||||
|
||||
- The end user must be logged in.
|
||||
|
||||
- You must provide the end user’s security identifier (SID).
|
||||
|
||||
**Cmdlet**: Publish-AppvClientPackage
|
||||
|
||||
**Example**: Publish-AppvClientPackage “ContosoApplication” -UserSID S-1-2-34-56789012-3456789012-345678901-2345
|
||||
|
||||
## <a href="" id="bkmk-add-pub-pkg-standalone-posh"></a>To add and publish a package
|
||||
|
||||
|
||||
Use the following information to add a package to a computer and publish it to the user.
|
||||
|
||||
**Cmdlet**: Add-AppvClientPackage
|
||||
|
||||
**Example**: Add-AppvClientPackage \\\\path\\to\\appv\\package.appv | Publish-AppvClientPackage
|
||||
|
||||
## <a href="" id="bkmk-unpub-pkg-standalone-posh"></a>To unpublish an existing package
|
||||
|
||||
|
||||
Use the following information to unpublish a package which has been entitled to a user but not remove the package from the computer.
|
||||
|
||||
**Cmdlet**: Unpublish-AppvClientPackage
|
||||
|
||||
**Example**: Unpublish-AppvClientPackage “ContosoApplication”
|
||||
|
||||
## <a href="" id="bkmk-unpub-pkg-specfc-use"></a>To unpublish a package for a specific user
|
||||
|
||||
|
||||
**Note**
|
||||
You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter.
|
||||
|
||||
|
||||
|
||||
An administrator can unpublish a package for a specific user by using the optional **–UserSID** parameter with the **Unpublish-AppvClientPackage** cmdlet, where **-UserSID** represents the end user’s security identifier (SID).
|
||||
|
||||
To use this parameter:
|
||||
|
||||
- You can run this cmdlet from the user or administrator session.
|
||||
|
||||
- You must be logged in with administrative credentials to use the parameter.
|
||||
|
||||
- The end user must be logged in.
|
||||
|
||||
- You must provide the end user’s security identifier (SID).
|
||||
|
||||
**Cmdlet**: Unpublish-AppvClientPackage
|
||||
|
||||
**Example**: Unpublish-AppvClientPackage “ContosoApplication” -UserSID S-1-2-34-56789012-3456789012-345678901-2345
|
||||
|
||||
## <a href="" id="bkmk-remove-pkg-standalone-posh"></a>To remove an existing package
|
||||
|
||||
|
||||
Use the following information to remove a package from the computer.
|
||||
|
||||
**Cmdlet**: Remove-AppvClientPackage
|
||||
|
||||
**Example**: Remove-AppvClientPackage “ContosoApplication”
|
||||
|
||||
**Note**
|
||||
App-V cmdlets have been assigned to variables for the previous examples for clarity only; assignment is not a requirement. Most cmdlets can be combined as displayed in [To add and publish a package](#bkmk-add-pub-pkg-standalone-posh). For a detailed tutorial, see [App-V 5.0 Client PowerShell Deep Dive](http://go.microsoft.com/fwlink/?LinkId=324466).
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-admins-pub-pkgs"></a>To enable only administrators to publish or unpublish packages
|
||||
|
||||
|
||||
**Note**
|
||||
**This feature is supported starting in App-V 5.0 SP3.**
|
||||
|
||||
|
||||
|
||||
Use the following cmdlet and parameter to enable only administrators (not end users) to publish or unpublish packages:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Cmdlet</strong></p></td>
|
||||
<td align="left"><p>Set-AppvClientConfiguration</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Parameter</strong></p></td>
|
||||
<td align="left"><p>-RequirePublishAsAdmin</p>
|
||||
<p>Parameter values:</p>
|
||||
<ul>
|
||||
<li><p>0 - False</p></li>
|
||||
<li><p>1 - True</p></li>
|
||||
</ul>
|
||||
<p><strong>Example:</strong>: Set-AppvClientConfiguration –RequirePublishAsAdmin1</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
To use the App-V Management console to set this configuration, see [How to Publish a Package by Using the Management Console](appv-publish-a-packages-with-the-management-console.md).
|
||||
|
||||
## <a href="" id="bkmk-understd-pend-pkgs"></a>Understanding pending packages (UserPending and GlobalPending)
|
||||
|
||||
|
||||
**Starting in App-V 5.0 SP2**: If you run a PowerShell cmdlet that affects a package that is currently in use, the task that you are trying to perform is placed in a pending state. For example, if you try to publish a package when an application in that package is being used, and then run **Get-AppvClientPackage**, the pending status appears in the cmdlet output as follows:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Cmdlet output item</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>UserPending</p></td>
|
||||
<td align="left"><p>Indicates whether the listed package has a pending task that is being applied to the user:</p>
|
||||
<ul>
|
||||
<li><p>True</p></li>
|
||||
<li><p>False</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>GlobalPending</p></td>
|
||||
<td align="left"><p>Indicates whether the listed package has a pending task that is being applied globally to the computer:</p>
|
||||
<ul>
|
||||
<li><p>True</p></li>
|
||||
<li><p>False</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
The pending task will run later, according to the following rules:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Task type</th>
|
||||
<th align="left">Applicable rule</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>User-based task, e.g., publishing a package to a user</p></td>
|
||||
<td align="left"><p>The pending task will be performed after the user logs off and then logs back on.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Globally based task, e.g., enabling a connection group globally</p></td>
|
||||
<td align="left"><p>The pending task will be performed when the computer is shut down and then restarted.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
For more information about pending tasks, see [About App-V 5.0 SP2](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/about-app-v-50-sp2.md#bkmk-pkg-upgr-pendg-tasks).
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,146 @@
|
||||
---
|
||||
title: How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell (Windows 10)
|
||||
description: How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell
|
||||
|
||||
|
||||
An App-V connection group allows you to run all the virtual applications as a defined set of packages in a single virtual environment. For example, you can virtualize an application and its plug-ins by using separate packages, but run them together in a single connection group.
|
||||
|
||||
A connection group XML file defines the connection group that runs on the computer where you’ve installed the App-V client. For information about the connection group XML file and how to configure it, see [About the Connection Group File](appv-connection-group-file.md).
|
||||
|
||||
This topic explains the following procedures:
|
||||
|
||||
- [To add and publish the App-V packages in the connection group](#bkmk-add-pub-pkgs-in-cg)
|
||||
|
||||
- [To add and enable the connection group on the App-V client](#bkmk-add-enable-cg-on-clt)
|
||||
|
||||
- [To enable or disable a connection group for a specific user](#bkmk-enable-cg-for-user-poshtopic)
|
||||
|
||||
- [To allow only administrators to enable connection groups](#bkmk-admin-only-posh-topic-cg)
|
||||
|
||||
**To add and publish the App-V packages in the connection group**
|
||||
|
||||
1. To add and publish the App-V packages to the computer running the App-V client, type the following command:
|
||||
|
||||
Add-AppvClientPackage –path c:\\tmpstore\\quartfin.appv | Publish-AppvClientPackage
|
||||
|
||||
2. Repeat **step 1** of this procedure for each package in the connection group.
|
||||
|
||||
**To add and enable the connection group on the App-V client**
|
||||
|
||||
1. Add the connection group by typing the following command:
|
||||
|
||||
Add-AppvClientConnectionGroup –path c:\\tmpstore\\financ.xml
|
||||
|
||||
2. Enable the connection group by typing the following command:
|
||||
|
||||
Enable-AppvClientConnectionGroup –name “Financial Applications”
|
||||
|
||||
When any virtual applications that are in the member packages are run on the target computer, they will run inside the connection group’s virtual environment and will be available to all the virtual applications in the other packages in the connection group.
|
||||
|
||||
**To enable or disable a connection group for a specific user**
|
||||
|
||||
1. Review the parameter description and requirements:
|
||||
|
||||
- The parameter enables an administrator to enable or disable a connection group for a specific user.
|
||||
|
||||
- You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter.
|
||||
|
||||
- You can run this cmdlet from the user or administrator session.
|
||||
|
||||
- You must be logged in with administrative credentials to use the parameter.
|
||||
|
||||
- The end user must be logged in.
|
||||
|
||||
- You must provide the end user’s security identifier (SID).
|
||||
|
||||
2. Use the following cmdlets, and add the optional **–UserSID** parameter, where **-UserSID** represents the end user’s security identifier (SID):
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Cmdlet</th>
|
||||
<th align="left">Examples</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Enable-AppVClientConnectionGroup</p></td>
|
||||
<td align="left"><p>Enable-AppVClientConnectionGroup “ConnectionGroupA” -UserSID S-1-2-34-56789012-3456789012-345678901-2345</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Disable -AppVClientConnectionGroup</p></td>
|
||||
<td align="left"><p>Disable -AppVClientConnectionGroup “ConnectionGroupA” -UserSID S-1-2-34-56789012-3456789012-345678901-2345</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**To allow only administrators to enable connection groups**
|
||||
|
||||
1. Review the description and requirement for using this cmdlet:
|
||||
|
||||
- Use this cmdlet and parameter to configure the App-V client to allow only administrators (not end users) to enable or disable connection groups.
|
||||
|
||||
- You must be using at least App-V 5.0 SP3 to use this cmdlet.
|
||||
|
||||
2. Run the following cmdlet and parameter:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Cmdlet</th>
|
||||
<th align="left">Parameter and values</th>
|
||||
<th align="left">Example</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Set-AppvClientConfiguration</p></td>
|
||||
<td align="left"><p>–RequirePublishAsAdmin</p>
|
||||
<ul>
|
||||
<li><p>0 - False</p></li>
|
||||
<li><p>1 - True</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p>Set-AppvClientConfiguration –RequirePublishAsAdmin1</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
76
windows/manage/appv-managing-connection-groups.md
Normal file
76
windows/manage/appv-managing-connection-groups.md
Normal file
@ -0,0 +1,76 @@
|
||||
---
|
||||
title: Managing Connection Groups (Windows 10)
|
||||
description: Managing Connection Groups
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Managing Connection Groups
|
||||
|
||||
|
||||
Connection groups enable the applications within a package to interact with each other in the virtual environment, while remaining isolated from the rest of the system. By using connection groups, administrators can manage packages independently and can avoid having to add the same application multiple times to a client computer.
|
||||
|
||||
**Note**
|
||||
In some previous versions of App-V, connection groups were referred to as Dynamic Suite Composition.
|
||||
|
||||
|
||||
|
||||
**In this topic:**
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[About the Connection Group Virtual Environment](appv-connection-group-virtual-environment.md)</p></td>
|
||||
<td align="left"><p>Describes the connection group virtual environment.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[About the Connection Group File](appv-connection-group-file.md)</p></td>
|
||||
<td align="left"><p>Describes the connection group file.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[How to Create a Connection Group](appv-create-a-connection-group.md)</p></td>
|
||||
<td align="left"><p>Explains how to create a new connection group.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[How to Create a Connection Group with User-Published and Globally Published Packages](appv-create-a-connection-group-with-user-published-and-globally-published-packages.md)</p></td>
|
||||
<td align="left"><p>Explains how to create a new connection group that contains a mix of packages that are published to the user and published globally.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[How to Delete a Connection Group](appv-delete-a-connection-group.md)</p></td>
|
||||
<td align="left"><p>Explains how to delete a connection group.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[How to Publish a Connection Group](appv-publish-a-connection-group.md)</p></td>
|
||||
<td align="left"><p>Explains how to publish a connection group.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Other resources for App-V connection groups
|
||||
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
300
windows/manage/appv-migrating-to-appv-from-a-previous-version.md
Normal file
300
windows/manage/appv-migrating-to-appv-from-a-previous-version.md
Normal file
@ -0,0 +1,300 @@
|
||||
---
|
||||
title: Migrating to App-V from a Previous Version (Windows 10)
|
||||
description: Migrating to App-V from a Previous Version
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Migrating to App-V from a Previous Version
|
||||
|
||||
|
||||
With Microsoft Application Virtualization (App-V), you can migrate your existing App-V 4.6 or App-V 5.0 infrastructure to the more flexible, integrated, and easier to manage App-V infrastructure.
|
||||
However, you cannot migrate directly from App-V 4.x to App-V, you must migrate to App-V 5.0 first. For more information on migrating from App-V 4.x to App-V 5.0, see [Migrating from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)
|
||||
|
||||
**Note**
|
||||
App-V packages are exactly the same as App-V 5.0 packages. There has been no change in the package format between the versions and therefore, there is no need to convert App-V 5.0 packages to App-V packages.
|
||||
|
||||
For more information about the differences between App-V 4.6 and App-V, see the **Differences between App-4.6 and App-V 5.0 section** of [About App-V 5.0](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/about-app-v-50).
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-pkgconvimprove"></a>Improvements to the App-V Package Converter
|
||||
|
||||
|
||||
You can now use the package converter to convert App-V 4.6 packages that contain scripts, and registry information and scripts from source .osd files are now included in package converter output.
|
||||
|
||||
You can also use the `–OSDsToIncludeInPackage` parameter with the `ConvertFrom-AppvLegacyPackage` cmdlet to specify which .osd files’ information is converted and placed within the new package.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">New in App-V</th>
|
||||
<th align="left">Prior to App-V</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>New .xml files are created corresponding to the .osd files associated with a package; these files include the following information:</p>
|
||||
<ul>
|
||||
<li><p>environment variables</p></li>
|
||||
<li><p>shortcuts</p></li>
|
||||
<li><p>file type associations</p></li>
|
||||
<li><p>registry information</p></li>
|
||||
<li><p>scripts</p></li>
|
||||
</ul>
|
||||
<p>You can now choose to add information from a subset of the .osd files in the source directory to the package using the <code>-OSDsToIncludeInPackage</code> parameter.</p></td>
|
||||
<td align="left"><p>Registry information and scripts included in .osd files associated with a package were not included in package converter output.</p>
|
||||
<p>The package converter would populate the new package with information from all of the .osd files in the source directory.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Example conversion statement
|
||||
|
||||
To understand the new process, review the following example `ConvertFrom-AppvLegacyPackage` package converter statement.
|
||||
|
||||
**If the source directory (\\\\OldPkgStore\\ContosoApp) includes the following:**
|
||||
|
||||
- ContosoApp.sft
|
||||
|
||||
- ContosoApp.msi
|
||||
|
||||
- ContosoApp.sprj
|
||||
|
||||
- ContosoApp\_manifest.xml
|
||||
|
||||
- X.osd
|
||||
|
||||
- Y.osd
|
||||
|
||||
- Z.osd
|
||||
|
||||
**And you run this command:**
|
||||
|
||||
``` syntax
|
||||
ConvertFrom-AppvLegacyPackage –SourcePath \\OldPkgStore\ContosoApp\
|
||||
-DestinationPath \\NewPkgStore\ContosoApp\
|
||||
-OSDsToIncludeInPackage X.osd,Y.osd
|
||||
```
|
||||
|
||||
**The following is created in the destination directory (\\\\NewPkgStore\\ContosoApp):**
|
||||
|
||||
- ContosoApp.appv
|
||||
|
||||
- ContosoApp.msi
|
||||
|
||||
- ContosoApp\_DeploymentConfig.xml
|
||||
|
||||
- ContosoApp\_UserConfig.xml
|
||||
|
||||
- X\_Config.xml
|
||||
|
||||
- Y\_Config.xml
|
||||
|
||||
- Z\_Config.xml
|
||||
|
||||
**In the above example:**
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="25%" />
|
||||
<col width="25%" />
|
||||
<col width="25%" />
|
||||
<col width="25%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">These Source directory files…</th>
|
||||
<th align="left">…are converted to these Destination directory files…</th>
|
||||
<th align="left">…and will contain these items</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><ul>
|
||||
<li><p>X.osd</p></li>
|
||||
<li><p>Y.osd</p></li>
|
||||
<li><p>Z.osd</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>X_Config.xml</p></li>
|
||||
<li><p>Y_Config.xml</p></li>
|
||||
<li><p>Z_Config.xml</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Environment variables</p></li>
|
||||
<li><p>Shortcuts</p></li>
|
||||
<li><p>File type associations</p></li>
|
||||
<li><p>Registry information</p></li>
|
||||
<li><p>Scripts</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p>Each .osd file is converted to a separate, corresponding .xml file that contains the items listed here in App-V deployment configuration format. These items can then be copied from these .xml files and placed in the deployment configuration or user configuration files as desired.</p>
|
||||
<p>In this example, there are three .xml files, corresponding with the three .osd files in the source directory. Each .xml file contains the environment variables, shortcuts, file type associations, registry information, and scripts in its corresponding .osd file.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><ul>
|
||||
<li><p>X.osd</p></li>
|
||||
<li><p>Y.osd</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>ContosoApp.appv</p></li>
|
||||
<li><p>ContosoApp_DeploymentConfig.xml</p></li>
|
||||
<li><p>ContosoApp_UserConfig.xml</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Environment variables</p></li>
|
||||
<li><p>Shortcuts</p></li>
|
||||
<li><p>File type associations</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p>The information from the .osd files specified in the <code>-OSDsToIncludeInPackage</code> parameter are converted and placed inside the package. The converter then populates the deployment configuration file and the user configuration file with the contents of the package, just as App-V Sequencer does when sequencing a new package.</p>
|
||||
<p>In this example, environment variables, shortcuts, and file type associations included in X.osd and Y.osd were converted and placed in the App-V package, and some of this information was also included in the deployment configuration and user configuration files. X.osd and Y.osd were used because they were included as arguments to the <code>-OSDsToIncludeInPackage</code> parameter. No information from Z.osd was included in the package, because it was not included as one of these arguments.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Converting packages created using a prior version of App-V
|
||||
|
||||
|
||||
Use the package converter utility to upgrade virtual application packages created using versions of App-V prior to App-V 5.0. The package converter uses PowerShell to convert packages and can help automate the process if you have many packages that require conversion.
|
||||
|
||||
**Important**
|
||||
After you convert an existing package you should test the package prior to deploying the package to ensure the conversion process was successful.
|
||||
|
||||
|
||||
|
||||
**What to know before you convert existing packages**
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Issue</th>
|
||||
<th align="left">Workaround</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Virtual packages using DSC are not linked after conversion.</p></td>
|
||||
<td align="left"><p>Link the packages using connection groups. See [Managing Connection Groups](appv-managing-connection-groups.md).</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Environment variable conflicts are detected during conversion.</p></td>
|
||||
<td align="left"><p>Resolve any conflicts in the associated <strong>.osd</strong> file.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Hard-coded paths are detected during conversion.</p></td>
|
||||
<td align="left"><p>Hard-coded paths are difficult to convert correctly. The package converter will detect and return packages with files that contain hard-coded paths. View the file with the hard-coded path, and determine whether the package requires the file. If so, it is recommended to re-sequence the package.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
When converting a package check for failing files or shortcuts. Locate the item in App-V 4.6 package. It could possibly be a hard-coded path. Convert the path.
|
||||
|
||||
**Note**
|
||||
It is recommended that you use the App-V sequencer for converting critical applications or applications that need to take advantage of features. See, [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md).
|
||||
|
||||
If a converted package does not open after you convert it, it is also recommended that you re-sequence the application using the App-V sequencer.
|
||||
|
||||
|
||||
|
||||
[How to Convert a Package Created in a Previous Version of App-V](appv-convert-a-package-created-in-a-previous-version-of-appv.md)
|
||||
|
||||
## Migrating Clients
|
||||
|
||||
|
||||
The following table displays the recommended method for upgrading clients.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Task</th>
|
||||
<th align="left">More Information</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Upgrade your environment to the latest version of App-V 4.6</p></td>
|
||||
<td align="left"><p>[Application Virtualization Deployment and Upgrade Considerations](https://technet.microsoft.com/en-us/itpro/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy).</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Sequence and roll out App-V packages. As needed, unpublish App-V 4.6 packages.</p></td>
|
||||
<td align="left"><p>[How to Sequence a New Application with App-V](appv-sequence-a-new-application.md).</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Important**
|
||||
You must be running the latest version of App-V 4.6 to use coexistence mode. Additionally, when you sequence a package, you must configure the Managing Authority setting, which is in the **User Configuration** is located in the **User Configuration** section.
|
||||
|
||||
|
||||
|
||||
## Migrating the App-V Server Full Infrastructure
|
||||
|
||||
|
||||
There is no direct method to upgrade to a full App-V infrastructure. Use the information in the following section for information about upgrading the App-V server.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Task</th>
|
||||
<th align="left">More Information</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Upgrade your environment to the latest version of App-V 4.6.</p></td>
|
||||
<td align="left"><p>[Application Virtualization Deployment and Upgrade Considerations](https://technet.microsoft.com/en-us/itpro/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy).</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Deploy App-V version of the client.</p></td>
|
||||
<td align="left"><p>[Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Install App-V server.</p></td>
|
||||
<td align="left"><p>[How to Deploy the App-V Server](appv-deploy-the-appv-server.md).</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Migrate existing packages.</p></td>
|
||||
<td align="left"><p>See the <strong>Converting packages created using a prior version of App-V</strong> section of this article.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Other resources for performing App-V migration tasks
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
|
||||
- [A simplified Microsoft App-V Management Server upgrade procedure](http://go.microsoft.com/fwlink/p/?LinkId=786330)
|
||||
@ -0,0 +1,178 @@
|
||||
---
|
||||
title: How to Modify an Existing Virtual Application Package (Windows 10)
|
||||
description: How to Modify an Existing Virtual Application Package
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Modify an Existing Virtual Application Package
|
||||
|
||||
|
||||
This topic explains how to:
|
||||
|
||||
- [Update an application in an existing virtual application package](#bkmk-update-app-in-pkg)
|
||||
|
||||
- [Modify the properties associated with an existing virtual application package](#bkmk-chg-props-in-pkg)
|
||||
|
||||
- [Add a new application to an existing virtual application package](#bkmk-add-app-to-pkg)
|
||||
|
||||
**Before you update a package:**
|
||||
|
||||
- Ensure that you’ve installed the Microsoft Application Virtualization (App-V) Sequencer, which is required for modifying a virtual application package. To install the App-V Sequencer, see [How to Install the Sequencer](appv-install-the-sequencer.md).
|
||||
|
||||
- Save the .appv file in a secure location and always trust the source before trying to open the package for editing.
|
||||
|
||||
- The Managing Authority section is erroneously removed from the deployment configuration file when you update a package. Before starting the update, copy the Managing Authority section from the existing deployment configuration file, and then paste the copied section into the new configuration file after the conversion is complete.
|
||||
|
||||
- If you click **Modify an Existing Virtual Application Package** in the Sequencer in order to edit a package, but then make no changes and close the package, the streaming behavior of the package is changed. The primary feature block is removed from the StreamMap.xml file, and any files that were listed in the publishing feature block are removed. Users who receive the edited package experience that package as if it were stream-faulted, regardless of how the original package was configured.
|
||||
|
||||
**Update an application in an existing virtual application package**
|
||||
|
||||
1. On the computer that runs the sequencer, click **All Programs**, point to **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. In the App-V Sequencer, click **Modify an Existing Virtual Application Package** > **Next**.
|
||||
|
||||
3. On the **Select Task** page, click **Update Application in Existing Package** > **Next**.
|
||||
|
||||
4. On the **Select Package** page, click **Browse** to locate the virtual application package that contains the application to update, and then click **Next**.
|
||||
|
||||
5. On the **Prepare Computer** page, review the issues that could cause the application update to fail or cause the updated application to contain unnecessary data. Resolve all potential issues before you continue. After making any corrections and resolving all potential issues, click **Refresh** > **Next**.
|
||||
|
||||
**Important**
|
||||
If you are required to disable virus scanning software, first scan the computer that runs the sequencer to ensure that no unwanted or malicious files are added to the package.
|
||||
|
||||
|
||||
|
||||
6. On the **Select Installer** page, click **Browse** and specify the update installation file for the application. If the update does not have an associated installer file, and if you plan to run all installation steps manually, select the **Select this option to perform a custom installation** check box, and then click **Next**.
|
||||
|
||||
7. On the **Installation** page, when the sequencer and application installer are ready you can proceed to install the application update so the sequencer can monitor the installation process. If additional installation files must be run as part of the installation, click **Run**, and then locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**. Click **Next**.
|
||||
|
||||
**Note**
|
||||
The sequencer monitors all changes and installations that occur on the computer that runs the sequencer. This includes any changes and installations that are performed outside of the sequencing wizard.
|
||||
|
||||
|
||||
|
||||
8. On the **Installation Report** page, you can review information about the updated virtual application. In **Additional Information**, double-click the event to obtain more detailed information. To proceed, click **Next**.
|
||||
|
||||
9. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. It can take several minutes for all of the applications to run. After all applications have run, close each of the applications, and then click **Next**.
|
||||
|
||||
**Note**
|
||||
You can stop an application from loading during this step. In the **Application Launch** dialog box, click **Stop**, and then select either **Stop all applications** or **Stop this application only**.
|
||||
|
||||
|
||||
|
||||
10. On the **Create Package** page, to modify the package without saving it, select the check box for **Continue to modify package without saving using the package editor**. When you select this option, the package opens in the App-V Sequencer console, where you can modify the package before it is saved. Click **Next**.
|
||||
|
||||
To save the package immediately, select the default **Save the package now**. Add optional **Comments** to associate with the package. Comments are useful to identify the application version and provide other information about the package. The default **Save Location** is also displayed. To change the default location, click **Browse** and specify the new location. Click **Create**.
|
||||
|
||||
11. On the **Completion** page, click **Close** to close the wizard. The package is now available in the sequencer.
|
||||
|
||||
**Modify the properties associated with an existing virtual application package**
|
||||
|
||||
1. On the computer that runs the sequencer, click **All Programs**, point to **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. In the App-V Sequencer, click **Modify an Existing Virtual Application Package** > **Next**.
|
||||
|
||||
3. On the **Select Task** page, click **Edit Package** > **Next**.
|
||||
|
||||
4. On the **Select Package** page, click **Browse** to locate the virtual application package that contains the application properties to modify, and then click **Edit**.
|
||||
|
||||
5. In the App-V Sequencer console, perform any of the following tasks as needed:
|
||||
|
||||
- Import and export the manifest file.
|
||||
|
||||
- Enable or disable Browser Helper Objects.
|
||||
|
||||
- Import or export a VFS file.
|
||||
|
||||
- Import a directory into the virtual file system.
|
||||
|
||||
- Import and export virtual registry keys.
|
||||
|
||||
- View package properties.
|
||||
|
||||
- View associated package files.
|
||||
|
||||
- Edit registry settings.
|
||||
|
||||
- Review additional package settings (except operating system file properties).
|
||||
|
||||
- Set virtualized registry key state (override or merge).
|
||||
|
||||
- Set virtualized folder state.
|
||||
|
||||
- Add or edit shortcuts and file type associations.
|
||||
|
||||
**Note**
|
||||
To edit shortcuts or file type associations, you must first open the package for upgrade to add a new application, and then proceed to the final editing page.
|
||||
|
||||
|
||||
|
||||
6. When you finish changing the package properties, click **File** > **Save** to save the package.
|
||||
|
||||
**Add a new application to an existing virtual application package**
|
||||
|
||||
1. On the computer that runs the sequencer, click **All Programs**, point to **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. In the App-V Sequencer, click **Modify an Existing Virtual Application Package** > **Next**.
|
||||
|
||||
3. On the **Select Task** page, click **Add New Application** > **Next**.
|
||||
|
||||
4. On the **Select Package** page, click **Browse** to locate the virtual application package to which you will add the application, and then click **Next**.
|
||||
|
||||
5. On the **Prepare Computer** page, review the issues that could cause the package creation to fail or cause the revised package to contain unnecessary data. Resolve all potential issues before you continue. After making any corrections and resolving all potential issues, click **Refresh** > **Next**.
|
||||
|
||||
**Important**
|
||||
If you are required to disable virus scanning software, first scan the computer that runs the sequencer to ensure that no unwanted or malicious files can be added to the package.
|
||||
|
||||
|
||||
|
||||
6. On the **Select Installer** page, click **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 click **Next**.
|
||||
|
||||
7. On the **Installation** page, when the sequencer and application installer are ready, install the application so that the sequencer can monitor the installation process. If additional installation files must be run as part of the installation, click **Run**, and locate and run the additional installation files. When you finish the installation, select **I am finished installing** > **Next**. In the **Browse for Folder** dialog box, specify the primary directory where the application will be installed. Ensure that this is a new location so that you don’t overwrite the existing version of the virtual application package.
|
||||
|
||||
**Note**
|
||||
The sequencer monitors all changes and installations that occur on the computer that runs the sequencer. This includes any changes and installations that are performed outside of the sequencing wizard.
|
||||
|
||||
|
||||
|
||||
8. On the **Configure Software** page, optionally run the programs contained in the package. This step completes any associated license or configuration tasks that are required to run the application before you deploy and run the package on target computers. To run all the programs at the same time, select at least one program, and then click **Run All**. To run specific programs, select the program or programs you want to run, and then click **Run Selected**. Complete the required configuration tasks and then close the applications. It can take several minutes for all programs to run. Click **Next**.
|
||||
|
||||
9. On the **Installation Report** page, you can review information about the updated virtual application. In **Additional Information**, double-click the event to obtain more detailed information, and then click **Next** to open the **Customize** page.
|
||||
|
||||
10. If you are finished installing and configuring the virtual application, select **Stop now** and skip to step 13 of this procedure. If you want to perform the following described customization, click **Customize**.
|
||||
|
||||
If you are customizing, prepare the virtual package for streaming, and then click **Next**. Streaming improves the experience when the virtual application package is run on target computers.
|
||||
|
||||
11. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. It can take several minutes for all the applications to run. After all applications have run, close each of the applications, and then click **Next**.
|
||||
|
||||
**Note**
|
||||
You can stop an application from loading during this step. In the **Application Launch** dialog box, click **Stop** and then select either **Stop all applications** or **Stop this application only**.
|
||||
|
||||
|
||||
|
||||
12. On the **Create Package** page, to modify the package without saving it, select the **Continue to modify package without saving using the package editor** check box. Selecting this option opens the package in the App-V Sequencer console, where you can modify the package before saving it. Click **Next**.
|
||||
|
||||
To save the package immediately, select the default **Save the package now**. Add optional **Comments** to associate with the package. Comments are useful for providing application versions and other information about the package. The default **Save Location** is also displayed. To change the default location, click **Browse** and specify the new location. The uncompressed package size is displayed. Click **Create**.
|
||||
|
||||
13. On the **Completion** page, click **Close**. The package is now available in the sequencer.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,43 @@
|
||||
---
|
||||
title: How to Modify Client Configuration by Using PowerShell (Windows 10)
|
||||
description: How to Modify Client Configuration by Using PowerShell
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Modify Client Configuration by Using PowerShell
|
||||
|
||||
|
||||
Use the following procedure to configure the App-V client configuration.
|
||||
|
||||
**To modify App-V client configuration using PowerShell**
|
||||
|
||||
1. To configure the client settings using PowerShell, use the **Set-AppvClientConfiguration** cmdlet. For more information about installing PowerShell, and a list of cmdlets see, [How to Load the PowerShell Cmdlets and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md).
|
||||
|
||||
2. To modify the client configuration, open a PowerShell Command prompt and run the following cmdlet **Set-AppvClientConfiguration** with any required parameters. For example:
|
||||
|
||||
`$config = Get-AppvClientConfiguration`
|
||||
|
||||
`Set-AppcClientConfiguration $config`
|
||||
|
||||
`Set-AppcClientConfiguration –Name1 MyConfig –Name2 “xyz”`
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,23 @@
|
||||
---
|
||||
title: How to Modify App-V Client Configuration Using the ADMX Template and Group Policy (Windows 10)
|
||||
description: How to Modify App-V Client Configuration Using the ADMX Template and Group Policy
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Modify App-V client configuration using the ADMX template and Group Policy
|
||||
|
||||
You can use Group Policy to configure App-V client settings by using the Group Policy Management Console under **Computer Configuration** > **Policies** > **Administrative Templates** > **System** > **App-V**.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
- [About Client Configuration Settings](appv-client-configuration-settings.md)
|
||||
@ -0,0 +1,40 @@
|
||||
---
|
||||
title: How to Move the App-V Server to Another Computer (Windows 10)
|
||||
description: How to Move the App-V Server to Another Computer
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Move the App-V Server to Another Computer
|
||||
|
||||
|
||||
Use the following information to create a new management server console in your environment.
|
||||
|
||||
## To create a new management server console
|
||||
|
||||
|
||||
The following list displays the steps necessary to create a new management server console:
|
||||
|
||||
1. Install the management server on a computer in your environment. For more information about installing the management server see [Deploying the App-V Server](appv-deploying-the-appv-server.md).
|
||||
|
||||
2. After you have completed the installation, use the following link to connect it to the App-V database - [How to install the Management Server on a Standalone Computer and Connect it to the Database](appv-install-the-management-server-on-a-standalone-computer.md).
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
75
windows/manage/appv-operations.md
Normal file
75
windows/manage/appv-operations.md
Normal file
@ -0,0 +1,75 @@
|
||||
---
|
||||
title: Operations for App-V (Windows 10)
|
||||
description: Operations for App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Operations for App-V
|
||||
|
||||
|
||||
This section of the Microsoft Application Virtualization (App-V) Administrator’s Guide includes information about the various types of App-V administration and operating tasks that are typically performed by an administrator. This section also includes step-by-step procedures to help you successfully perform those tasks.
|
||||
|
||||
## Operations Information
|
||||
|
||||
|
||||
- [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md)
|
||||
|
||||
Describes how to create, modify, and convert virtualized packages.
|
||||
|
||||
- [Administering App-V Virtual Applications by Using the Management Console](appv-administering-virtual-applications-with-the-management-console.md)
|
||||
|
||||
Describes how to use the App-V Management console to perform tasks such as sequencing an application, changing a package, using a project template, and using a package accelerator.
|
||||
|
||||
- [Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
|
||||
Describes how connection groups enable virtualized applications to communicate with each other in the virtual environment; explains how to create, publish, and delete them; and describes how connection groups can help you better manage your virtualized applications.
|
||||
|
||||
- [Deploying App-V Packages by Using Electronic Software Distribution (ESD)](appv-deploying-packages-with-electronic-software-distribution-solutions.md)
|
||||
|
||||
Describes how to deploy App-V packages by using an ESD.
|
||||
|
||||
- [Using the App-V Client Management Console](appv-using-the-client-management-console.md)
|
||||
|
||||
Describes how perform client configuration tasks using the client management console.
|
||||
|
||||
- [Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)
|
||||
|
||||
Provides instructions for migrating to App-V from a previous version.
|
||||
|
||||
- [Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
Describes the set of Windows PowerShell cmdlets available for administrators performing various App-V server tasks.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Other Resources for App-V Operations
|
||||
|
||||
|
||||
- [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)
|
||||
|
||||
- [Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
- [Troubleshooting App-V](appv-troubleshooting.md)
|
||||
|
||||
- [Technical Reference for App-V](appv-technical-reference.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
761
windows/manage/appv-performance-guidance.md
Normal file
761
windows/manage/appv-performance-guidance.md
Normal file
@ -0,0 +1,761 @@
|
||||
---
|
||||
title: Performance Guidance for Application Virtualization (Windows 10)
|
||||
description: Performance Guidance for Application Virtualization
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Performance Guidance for Application Virtualization
|
||||
|
||||
|
||||
Learn how to configure App-V for optimal performance, optimize virtual app packages, and provide a better user experience with RDS and VDI.
|
||||
|
||||
Implementing multiple methods can help you improve the end-user experience. However, your environment may not support all methods.
|
||||
|
||||
You should read and understand the following information before reading this document.
|
||||
|
||||
- [Application Virtualization (App-V) overview](appv-for-windows.md)
|
||||
|
||||
- [App-V 5 SP2 Application Publishing and Client Interaction](http://go.microsoft.com/fwlink/?LinkId=395206)
|
||||
|
||||
- [Microsoft Application Virtualization Sequencing Guide](http://go.microsoft.com/fwlink/?LinkId=269953)
|
||||
|
||||
**Note**
|
||||
Some terms used in this document may have different meanings depending on external source and context. For more information about terms used in this document followed by an asterisk **\*** review the [Application Virtualization Performance Guidance Terminology](#bkmk-terms1) section of this document.
|
||||
|
||||
|
||||
|
||||
Finally, this document will provide you with the information to configure the computer running App-V client and the environment for optimal performance. Optimize your virtual application packages for performance using the sequencer, and to understand how to use User Experience Virtualization (UE-V) or other user environment management technologies to provide the optimal user experience with App-V in both Remote Desktop Services (RDS) and non-persistent virtual desktop infrastructure (VDI).
|
||||
|
||||
To help determine what information is relevant to your environment you should review each section’s brief overview and applicability checklist.
|
||||
|
||||
## <a href="" id="---------app-v-5-1-in-stateful--non-persistent-deployments"></a> App-V in stateful\* non-persistent deployments
|
||||
|
||||
|
||||
This section provides information about an approach that helps ensure a user will have access to all virtual applications within seconds after logging in. This is achieved by uniquely addressing the often long-running App-V publishing refresh. As you will discover the basis of the approach, the fastest publishing refresh, is one that doesn’t have to actually do anything. A number of conditions must be met and steps followed to provide the optimal user experience.
|
||||
|
||||
Use the information in the following section for more information:
|
||||
|
||||
[Usage Scenarios](#bkmk-us) - As you review the two scenarios, keep in mind that these are the approach extremes. Based on your usage requirements, you may choose to apply these steps to a subset of users and/or virtual applications packages.
|
||||
|
||||
- Optimized for Performance – To provide the optimal experience, you can expect the base image to include some of the App-V virtual application package. This and other requirements are discussed.
|
||||
|
||||
- Optimized for Storage – If you are concerned with the storage impact, following this scenario will help address those concerns.
|
||||
|
||||
[Preparing your Environment](#bkmk-pe)
|
||||
|
||||
- Steps to Prepare the Base Image – Whether in a non-persistent VDI or RDSH environment, only a few steps must be completed in the base image to enable this approach.
|
||||
|
||||
- Use UE-V 2.1 as the User Profile Management (UPM) solution for the App-V approach – the cornerstone of this approach is the ability of a UEM solution to persist the contents of just a few registry and file locations. These locations constitute the user integrations\*. Be sure to review the specific requirements for the UPM solution.
|
||||
|
||||
[User Experience Walk-through](#bkmk-uewt)
|
||||
|
||||
- Walk-through – This is a step-by-step walk-through of the App-V and UE-V operations and the expectations users should have.
|
||||
|
||||
- Outcome – This describes the expected results.
|
||||
|
||||
[Impact to Package Lifecycle](#bkmk-plc)
|
||||
|
||||
[Enhancing the VDI Experience through Performance Optimization/Tuning](#bkmk-evdi)
|
||||
|
||||
### <a href="" id="applicability-checklist-"></a>Applicability Checklist
|
||||
|
||||
Deployment Environment
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
|
||||
<td align="left"><p>Non-Persistent VDI or RDSH.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
|
||||
<td align="left"><p>User Experience Virtualization (UE-V), other UPM solutions or User Profile Disks (UPD).</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
Expected Configuration
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
|
||||
<td align="left"><p>User Experience Virtualization (UE-V) with the App-V user state template enabled or User Profile Management (UPM) software. Non-UE-V UPM software must be capable of triggering on Login or Process/Application Start and Logoff.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
|
||||
<td align="left"><p>App-V Shared Content Store (SCS) is configured or can be configured.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
IT Administration
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
|
||||
<td align="left"><p>Admin may need to update the VM base image regularly to ensure optimal performance or Admin may need to manage multiple images for different user groups.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### <a href="" id="bkmk-us"></a>Usage Scenario
|
||||
|
||||
As you review the two scenarios, keep in mind that these approach the extremes. Based on your usage requirements, you may choose to apply these steps to a subset of users, virtual application packages, or both.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Optimized for Performance</th>
|
||||
<th align="left">Optimized for Storage</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>To provide the most optimal user experience, this approach leverages the capabilities of a UPM solution and requires additional image preparation and can incur some additional image management overhead.</p>
|
||||
<p>The following describes many performance improvements in stateful non-persistent deployments. For more information, see the <strong>Sequencing Steps to Optimize Packages for Publishing Performance</strong> and reference to <strong>App-V Sequencing Guide</strong> in the <strong>See Also section of this document</strong>.</p></td>
|
||||
<td align="left"><p>The general expectations of the previous scenario still apply here. However, keep in mind that VM images are typically stored in very costly arrays; a slight alteration has been made to the approach. Do not pre-configure user-targeted virtual application packages in the base image.</p>
|
||||
<p>The impact of this alteration is detailed in the User Experience Walkthrough section of this document.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### <a href="" id="bkmk-pe"></a>Preparing your Environment
|
||||
|
||||
The following table displays the required steps to prepare the base image and the UE-V or another UPM solution for the approach.
|
||||
|
||||
**Prepare the Base Image**
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Optimized for Performance</th>
|
||||
<th align="left">Optimized for Storage</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>Install the App-V client version of the client.</p></li>
|
||||
<li><p>Install UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.</p></li>
|
||||
<li><p>Configure for Shared Content Store (SCS) mode. For more information see [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md).</p></li>
|
||||
<li><p>Configure Preserve User Integrations on Login Registry DWORD.</p></li>
|
||||
<li><p>Pre-configure all user- and global-targeted packages for example, <strong>Add-AppvClientPackage</strong>.</p></li>
|
||||
<li><p>Pre-configure all user- and global-targeted connection groups for example, <strong>Add-AppvClientConnectionGroup</strong>.</p></li>
|
||||
<li><p>Pre-publish all global-targeted packages.</p>
|
||||
<p></p>
|
||||
<p>Alternatively,</p>
|
||||
<ul>
|
||||
<li><p>Perform a global publishing/refresh.</p></li>
|
||||
<li><p>Perform a user publishing/refresh.</p></li>
|
||||
<li><p>Un-publish all user-targeted packages.</p></li>
|
||||
<li><p>Delete the following user-Virtual File System (VFS) entries.</p></li>
|
||||
</ul>
|
||||
<p><code>AppData\Local\Microsoft\AppV\Client\VFS</code></p>
|
||||
<p><code>AppData\Roaming\Microsoft\AppV\Client\VFS</code></p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>Install the App-V client version of the client.</p></li>
|
||||
<li><p>Install UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.</p></li>
|
||||
<li><p>Configure for Shared Content Store (SCS) mode. For more information see [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md).</p></li>
|
||||
<li><p>Configure Preserve User Integrations on Login Registry DWORD.</p></li>
|
||||
<li><p>Pre-configure all global-targeted packages for example, <strong>Add-AppvClientPackage</strong>.</p></li>
|
||||
<li><p>Pre-configure all global-targeted connection groups for example, <strong>Add-AppvClientConnectionGroup</strong>.</p></li>
|
||||
<li><p>Pre-publish all global-targeted packages.</p>
|
||||
<p></p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Configurations** - For critical App-V Client configurations and for a little more context and how-to, review the following information:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Configuration Setting</th>
|
||||
<th align="left">What does this do?</th>
|
||||
<th align="left">How should I use it?</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Shared Content Store (SCS) Mode</p>
|
||||
<ul>
|
||||
<li><p>Configurable in PowerShell using <strong>Set- AppvClientConfiguration</strong> –<strong>SharedContentStoreMode</strong>, or</p></li>
|
||||
<li><p>During installation of the App-V client.</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p>When running the shared content store only publishing data is maintained on hard disk; other virtual application assets are maintained in memory (RAM).</p>
|
||||
<p>This helps to conserve local storage and minimize disk I/O per second (IOPS).</p></td>
|
||||
<td align="left"><p>This is recommended when low-latency connections are available between the App-V Client endpoint and the SCS content server, SAN.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>PreserveUserIntegrationsOnLogin</p>
|
||||
<ul>
|
||||
<li><p>Configure in the Registry under <strong>HKEY_LOCAL_MACHINE</strong> \ <strong>Software</strong> \ <strong>Microsoft</strong> \ <strong>AppV</strong> \ <strong>Client</strong> \ <strong>Integration</strong>.</p></li>
|
||||
<li><p>Create the DWORD value <strong>PreserveUserIntegrationsOnLogin</strong> with a value of <strong>1</strong>.</p></li>
|
||||
<li><p>Restart the App-V client service or restart the computer running the App-V Client.</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p>If you have not pre-configured (<strong>Add-AppvClientPackage</strong>) a specific package and this setting is not configured, the App-V Client will de-integrate* the persisted user integrations, then re-integrate*.</p>
|
||||
<p>For every package that meets the above conditions, effectively twice the work will be done during publishing/refresh.</p></td>
|
||||
<td align="left"><p>If you don’t plan to pre-configure every available user package in the base image, use this setting.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>MaxConcurrentPublishingRefresh</p>
|
||||
<ul>
|
||||
<li><p>Configure in the Registry under <strong>HKEY_LOCAL_MACHINE</strong> \<strong>Software</strong> \ <strong>Microsoft</strong> \ <strong>AppV</strong> \<strong>Client</strong> \ <strong>Publishing</strong>.</p></li>
|
||||
<li><p>Create the DWORD value <strong>MaxConcurrentPublishingrefresh</strong> with the desired maximum number of concurrent publishing refreshes.</p></li>
|
||||
<li><p>The App-V client service and computer do not need to be restarted.</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p>This setting determines the number of users that can perform a publishing refresh/sync at the same time. The default setting is no limit.</p></td>
|
||||
<td align="left"><p>Limiting the number of concurrent publishing refreshes prevents excessive CPU usage that could impact computer performance. This limit is recommended in an RDS environment, where multiple users can log in to the same computer at the same time and perform a publishing refresh sync.</p>
|
||||
<p>If the concurrent publishing refresh threshold is reached, the time required to publish new applications and make them available to end users after they log in could take an indeterminate amount of time.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Configure UE-V solution for App-V Approach
|
||||
|
||||
We recommend using Microsoft User Experience Virtualization (UE-V) to capture and centralize application settings and Windows operating system settings for a specific user. These settings are then applied to the different computers that are accessed by the user, including desktop computers, laptop computers, and virtual desktop infrastructure (VDI) sessions. UE-V is optimized for RDS and VDI scenarios.
|
||||
|
||||
For more information see [Getting Started With User Experience Virtualization 2.0](https://technet.microsoft.com/library/dn458926.aspx)
|
||||
|
||||
In essence all that is required is to install the UE-V client and download the following Microsoft authored App-V settings template from the [Microsoft User Experience Virtualization (UE-V) template gallery](http://gallery.technet.microsoft.com/Authored-UE-V-Settings-bb442a33). Register the template. For more information around UE-V templates see [The UE-V specific resource for acquiring and registering the template](https://technet.microsoft.com/library/dn458926.aspx).
|
||||
|
||||
**Note**
|
||||
Without performing an additional configuration step, the Microsoft User Environment Virtualization (UE-V) will not be able to synchronize the Start menu shortcuts (.lnk files) on the target computer. The .lnk file type is excluded by default.
|
||||
|
||||
UE-V will only support removing the .lnk file type from the exclusion list in the RDS and VDI scenarios, where every user’s device will have the same set of applications installed to the same location and every .lnk file is valid for all the users’ devices. For example, UE-V would not currently support the following 2 scenarios, because the net result will be that the shortcut will be valid on one but not all devices.
|
||||
|
||||
- If a user has an application installed on one device with .lnk files enabled and the same native application installed on another device to a different installation root with .lnk files enabled.
|
||||
|
||||
- If a user has an application installed on one device but not another with .lnk files enabled.
|
||||
|
||||
|
||||
|
||||
**Important**
|
||||
This topic describes how to change the Windows registry by using Registry Editor. If you change the Windows registry incorrectly, you can cause serious problems that might require you to reinstall Windows. You should make a backup copy of the registry files (System.dat and User.dat) before you change the registry. Microsoft cannot guarantee that the problems that might occur when you change the registry can be resolved. Change the registry at your own risk.
|
||||
|
||||
|
||||
|
||||
Using the Microsoft Registry Editor (regedit.exe), navigate to **HKEY\_LOCAL\_MACHINE** \\ **Software** \\ **Microsoft** \\ **UEV** \\ **Agent** \\ **Configuration** \\ **ExcludedFileTypes** and remove **.lnk** from the excluded file types.
|
||||
|
||||
**Configure other User Profile Management (UPM) solution for App-V Approach**
|
||||
|
||||
The expectation in a stateful environment is that a UPM solution is implemented and can support persistence of user data across sessions and between logins.
|
||||
|
||||
The requirements for the UPM solution are as follows.
|
||||
|
||||
To enable an optimized login experience, for example the App-V approach for the user, the solution must be capable of:
|
||||
|
||||
- Persisting the below user integrations as part of the user profile/persona.
|
||||
|
||||
- Triggering a user profile sync on login (or application start), which can guarantee that all user integrations are applied before publishing/refresh begin, or,
|
||||
|
||||
- Attaching and detaching a user profile disk (UPD) or similar technology that contains the user integrations.
|
||||
|
||||
**Note**
|
||||
App-V is supported when using UPD only when the entire profile is stored on the user profile disk.
|
||||
|
||||
App-V packages are not supported when using UPD with selected folders stored in the user profile disk. The Copy on Write driver does not handle UPD selected folders.
|
||||
|
||||
|
||||
|
||||
- Capturing changes to the locations, which constitute the user integrations, prior to session logoff.
|
||||
|
||||
With App-V when you add a publishing server (**Add-AppvPublishingServer**) you can configure synchronization, for example refresh during log on and/or after a specified refresh interval. In both cases a scheduled task is created.
|
||||
|
||||
In previous versions of App-V, both scheduled tasks were configured using a VBScript that would initiate the user and global refresh. With Hotfix Package 4 for Application Virtualization 5.0 SP2 the user refresh on log on was initiated by **SyncAppvPublishingServer.exe**. This change was introduced to provide UPM solutions a trigger process. This process delays the publish /refresh to allow the UPM solution to apply the user integrations. It will exit once the publishing/refresh is complete.
|
||||
|
||||
**User Integrations**
|
||||
|
||||
Registry – HKEY\_CURRENT\_USER
|
||||
|
||||
- Path - Software\\Classes
|
||||
|
||||
Exclude: Local Settings, ActivatableClasses, AppX\*
|
||||
|
||||
- Path - Software\\Microsoft\\AppV
|
||||
|
||||
- Path- Software\\Microsoft\\Windows\\CurrentVersion\\App Paths
|
||||
|
||||
**File Locations**
|
||||
|
||||
- Root – “Environment Variable” APPDATA
|
||||
|
||||
Path – Microsoft\\AppV\\Client\\Catalog
|
||||
|
||||
- Root – “Environment Variable” APPDATA
|
||||
|
||||
Path – Microsoft\\AppV\\Client\\Integration
|
||||
|
||||
- Root – “Environment Variable” APPDATA
|
||||
|
||||
Path - Microsoft\\Windows\\Start Menu\\Programs
|
||||
|
||||
- (To persist all desktop shortcuts, virtual and non-virtual)
|
||||
|
||||
Root - “KnownFolder” {B4BFCC3A-DB2C-424C-B029-7FE99A87C641}FileMask - \*.lnk
|
||||
|
||||
**Microsoft User Experience Virtualization (UE-V)**
|
||||
|
||||
Additionally, we recommend using Microsoft User Experience Virtualization (UE-V) to capture and centralize application settings and Windows operating system settings for a specific user. These settings are then applied to the different computers that are accessed by the user, including desktop computers, laptop computers, and virtual desktop infrastructure (VDI) sessions.
|
||||
|
||||
For more information see [Getting Started With User Experience Virtualization 1.0](http://technet.microsoft.com/library/jj680015.aspx) and [Sharing Settings Location Templates with the UE-V Template Gallery](http://technet.microsoft.com/library/jj679972.aspx).
|
||||
|
||||
### <a href="" id="bkmk-uewt"></a>User Experience Walk-through
|
||||
|
||||
This following is a step-by-step walk-through of the App-V and UPM operations and the expectations users should expect.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Optimized for Performance</th>
|
||||
<th align="left">Optimized for Storage</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>After implementing this approach in the VDI/RDSH environment, on first login,</p>
|
||||
<ul>
|
||||
<li><p>(Operation) A user-publishing/refresh is initiated. (Expectation) If this is the first time a user has published virtual applications (e.g. non-persistent), this will take the usual duration of a publishing/refresh.</p></li>
|
||||
<li><p>(Operation) After the publishing/refresh, the UPM solution captures the user integrations. (Expectation) Depending on how the UPM solution is configured, this may occur as part of the logoff process. This will incur the same/similar overhead as persisting the user state.</p></li>
|
||||
</ul>
|
||||
<p>On subsequent logins:</p>
|
||||
<ul>
|
||||
<li><p>(Operation) UPM solution applies the user integrations to the system prior to publishing/refresh.</p>
|
||||
<p>(Expectation) There will be shortcuts present on the desktop, or in the start menu, which work immediately. When the publishing/refresh completes (i.e., package entitlements change), some may go away.</p></li>
|
||||
<li><p>(Operation) Publishing/refresh will process un-publish and publish operations for changes in user package entitlements. (Expectation) If there are no entitlement changes, publishing1 will complete in seconds. Otherwise, the publishing/refresh will increase relative to the number and complexity* of virtual applications</p></li>
|
||||
<li><p>(Operation) UPM solution will capture user integrations again at logoff. (Expectation) Same as previous.</p></li>
|
||||
</ul>
|
||||
<p>¹ The publishing operation (<strong>Publish-AppVClientPackage</strong>) adds entries to the user catalog, maps entitlement to the user, identifies the local store, and finishes by completing any integration steps.</p></td>
|
||||
<td align="left"><p>After implementing this approach in the VDI/RDSH environment, on first login,</p>
|
||||
<ul>
|
||||
<li><p>(Operation) A user-publishing/refresh is initiated. (Expectation)</p>
|
||||
<ul>
|
||||
<li><p>If this is the first time a user has published virtual applications (e.g., non-persistent), this will take the usual duration of a publishing/refresh.</p></li>
|
||||
<li><p>First and subsequent logins will be impacted by pre-configuring of packages (add/refresh).</p>
|
||||
<p></p></li>
|
||||
</ul></li>
|
||||
<li><p>(Operation) After the publishing/refresh, the UPM solution captures the user integrations. (Expectation) Depending on how the UPM solution is configured, this may occur as part of the logoff process. This will incur the same/similar overhead as persisting the user state</p></li>
|
||||
</ul>
|
||||
<p>On subsequent logins:</p>
|
||||
<ul>
|
||||
<li><p>(Operation) UPM solution applies the user integrations to the system prior to publishing/refresh.</p></li>
|
||||
<li><p>(Operation) Add/refresh must pre-configure all user targeted applications. (Expectation)</p>
|
||||
<ul>
|
||||
<li><p>This may increase the time to application availability significantly (on the order of 10’s of seconds).</p></li>
|
||||
<li><p>This will increase the publishing refresh time relative to the number and complexity* of virtual applications.</p>
|
||||
<p></p></li>
|
||||
</ul></li>
|
||||
<li><p>(Operation) Publishing/refresh will process un-publish and publish operations for changes to user package entitlements.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Outcome</th>
|
||||
<th align="left">Outcome</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>Because the user integrations are entirely preserved, there will be no work for example, integration for the publishing/refresh to complete. All virtual applications will be available within seconds of login.</p></li>
|
||||
<li><p>The publishing/refresh will process changes to the users entitled virtual applications which impacts the experience.</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p>Because the add/refresh must re-configure all the virtual applications to the VM, the publishing refresh time on every login will be extended.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### <a href="" id="bkmk-plc"></a>Impact to Package Life Cycle
|
||||
|
||||
Upgrading a package is a crucial aspect of the package lifecycle. To help guarantee users have access to the appropriate upgraded (published) or downgraded (un-published) virtual application packages, it is recommended you update the base image to reflect these changes. To understand why review the following section:
|
||||
|
||||
App-V 5.0 SP2 introduced the concept of pending states. In the past,
|
||||
|
||||
- If an administrator changed entitlements or created a new version of a package (upgraded) and during a publishing/refresh that package was in-use, the un-publish or publish operation, respectively, would fail.
|
||||
|
||||
- Now, if a package is in-use the operation will be pended. The un-publish and publish-pend operations will be processed on service restart or if another publish or un-publish command is issued. In the latter case, if the virtual application is in-use otherwise, the virtual application will remain in a pending state. For globally published packages, a restart (or service restart) often needed.
|
||||
|
||||
In a non-persistent environment, it is unlikely these pended operations will be processed. The pended operations, for example tasks are captured under **HKEY\_CURRENT\_USER** \\ **Software** \\ **Microsoft** \\ **AppV** \\ **Client** \\ **PendingTasks**. Although this location is persisted by the UPM solution, if it is not applied to the environment prior to log on, it will not be processed.
|
||||
|
||||
### <a href="" id="bkmk-evdi"></a>Enhancing the VDI Experience through Performance Optimization Tuning
|
||||
|
||||
The following section contains lists with information about Microsoft documentation and downloads that may be useful when optimizing your environment for performance.
|
||||
|
||||
**.NET NGEN Blog and Script (Highly Recommended)**
|
||||
|
||||
About NGEN technology
|
||||
|
||||
- [How to speed up NGEN optimaztion](http://blogs.msdn.com/b/dotnet/archive/2013/08/06/wondering-why-mscorsvw-exe-has-high-cpu-usage-you-can-speed-it-up.aspx)
|
||||
|
||||
- [Script](http://aka.ms/DrainNGenQueue)
|
||||
|
||||
**Windows Server and Server Roles**
|
||||
|
||||
Server Performance Tuning Guidelines for
|
||||
|
||||
- [Microsoft Windows Server 2012 R2](http://msdn.microsoft.com/library/windows/hardware/dn529133.aspx)
|
||||
|
||||
- [Microsoft Windows Server 2012](http://download.microsoft.com/download/0/0/B/00BE76AF-D340-4759-8ECD-C80BC53B6231/performance-tuning-guidelines-windows-server-2012.docx)
|
||||
|
||||
- [Microsoft Windows Server 2008 R2](http://download.microsoft.com/download/6/B/2/6B2EBD3A-302E-4553-AC00-9885BBF31E21/Perf-tun-srv-R2.docx)
|
||||
|
||||
**Server Roles**
|
||||
|
||||
- [Remote Desktop Virtualization Host](http://msdn.microsoft.com/library/windows/hardware/dn567643.aspx)
|
||||
|
||||
- [Remote Desktop Session Host](http://msdn.microsoft.com/library/windows/hardware/dn567648.aspx)
|
||||
|
||||
- [IIS Relevance: App-V Management, Publishing, Reporting Web Services](http://msdn.microsoft.com/library/windows/hardware/dn567678.aspx)
|
||||
|
||||
- [File Server (SMB) Relevance: If used for App-V Content Storage and Delivery in SCS Mode](http://technet.microsoft.com/library/jj134210.aspx)
|
||||
|
||||
**Windows Client (Guest OS) Performance Tuning Guidance**
|
||||
|
||||
- [Microsoft Windows 7](http://download.microsoft.com/download/E/5/7/E5783D68-160B-4366-8387-114FC3E45EB4/Performance Tuning Guidelines for Windows 7 Desktop Virtualization v1.9.docx)
|
||||
|
||||
- [Optimization Script: (Provided by Microsoft Support)](http://blogs.technet.com/b/jeff_stokes/archive/2012/10/15/the-microsoft-premier-field-engineer-pfe-view-on-virtual-desktop-vdi-density.aspx)
|
||||
|
||||
- [Microsoft Windows 8](http://download.microsoft.com/download/6/0/1/601D7797-A063-4FA7-A2E5-74519B57C2B4/Windows_8_VDI_Image_Client_Tuning_Guide.pdf)
|
||||
|
||||
- [Optimization Script: (Provided by Microsoft Support)](http://blogs.technet.com/b/jeff_stokes/archive/2013/04/09/hot-off-the-presses-get-it-now-the-windows-8-vdi-optimization-script-courtesy-of-pfe.aspx)
|
||||
|
||||
## Sequencing Steps to Optimize Packages for Publishing Performance
|
||||
|
||||
|
||||
Several App-V features facilitate new scenarios or enable new customer deployment scenarios. These following features can impact the performance of the publishing and launch operations.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="25%" />
|
||||
<col width="25%" />
|
||||
<col width="25%" />
|
||||
<col width="25%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Step</th>
|
||||
<th align="left">Consideration</th>
|
||||
<th align="left">Benefits</th>
|
||||
<th align="left">Tradeoffs</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>No Feature Block 1 (FB1, also known as Primary FB)</p></td>
|
||||
<td align="left"><p>No FB1 means the application will launch immediately and stream fault (application requires file, DLL and must pull down over the network) during launch.If there are network limitations, FB1 will:</p>
|
||||
<ul>
|
||||
<li><p>Reduce the number of stream faults and network bandwidth used when you launch an application for the first time.</p></li>
|
||||
<li><p>Delay launch until the entire FB1 has been streamed.</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p>Stream faulting decreases the launch time.</p></td>
|
||||
<td align="left"><p>Virtual application packages with FB1 configured will need to be re-sequenced.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Removing FB1
|
||||
|
||||
Removing FB1 does not require the original application installer. After completing the following steps, it is suggested that you revert the computer running the sequencer to a clean snapshot.
|
||||
|
||||
**Sequencer UI** - Create a New Virtual Application Package.
|
||||
|
||||
1. Complete the sequencing steps up to Customize -> Streaming.
|
||||
|
||||
2. At the Streaming step, do not select **Optimize the package for deployment over slow or unreliable network**.
|
||||
|
||||
3. If desired, move on to **Target OS**.
|
||||
|
||||
**Modify an Existing Virtual Application Package**
|
||||
|
||||
1. Complete the sequencing steps up to Streaming.
|
||||
|
||||
2. Do not select **Optimize the package for deployment over a slow or unreliable network**.
|
||||
|
||||
3. Move to **Create Package**.
|
||||
|
||||
**PowerShell** - Update an Existing Virtual Application Package.
|
||||
|
||||
1. Open an elevated PowerShell session.
|
||||
|
||||
2. Import-module **appvsequencer**.
|
||||
|
||||
3. **Update-AppvSequencerPackage** - **AppvPackageFilePath**
|
||||
|
||||
"C:\\Packages\\MyPackage.appv" -Installer
|
||||
|
||||
"C:\\PackageInstall\\PackageUpgrade.exe empty.exe" -OutputPath
|
||||
|
||||
"C:\\UpgradedPackages"
|
||||
|
||||
**Note**
|
||||
This cmdlet requires an executable (.exe) or batch file (.bat). You must provide an empty (does nothing) executable or batch file.
|
||||
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="25%" />
|
||||
<col width="25%" />
|
||||
<col width="25%" />
|
||||
<col width="25%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Step</th>
|
||||
<th align="left">Considerations</th>
|
||||
<th align="left">Benefits</th>
|
||||
<th align="left">Tradeoffs</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>No SXS Install at Publish (Pre-Install SxS assemblies)</p></td>
|
||||
<td align="left"><p>Virtual Application packages do not need to be re-sequenced. SxS Assemblies can remain in the virtual application package.</p></td>
|
||||
<td align="left"><p>The SxS Assembly dependencies will not install at publishing time.</p></td>
|
||||
<td align="left"><p>SxS Assembly dependencies must be pre-installed.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Creating a new virtual application package on the sequencer
|
||||
|
||||
If, during sequencer monitoring, an SxS Assembly (such as a VC++ Runtime) is installed as part of an application’s installation, SxS Assembly will be automatically detected and included in the package. The administrator will be notified and will have the option to exclude the SxS Assembly.
|
||||
|
||||
**Client Side**:
|
||||
|
||||
When publishing a virtual application package, the App-V Client will detect if a required SxS dependency is already installed. If the dependency is unavailable on the computer and it is included in the package, a traditional Windows Insataller (.**msi**) installation of the SxS assembly will be initiated. As previously documented, simply install the dependency on the computer running the client to ensure that the Windows Installer (.msi) installation will not occur.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="25%" />
|
||||
<col width="25%" />
|
||||
<col width="25%" />
|
||||
<col width="25%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Step</th>
|
||||
<th align="left">Considerations</th>
|
||||
<th align="left">Benefits</th>
|
||||
<th align="left">Tradeoffs</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Selectively Employ Dynamic Configuration files</p></td>
|
||||
<td align="left"><p>The App-V client must parse and process these Dynamic Configuration files.</p>
|
||||
<p>Be conscious of size and complexity (script execution, VREG inclusions/exclusions) of the file.</p>
|
||||
<p>Numerous virtual application packages may already have User- or computer–specific dynamic configurations files.</p></td>
|
||||
<td align="left"><p>Publishing times will improve if these files are used selectively or not at all.</p></td>
|
||||
<td align="left"><p>Virtual application packages would need to be reconfigured individually or via the App-V server management console to remove associated Dynamic Configuration files.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Disabling a Dynamic Configuration using Powershell
|
||||
|
||||
- For already published packages, you can use `Set-AppVClientPackage –Name Myapp –Path c:\Packages\Apps\MyApp.appv` without
|
||||
|
||||
**-DynamicDeploymentConfiguration** parameter
|
||||
|
||||
- Similarly, when adding new packages using `Add-AppVClientPackage –Path c:\Packages\Apps\MyApp.appv`, do not use the
|
||||
|
||||
**-DynamicDeploymentConfiguration** parameter.
|
||||
|
||||
For documentation on How to Apply a Dynamic Configuration, see:
|
||||
|
||||
- [How to Apply the User Configuration File by Using PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)
|
||||
|
||||
- [How to Apply the Deployment Configuration File by Using PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="25%" />
|
||||
<col width="25%" />
|
||||
<col width="25%" />
|
||||
<col width="25%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Step</th>
|
||||
<th align="left">Considerations</th>
|
||||
<th align="left">Benefits</th>
|
||||
<th align="left">Tradeoffs</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Account for Synchronous Script Execution during Package Lifecycle.</p></td>
|
||||
<td align="left"><p>If script collateral is embedded in the package, Add (Powershell) may be significantly slower.</p>
|
||||
<p>Running of scripts during virtual application launch (StartVirtualEnvironment, StartProcess) and/or Add+Publish will impact the perceived performance during one or more of these lifecycle operations.</p></td>
|
||||
<td align="left"><p>Use of Asynchronous (Non-Blocking) Scripts will ensure that the lifecycle operations complete efficiently.</p></td>
|
||||
<td align="left"><p>This step requires working knowledge of all virtual application packages with embedded script collateral, which have associated dynamic configurations files and which reference and run scripts synchronously.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Remove Extraneous Virtual Fonts from Package.</p></td>
|
||||
<td align="left"><p>The majority of applications investigated by the App-V product team contained a small number of fonts, typically fewer than 20.</p></td>
|
||||
<td align="left"><p>Virtual Fonts impact publishing refresh performance.</p></td>
|
||||
<td align="left"><p>Desired fonts will need to be enabled/installed natively. For instructions, see Install or uninstall fonts.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Determining what virtual fonts exist in the package
|
||||
|
||||
- Make a copy of the package.
|
||||
|
||||
- Rename Package\_copy.appv to Package\_copy.zip
|
||||
|
||||
- Open AppxManifest.xml and locate the following:
|
||||
|
||||
<appv:Extension Category="AppV.Fonts">
|
||||
|
||||
<appv:Fonts>
|
||||
|
||||
<appv:Font Path="\[{Fonts}\]\\private\\CalibriL.ttf" DelayLoad="true"></appv:Font>
|
||||
|
||||
**Note**
|
||||
If there are fonts marked as **DelayLoad**, those will not impact first launch.
|
||||
|
||||
|
||||
|
||||
</appv:Fonts>
|
||||
|
||||
### Excluding virtual fonts from the package
|
||||
|
||||
Use the dynamic configuration file that best suits the user scope – deployment configuration for all users on computer, user configuration for specific user or users.
|
||||
|
||||
- Disable fonts with the deployment or user configuration.
|
||||
|
||||
Fonts
|
||||
|
||||
-->
|
||||
|
||||
<Fonts Enabled="false" />
|
||||
|
||||
<!--
|
||||
|
||||
## <a href="" id="bkmk-terms1"></a> App-V Performance Guidance Terminology
|
||||
|
||||
|
||||
The following terms are used when describing concepts and actions related to App-V performance optimization.
|
||||
|
||||
- **Complexity** – Refers to the one or more package characteristics that may impact performance during pre-configure (**Add-AppvClientPackage**) or integration (**Publish-AppvClientPackage**). Some example characteristics are: manifest size, number of virtual fonts, number of files.
|
||||
|
||||
- **De-Integrate** – Removes the user integrations
|
||||
|
||||
- **Re-Integrate** – Applies the user integrations.
|
||||
|
||||
- **Non-Persistent, Pooled** – Creates a computer running a virtual environment each time they log in.
|
||||
|
||||
- **Persistent, Personal** – A computer running a virtual environment that remains the same for every login.
|
||||
|
||||
- **Stateful** - For this document, implies that user integrations are persisted between sessions and a user environment management technology is used in conjunction with non-persistent RDSH or VDI.
|
||||
|
||||
- **Stateless** – Represents a scenario when no user state is persisted between sessions.
|
||||
|
||||
- **Trigger** – (or Native Action Triggers). UPM uses these types of triggers to initiate monitoring or synchronization operations.
|
||||
|
||||
- **User Experience** - In the context of App-V, the user experience, quantitatively, is the sum of the following parts:
|
||||
|
||||
- From the point that users initiate a log-in to when they are able to manipulate the desktop.
|
||||
|
||||
- From the point where the desktop can be interacted with to the point a publishing refresh begins (in PowerShell terms, sync) when using the App-V full server infrastructure. In standalone instances, it is when the **Add-AppVClientPackage** and **Publish-AppVClientPackage Powershell** commands are initiated.
|
||||
|
||||
- From start to completion of the publishing refresh. In standalone instances, this is the first to last virtual application published.
|
||||
|
||||
- From the point where the virtual application is available to launch from a shortcut. Alternatively, it is from the point at which the file type association is registered and will launch a specified virtual application.
|
||||
|
||||
- **User Profile Management** – The controlled and structured approach to managing user components associated with the environment. For example, user profiles, preference and policy management, application control and application deployment. You can use scripting or third-party solutions configure the environment as needed.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Application Virtualization (App-V) overview](appv-for-windows.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
81
windows/manage/appv-planning-checklist.md
Normal file
81
windows/manage/appv-planning-checklist.md
Normal file
@ -0,0 +1,81 @@
|
||||
---
|
||||
title: App-V Planning Checklist (Windows 10)
|
||||
description: App-V Planning Checklist
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# App-V Planning Checklist
|
||||
|
||||
|
||||
This checklist can be used to help you plan for preparing your organization for an App-V deployment.
|
||||
|
||||
> [!NOTE]
|
||||
> This checklist outlines the recommended steps and a high-level list of items to consider when planning for an App-V deployment. It is recommended that you copy this checklist and customize it for your use.
|
||||
|
||||
<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 1.0 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 so you 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>[Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.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 running App-V clients using in shared content store mode.</p></td>
|
||||
<td align="left"><p>[How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
[Planning for App-V](appv-planning-for-appv.md)
|
||||
146
windows/manage/appv-planning-folder-redirection-with-appv.md
Normal file
146
windows/manage/appv-planning-folder-redirection-with-appv.md
Normal file
@ -0,0 +1,146 @@
|
||||
---
|
||||
title: Planning to Use Folder Redirection with App-V (Windows 10)
|
||||
description: Planning to Use Folder Redirection with App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# Planning to Use Folder Redirection with App-V
|
||||
|
||||
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.
|
||||
|
||||
This topic contains the following sections:
|
||||
|
||||
- [Requirements for using folder redirection](#bkmk-folder-redir-reqs)
|
||||
|
||||
- [How to configure folder redirection for use with App-V](#bkmk-folder-redir-cfg)
|
||||
|
||||
- [How folder redirection works with App-V](#bkmk-folder-redir-works)
|
||||
|
||||
- [Overview of folder redirection](#bkmk-folder-redir-overview)
|
||||
|
||||
## <a href="" id="bkmk-folder-redir-reqs"></a>Requirements and unsupported scenarios for using folder redirection
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Requirements</p></td>
|
||||
<td align="left"><p>To use %AppData% folder redirection, you must:</p>
|
||||
<ul>
|
||||
<li><p>Have an App-V package that has an AppData virtual file system (VFS) folder.</p></li>
|
||||
<li><p>Enable folder redirection and redirect users’ folders to a shared folder, typically a network folder.</p></li>
|
||||
<li><p>Roam both or neither of the following:</p>
|
||||
<ul>
|
||||
<li><p>Files under %appdata%\Microsoft\AppV\Client\Catalog</p></li>
|
||||
<li><p>Registry settings under HKEY_CURRENT_USER\Software\Microsoft\AppV\Client\Packages</p>
|
||||
<p>For more detail, see [Application Publishing and Client Interaction](appv-application-publishing-and-client-interaction.md#bkmk-clt-inter-roam-reqs).</p></li>
|
||||
</ul></li>
|
||||
<li><p>Ensure that the following folders are available to each user who logs into the computer that is running the App-V client:</p>
|
||||
<ul>
|
||||
<li><p>%AppData% is configured to the desired network location (with or without [Offline Files](http://technet.microsoft.com/library/cc780552.aspx) support).</p></li>
|
||||
<li><p>%LocalAppData% is configured to the desired local folder.</p></li>
|
||||
</ul></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Unsupported scenarios</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Configuring %LocalAppData% as a network drive.</p></li>
|
||||
<li><p>Redirecting the Start menu to a single folder for multiple users.</p></li>
|
||||
<li><p>If roaming AppData (%AppData%) is redirected to a network share that is not available, App-V applications will fail to launch, unless the unavailable network share has been enabled for Offline Files.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-folder-redir-cfg"></a>How to configure folder redirection for use with App-V
|
||||
|
||||
|
||||
Folder redirection can be applied to different folders, such as Desktop, My Documents, My Pictures, etc. However, the only folder that impacts the use of App-V applications is the user’s roaming AppData folder (%AppData%). You can apply folder redirection to any other supported folders without impacting App-V.
|
||||
|
||||
## <a href="" id="bkmk-folder-redir-works"></a>How folder redirection works with App-V
|
||||
|
||||
|
||||
The following table describes how folder redirection works when %AppData% is redirected to a network and when you have met the requirements listed earlier in this article.
|
||||
|
||||
<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, which 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>To provide redundancy, App-V keeps the three most recent copies of the compressed data under %AppData%.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-folder-redir-overview"></a>Overview of folder redirection
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Purpose</p></td>
|
||||
<td align="left"><p>Enables end users to work with files, which have been redirected to another folder, as if the files still existed on the local drive.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Description</p></td>
|
||||
<td align="left"><p>Folder redirection allows users and administrators to redirect the path of a folder to a network location. The documents in the folder are available to the user from any computer on the network.</p>
|
||||
<ul>
|
||||
<li><p>Folder redirection allows users and administrators to redirect the path of a folder to a network location. The documents in the folder are available to the user from any computer on the network.</p></li>
|
||||
<li><p>The new location can be a folder on the local computer or a folder on a shared network.</p></li>
|
||||
<li><p>Folder redirection updates the files immediately, whereas roaming data is typically synchronized when the user logs in or logs off.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Usage example</p></td>
|
||||
<td align="left"><p>You can redirect the Documents folder, which is usually stored on the computer's local hard disk, to a network location. The user can access the documents in the folder from any computer on the network.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>More resources</p></td>
|
||||
<td align="left"><p>[Folder redirection overview](http://technet.microsoft.com/library/cc778976.aspx)</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
116
windows/manage/appv-planning-for-appv-server-deployment.md
Normal file
116
windows/manage/appv-planning-for-appv-server-deployment.md
Normal file
@ -0,0 +1,116 @@
|
||||
---
|
||||
title: Planning for the App-V Server Deployment (Windows 10)
|
||||
description: Planning for the App-V Server Deployment
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Planning for the App-V Server Deployment
|
||||
|
||||
|
||||
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.
|
||||
|
||||
## Planning for App-V Server Deployment
|
||||
|
||||
|
||||
The App-V server consists of the following features:
|
||||
|
||||
- Management Server – provides overall management functionality for the App-V infrastructure.
|
||||
|
||||
- Management Database – facilitates database predeployments for App-V management.
|
||||
|
||||
- Publishing Server – provides hosting and streaming functionality for virtual applications.
|
||||
|
||||
- Reporting Server – provides App-V reporting services.
|
||||
|
||||
- Reporting Database – facilitates database predeployments for App-V reporting.
|
||||
|
||||
The following list displays the recommended methods for installing the App-V server infrastructure:
|
||||
|
||||
- Install the App-V server. For more information, see [How to Deploy the App-V Server](appv-deploy-the-appv-server.md).
|
||||
|
||||
- Install the database, reporting, and management features on separate computers. For more information, see [How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services](appv-install-the-management-and-reporting-databases-on-separate-computers.md).
|
||||
|
||||
- Use Electronic Software Distribution (ESD). For more information, see [How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md).
|
||||
|
||||
- Install all server features on a single computer.
|
||||
|
||||
## <a href="" id="---------app-v-5-1-server-interaction"></a> App-V Server Interaction
|
||||
|
||||
|
||||
This section contains information about how the various App-V server roles interact with each other.
|
||||
|
||||
The App-V Management Server contains the repository of packages and their assigned configurations. For Publishing Servers that are registered with the Management Server, the associated metadata is provided to the Publishing servers for use when publishing refresh requests are received from computers running the App-V Client. App-V publishing servers managed by a single management server can be serving different clients and can have different website names and port bindings. Additionally, all Publishing Servers managed by the same Management Server are replicas of each other.
|
||||
|
||||
**Note**
|
||||
The Management Server does not perform any load balancing. The associated metadata is simply passed to the publishing server for use when processing client requests.
|
||||
|
||||
|
||||
|
||||
## Server-Related Protocols and External Features
|
||||
|
||||
|
||||
The following displays information about server-related protocols used by the App-V servers. The table also includes the reporting mechanism for each server type.
|
||||
|
||||
<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 the 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 with file sharing or streaming capability.</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 [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
|
||||
[Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
46
windows/manage/appv-planning-for-appv.md
Normal file
46
windows/manage/appv-planning-for-appv.md
Normal file
@ -0,0 +1,46 @@
|
||||
---
|
||||
title: Planning for App-V (Windows 10)
|
||||
description: Planning for App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Planning for App-V
|
||||
|
||||
Use this information to plan how to deploy App-V so that it does not disrupt your users or the network.
|
||||
|
||||
## Planning information
|
||||
|
||||
- [Preparing Your Environment for App-V](appv-preparing-your-environment.md)
|
||||
|
||||
This section describes the computing environment requirements and installation prerequisites that should be planned for before beginning App-V setup.
|
||||
|
||||
- [Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
|
||||
This section describes the minimum hardware and software requirements necessary for App-V client, sequencer and server feature installations. Additionally, associated feature planning information is also displayed.
|
||||
|
||||
- [App-V Planning Checklist](appv-planning-checklist.md)
|
||||
|
||||
Planning checklist that can be used to assist in App-V deployment planning.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Other resources for App-V planning
|
||||
|
||||
- [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)
|
||||
134
windows/manage/appv-planning-for-high-availability-with-appv.md
Normal file
134
windows/manage/appv-planning-for-high-availability-with-appv.md
Normal file
@ -0,0 +1,134 @@
|
||||
---
|
||||
title: Planning for High Availability with App-V Server (Windows 10)
|
||||
description: Planning for High Availability with App-V Server
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Planning for High Availability with App-V Server
|
||||
|
||||
Microsoft Application Virtualization (App-V) system configurations can take advantage of options that maintain a high level of available service.
|
||||
|
||||
Use the information in the following sections to help you understand the options to deploy App-V in a highly available configuration.
|
||||
|
||||
- [Support for Microsoft SQL Server clustering](#bkmk-sqlcluster)
|
||||
|
||||
- [Support for IIS Network Load Balancing](#bkmk-iisloadbal)
|
||||
|
||||
- [Support for clustered file servers when running (SCS) mode](#bkmk-clusterscsmode)
|
||||
|
||||
- [Support for Microsoft SQL Server Mirroring](#bkmk-sqlmirroring)
|
||||
|
||||
- [Support for Microsoft SQL Server Always On](#bkmk-sqlalwayson)
|
||||
|
||||
## <a href="" id="bkmk-sqlcluster"></a>Support for Microsoft SQL Server clustering
|
||||
|
||||
|
||||
You can run the App-V Management database and Reporting database on computers that are running Microsoft SQL Server clusters. However, you must install the databases using scripts.
|
||||
|
||||
For instructions, see [How to Deploy the App-V Databases by Using SQL Scripts](appv-deploy-appv-databases-with-sql-scripts.md).
|
||||
|
||||
## <a href="" id="bkmk-iisloadbal"></a>Support for IIS Network Load Balancing
|
||||
|
||||
|
||||
You can use Internet Information Services (IIS) Network Load Balancing to configure a highly available environment for computers running the App-V Management, Publishing, and Reporting services which are deployed through IIS.
|
||||
|
||||
Review the following for more information about configuring IIS and Network Load Balancing for computers running Windows Server operating systems:
|
||||
|
||||
- Provides information about configuring Internet Information Services (IIS) 7.0.
|
||||
|
||||
[Achieving High Availability and Scalability - ARR and NLB](http://www.iis.net/learn/extensions/configuring-application-request-routing-arr/achieving-high-availability-and-scalability-arr-and-nlb)
|
||||
|
||||
- Configuring Microsoft Windows Server
|
||||
|
||||
[Network Load Balancing Overview](https://technet.microsoft.com/library/hh831698(v=ws.11).aspx).
|
||||
|
||||
This information also applies to IIS Network Load Balancing (NLB) clusters in Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012.
|
||||
|
||||
**Note**
|
||||
The IIS Network Load Balancing functionality in Windows Server 2012 is generally the same as in Windows Server 2008 R2. However, some task details are changed in Windows Server 2012. For information on new ways to do tasks, see [Common Management Tasks and Navigation in Windows](https://technet.microsoft.com/library/hh831491.aspx).
|
||||
|
||||
## <a href="" id="bkmk-clusterscsmode"></a>Support for clustered file servers when running SCS mode
|
||||
|
||||
Running App-V Server in Share Content Store (SCS) mode with clustered file servers is supported.
|
||||
|
||||
The following steps can be used to enable this configuration:
|
||||
|
||||
- Configure App-V to run in client SCS mode. For more information about configuring App-V SCS mode, see [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md).
|
||||
|
||||
- Configure the file server cluster, configured in either the scale out mode (which started with Windows Server 2012) or the earlier clustering mode, with a virtual SAN.
|
||||
|
||||
The following steps can be used to validate the configuration:
|
||||
|
||||
1. Add a package on the publishing server. For more information about adding a package, see [How to Add or Upgrade Packages by Using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md).
|
||||
|
||||
2. Perform a publishing refresh on the computer running the App-V client and open an application.
|
||||
|
||||
3. Switch cluster nodes mid-publishing refresh and mid-streaming to ensure failover works correctly.
|
||||
|
||||
Review the following for more information about configuring Windows Server Failover clusters:
|
||||
|
||||
- [Create a Failover Cluster](https://technet.microsoft.com/library/dn505754(v=ws.11).aspx).
|
||||
|
||||
- [Use Cluster Shared Volumes in a Failover Cluster](https://technet.microsoft.com/library/jj612868(v=ws.11).aspx).
|
||||
|
||||
## <a href="" id="bkmk-sqlmirroring"></a>Support for Microsoft SQL Server Mirroring
|
||||
|
||||
Using Microsoft SQL Server mirroring, where the App-V management server database is mirrored utilizing two SQL Server instances, for App-V management server databases is supported.
|
||||
|
||||
Review the following for more information about configuring Microsoft SQL Server Mirroring:
|
||||
|
||||
- [Prepare a Mirror Database for Mirroring (SQL Server)](https://technet.microsoft.com/library/ms189053.aspx)
|
||||
|
||||
- [Establish a Database Mirroring Session Using Windows Authentication (SQL Server Management Studio)](https://msdn.microsoft.com/library/ms188712.aspx)
|
||||
|
||||
The following steps can be used to validate the configuration:
|
||||
|
||||
1. Initiate a Microsoft SQL Server Mirroring session.
|
||||
|
||||
2. Select **Failover** to designate a new master Microsoft SQL Server instance.
|
||||
|
||||
3. Verify that the App-V management server continues to function as expected after the failover.
|
||||
|
||||
The connection string on the management server can be modified to include **failover partner = <server2>**. This will only help when the primary on the mirror has failed over to the secondary and the computer running the App-V client is doing a fresh connection (say after reboot).
|
||||
|
||||
Use the following steps to modify the connection string to include **failover partner = <server2>**:
|
||||
|
||||
**Important**
|
||||
This topic describes how to change the Windows registry by using Registry Editor. If you change the Windows registry incorrectly, you can cause serious problems that might require you to reinstall Windows. You should make a backup copy of the registry files (System.dat and User.dat) before you change the registry. Microsoft cannot guarantee that the problems that might occur when you change the registry can be resolved. Change the registry at your own risk.
|
||||
|
||||
|
||||
1. Login to the management server and open **regedit**.
|
||||
|
||||
2. Navigate to **HKEY\_LOCAL\_MACHINE** \\ **Software** \\ **Microsoft** \\ **AppV** \\ **Server** \\ **ManagementService**.
|
||||
|
||||
3. Modify the **MANAGEMENT\_SQL\_CONNECTION\_STRING** value with the **failover partner = <server2>**.
|
||||
|
||||
4. Restart management service using the IIS console.
|
||||
|
||||
**Note**
|
||||
Database Mirroring is on the list of Deprecated Database Engine Features for Microsoft SQL Server 2012 due to the **AlwaysOn** feature available starting with Microsoft SQL Server 2012.
|
||||
|
||||
Click any of the following links for more information:
|
||||
|
||||
- [Prepare a Mirror Database for Mirroring (SQL Server)](https://technet.microsoft.com/library/ms189053.aspx).
|
||||
|
||||
- [Establish a Database Mirroring Session Using Windows Authentication (SQL Server Management Studio)](https://technet.microsoft.com/library/ms188712(v=sql.130).aspx).
|
||||
|
||||
- [Deprecated Database Engine Features in SQL Server 2012](https://msdn.microsoft.com/library/ms143729(v=sql.110).aspx).
|
||||
|
||||
## <a href="" id="bkmk-sqlalwayson"></a>Support for Microsoft SQL Server Always On configuration
|
||||
|
||||
The App-V management server database supports deployments to computers running Microsoft SQL Server with the **Always On** configuration. For more information, see [Always On Availability Groups (SQL Server)](https://technet.microsoft.com/library/hh510230.aspx).
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
@ -0,0 +1,154 @@
|
||||
---
|
||||
title: Planning for Migrating from a Previous Version of App-V (Windows 10)
|
||||
description: Planning for Migrating from a Previous Version of App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Planning for Migrating from a Previous Version of App-V
|
||||
|
||||
|
||||
Use the following information to plan how to migrate to Microsoft Application Virtualization (App-V) from previous versions of App-V.
|
||||
|
||||
## Migration requirements
|
||||
|
||||
|
||||
Before you start any upgrades, review the following requirements:
|
||||
|
||||
- If you are upgrading from a version earlier than 4.6 SP2, upgrade to version 4.6 SP2 or version 4.6 SP3 first before upgrading to App-V or later. In this scenario, upgrade the App-V clients first, and then upgrade the server components.
|
||||
|
||||
- App-V supports only packages that are created using App-V 5.0 or App-V, or packages that have been converted to the **.appv** format.
|
||||
|
||||
- If you are upgrading the App-V Server from App-V 5.0 SP1, see [About App-V](appv-about-appv.md#bkmk-migrate-to-51) for instructions.
|
||||
|
||||
## Running the App-V client concurrently with App-V 4.6 SP2 or later
|
||||
|
||||
|
||||
You can run the App-V client concurrently on the same computer with the App-V 4.6 SP2 client or App-V 4.6 SP3 client.
|
||||
|
||||
When you run coexisting App-V clients, you can:
|
||||
|
||||
- Convert an App-V 4.6 SP2 or 4.6 SP3 package to the App-V format and publish both packages, when you have both clients running.
|
||||
|
||||
- Define the migration policy for the converted package, which allows the converted App-V package to assume the file type associations and shortcuts from the App-V 4.6 SP2 package.
|
||||
|
||||
### Supported coexistence scenarios
|
||||
|
||||
The following table shows the supported App-V coexistence scenarios. We recommend that you install the latest available updates of a given release when you are running coexisting clients.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">App-V 4.6.x client type</th>
|
||||
<th align="left">App-V client type</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP2</p></td>
|
||||
<td align="left"><p>App-V</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP2 RDS</p></td>
|
||||
<td align="left"><p>App-V RDS</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>App-V</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP3 RDS</p></td>
|
||||
<td align="left"><p>App-V RDS</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Requirements for running coexisting clients
|
||||
|
||||
To run coexisting clients, you must:
|
||||
|
||||
- Install the App-V 4.6 SP2 or App-V 4.6 SP3 client before you install the App-V client.
|
||||
|
||||
- Enable the **Enable Migration Mode** Group Policy setting, which is in the **App-V** > **Client Coexistence** node. To deploy the .admx template, see [How to Download and Deploy MDOP Group Policy (.admx) Templates](http://technet.microsoft.com/library/dn659707.aspx).
|
||||
|
||||
**Note**
|
||||
App-V packages can run side by side with App-V 4.X packages if you have coexisting installations of App-V and 4.X. However, App-V packages cannot interact with App-V 4.X packages in the same virtual environment.
|
||||
|
||||
|
||||
|
||||
### Client downloads and documentation
|
||||
|
||||
The following table provides links to the App-V 4.6.x client downloads and to the TechNet documentation about the releases. The downloads include the App-V “regular” and RDS clients. The TechNet documentation about the App-V client applies to both clients, unless stated otherwise.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">App-V version</th>
|
||||
<th align="left">Link to download the client</th>
|
||||
<th align="left">Link to TechNet documentation</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP2</p></td>
|
||||
<td align="left"><p>[Microsoft Application Virtualization 4.6 Service Pack 2](http://www.microsoft.com/download/details.aspx?id=35513)</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 4.6 SP2](http://technet.microsoft.com/library/jj680847.aspx)</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>[Microsoft Application Virtualization 4.6 Service Pack 3](http://www.microsoft.com/download/details.aspx?id=41187)</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 4.6 SP3](http://technet.microsoft.com/library/dn511019.aspx)</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
For more information about how to configure App-V client coexistence, see:
|
||||
|
||||
- [App-V 5.0 Coexistence and Migration](http://technet.microsoft.com/windows/jj835811.aspx)
|
||||
|
||||
## <a href="" id="converting--previous-version--packages-using-the-package-converter-"></a>Converting “previous-version” packages using the package converter
|
||||
|
||||
|
||||
Before migrating a package, created using App- 4.6 SP2 or earlier, to App-V, review the following requirements:
|
||||
|
||||
- You must convert the package to the **.appv** file format.
|
||||
|
||||
- The Package Converter supports only the direct conversion of packages that were created by using App-V 4.5 and later. To use the package converter on a package that was created using a previous version, you must use an App-V 4.5 or later version of the sequencer to upgrade the package, and then you can perform the package conversion.
|
||||
|
||||
For more information about using the package converter to convert a package, see [How to Convert a Package Created in a Previous Version of App-V](appv-convert-a-package-created-in-a-previous-version-of-appv.md). After you convert the file, you can deploy it to target computers that run the App-V client.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,72 @@
|
||||
---
|
||||
title: Planning for the App-V Sequencer and Client Deployment (Windows 10)
|
||||
description: Planning for the App-V Sequencer and Client Deployment
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# Planning for the App-V Sequencer and Client Deployment
|
||||
|
||||
|
||||
Before you can use App-V, you must install the App-V Sequencer, enable the App-V client, and optionally the App-V shared content store. The following sections address planning for these installations.
|
||||
|
||||
## Planning for App-V Sequencer deployment
|
||||
|
||||
|
||||
App-V uses a process called sequencing to create virtualized applications and application packages. Sequencing requires the use of a computer that runs the App-V Sequencer.
|
||||
|
||||
> [!NOTE]
|
||||
> For information about the new functionality of App-V sequencer, see the **Sequencer Improvements** section of [About App-V](appv-about-appv.md).
|
||||
|
||||
|
||||
The computer that runs the App-V sequencer must meet the minimum system requirements. For a list of these requirements, see [App-V Supported Configurations](appv-supported-configurations.md).
|
||||
|
||||
Ideally, you should install the sequencer on a computer running as a virtual machine. This enables you to more easily revert the computer running the sequencer to a “clean” state before sequencing another application. When you install the sequencer using a virtual machine, you should perform the following steps:
|
||||
|
||||
1. Install all associated sequencer prerequisites.
|
||||
|
||||
2. Install the sequencer.
|
||||
|
||||
3. Take a “snapshot” of the environment.
|
||||
|
||||
> [!IMPORTANT]
|
||||
>You should have your corporate security team review and approve the sequencing process plan. For security reasons, you should keep the sequencer operations in a lab that is separate from the production environment. The separation arrangement can be as simple or as comprehensive as necessary, based on your business requirements. The sequencing computers must be able to connect to the corporate network to copy finished packages to the production servers. However, because the sequencing computers are typically operated without antivirus protection, they must not be on the corporate network unprotected. For example, you might be able to operate behind a firewall or on an isolated network segment. You might also be able to use virtual machines that are configured to share an isolated virtual network. Follow your corporate security policies to safely address these concerns.
|
||||
|
||||
|
||||
## Planning for App-V client deployment
|
||||
|
||||
In Windows 10, version 1607, the App-V client is included with the operating system. For more info, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
|
||||
|
||||
For a list of the client minimum requirements see [App-V Prerequisites](appv-prerequisites.md).
|
||||
|
||||
|
||||
## Planning for the App-V Shared Content Store (SCS)
|
||||
|
||||
The App-V Shared Content Store mode allows the computer running the App-V client to run virtualized applications and none of the package contents is saved on the computer running the App-V client. Virtual applications are streamed to target computers only when requested by the client.
|
||||
|
||||
The following list displays some of the benefits of using the App-V Shared Content Store:
|
||||
|
||||
- Reduced app-to-app and multi-user application conflicts and hence a reduced need for regression testing
|
||||
|
||||
- Accelerated application deployment by reduction of deployment risk
|
||||
|
||||
- Simplified profile management
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Other resources for the App-V deployment
|
||||
|
||||
- [Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
|
||||
## Related topics
|
||||
|
||||
- [How to Install the Sequencer](appv-install-the-sequencer.md)
|
||||
|
||||
- [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)
|
||||
|
||||
- [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)
|
||||
303
windows/manage/appv-planning-for-using-appv-with-office.md
Normal file
303
windows/manage/appv-planning-for-using-appv-with-office.md
Normal file
@ -0,0 +1,303 @@
|
||||
---
|
||||
title: Planning for Using App-V with Office (Windows 10)
|
||||
description: Planning for Using App-V with Office
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Planning for Using App-V with Office
|
||||
|
||||
Use the following information to plan how to deploy Office by using Microsoft Application Virtualization (App-V). This article includes:
|
||||
|
||||
- [App-V support for Language Packs](#bkmk-lang-pack)
|
||||
|
||||
- [Supported versions of Microsoft Office](#bkmk-office-vers-supp-appv)
|
||||
|
||||
- [Planning for using App-V with coexisting versions of Office](#bkmk-plan-coexisting)
|
||||
|
||||
- [How Office integrates with Windows when you deploy use App-V to deploy Office](#bkmk-office-integration-win)
|
||||
|
||||
## <a href="" id="bkmk-lang-pack"></a>App-V support for Language Packs
|
||||
|
||||
You can use the App-V Sequencer to create plug-in packages for Language Packs, Language Interface Packs, Proofing Tools and ScreenTip Languages. You can then include the plug-in packages in a Connection Group, along with the Office 2013 package that you create by using the Office Deployment Toolkit. The Office applications and the plug-in Language Packs interact seamlessly in the same connection group, just like any other packages that are grouped together in a connection group.
|
||||
|
||||
**Note**
|
||||
Microsoft Visio and Microsoft Project do not provide support for the Thai Language Pack.
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-office-vers-supp-appv"></a>Supported versions of Microsoft Office
|
||||
|
||||
|
||||
The following table lists the versions of Microsoft Office that App-V supports, methods of Office package creation, supported licensing, and supported deployments.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="20%" />
|
||||
<col width="20%" />
|
||||
<col width="20%" />
|
||||
<col width="20%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Supported Office Version</th>
|
||||
<th align="left">Package Creation</th>
|
||||
<th align="left">Supported Licensing</th>
|
||||
<th align="left">Supported Deployments</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Office 365 ProPlus</p>
|
||||
<p>Also supported:</p>
|
||||
<ul>
|
||||
<li><p>Visio Pro for Office 365</p></li>
|
||||
<li><p>Project Pro for Office 365</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p>Office Deployment Tool</p></td>
|
||||
<td align="left"><p>Subscription</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Desktop</p></li>
|
||||
<li><p>Personal VDI</p></li>
|
||||
<li><p>Pooled VDI</p></li>
|
||||
<li><p>RDS</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Office Professional Plus 2013</p>
|
||||
<p>Also supported:</p>
|
||||
<ul>
|
||||
<li><p>Visio Professional 2013</p></li>
|
||||
<li><p>Project Professional 2013</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p>Office Deployment Tool</p></td>
|
||||
<td align="left"><p>Volume Licensing</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Desktop</p></li>
|
||||
<li><p>Personal VDI</p></li>
|
||||
<li><p>Pooled VDI</p></li>
|
||||
<li><p>RDS</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-plan-coexisting"></a>Planning for using App-V with coexisting versions of Office
|
||||
|
||||
|
||||
You can install more than one version of Microsoft Office side by side on the same computer by using “Microsoft Office coexistence.” You can implement Office coexistence with combinations of all major versions of Office and with installation methods, as applicable, by using the Windows Installer-based (MSi) version of Office, Click-to-Run, and App-V. However, using Office coexistence is not recommended by Microsoft.
|
||||
|
||||
Microsoft’s recommended best practice is to avoid Office coexistence completely to prevent compatibility issues. However, when you are migrating to a newer version of Office, issues occasionally arise that can’t be resolved immediately, so you can temporarily implement coexistence to help facilitate a faster migration to the latest product version. Using Office coexistence on a long-term basis is never recommended, and your organization should have a plan to fully transition in the immediate future.
|
||||
|
||||
### Before you implement Office coexistence
|
||||
|
||||
Before implementing Office coexistence, review the following Office documentation. Choose the article that corresponds to the newest version of Office for which you plan to implement coexistence.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Office version</th>
|
||||
<th align="left">Link to guidance</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Office 2013</p></td>
|
||||
<td align="left"><p>[Information about how to use Office 2013 suites and programs (MSI deployment) on a computer that is running another version of Office](http://support.microsoft.com/kb/2784668)</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Office 2010</p></td>
|
||||
<td align="left"><p>[Information about how to use Office 2010 suites and programs on a computer that is running another version of Office](http://support.microsoft.com/kb/2121447)</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
The Office documentation provides extensive guidance on coexistence for Windows Installer-based (MSi) and Click-to-Run installations of Office. This App-V topic on coexistence supplements the Office guidance with information that is more specific to App-V deployments.
|
||||
|
||||
### Supported Office coexistence scenarios
|
||||
|
||||
The following tables summarize the supported coexistence scenarios. They are organized according to the version and deployment method you’re starting with and the version and deployment method you are migrating to. Be sure to fully test all coexistence solutions before deploying them to a production audience.
|
||||
|
||||
**Note**
|
||||
Microsoft does not support the use of multiple versions of Office in Windows Server environments that have the Remote Desktop Session Host role service enabled. To run Office coexistence scenarios, you must disable this role service.
|
||||
|
||||
|
||||
|
||||
### Windows integrations & Office coexistence
|
||||
|
||||
The Windows Installer-based and Click-to-Run Office installation methods integrate with certain points of the underlying Windows operating system. When you use coexistence, common operating system integrations between two Office versions can conflict, causing compatibility and user experience issues. With App-V, you can sequence certain versions of Office to exclude integrations, thereby “isolating” them from the operating system.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left"></th>
|
||||
<th align="left">Mode in which App-V can sequence this version of Office</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>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
Microsoft recommends that you deploy 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
|
||||
|
||||
The following sections describe some issues that you might encounter when using App-V to implement coexistence with Office.
|
||||
|
||||
### Limitations common to Windows Installer-based/Click-to-Run and App-V Office coexistence scenarios
|
||||
|
||||
The following limitations can occur when you install the following versions of Office on the same computer:
|
||||
|
||||
- Office 2010 by using the Windows Installer-based version
|
||||
|
||||
- Office 2013 by using App-V
|
||||
|
||||
After you publish Office 2013 by using App-V side by side with an earlier version of the Windows Installer-based Office 2010 might also cause the Windows Installer to start. This is because the Windows Installer-based or Click-to-Run version of Office 2010 is trying to automatically register itself to the computer.
|
||||
|
||||
To bypass the auto-registration operation for native Word 2010, follow these steps:
|
||||
|
||||
1. Exit Word 2010.
|
||||
|
||||
2. Start the Registry Editor by doing the following:
|
||||
|
||||
- In Windows 7: Click **Start**, type **regedit** in the Start Search box, and then press Enter.
|
||||
|
||||
- In Windows 8.1 or Windows 10, type **regedit** press Enter on the Start page and then press Enter.
|
||||
|
||||
If you are prompted for an administrator password or for a confirmation, type the password, or click **Continue**.
|
||||
|
||||
3. Locate and then select the following registry subkey:
|
||||
|
||||
``` syntax
|
||||
HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Word\Options
|
||||
```
|
||||
|
||||
4. On the **Edit** menu, click **New**, and then click **DWORD Value**.
|
||||
|
||||
5. Type **NoReReg**, and then press Enter.
|
||||
|
||||
6. Right-click **NoReReg** and then click **Modify**.
|
||||
|
||||
7. In the **Valuedata** box, type **1**, and then click **OK**.
|
||||
|
||||
8. On the File menu, click **Exit** to close Registry Editor.
|
||||
|
||||
## <a href="" id="bkmk-office-integration-win"></a>How Office integrates with Windows when you use App-V to deploy Office
|
||||
|
||||
|
||||
When you deploy Office 2013 by using App-V, Office is fully integrated with the operating system, which provides end users with the same features and functionality as Office has when it is deployed without App-V.
|
||||
|
||||
The Office 2013 App-V package supports the following integration points with the Windows operating system:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Extension Point</th>
|
||||
<th align="left">Description</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>
|
||||
</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 Lync and Outlook</p></td>
|
||||
<td align="left"><p>Firewall Exception for 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 [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
@ -0,0 +1,28 @@
|
||||
---
|
||||
title: Planning to Deploy App-V with an Electronic Software Distribution System (Windows 10)
|
||||
description: Planning to Deploy App-V with an Electronic Software Distribution System
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# Planning to Deploy App-V with an electronic software distribution system
|
||||
|
||||
If you are using an electronic software distribution system to deploy App-V packages, review the following planning considerations. For information about using System Center Configuration Manager to deploy App-V, see [Introduction to Application Management in Configuration Manager](http://go.microsoft.com/fwlink/?LinkId=281816).
|
||||
|
||||
Review the following component and architecture requirements options that apply when you use an ESD to deploy App-V packages:
|
||||
|
||||
| Deployment requirement or option | Description |
|
||||
| - | - |
|
||||
| The App-V Management server, Management database, and Publishing server are not required. | These functions are handled by the implemented ESD solution. |
|
||||
| You can deploy the App-V Reporting server and Reporting database side by side with the ESD. | The side-by-side deployment lets you to collect data and generate reports.<br/>If you enable the App-V client to send report information, and you are not using the App-V Reporting server, the reporting data is stored in associated .xml files. |
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Planning to deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
74
windows/manage/appv-planning-to-deploy-appv.md
Normal file
74
windows/manage/appv-planning-to-deploy-appv.md
Normal file
@ -0,0 +1,74 @@
|
||||
---
|
||||
title: Planning to Deploy App-V (Windows 10)
|
||||
description: Planning to Deploy App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Planning to Deploy App-V
|
||||
|
||||
You should consider a number of different deployment configurations and prerequisites before you create your deployment plan for App-V. This section includes information that can help you gather the information that you must have to formulate a deployment plan that best meets your business requirements.
|
||||
|
||||
## App-V supported configurations
|
||||
|
||||
Describes the minimum hardware and operating system requirements for each App-V components. For information about software prerequisites that you must install before you install App-V, see [App-V Prerequisites](appv-prerequisites.md).
|
||||
|
||||
[App-V Supported Configurations](appv-supported-configurations.md)
|
||||
|
||||
## App-V capacity planning
|
||||
|
||||
Describes the available options for scaling your App-V deployment.
|
||||
|
||||
[App-V Capacity Planning](appv-capacity-planning.md)
|
||||
|
||||
## Planning for high availability with App-V
|
||||
|
||||
Describes the available options for ensuring high availability of App-V databases and services.
|
||||
|
||||
[Planning for High Availability with App-V](appv-planning-for-high-availability-with-appv.md)
|
||||
|
||||
## Planning to Deploy App-V with an Electronic Software Distribution System
|
||||
|
||||
Describes the options and requirements for deploying App-V with an electronic software distribution system.
|
||||
|
||||
[Planning to Deploy App-V with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md)
|
||||
|
||||
## Planning for the App-V Server deployment
|
||||
|
||||
Describes the planning considerations for the App-V Server components and their functions.
|
||||
|
||||
[Planning for the App-V Server Deployment](appv-planning-for-appv-server-deployment.md)
|
||||
|
||||
## Planning for the App-V Sequencer and Client deployment
|
||||
|
||||
Describes the planning considerations for the App-V Client and for the Sequencer software, which you use to create virtual applications and application packages.
|
||||
|
||||
[Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md)
|
||||
|
||||
## Planning for migrating from a previous version of App-V
|
||||
|
||||
Describes the recommended path for migrating from previous versions of App-V, while ensuring that existing server configurations, packages and clients continue to work in your new App-V environment.
|
||||
|
||||
[Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md)
|
||||
|
||||
## Planning for using App-V with Office
|
||||
|
||||
Describes the requirements for using App-V with Office and explains the supported scenarios, including information about coexisting versions of Office.
|
||||
|
||||
[Planning for Using App-V with Office](appv-planning-for-using-appv-with-office.md)
|
||||
|
||||
## Planning to use folder redirection with App-V
|
||||
|
||||
Explains how folder redirection works with App-V.
|
||||
|
||||
[Planning to Use Folder Redirection with App-V](appv-planning-folder-redirection-with-appv.md)
|
||||
|
||||
## Other Resources for App-V Planning
|
||||
|
||||
- [Planning for App-V](appv-planning-for-appv.md)
|
||||
|
||||
- [Performance Guidance for Application Virtualization](appv-performance-guidance.md)
|
||||
33
windows/manage/appv-preparing-your-environment.md
Normal file
33
windows/manage/appv-preparing-your-environment.md
Normal file
@ -0,0 +1,33 @@
|
||||
---
|
||||
title: Preparing Your Environment for App-V (Windows 10)
|
||||
description: Preparing Your Environment for App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# Preparing Your Environment for App-V
|
||||
|
||||
There are a number of different deployment configurations and prerequisites that you must consider before you create your deployment plan for Microsoft Application Virtualization (App-V). This section includes information that can help you gather the information that you must have to formulate a deployment plan that best meets your business requirements.
|
||||
|
||||
## App-V prerequisites
|
||||
|
||||
- [App-V Prerequisites](appv-prerequisites.md)
|
||||
|
||||
Lists the prerequisite software that you must install before installing App-V.
|
||||
|
||||
## App-V security considerations
|
||||
|
||||
- [App-V Security Considerations](appv-security-considerations.md)
|
||||
|
||||
Describes accounts, groups, log files, and other considerations for securing your App-V environment.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Other resources for App-V planning
|
||||
|
||||
- [Planning for App-V](appv-planning-for-appv.md)
|
||||
658
windows/manage/appv-prerequisites.md
Normal file
658
windows/manage/appv-prerequisites.md
Normal file
@ -0,0 +1,658 @@
|
||||
---
|
||||
title: App-V Prerequisites (Windows 10)
|
||||
description: App-V Prerequisites
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# App-V Prerequisites
|
||||
|
||||
|
||||
Before installing App-V, ensure that you have installed all of the following required prerequisite software.
|
||||
|
||||
For a list of supported operating systems and hardware requirements for the App-V Server, Sequencer, and Client, see [App-V Supported Configurations](appv-supported-configurations.md).
|
||||
|
||||
## Summary of software preinstalled on each operating system
|
||||
|
||||
|
||||
The following table indicates the software that is already installed for different operating systems.
|
||||
|
||||
<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 of the 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 of the 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 2012</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>The prerequisite software is not already installed. You must install it 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.
|
||||
|
||||
### What to know before you start
|
||||
|
||||
<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>
|
||||
|
||||
|
||||
|
||||
### Management server prerequisite software
|
||||
|
||||
<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.
|
||||
|
||||
### Management server database prerequisite software
|
||||
|
||||
The Management database is required only if you are using the App-V Management server.
|
||||
|
||||
<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 is based on the assumption 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
|
||||
|
||||
<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 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="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">Format to use for the URL</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
|
||||
|
||||
<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
|
||||
|
||||
The Reporting database is required only if you are using the App-V Reporting server.
|
||||
|
||||
<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 is based on the assumption 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>Machine account on which the Reporting server is deployed.</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>
|
||||
|
||||
|
||||
|
||||
## App-V client prerequisite software
|
||||
|
||||
|
||||
Install the following prerequisite software for the App-V client.
|
||||
|
||||
> [!NOTE]
|
||||
> This is not required on Windows 10, version 1607.
|
||||
|
||||
<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 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>
|
||||
<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>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Remote Desktop Services client prerequisite software
|
||||
|
||||
|
||||
Install the following prerequisite software for the App-V Remote Desktop Services client.
|
||||
|
||||
<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 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>
|
||||
<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>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Sequencer prerequisite software
|
||||
|
||||
|
||||
**What to know before installing the prerequisites:**
|
||||
|
||||
- Best practice: The computer that runs the Sequencer should have the same hardware and software configurations as the computers that will run the virtual applications.
|
||||
|
||||
- The sequencing process is resource intensive, so make sure that the computer that runs the Sequencer has plenty of memory, a fast processor, and a fast hard drive. The system requirements of locally installed applications cannot exceed those of the Sequencer. For more information, see [App-V Supported Configurations](appv-supported-configurations.md).
|
||||
|
||||
<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>
|
||||
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Planning for App-V](appv-planning-for-appv.md)
|
||||
- [App-V Supported Configurations](appv-supported-configurations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
39
windows/manage/appv-publish-a-connection-group.md
Normal file
39
windows/manage/appv-publish-a-connection-group.md
Normal file
@ -0,0 +1,39 @@
|
||||
---
|
||||
title: How to Publish a Connection Group (Windows 10)
|
||||
description: How to Publish a Connection Group
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Publish a Connection Group
|
||||
|
||||
|
||||
After you create a connection group, you must publish it to computers that run the App-V client.
|
||||
|
||||
**To publish a connection group**
|
||||
|
||||
1. Open the App-V Management Console, and select **CONNECTION GROUPS**.
|
||||
|
||||
2. Right-click the connection group to be published, and select **publish**.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
[Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,56 @@
|
||||
---
|
||||
title: How to Publish a Package by Using the Management Console (Windows 10)
|
||||
description: How to Publish a Package by Using the Management Console
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Publish a Package by Using the Management Console
|
||||
|
||||
|
||||
Use the following procedure to publish an App-V package. Once you publish a package, computers that are running the App-V client can access and run the applications in that package.
|
||||
|
||||
**Note**
|
||||
The ability to enable only administrators to publish or unpublish packages (described below) is supported starting in App-V 5.0 SP3.
|
||||
|
||||
|
||||
|
||||
**To publish an App-V package**
|
||||
|
||||
1. In the App-V Management console. Click or right-click the name of the package to be published. Select **Publish**.
|
||||
|
||||
2. Review the **Status** column to verify that the package has been published and is now available. If the package is available, the status **published** is displayed.
|
||||
|
||||
If the package is not published successfully, the status **unpublished** is displayed, along with error text that explains why the package is not available.
|
||||
|
||||
**To enable only administrators to publish or unpublish packages**
|
||||
|
||||
1. Navigate to the following Group Policy Object node:
|
||||
|
||||
**Computer Configuration > Policies > Administrative Templates > System > App-V > Publishing**.
|
||||
|
||||
2. Enable the **Require publish as administrator** Group Policy setting.
|
||||
|
||||
To alternatively use PowerShell to set this item, see [How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs).
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
[How to Configure Access to Packages by Using the Management Console](appv-configure-access-to-packages-with-the-management-console.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,51 @@
|
||||
---
|
||||
title: How to Register and Unregister a Publishing Server by Using the Management Console (Windows 10)
|
||||
description: How to Register and Unregister a Publishing Server by Using the Management Console
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Register and Unregister a Publishing Server by Using the Management Console
|
||||
|
||||
|
||||
You can register and unregister publishing servers that will synchronize with the App-V management server. You can also see the last attempt that the publishing server made to synchronize the information with the management server.
|
||||
|
||||
Use the following procedure to register or unregister a publishing server.
|
||||
|
||||
**To register a publishing server using the Management Console**
|
||||
|
||||
1. Connect to the Management Console and select **Servers**. For more information about how to connect to the Management Console, see [How to Connect to the Management Console](appv-connect-to-the-management-console.md).
|
||||
|
||||
2. A list of publishing servers that already synchronize with the management server is displayed. Click Register New Server to register a new server.
|
||||
|
||||
3. Type a computer name of a domain joined computer on the **Server Name** line, to specify a name for the server. You should also include a domain name, for example, **MyDomain\\TestServer**. Click **Check**.
|
||||
|
||||
4. Select the computer and click **Add** to add the computer to the list of servers. The new server will be displayed in the list.
|
||||
|
||||
**To unregister a publishing server using the Management Console**
|
||||
|
||||
1. Connect to the Management Console and select **Servers**. For more information about how to connect to the Management Console, see [How to Connect to the Management Console](appv-connect-to-the-management-console.md).
|
||||
|
||||
2. A list of publishing servers that synchronize with the management server is displayed.
|
||||
|
||||
3. To unregister the server, right-click the computer name and select the computer name and select **unregister server**.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
162
windows/manage/appv-release-notes-for-appv-for-windows.md
Normal file
162
windows/manage/appv-release-notes-for-appv-for-windows.md
Normal file
@ -0,0 +1,162 @@
|
||||
---
|
||||
title: Release Notes for App-V (Windows 10)
|
||||
description: Release Notes for App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Release Notes for App-V
|
||||
|
||||
|
||||
The following are known issues in Microsoft Application Virtualization (App-V).
|
||||
|
||||
## Error occurs during publishing refresh between App-V 5.0 SP3 Management Server and App-V Client on Windows 10
|
||||
|
||||
|
||||
An error is generated during publishing refresh when synchronizing packages from the App-V 5.0 SP3 management server to an App-V client on Windows 10 . This error occurs because the App-V 5.0 SP3 server does not understand the Windows 10 operating system that is specified in the publishing URL. The issue is fixed for App-V publishing server, but is not backported to versions of App-V 5.0 SP3 or earlier.
|
||||
|
||||
**Workaround**: Upgrade the App-V 5.0 Management server to the App-V Management server for Windows 10 Clients.
|
||||
|
||||
## Custom configurations do not get applied for packages that will be published globally if they are set using the App-V Server
|
||||
|
||||
|
||||
If you assign a package to an AD group that contains machine accounts and apply a custom configuration to that group using the App-V Server, the custom configuration will not be applied to those machines. The App-V Client will publish packages assigned to a machine account globally. However, it stores custom configuration files per user in each user’s profile. Globally published packages will not have access to this custom configuration.
|
||||
|
||||
**Workaround**: Do one of the following:
|
||||
|
||||
- Assign the package to groups containing only user accounts. This will ensure that the package’s custom configuration will be stored in each user’s profile and will be applied correctly.
|
||||
|
||||
- Create a custom deployment configuration file and apply it to the package on the client using the Add-AppvClientPackage cmdlet with the –DynamicDeploymentConfiguration parameter. See [About App-V Dynamic Configuration](appv-dynamic-configuration.md) for more information.
|
||||
|
||||
- Create a new package with the custom configuration using the App-V Sequencer.
|
||||
|
||||
## Server files not deleted after new App-V Server installation
|
||||
|
||||
|
||||
If you uninstall the App-V 5.0 SP1 Server and then install the App-V Server, the installation fails, the wrong version of the Management server is installed, and an error message is returned. The issue occurs because the Server files are not being deleted when you uninstall App-V 5.0 SP1, so the installation process does an upgrade instead of a new installation.
|
||||
|
||||
**Workaround**: Delete this registry key before you start installing App-V:
|
||||
|
||||
Under HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall, locate and delete the installation GUID key that contains the DWORD value "DisplayName" with value data "Microsoft Application Virtualization (App-V) Server". This is the only key that should be deleted.
|
||||
|
||||
## File type associations added manually are not saved correctly
|
||||
|
||||
|
||||
File type associations added to an application package manually using the Shortcuts and FTAs tab at the end of the application upgrade wizard are not saved correctly. They will not be available to the App-V Client or to the Sequencer when updating the saved package again.
|
||||
|
||||
**Workaround**: To add a file type association, open the package for modification and run the update wizard. During the Installation step, add the new file type association through the operating system. The sequencer will detect the new association in the system registry and add it to the package’s virtual registry, where it will be available to the client.
|
||||
|
||||
## When streaming packages in Shared Content Store (SCS) mode to a client that is also managed with AppLocker, additional data is written to the local disk.
|
||||
|
||||
|
||||
To decrease the amount of data written to a client’s local disk, you can enable SCS mode on the App-V Client to stream the contents of a package on demand. However, if AppLocker manages an application within the package, some data might be written to the client’s local disk that would not otherwise be written.
|
||||
|
||||
**Workaround**: None
|
||||
|
||||
## In the Management Console Add Package dialog box, the Browse button is not available when using Chrome or Firefox
|
||||
|
||||
|
||||
On the Packages page of the Management Console, if you click **Add or Upgrade** in the lower-right corner, the **Add Package** dialog box appears. If you are accessing the Management Console using Chrome or Firefox as your browser, you will not be able to browse to the location of the package.
|
||||
|
||||
**Workaround**: Type or copy and paste the path to the package into the **Add Package** input field. If the Management Console has access to this path, you will be able to add the package. If the package is on a network share, you can browse to the location using File Explorer by doing these steps:
|
||||
|
||||
1. While pressing **Shift**, right-click on the package file
|
||||
|
||||
2. Select **Copy as path**
|
||||
|
||||
3. Paste the path into the **Add Package** dialog box input field
|
||||
|
||||
## <a href="" id="upgrading-app-v-management-server-to-5-1-sometimes-fails-with-the-message--a-database-error-occurred-"></a>Upgrading App-V Management Server to 5.1 sometimes fails with the message “A database error occurred”
|
||||
|
||||
|
||||
If you install the App-V 5.0 SP1 Management Server, and then try to upgrade to App-V Server when multiple connection groups are configured and enabled, the following error is displayed: “A database error occurred. Reason: 'Invalid column name 'PackageOptional'. Invalid column name 'VersionOptional'.”
|
||||
|
||||
**Workaround**: Run this command on your SQL database:
|
||||
|
||||
`ALTER TABLE AppVManagement.dbo.PackageGroupMembers ADD PackageOptional bit NOT NULL DEFAULT 0, VersionOptional bit NOT NULL DEFAULT 0`
|
||||
|
||||
where “AppVManagement” is the name of the database.
|
||||
|
||||
## Users cannot open a package in a user-published connection group if you add or remove an optional package
|
||||
|
||||
|
||||
In environments that are running the RDS Client or that have multiple concurrent users per computer, logged-in users cannot open applications in packages that are in a user-published connection group if an optional package is added to or removed from the connection group.
|
||||
|
||||
**Workaround**: Have users log out and then log back in.
|
||||
|
||||
## Error message is erroneously displayed when the connection group is published only to the user
|
||||
|
||||
|
||||
When you run Repair-AppvClientConnectionGroup, the following error is displayed, even when the connection group is published only to the user: “Internal App-V Integration error: Package not integrated for the user. Please ensure that the package is added to the machine and published to the user.”
|
||||
|
||||
**Workaround**: Do one of the following:
|
||||
|
||||
- Publish all packages in a connection group.
|
||||
|
||||
The problem arises when the connection group being repaired has packages that are missing or not available to the user (that is, not published globally or to the user). However, the repair will work if all of the connection group’s packages are available, so ensure that all packages are published.
|
||||
|
||||
- Repair packages individually using the Repair-AppvClientPackage command rather than the Repair-AppvClientConnectionGroup command.
|
||||
|
||||
Determine which packages are available to users and then run the Repair-AppvClientPackage command once for each package. Use PowerShell cmdlets to do the following:
|
||||
|
||||
1. Get all the packages in a connection group.
|
||||
|
||||
2. Check to see if each package is currently published.
|
||||
|
||||
3. If the package is currently published, run Repair-AppvClientPackage on that package.
|
||||
|
||||
## Icons not displayed properly in Sequencer
|
||||
|
||||
|
||||
Icons in the Shortcuts and File Type Associations tab are not displayed correctly when modifying a package in the App-V Sequencer. This problem occurs when the size of the icons are not 16x16 or 32x32.
|
||||
|
||||
**Workaround**: Only use icons that are 16x16 or 32x32.
|
||||
|
||||
## InsertVersionInfo.sql script no longer required for the Management Database
|
||||
|
||||
|
||||
The InsertVersionInfo.sql script is not required for versions of the App-V management database later than App-V 5.0 SP3.
|
||||
|
||||
The Permissions.sql script should be updated according to **Step 2** in [KB article 3031340](https://support.microsoft.com/kb/3031340).
|
||||
|
||||
**Important**
|
||||
**Step 1** is not required for versions of App-V later than App-V 5.0 SP3.
|
||||
|
||||
|
||||
|
||||
## Microsoft Visual Studio 2012 not supported
|
||||
|
||||
|
||||
App-V does not support Visual Studio 2012.
|
||||
|
||||
**Workaround**: None
|
||||
|
||||
## Application filename restrictions for App-V Sequencer
|
||||
|
||||
|
||||
The App-V Sequencer cannot sequence applications with filenames matching "CO_<x>" where x is any numeral. Error 0x8007139F will be generated.
|
||||
|
||||
**Workaround**: Use a different filename
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[About App-V](appv-about-appv.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
322
windows/manage/appv-reporting.md
Normal file
322
windows/manage/appv-reporting.md
Normal file
@ -0,0 +1,322 @@
|
||||
---
|
||||
title: About App-V Reporting (Windows 10)
|
||||
description: About App-V Reporting
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# About App-V Reporting
|
||||
|
||||
|
||||
Microsoft Application Virtualization (App-V) includes a built-in reporting feature that helps you collect information about computers running the App-V client as well as information about virtual application package usage. You can use this information to generate reports from a centralized database.
|
||||
|
||||
## <a href="" id="---------app-v-5-1-reporting-overview"></a> App-V Reporting Overview
|
||||
|
||||
|
||||
The following list displays the end–to-end high-level workflow for reporting in App-V.
|
||||
|
||||
1. The App-V Reporting server has the following prerequisites:
|
||||
|
||||
- Internet Information Service (IIS) web server role
|
||||
|
||||
- Windows Authentication role (under **IIS / Security**)
|
||||
|
||||
- SQL Server installed and running with SQL Server Reporting Services (SSRS)
|
||||
|
||||
To confirm SQL Server Reporting Services is running, view `http://localhost/Reports` in a web browser as administrator on the server that will host App-V Reporting. The SQL Server Reporting Services Home page should display.
|
||||
|
||||
2. Install the App-V reporting server and associated database. For more information about installing the reporting server see [How to install the Reporting Server on a Standalone Computer and Connect it to the Database](appv-install-the-reporting-server-on-a-standalone-computer.md). Configure the time when the computer running the App-V client should send data to the reporting server.
|
||||
|
||||
3. If you are not using an electronic software distribution system such as Configuration Manager to view reports then you can define reports in SQL Server Reporting Service. Download predefined appvshort Reports from the Download Center at <http://go.microsoft.com/fwlink/?LinkId=397255>.
|
||||
|
||||
**Note**
|
||||
If you are using the Configuration Manager integration with App-V, most reports are generated from Configuration Manager rather than from App-V.
|
||||
|
||||
|
||||
|
||||
4. After importing the App-V PowerShell module using `Import-Module AppvClient` as administrator, enable the App-V client. This sample PowerShell cmdlet enables App-V reporting:
|
||||
|
||||
``` syntax
|
||||
Set-AppvClientConfiguration –reportingserverurl <url>:<port> -reportingenabled 1 – ReportingStartTime <0-23> - ReportingRandomDelay <#min>
|
||||
```
|
||||
|
||||
To immediately send App-V report data, run `Send-AppvClientReport` on the App-V client.
|
||||
|
||||
For more information about installing the App-V client with reporting enabled see [About Client Configuration Settings](appv-client-configuration-settings.md). To administer App-V Reporting with Windows PowerShell, see [How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md).
|
||||
|
||||
5. After the reporting server receives the data from the App-V client it sends the data to the reporting database. When the database receives and processes the client data, a successful reply is sent to the reporting server and then a notification is sent to the App-V client.
|
||||
|
||||
6. When the App-V client receives the success notification, it empties the data cache to conserve space.
|
||||
|
||||
**Note**
|
||||
By default the cache is cleared after the server confirms receipt of data. You can manually configure the client to save the data cache.
|
||||
|
||||
|
||||
|
||||
If the App-V client device does not receive a success notification from the server, it retains data in the cache and tries to resend data at the next configured interval. Clients continue to collect data and add it to the cache.
|
||||
|
||||
### <a href="" id="-------------app-v-5-1-reporting-server-frequently-asked-questions"></a> App-V reporting server frequently asked questions
|
||||
|
||||
The following table displays answers to common questions about App-V reporting
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Question</th>
|
||||
<th align="left">More Information</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>What is the frequency that reporting information is sent to the reporting database?</p></td>
|
||||
<td align="left"><p>The frequency depends on how the reporting task is configured on the computer running the App-V client. You must configure the frequency / interval for sending the reporting data. App-V Reporting is not enabled by default.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>What information is stored in the reporting server database?</p></td>
|
||||
<td align="left"><p>The following list displays what is stored in the reporting database:</p>
|
||||
<ul>
|
||||
<li><p>The operating system running on the computer running the App-V client: host name, version, service pack, type - client/server, processor architecture.</p></li>
|
||||
<li><p>App-V Client information: version.</p></li>
|
||||
<li><p>Published package list: GUID, version GUID, name.</p></li>
|
||||
<li><p>Application usage information: name, version, streaming server, user (domain\alias), package version GUID, launch status and time, shutdown time.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>What is the average volume of information that is sent to the reporting server?</p></td>
|
||||
<td align="left"><p>It depends. The following list displays the three sets of the data sent to the reporting server:</p>
|
||||
<ol>
|
||||
<li><p>Operating system, and App-V client information. ~150 Bytes, every time this data is sent.</p></li>
|
||||
<li><p>Published package list. ~7 KB for 30 packages. This is sent only when the package list is updated with a publishing refresh, which is done infrequently; if there is no change, this information is not sent.</p></li>
|
||||
<li><p>Virtual application usage information – about 0.25KB per event. Opening and closing count as one event if both occur before sending the information. When sending using a scheduled task, only the data since the last successful upload is sent to the server. If sending manually through the PowerShell cmdlet, there is an optional argument that controls if the data needs to be re-sent next time around – that argument is <strong>DeleteOnSuccess</strong>.</p>
|
||||
<p></p>
|
||||
<p>So for example, if twenty applications are opened and closed and reporting information is scheduled to be sent daily, the typical daily traffic should be about 0.15KB + 20 x 0.25KB, or about 5KB/user</p></li>
|
||||
</ol></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Can reporting be scheduled?</p></td>
|
||||
<td align="left"><p>Yes. Besides manually sending reporting using PowerShell Cmdlets (<strong>Send-AppvClientReport</strong>), the task can be scheduled so it will happen automatically. There are two ways to schedule the reporting:</p>
|
||||
<ol>
|
||||
<li><p>Using PowerShell cmdlets - <strong>Set-AppvClientConfiguration</strong>. For example:</p>
|
||||
<p>Set-AppvClientConfiguration -ReportingEnabled 1 - ReportingServerURL http://any.com/appv-reporting</p>
|
||||
<p></p>
|
||||
<p>For a complete list of client configuration settings see [About Client Configuration Settings](appv-client-configuration-settings.md) and look for the following entries: <strong>ReportingEnabled</strong>, <strong>ReportingServerURL</strong>, <strong>ReportingDataCacheLimit</strong>, <strong>ReportingDataBlockSize</strong>, <strong>ReportingStartTime</strong>, <strong>ReportingRandomDelay</strong>, <strong>ReportingInterval</strong>.</p>
|
||||
<p></p></li>
|
||||
<li><p>By using Group Policy. If distributed using the domain controller, the settings are the same as previously listed.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>Group Policy settings override local settings configured using PowerShell.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
</div></li>
|
||||
</ol></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## <a href="" id="---------app-v-5-1-client-reporting"></a> App-V Client Reporting
|
||||
|
||||
|
||||
To use App-V reporting you must install and configure the App-V client. After the client has been installed, use the **Set-AppVClientConfiguration** PowerShell cmdlet or the **ADMX Template** to configure reporting. The reporting feature cmdlets are available by using the following link and are prefaced by **Reporting**. For a complete list of client configuration settings see [About Client Configuration Settings](appv-client-configuration-settings.md). The following section provides examples of App-V client reporting configuration using PowerShell.
|
||||
|
||||
### Configuring App-V Client reporting using PowerShell
|
||||
|
||||
The following examples show how PowerShell parameters can configure the reporting features of the App-V client.
|
||||
|
||||
**Note**
|
||||
The following configuration task can also be configured using Group Policy settings in the App-V ADMX template. For more information about using the ADMX template, see [How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md).
|
||||
|
||||
|
||||
|
||||
**To enable reporting and to initiate data collection on the computer running the App-V client**:
|
||||
|
||||
`Set-AppVClientConfiguration –ReportingEnabled 1`
|
||||
|
||||
**To configure the client to automatically send data to a specific reporting server**:
|
||||
|
||||
``` syntax
|
||||
Set-AppVClientConfiguration –ReportingServerURL http://MyReportingServer:MyPort/ -ReportingStartTime 20 -ReportingInterval 1 -ReportingRandomDelay 30
|
||||
```
|
||||
|
||||
`-ReportingInterval 1 -ReportingRandomDelay 30`
|
||||
|
||||
This example configures the client to automatically send the reporting data to the reporting server URL **http://MyReportingServer:MyPort/**. Additionally, the reporting data will be sent daily between 8:00 and 8:30 PM, depending on the random delay generated for the session.
|
||||
|
||||
**To limit the size of the data cache on the client**:
|
||||
|
||||
`Set-AppvClientConfiguration –ReportingDataCacheLimit 100`
|
||||
|
||||
Configures the maximum size of the reporting cache on the computer running the App-V client to 100 MB. If the cache limit is reached before the data is sent to the server, then the log rolls over and data will be overwritten as necessary.
|
||||
|
||||
**To configure the data block size transmitted across the network between the client and the server**:
|
||||
|
||||
`Set-AppvClientConfiguration –ReportingDataBlockSize 10240`
|
||||
|
||||
Specifies the maximum data block that the client sends to 10240 MB.
|
||||
|
||||
### Types of data collected
|
||||
|
||||
The following table displays the types of information you can collect by using App-V reporting.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Client Information</th>
|
||||
<th align="left">Package Information</th>
|
||||
<th align="left">Application Usage</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Host Name</p></td>
|
||||
<td align="left"><p>Package Name</p></td>
|
||||
<td align="left"><p>Start and End Times</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V Client Version</p></td>
|
||||
<td align="left"><p>Package Version</p></td>
|
||||
<td align="left"><p>Run Status</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Processor Architecture</p></td>
|
||||
<td align="left"><p>Package Source</p></td>
|
||||
<td align="left"><p>Shutdown State</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Operating System Version</p></td>
|
||||
<td align="left"><p>Percent Cached</p></td>
|
||||
<td align="left"><p>Application Name</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Service Pack Level</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>Application Version</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Operating System Type</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>Username</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>Connection Group</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
The client collects and saves this data in an **.xml** format. The data cache is hidden by default and requires administrator rights to open the XML file.
|
||||
|
||||
### Sending data to the server
|
||||
|
||||
You can configure the computer that is running the App-V client to automatically send data to the specified reporting server. To specify the server use the **Set-AppvClientConfiguration** cmdlet with the following settings:
|
||||
|
||||
- ReportingEnabled
|
||||
|
||||
- ReportingServerURL
|
||||
|
||||
- ReportingStartTime
|
||||
|
||||
- ReportingInterval
|
||||
|
||||
- ReportingRandomDelay
|
||||
|
||||
After you configure the previous settings, you must create a scheduled task. The scheduled task will contact the server specified by the **ReportingServerURL** setting and will initiate the transfer. If you want to manually send data outside of the scheduled times, use the following PowerShell cmdlet:
|
||||
|
||||
`Send-AppVClientReport –URL http://MyReportingServer:MyPort/ -DeleteOnSuccess`
|
||||
|
||||
If the reporting server has been previously configured, then the **–URL** parameter can be omitted. Alternatively, if the data should be sent to an alternate location, specify a different URL to override the configured **ReportingServerURL** for this data collection.
|
||||
|
||||
The **-DeleteOnSuccess** parameter indicates that if the transfer is successful, then the data cache is cleared. If this is not specified, then the cache will not be cleared.
|
||||
|
||||
### Manual Data Collection
|
||||
|
||||
You can also use the **Send-AppVClientReport** cmdlet to manually collect data. This solution is helpful with or without an existing reporting server. The following list displays information about collecting data with or without a reporting server.
|
||||
|
||||
<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 send the data to the specified location with 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:
|
||||
|
||||
- **Microsoft SQL Server Reporting Services (SSRS)** - Microsoft SQL Server Reporting Services is available with Microsoft SQL Server. SSRS is not installed when you install the App-V reporting server. It must be deployed separately to generate the associated reports.
|
||||
|
||||
Use the following link for more information about using [Microsoft SQL Server Reporting Services](http://go.microsoft.com/fwlink/?LinkId=285596).
|
||||
|
||||
- **Scripting** – You can generate reports by scripting directly against the App-V reporting database. For example:
|
||||
|
||||
**Stored Procedure:**
|
||||
|
||||
**spProcessClientReport** is scheduled to run at midnight or 12:00 AM.
|
||||
|
||||
To run the Microsoft SQL Server Scheduled Stored procedure, the Microsoft SQL Server Agent must be running. You should ensure that the Microsoft SQL Server Agent is set to **AutoStart**. For more information see [Autostart SQL Server Agent (SQL Server Management Studio)](http://go.microsoft.com/fwlink/?LinkId=287045).
|
||||
|
||||
The stored procedure is also created when using the App-V database scripts.
|
||||
|
||||
You should also ensure that the reporting server web service’s **Maximum Concurrent Connections** is set to a value that the server will be able to manage without impacting availability. The recommended number of **Maximum Concurrent Connections** for the **Reporting Web Service** is **10,000**.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
|
||||
[How to install the Reporting Server on a Standalone Computer and Connect it to the Database](appv-install-the-reporting-server-on-a-standalone-computer.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,190 @@
|
||||
---
|
||||
title: Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications (Windows 10)
|
||||
description: Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications
|
||||
|
||||
|
||||
You can run a locally installed application in a virtual environment, alongside applications that have been virtualized by using Microsoft Application Virtualization (App-V). You might want to do this if you:
|
||||
|
||||
- Want to install and run an application locally on client computers, but want to virtualize and run specific plug-ins that work with that local application.
|
||||
|
||||
- Are troubleshooting an App-V client package and want to open a local application within the App-V virtual environment.
|
||||
|
||||
Use any of the following methods to open a local application inside the App-V virtual environment:
|
||||
|
||||
- [RunVirtual registry key](#bkmk-runvirtual-regkey)
|
||||
|
||||
- [Get-AppvClientPackage PowerShell cmdlet](#bkmk-get-appvclientpackage-posh)
|
||||
|
||||
- [Command line switch /appvpid:<PID>](#bkmk-cl-switch-appvpid)
|
||||
|
||||
- [Command line hook switch /appvve:<GUID>](#bkmk-cl-hook-switch-appvve)
|
||||
|
||||
Each method accomplishes essentially the same task, but some methods may be better suited for some applications than others, depending on whether the virtualized application is already running.
|
||||
|
||||
## <a href="" id="bkmk-runvirtual-regkey"></a>RunVirtual registry key
|
||||
|
||||
|
||||
To add a locally installed application to a package or to a connection group’s virtual environment, you add a subkey to the `RunVirtual` registry key in the Registry Editor, as described in the following sections.
|
||||
|
||||
There is no Group Policy setting available to manage this registry key, so you have to use System Center Configuration Manager or another electronic software distribution (ESD) system, or manually edit the registry.
|
||||
|
||||
### <a href="" id="bkmk-"></a>Supported methods of publishing packages when using RunVirtual
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">App-V version</th>
|
||||
<th align="left">Supported publishing methods</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 5.0 SP3 and App-V</p></td>
|
||||
<td align="left"><p>Published globally or to the user</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 5.0 through App-V 5.0 SP2</p></td>
|
||||
<td align="left"><p>Published globally only</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Steps to create the subkey
|
||||
|
||||
1. Using the information in the following table, create a new registry key using the name of the executable file, for example, **MyApp.exe**.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Package publishing method</th>
|
||||
<th align="left">Where to create the registry key</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Published globally</p></td>
|
||||
<td align="left"><p>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual</p>
|
||||
<p><strong>Example</strong>: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual\MyApp.exe</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Published to the user</p></td>
|
||||
<td align="left"><p>HKEY_CURRENT_USER\SOFTWARE\Microsoft\AppV\Client\RunVirtual</p>
|
||||
<p><strong>Example</strong>: HKEY_CURRENT_USER \SOFTWARE\Microsoft\AppV\Client\RunVirtual\MyApp.exe</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Connection group can contain:</p>
|
||||
<ul>
|
||||
<li><p>Packages that are published just globally or just to the user</p></li>
|
||||
<li><p>Packages that are published globally and to the user</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p>Either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER key, but all of the following must be true:</p>
|
||||
<ul>
|
||||
<li><p>If you want to include multiple packages in the virtual environment, you must include them in an enabled connection group.</p></li>
|
||||
<li><p>Create only one subkey for one of the packages in the connection group. If, for example, you have one package that is published globally, and another package that is published to the user, you create a subkey for either of these packages, but not both. Although you create a subkey for only one of the packages, all of the packages in the connection group, plus the local application, will be available in the virtual environment.</p></li>
|
||||
<li><p>The key under which you create the subkey must match the publishing method you used for the package.</p>
|
||||
<p>For example, if you published the package to the user, you must create the subkey under <code>HKEY_CURRENT_USER\SOFTWARE\Microsoft\AppV\Client\RunVirtual</code>.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
2. Set the new registry subkey’s value to the PackageId and VersionId of the package, separating the values with an underscore.
|
||||
|
||||
**Syntax**: <PackageId>\_<VersionId>
|
||||
|
||||
**Example**: 4c909996-afc9-4352-b606-0b74542a09c1\_be463724-Oct1-48f1-8604-c4bd7ca92fa
|
||||
|
||||
The application in the previous example would produce a registry export file (.reg file) like the following:
|
||||
|
||||
``` syntax
|
||||
Windows Registry Editor Version 5.00
|
||||
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual]
|
||||
@=""
|
||||
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual\MyApp.exe]
|
||||
@="aaaaaaaa-bbbb-cccc-dddd-eeeeeeee_11111111-2222-3333-4444-555555555
|
||||
```
|
||||
|
||||
## <a href="" id="bkmk-get-appvclientpackage-posh"></a>Get-AppvClientPackage PowerShell cmdlet
|
||||
|
||||
|
||||
You can use the **Start-AppVVirtualProcess** cmdlet to retrieve the package name and then start a process within the specified package's virtual environment. This method lets you launch any command within the context of an App-V package, regardless of whether the package is currently running.
|
||||
|
||||
Use the following example syntax, and substitute the name of your package for **<Package>**:
|
||||
|
||||
`$AppVName = Get-AppvClientPackage <Package>`
|
||||
|
||||
`Start-AppvVirtualProcess -AppvClientObject $AppVName cmd.exe`
|
||||
|
||||
If you don’t know the exact name of your package, you can use the command line **Get-AppvClientPackage \*executable\***, where **executable** is the name of the application, for example: Get-AppvClientPackage \*Word\*.
|
||||
|
||||
## <a href="" id="bkmk-cl-switch-appvpid"></a>Command line switch /appvpid:<PID>
|
||||
|
||||
|
||||
You can apply the **/appvpid:<PID>** switch to any command, which enables that command to run within a virtual process that you select by specifying its process ID (PID). Using this method launches the new executable in the same App-V environment as an executable that is already running.
|
||||
|
||||
Example: `cmd.exe /appvpid:8108`
|
||||
|
||||
To find the process ID (PID) of your App-V process, run the command **tasklist.exe** from an elevated command prompt.
|
||||
|
||||
## <a href="" id="bkmk-cl-hook-switch-appvve"></a>Command line hook switch /appvve:<GUID>
|
||||
|
||||
|
||||
This switch lets you run a local command within the virtual environment of an App-V package. Unlike the **/appvid** switch, where the virtual environment must already be running, this switch enables you to start the virtual environment.
|
||||
|
||||
Syntax: `cmd.exe /appvve:<PACKAGEGUID_VERSIONGUID>`
|
||||
|
||||
Example: `cmd.exe /appvve:aaaaaaaa-bbbb-cccc-dddd-eeeeeeee_11111111-2222-3333-4444-55555555`
|
||||
|
||||
To get the package GUID and version GUID of your application, run the **Get-AppvClientPackage** cmdlet. Concatenate the **/appvve** switch with the following:
|
||||
|
||||
- A colon
|
||||
|
||||
- Package GUID of the desired package
|
||||
|
||||
- An underscore
|
||||
|
||||
- Version ID of the desired package
|
||||
|
||||
If you don’t know the exact name of your package, use the command line **Get-AppvClientPackage \*executable\***, where **executable** is the name of the application, for example: Get-AppvClientPackage \*Word\*.
|
||||
|
||||
This method lets you launch any command within the context of an App-V package, regardless of whether the package is currently running.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Technical Reference for App-V](appv-technical-reference.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
145
windows/manage/appv-security-considerations.md
Normal file
145
windows/manage/appv-security-considerations.md
Normal file
@ -0,0 +1,145 @@
|
||||
---
|
||||
title: App-V Security Considerations (Windows 10)
|
||||
description: App-V Security Considerations
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# App-V Security Considerations
|
||||
|
||||
|
||||
This topic contains a brief overview of the accounts and groups, log files, and other security-related considerations for Microsoft Application Virtualization (App-V).
|
||||
|
||||
**Important**
|
||||
App-V is not a security product and does not provide any guarantees for a secure environment.
|
||||
|
||||
|
||||
|
||||
## PackageStoreAccessControl (PSAC) feature has been deprecated
|
||||
|
||||
|
||||
Effective as of June, 2014, the PackageStoreAccessControl (PSAC) feature that was introduced in Microsoft Application Virtualization (App-V) 5.0 Service Pack 2 (SP2) has been deprecated in both single-user and multi-user environments.
|
||||
|
||||
## General security considerations
|
||||
|
||||
|
||||
**Understand the security risks.** The most serious risk to App-V is that its functionality could be hijacked by an unauthorized user who could then reconfigure key data on App-V clients. The loss of App-V functionality for a short period of time due to a denial-of-service attack would not generally have a catastrophic impact.
|
||||
|
||||
**Physically secure your computers**. Security is incomplete without physical security. Anyone with physical access to an App-V server could potentially attack the entire client base. Any potential physical attacks must be considered high risk and mitigated appropriately. App-V servers should be stored in a physically secure server room with controlled access. Secure these computers when administrators are not physically present by having the operating system lock the computer, or by using a secured screen saver.
|
||||
|
||||
**Apply the most recent security updates to all computers**. To stay informed about the latest updates for operating systems, Microsoft SQL Server, and App-V, subscribe to the Security Notification service (<http://go.microsoft.com/fwlink/p/?LinkId=28819>).
|
||||
|
||||
**Use strong passwords or pass phrases**. Always use strong passwords with 15 or more characters for all App-V and App-V administrator accounts. Never use blank passwords. For more information about password concepts, see the “Account Passwords and Policies” white paper on TechNet (<http://go.microsoft.com/fwlink/p/?LinkId=30009>).
|
||||
|
||||
## Accounts and groups in App-V
|
||||
|
||||
|
||||
A best practice for user account management is to create domain global groups and add user accounts to them. Then, add the domain global accounts to the necessary App-V local groups on the App-V servers.
|
||||
|
||||
**Note**
|
||||
App-V client computer accounts that need to connect to the publishing server must be part of the publishing server’s **Users** local group. By default, all computers in the domain are part of the **Authorized Users** group, which is part of the **Users** local group.
|
||||
|
||||
|
||||
|
||||
### <a href="" id="-------------app-v-5-1-server-security"></a> App-V server security
|
||||
|
||||
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.
|
||||
|
||||
<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>There is no method to create the group using the management console after you have completed the installation.</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 the 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 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 the 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.
|
||||
|
||||
**Note**
|
||||
In previous versions of App-V, package share was referred to as content share.
|
||||
|
||||
|
||||
|
||||
- Registering publishing servers with Management Server - A publishing server must be registered with the Management server. For example, it must be added to the database, so that the Publishing server machine accounts are able to call into the Management service API.
|
||||
|
||||
### <a href="" id="-------------app-v-5-1-package-security"></a> App-V package security
|
||||
|
||||
The following will help you plan how to ensure that virtualized packages are secure.
|
||||
|
||||
- If an application installer applies an access control list (ACL) to a file or directory, then that ACL is not persisted in the package. When the package is deployed, if the file or directory is modified by a user it will either inherit the ACL in the **%userprofile%** or inherit the ACL of the target computer’s directory. The former case occurs if the file or directory does not exist in a virtual file system location; the latter case occurs if the file or directory exists in a virtual file system location, for example **%windir%**.
|
||||
|
||||
## <a href="" id="---------app-v-5-1-log-files"></a> App-V log files
|
||||
|
||||
|
||||
During App-V Setup, setup log files are created in the **%temp%** folder of the installing user.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Preparing Your Environment for App-V](appv-preparing-your-environment.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
240
windows/manage/appv-sequence-a-new-application.md
Normal file
240
windows/manage/appv-sequence-a-new-application.md
Normal file
@ -0,0 +1,240 @@
|
||||
---
|
||||
title: How to Sequence a New Application with App-V (Windows 10)
|
||||
description: How to Sequence a New Application with App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Sequence a New Application with App-V
|
||||
|
||||
In Windows 10, version 1607, the App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
|
||||
|
||||
**To review or do before you start sequencing**
|
||||
|
||||
1. Determine the type of virtualized application package you want to create:
|
||||
|
||||
| Application type | Description |
|
||||
| - | - |
|
||||
| Standard | Creates a package that contains an application or a suite of applications. This is the preferred option for most application types. |
|
||||
| Add-on or plug-in | Creates a package that extends the functionality of a standard application, for example, a plug-in for Microsoft Excel. Additionally, you can use plug-ins for natively installed applications, or for another package that is linked by using connection groups. |
|
||||
| Middleware | Creates a package that is required by a standard application, for example, Java. Middleware packages are used for linking to other packages by using connection groups. |
|
||||
|
||||
2. Copy all required installation files to the computer that is running the sequencer.
|
||||
|
||||
3. Make a backup image of your virtual environment before sequencing an application, and then revert to that image each time after you finish sequencing an application.
|
||||
|
||||
4. Review the following items:
|
||||
|
||||
- If an application installer changes the security access to a new or existing file or directory, those changes are not captured in the package.
|
||||
|
||||
- If short paths have been disabled for the virtualized package’s target volume, you must also sequence the package to a volume that was created and still has short-paths disabled. It cannot be the system volume.
|
||||
|
||||
> [!NOTE]
|
||||
> The App-V Sequencer cannot sequence applications with filenames matching "CO_<_x_>" where x is any numeral. Error 0x8007139F will be generated.
|
||||
|
||||
**To sequence a new standard application**
|
||||
|
||||
1. On the computer that runs the sequencer, click **All Programs**, and then click **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. In the sequencer, click **Create a New Virtual Application Package**. Select **Create Package (default)**, and then click **Next**.
|
||||
|
||||
3. On the **Prepare Computer** page, review the issues that could cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package.
|
||||
|
||||
4. On the **Type of Application** page, click the **Standard Application (default)** check box, and then click **Next**.
|
||||
|
||||
5. On the **Select Installer** page, click **Browse** and specify the installation file for the application.
|
||||
|
||||
> [!NOTE]
|
||||
> If the specified application installer modifies security access to a file or directory, existing or new, the associated changes will not be captured into the package.
|
||||
|
||||
|
||||
If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Perform a Custom Installation** check box, and then click **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.
|
||||
|
||||
Click **Next**.
|
||||
|
||||
7. On the **Installation** page, when the sequencer and application installer are ready you can proceed to install the application so that the sequencer can monitor the installation process.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> You should always install applications to a secure location and make sure no other users are logged on to the computer running the sequencer during monitoring.
|
||||
|
||||
|
||||
Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run** to locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**. Click **Next**.
|
||||
|
||||
8. On the **Installation** page, wait while the sequencer configures the virtualized application package.
|
||||
|
||||
9. On the **Configure Software** page, optionally run the programs contained in the package. This step allows you to complete any necessary license or configuration tasks before you deploy and run the package on target computers. To run all the programs at one time, select at least one program, and then click **Run All**. To run specific programs, select the program or programs, and then click **Run Selected**. Complete the required configuration tasks and then close the applications. You may need to wait several minutes for all programs to run.
|
||||
|
||||
> [!NOTE]
|
||||
> To run first-use tasks for any application that is not available in the list, open the application. The associated information will be captured during this step.
|
||||
|
||||
|
||||
Click **Next**.
|
||||
|
||||
10. On the **Installation Report** page, you can review information about the virtualized application package you have just sequenced. In **Additional Information**, double-click an event to obtain more detailed information. To proceed, click **Next**.
|
||||
|
||||
11. The **Customize** page is displayed. If you are finished installing and configuring the virtual application, select **Stop now** and skip to step 14 of this procedure. To perform either of the following customizations, select **Customize**.
|
||||
|
||||
- Prepare the virtual package for streaming. Streaming improves the experience when the virtual application package is run on target computers.
|
||||
|
||||
- Specify the operating systems that can run this package.
|
||||
|
||||
Click **Next**.
|
||||
|
||||
12. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. It can take several minutes for all the applications to run. After all applications have run, close each of the applications, and then click **Next**.
|
||||
|
||||
> [!NOTE]
|
||||
> If you do not open any applications during this step, the default streaming method is on-demand streaming delivery. This means applications will be downloaded bit by bit until it can be opened, and then depending on how the background loading is configured, will load the rest of the application.
|
||||
|
||||
|
||||
|
||||
13. On the **Target OS** page, specify the operating systems that can run this package. To allow all supported operating systems in your environment to run this package, select **Allow this package to run on any operating system**. To configure this package to run only on specific operating systems, select **Allow this package to run only on the following operating systems** and select the operating systems that can run this package. Click **Next**.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Make sure that the operating systems you specify here are supported by the application you are sequencing.
|
||||
|
||||
|
||||
14. 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. Click **Next**.
|
||||
|
||||
To save the package immediately, select **Save the package now** (default). Add optional **Comments** to be associated with the package. Comments 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 default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**.
|
||||
|
||||
15. The **Completion** page is displayed. Review the information in the **Virtual Application Package Report** pane as needed, then click **Close**. This information is also available in the **Report.xml** file that is located in the directory where the package was created.
|
||||
|
||||
The package is now available in the sequencer.
|
||||
|
||||
> [!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.
|
||||
|
||||
|
||||
|
||||
**To sequence an add-on or plug-in application**
|
||||
|
||||
> [!NOTE]
|
||||
>Before performing the following procedure, install the parent application locally on the computer that is running the sequencer. Or if you have the parent application virtualized, you can follow the steps in the add-on or plug-in workflow to unpack the parent application on the computer.
|
||||
|
||||
>For example, if you are sequencing a plug-in for Microsoft Excel, install Microsoft Excel locally on the computer that is running the sequencer. Also install the parent application in the same directory where the application is installed on target computers. If the plug-in or add-on is going to be used with an existing virtual application package, install the application on the same virtual application drive that was used when you created the parent virtual application package.
|
||||
|
||||
1. On the computer that runs the sequencer, click **All Programs**, and then Click **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. In the sequencer, click **Create a New Virtual Application Package**, select **Create Package (default)**, and then click **Next**.
|
||||
|
||||
3. On the **Prepare Computer** page, review the issues that might cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package.
|
||||
|
||||
|
||||
4. On the **Type of Application** page, select **Add-on or Plug-in**, and then click **Next**.
|
||||
|
||||
5. On the **Select Installer** page, click **Browse** and specify the installation file for the add-on or plug-in. If the add-on or plug-in 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 click **Next**.
|
||||
|
||||
6. On the **Install Primary** page, ensure that the primary application is installed on the computer that runs the sequencer. Alternatively, you can expand an existing package that has been saved locally on the computer that runs the sequencer. To do this, click **Expand Package**, and then select the package. After you have expanded or installed the parent program, select **I have installed the primary parent program**.
|
||||
|
||||
Click **Next**.
|
||||
|
||||
7. 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 will be displayed in the App-V 5.0 Management Console.
|
||||
|
||||
Click **Next**.
|
||||
|
||||
8. On the **Installation** page, when the sequencer and application installer are ready you can proceed to install the plug-in or add-in application so the sequencer can monitor the installation process. Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run** and locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**, and then click **Next**.
|
||||
|
||||
9. On the **Installation Report** page, you can review information about the virtual application package that you just sequenced. For a more detailed explanation about the information displayed in **Additional Information**, double-click the event. After you have reviewed the information, click **Next**.
|
||||
|
||||
10. The **Customize** page is displayed. If you are finished installing and configuring the virtual application, select **Stop now** and skip to step 12 of this procedure. To perform either of the following customizations, select **Customize**.
|
||||
|
||||
- Optimize how the package will run across a slow or unreliable network.
|
||||
|
||||
- Specify the operating systems that can run this package.
|
||||
|
||||
Click **Next**.
|
||||
|
||||
11. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. Streaming improves the experience when the virtual application package is run on target computers on high-latency networks. It can take several minutes for all the applications to run. After all applications have run, close each of the applications. You can also configure the package to be required to be fully downloaded before opening by selecting the **Force applications to be downloaded** check-box. Click **Next**.
|
||||
|
||||
> [!NOTE]
|
||||
> If necessary, you can stop an application from loading during this step. In the **Application Launch** dialog box, click **Stop** and select one of the check boxes: **Stop all applications** or **Stop this application only**.
|
||||
|
||||
|
||||
|
||||
12. On the **Target OS** page, specify the operating systems that can run this package. To allow 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 then select the operating systems that can run this package. Click **Next**.
|
||||
|
||||
13. 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. Click **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.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> 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, click **Browse** and specify the new location. Click **Create**.
|
||||
|
||||
**To sequence a middleware application**
|
||||
|
||||
1. On the computer that runs the sequencer, click **All Programs**, and then Click **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. In the sequencer, click **Create a New Virtual Application Package**, select **Create Package (default)**, and then click **Next**.
|
||||
|
||||
3. On the **Prepare Computer** page, review the issues that could cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you are required to disable virus scanning software, you should first scan the computer that runs the App-V 5.0 Sequencer in order to ensure that no unwanted or malicious files can be added to the package.
|
||||
|
||||
|
||||
4. On the **Type of Application** page, select **Middleware**, and then click **Next**.
|
||||
|
||||
5. On the **Select Installer** page, click **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 click **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 5.0 Management Console.
|
||||
|
||||
Click **Next**.
|
||||
|
||||
7. On the **Installation** page, when the sequencer and middleware application installer are ready you can proceed to install the application so that the sequencer can monitor the installation process. Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run**, to locate and run the additional installation files. When you are finished with the installation, select the **I am finished installing** check box, and then click **Next**.
|
||||
|
||||
8. On the **Installation** page, wait while the sequencer configures the virtual application package.
|
||||
|
||||
9. 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, click **Next**.
|
||||
|
||||
10. 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. Click **Next**.
|
||||
|
||||
11. 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. Click **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 default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**.
|
||||
|
||||
12. The **Completion** page is displayed. Review the information in the **Virtual Application Package Report** pane as needed, then click **Close**. This information is also available in the **Report.xml** file that is located in the directory specified in step 11 of this procedure.
|
||||
|
||||
The package is now available in the sequencer. To edit the package properties, click **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.
|
||||
|
||||
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Install the App-V Sequencer](appv-install-the-sequencer.md)
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
64
windows/manage/appv-sequence-a-package-with-powershell.md
Normal file
64
windows/manage/appv-sequence-a-package-with-powershell.md
Normal file
@ -0,0 +1,64 @@
|
||||
---
|
||||
title: How to sequence a package by using Windows PowerShell (Windows 10)
|
||||
description: How to sequence a package by using Windows PowerShell
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Sequence a Package by using Windows PowerShell
|
||||
|
||||
Use the following procedure to create a new App-V package using Windows PowerShell.
|
||||
|
||||
> [!NOTE]
|
||||
> Before you use this procedure you must copy the associated installer files to the computer running the sequencer and you have read and understand the sequencer section of [Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md).
|
||||
|
||||
|
||||
**To create a new virtual application by using Windows PowerShell**
|
||||
|
||||
1. Install the App-V sequencer. For more information about installing the sequencer see [How to Install the Sequencer](appv-install-the-sequencer.md).
|
||||
|
||||
2. Click **Start** and type **Windows PowerShell**. Right-click **Windows PowerShell**, and select **Run as Administrator**.
|
||||
|
||||
3. Using the Windows PowerShell console, type the following: **import-module appvsequencer**.
|
||||
|
||||
4. To create a package, use the **New-AppvSequencerPackage** cmdlet. The following parameters are required to create a package:
|
||||
|
||||
- **Name** - specifies the name of the package.
|
||||
|
||||
- **PrimaryVirtualApplicationDirectory** - specifies the path to the directory that will be used to install the application. This path must exist.
|
||||
|
||||
- **Installer** - specifies the path to the associated application installer.
|
||||
|
||||
- **Path** - specifies the output directory for the package.
|
||||
|
||||
For example:
|
||||
|
||||
```
|
||||
New-AppvSequencerPackage –Name <name of package> -PrimaryVirtualApplicationDirectory <path to the package root> -Installer <path to the installer executable> -OutputPath <directory of the output path>
|
||||
```
|
||||
|
||||
|
||||
Wait for the sequencer to create the package. Creating a package by using Windows PowerShell can take time. If the package was not created successfully, an error will be returned.
|
||||
|
||||
The following list displays additional optional parameters that can be used with **New-AppvSequencerPackage** cmdlet:
|
||||
|
||||
- AcceleratorFilePath – specifies the path to the accelerator .cab file to generate a package.
|
||||
|
||||
- InstalledFilesPath - specifies the path to where the local installed files of the application are saved.
|
||||
|
||||
- InstallMediaPath - specifies the path of the installation media
|
||||
|
||||
- TemplateFilePath - specifies the path to a template file if you want to customize the sequencing process.
|
||||
|
||||
- FullLoad - specifies that the package must be fully downloaded to the computer running the App-V before it can be opened.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md)
|
||||
657
windows/manage/appv-supported-configurations.md
Normal file
657
windows/manage/appv-supported-configurations.md
Normal file
@ -0,0 +1,657 @@
|
||||
---
|
||||
title: App-V Supported Configurations (Windows 10)
|
||||
description: App-V Supported Configurations
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# App-V Supported Configurations
|
||||
|
||||
|
||||
This topic specifies the requirements to install and run App-V in your environment.
|
||||
|
||||
## App-V Server system requirements
|
||||
|
||||
This section lists the operating system and hardware requirements for all of the App-V Server components.
|
||||
|
||||
### Unsupported App-V Server scenarios
|
||||
|
||||
The App-V Server does not support the following scenarios:
|
||||
|
||||
- Deployment to a computer that runs the Server Core installation option.
|
||||
|
||||
- Deployment to a computer that runs a previous version of App-V Server components. You can install App-V side by side with the App-V 4.5 Lightweight Streaming Server (LWS) server only. Deployment of App-V side by side with the App-V 4.5 Application Virtualization Management Service (HWS) server is not supported.
|
||||
|
||||
- Deployment to a computer that runs Microsoft SQL Server Express edition.
|
||||
|
||||
- Deployment to a domain controller.
|
||||
|
||||
- Short paths. If you plan to use a short path, you must create a new volume.
|
||||
|
||||
### Management server operating system requirements
|
||||
|
||||
The following table lists the operating systems that are supported for the App-V Management server installation.
|
||||
|
||||
|
||||
<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 2016</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 2012 R2</p></td>
|
||||
<td align="left"><p></p></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>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Deployment of the Management server role to a computer with Remote Desktop Services enabled is not supported.
|
||||
|
||||
|
||||
|
||||
### Management server hardware requirements
|
||||
|
||||
- Processor—1.4 GHz or faster, 64-bit (x64) processor
|
||||
|
||||
- RAM—1 GB RAM (64-bit)
|
||||
|
||||
- Disk space—200 MB available hard disk space, not including the content directory
|
||||
|
||||
### Management server database requirements
|
||||
|
||||
The following table lists the SQL Server versions that are supported for the App-V Management database installation.
|
||||
|
||||
<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 following table lists the operating systems that are supported for the App-V Publishing server installation.
|
||||
|
||||
<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 2016</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 2012 R2</p></td>
|
||||
<td align="left"><p></p></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>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Publishing server hardware requirements
|
||||
|
||||
App-V adds no additional requirements beyond those of Windows Server.
|
||||
|
||||
- Processor—1.4 GHz or faster, 64-bit (x64) processor
|
||||
|
||||
- RAM—2 GB RAM (64-bit)
|
||||
|
||||
- Disk space—200 MB available hard disk space, not including the content directory
|
||||
|
||||
### Reporting server operating system requirements
|
||||
|
||||
The following table lists the operating systems that are supported for the App-V Reporting server installation.
|
||||
|
||||
<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 2016</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 2012 R2</p></td>
|
||||
<td align="left"><p></p></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>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Reporting server hardware requirements
|
||||
|
||||
App-V adds no additional requirements beyond those of Windows Server.
|
||||
|
||||
- Processor—1.4 GHz or faster, 64-bit (x64) processor
|
||||
|
||||
- RAM—2 GB RAM (64-bit)
|
||||
|
||||
- Disk space—200 MB available hard disk space
|
||||
|
||||
### Reporting server database requirements
|
||||
|
||||
The following table lists the SQL Server versions that are supported for the App-V Reporting database installation.
|
||||
|
||||
<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 system requirements
|
||||
|
||||
|
||||
The following table lists the operating systems that are supported for the App-V client installation.
|
||||
|
||||
> [!NOTE]
|
||||
> App-V is included with Windows 10, version 1607 and later.
|
||||
|
||||
<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>Windows 10, version 1511</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>32-bit or 64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows 10, version 1507</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>Windows 8.1</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>32-bit or 64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows 8</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>Windows /p></td>
|
||||
<td align="left"><p>SP1</p></td>
|
||||
<td align="left"><p>32-bit or 64-bit</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
The following App-V client installation scenarios are not supported, except as noted:
|
||||
|
||||
- Computers that run Windows Server
|
||||
|
||||
- Computers that run App-V 4.6 SP1 or earlier versions
|
||||
|
||||
- The App-V Remote Desktop services client is supported only for RDS-enabled servers
|
||||
|
||||
### App-V client hardware requirements
|
||||
|
||||
The following list displays the supported hardware configuration for the App-V client installation.
|
||||
|
||||
- Processor— 1.4 GHz or faster 32-bit (x86) or 64-bit (x64) processor
|
||||
|
||||
- RAM— 1 GB (32-bit) or 2 GB (64-bit)
|
||||
|
||||
- Disk— 100 MB for installation, not including the disk space that is used by virtualized applications.
|
||||
|
||||
## Remote Desktop Services client system requirements
|
||||
|
||||
|
||||
The following table lists the operating systems that are supported for App-V Remote Desktop Services (RDS) client installation.
|
||||
|
||||
<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 2016</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 2012 R2</p></td>
|
||||
<td align="left"><p></p></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>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Remote Desktop Services client hardware requirements
|
||||
|
||||
App-V adds no additional requirements beyond those of Windows Server.
|
||||
|
||||
- Processor—1.4 GHz or faster, 64-bit (x64) processor
|
||||
|
||||
- RAM—2 GB RAM (64-bit)
|
||||
|
||||
- Disk space—200 MB available hard disk space
|
||||
|
||||
## Sequencer system requirements
|
||||
|
||||
|
||||
The following table lists the operating systems that are supported for the App-V Sequencer installation.
|
||||
|
||||
<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. App-V adds no additional hardware requirements.
|
||||
|
||||
## <a href="" id="bkmk-supp-ver-sccm"></a>Supported versions of System Center Configuration Manager
|
||||
|
||||
|
||||
The App-V client supports the following versions of System Center Configuration Manager:
|
||||
|
||||
- Microsoft System Center 2012 Configuration Manager
|
||||
|
||||
- System Center 2012 R2 Configuration Manager
|
||||
|
||||
- System Center 2012 R2 Configuration Manager SP1
|
||||
|
||||
The following App-V and System Center Configuration Manager version matrix shows all officially supported combinations of App-V and Configuration Manager.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">App-V Version</th>
|
||||
<th align="left">System Center Configuration Manager 2007</th>
|
||||
<th align="left">System Center 2012 Configuration Manager</th>
|
||||
<th align="left">System Center 2012 Configuration Manager SP1</th>
|
||||
<th align="left">System Center 2012 R2 Configuration Manager</th>
|
||||
<th align="left">System Center 2012 R2 Configuration Manager SP1</th>
|
||||
<th align="left">System Center 2012 Configuration Manager SP2</th>
|
||||
<th align="left">System Center Configuration Manager Version 1511</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.5</p></td>
|
||||
<td align="left"><p>R2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.5 CU1</p></td>
|
||||
<td align="left"><p>R2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.5 SP1</p></td>
|
||||
<td align="left"><p>R2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.5 SP2</p></td>
|
||||
<td align="left"><p>R2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6</p></td>
|
||||
<td align="left"><p>R2, SP1</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP1</p></td>
|
||||
<td align="left"><p>R2, R3, SP2</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP2</p></td>
|
||||
<td align="left"><p>R2, R3, SP2</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>R2, R3, SP2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 5.0</p></td>
|
||||
<td align="left"><p>MSI-Wrapper-Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 5.0 SP1</p></td>
|
||||
<td align="left"><p>MSI-Wrapper Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 5.0 SP2</p></td>
|
||||
<td align="left"><p>MSI-Wrapper Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>2012 SP1 CU4</p>
|
||||
<p>App-V 5.0 HF5 or later</p></td>
|
||||
<td align="left"><p>2012 R2 CU1</p>
|
||||
<p>App-V 5.0 HF5 or later</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>With App-V 5.0 SP2 HF5 or later</p></td>
|
||||
<td align="left"><p>With App-V 5.0 SP2 HF5 or later</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 5.0 SP2 HF4</p></td>
|
||||
<td align="left"><p>MSI-Wrapper Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>2012 SP1 CU4</p>
|
||||
<p>App-V 5.0 HF5 or later</p></td>
|
||||
<td align="left"><p>2012 R2 CU1</p>
|
||||
<p>App-V 5.0 HF5 or later</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Requires HF5 or later</p></td>
|
||||
<td align="left"><p>Requires HF5 or later</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 5.0 SP3</p></td>
|
||||
<td align="left"><p>MSI-Wrapper Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>2012 SP1 CU4</p></td>
|
||||
<td align="left"><p>2012 R2 CU1</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V</p></td>
|
||||
<td align="left"><p>MSI-Wrapper Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>2012 SP1 CU4</p></td>
|
||||
<td align="left"><p>2012 R2 CU1</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
For more information about how Configuration Manager integrates with App-V, see [Planning for App-V Integration with Configuration Manager](http://technet.microsoft.com/library/jj822982.aspx).
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
- [App-V Prerequisites](appv-prerequisites.md)
|
||||
45
windows/manage/appv-technical-reference.md
Normal file
45
windows/manage/appv-technical-reference.md
Normal file
@ -0,0 +1,45 @@
|
||||
---
|
||||
title: Technical Reference for App-V (Windows 10)
|
||||
description: Technical Reference for App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Technical Reference for App-V
|
||||
|
||||
|
||||
This section provides reference information related to managing App-V.
|
||||
|
||||
## In This Section
|
||||
|
||||
|
||||
- [Performance Guidance for Application Virtualization](appv-performance-guidance.md)
|
||||
|
||||
Provides strategy and context for a number of performance optimization practices. Not all practices will be applicable although they are supported and have been tested. Using all suggested practices that are applicable to your organization will provide the optimal end-user experience.
|
||||
|
||||
- [Application Publishing and Client Interaction](appv-application-publishing-and-client-interaction.md)
|
||||
|
||||
Describes how the following App-V client operations affect the local operating system: App-V files and data storage locations, package registry, package store behavior, roaming registry and data, client application lifecycle management, integration of App-V packages, dynamic configuration, side-by-side assemblies, and client logging.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Creating App-V 4.5 Databases Using SQL Scripting](https://technet.microsoft.com/en-us/itpro/mdop/solutions/creating-app-v-45-databases-using-sql-scripting)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,41 @@
|
||||
---
|
||||
title: How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console (Windows 10)
|
||||
description: How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console
|
||||
|
||||
|
||||
Use the following procedure to transfer the access and default package configurations to another version of a package by using the management console.
|
||||
|
||||
**To transfer access and configurations to another version of a package**
|
||||
|
||||
1. To view the package that you want to configure, open the App-V Management Console. Select the package to which you will transfer the new configuration, right-click the package and select **transfer default configuration from** or **transfer access and configurations from**, depending on the configuration that you want to transfer.
|
||||
|
||||
2. To transfer the configuration, in the **Select Previous Version** dialog box, select the package that contains the settings that you want to transfer, and then click **OK**.
|
||||
|
||||
If you select **transfer default configuration from**, then only the underlying dynamic deployment configuration will be transferred.
|
||||
|
||||
If you select **transfer access and configurations from**, then all access permissions, as well as the configuration settings, will be copied.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
92
windows/manage/appv-troubleshooting.md
Normal file
92
windows/manage/appv-troubleshooting.md
Normal file
@ -0,0 +1,92 @@
|
||||
---
|
||||
title: Troubleshooting App-V (Windows 10)
|
||||
description: Troubleshooting App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Troubleshooting App-V
|
||||
|
||||
|
||||
Troubleshooting content is not included in the Administrator’s Guide for this product. Instead, you can find troubleshooting information for this product on the [TechNet Wiki](http://go.microsoft.com/fwlink/p/?LinkId=224905).
|
||||
|
||||
## How to Find Troubleshooting Content
|
||||
|
||||
|
||||
You can use the following information to find troubleshooting or additional technical content for this product.
|
||||
|
||||
### Search the MDOP Documentation
|
||||
|
||||
The first step to find help content in the Administrator’s Guide is to search the MDOP documentation on TechNet.
|
||||
|
||||
After you search the MDOP documentation, your next step would be to search the troubleshooting information for the product in the TechNet Wiki.
|
||||
|
||||
**To search the MDOP product documentation**
|
||||
|
||||
1. Use a web browser to navigate to the [MDOP Information Experience](http://go.microsoft.com/fwlink/?LinkId=236032) TechNet home page.
|
||||
|
||||
2. Enter applicable search terms in the **Search TechNet with Bing** search box at the top of the MDOP Information Experience home page.
|
||||
|
||||
3. Review the search results for assistance.
|
||||
|
||||
**To search the TechNet Wiki**
|
||||
|
||||
1. Use a web browser to navigate to the [TechNet Wiki](http://go.microsoft.com/fwlink/p/?LinkId=224905) home page.
|
||||
|
||||
2. Enter applicable search terms in the **Search TechNet Wiki** search box on the TechNet Wiki home page.
|
||||
|
||||
3. Review the search results for assistance.
|
||||
|
||||
## How to Create a Troubleshooting Article
|
||||
|
||||
|
||||
If you have a troubleshooting tip or a best practice to share that is not already included in the MDOP OnlineHelp or TechNet Wiki, you can create your own TechNet Wiki articles.
|
||||
|
||||
**To create a TechNet Wiki troubleshooting or best practices article**
|
||||
|
||||
1. Use a web browser to navigate to the [TechNet Wiki](http://go.microsoft.com/fwlink/p/?LinkId=224905) home page.
|
||||
|
||||
2. Log in with your Windows Live ID.
|
||||
|
||||
3. Review the **Getting Started** section to learn the basics of the TechNet Wiki and its articles.
|
||||
|
||||
4. Select **Post an article >>** at the bottom of the **Getting Started** section.
|
||||
|
||||
5. On the Wiki article **Add Page** page, select **Insert Template** from the toolbar, select the troubleshooting article template (**Troubleshooting.html**), and then click **Insert**.
|
||||
|
||||
6. Be sure to give the article a descriptive title and then overwrite the template information as needed to create your troubleshooting or best practice article.
|
||||
|
||||
7. After you review your article, be sure to include a tag that is named **Troubleshooting** and another for the product name. This helps others to find your content.
|
||||
|
||||
8. Click **Save** to publish the article to the TechNet Wiki.
|
||||
|
||||
## Other resources for troubleshooting App-V
|
||||
|
||||
|
||||
- [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)
|
||||
|
||||
- [Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,105 @@
|
||||
---
|
||||
title: Upgrading to App-V for Windows 10 from an existing installation (Windows 10)
|
||||
description: Upgrading to App-V for Windows 10 from an existing installation
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# Upgrading to App-V for Windows 10 from an existing installation
|
||||
|
||||
If you’re already using App-V and you’re planning to upgrade user devices to Windows 10, you need to make only the following few adjustments to your existing environment to start using App-V for Windows 10.
|
||||
|
||||
1. [Upgrade user devices to Windows 10](#upgrade-user-devices-to-windows-10). Performing an in-place upgrade automatically installs the App-V client and migrates users’ App-V applications and settings.
|
||||
|
||||
2. [Verify that App-V applications and settings were migrated correctly](#verify-that-app-v-applications-and-settings-were-migrated-correctly).
|
||||
|
||||
3. [Enable the in-box App-V client](#enable-the-in-box-app-v-client).
|
||||
|
||||
4. [Configure the in-box App-V client to point to previously installed App-V server components](#configure-the-in-box-app-v-client-to-point-to-previously-installed-app-v-server-components).
|
||||
|
||||
5. [Verify that the in-box App-V client can receive and launch .appv packages](#verify-that-the-in-box-app-v-client-can-receive-and-launch-appv-packages).
|
||||
|
||||
These steps are explained in more detail below.
|
||||
|
||||
## Upgrade user devices to Windows 10
|
||||
|
||||
Performing an in-place upgrade automatically installs the App-V client and migrates users’ App-V applications and settings. See the [Windows 10 and Windows 10 Mobile document set](https://technet.microsoft.com/itpro/windows/index) for information about upgrading user devices to Windows 10.
|
||||
|
||||
## Verify that App-V applications and settings were migrated correctly
|
||||
|
||||
After upgrading a user device to Windows 10, it’s important to verify that App-V applications and settings were migrated correctly during the upgrade.
|
||||
|
||||
To verify that the user’s App-V application packages were migrated correctly, type `Get-AppvClientPackage` in Windows PowerShell.
|
||||
|
||||
To verify that the user’s App-V settings were migrated correctly, type `Get-AppvClientConfiguration` in Windows PowerShell.
|
||||
|
||||
## Enable the in-box App-V client
|
||||
|
||||
With Windows 10, the App-V client is installed automatically. You need to enable the client to allow user devices to access and run virtual applications. You can enable the client with the Group Policy editor or with Windows PowerShell.
|
||||
|
||||
**To enable the App-V client with Group Policy**:
|
||||
|
||||
1. Open the device’s **Local Group Policy Editor**.
|
||||
|
||||
2. Navigate to **Computer Configuration > Administrative Templates > System > App-V**.
|
||||
|
||||
3. Run **Enables App-V Client** and then select **Enabled** on the screen that appears.
|
||||
|
||||
4. Restart the device.
|
||||
|
||||
**To enable the App-V client with Windows PowerShell**:
|
||||
|
||||
1. Open Windows PowerShell.
|
||||
|
||||
2. Type `Enable-Appv` and press enter.
|
||||
|
||||
3. Restart the device.
|
||||
|
||||
4. To verify that the App-V client is enabled on the device, enter `AppvClientEnabled` or `Get-AppvStatus` in Windows PowerShell.
|
||||
|
||||
## Configure the in-box App-V client to point to previously installed App-V server components
|
||||
|
||||
Once you’ve enabled the in-box App-V client, you need to configure it to point to your existing App-V server components. You can configure the App-V client with Windows PowerShell cmdlets or with the device’s local Group Policy editor.
|
||||
|
||||
**To modify client settings to point to an existing App-V publishing server with Windows PowerShell**
|
||||
|
||||
Type the following cmdlet in a Windows PowerShell window:
|
||||
|
||||
`Add-AppvPublishingServer -Name AppVServer -URL http:// appvserver:2222`
|
||||
|
||||
**To modify client settings to point to an existing App-V publishing server with Group Policy**
|
||||
|
||||
1. Open the device’s **Local Group Policy Editor**.
|
||||
|
||||
2. Navigate to **Computer Configuration > Administrative Templates > System > App-V > Publishing**.
|
||||
|
||||
3. Enter your existing App-V publishing server’s details in **Options** and then click or press **Apply**.
|
||||
|
||||
<!-- For the following three items, we're looking for more detail from Chintan -->
|
||||
|
||||
Ensure newly added machine/ user is entitled to receive packages from the server configure in step #2.
|
||||
|
||||
Sync and verify packages and/or connection groups pushed by the App-V server function correctly.
|
||||
|
||||
Validate other package management commands (unpublish, remove etc.).
|
||||
|
||||
<!-- ++++++++++++++++++++++++++++++ -->
|
||||
|
||||
## Verify that the in-box App-V client can receive and launch .appv packages
|
||||
|
||||
1. Add and publish a package using the following Windows PowerShell cmdlets:
|
||||
|
||||
`Add-AppvClientPackage \\path\to\appv\package.appv | Publish-AppvClientPackage`
|
||||
|
||||
2. Launch the published package.
|
||||
|
||||
3. Unpublish an existing package use the following cmdlet:
|
||||
|
||||
`Unpublish-AppvClientPackage "ContosoApplication"`
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
91
windows/manage/appv-using-the-client-management-console.md
Normal file
91
windows/manage/appv-using-the-client-management-console.md
Normal file
@ -0,0 +1,91 @@
|
||||
---
|
||||
title: Using the App-V Client Management Console (Windows 10)
|
||||
description: Using the App-V Client Management Console
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Using the App-V Client Management Console
|
||||
|
||||
|
||||
This topic provides information about how you can configure and manage the Microsoft Application Virtualization (App-V) client.
|
||||
|
||||
## Modify App-V client configuration
|
||||
|
||||
|
||||
The App-V client has associated settings that can be configured to determine how the client will run in your environment. You can manage these settings on the computer that runs the client or by using PowerShell or Group Policy. For more information about how to modify the client using PowerShell or Group Policy configuration see, [How to Modify Client Configuration by Using PowerShell](appv-modify-client-configuration-with-powershell.md).
|
||||
|
||||
## <a href="" id="the-app-v-5-1-client-management-console-"></a>The App-V client management console
|
||||
|
||||
|
||||
You can obtain information about the App-V client or perform specific tasks by using the App-V client management console. Many of the tasks that you can perform in the client management console you can also perform by using PowerShell. The associated PowerShell cmdlets for each action are also displayed in the following table. For more information about how to use PowerShell, see [Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md).
|
||||
|
||||
The client management console contains the following described main tabs.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Tab</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Overview</p></td>
|
||||
<td align="left"><p>The <strong>Overview</strong> tab contains the following elements:</p>
|
||||
<ul>
|
||||
<li><p>Update – Use the <strong>Update</strong> tile to refresh a virtualized application or to receive a new virtualized package.</p>
|
||||
<p>The <strong>Last Refresh</strong> displays the current version of the virtualized package.</p></li>
|
||||
<li><p>Download all virtual applications – Use the <strong>Download</strong> tile to download all of the packages provisioned to the current user.</p>
|
||||
<p>(Associated PowerShell cmdlet: <strong>Mount-AppvClientPackage</strong>)</p>
|
||||
<p></p></li>
|
||||
<li><p>Work Offline – Use this tile to disallow all automatic and manual virtual application updates.</p>
|
||||
<p>(Associated PowerShell cmdlet: <strong>Set-AppvPublishServer –UserRefreshEnabled –GlobalRefreshEnabled</strong>)</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Virtual Apps</p></td>
|
||||
<td align="left"><p>The <strong>VIRTUAL APPS</strong> tab displays all of the packages that have been published to the user. You can also click a specific package and see all of the applications that are part of that package. This displays information about packages that are currently in use and how much of each package has been downloaded to the computer. You can also start and stop package downloads. Additionally, you can repair the user state. A repair will delete all user data that is associated with a package.</p>
|
||||
<p></p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App Connection Groups</p></td>
|
||||
<td align="left"><p>The <strong>APP CONNECTION GROUPS</strong> tab displays all of the connection groups that are available to the current user. Click a specific connection group to see all of the packages that are part of the selected group. This displays information about connection groups that are already in use and how much of the connection group contents have been downloaded to the computer. Additionally, you can start and stop connection group downloads. You can use this section to initiate a repair. A repair will remove all of the user state that is associated a connection group.</p>
|
||||
<p>(Associated PowerShell cmdlets: Download - <strong>Mount-AppvClientConnectionGroup</strong>. Repair -<strong>AppvClientConnectionGroup</strong>.)</p>
|
||||
<p></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
[How to Access the Client Management Console](appv-accessing-the-client-management-console.md)
|
||||
|
||||
[How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md)
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,45 @@
|
||||
---
|
||||
title: How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console (Windows 10)
|
||||
description: How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console
|
||||
|
||||
|
||||
Use the following procedure to view and configure default package extensions.
|
||||
|
||||
**To view and configure default virtual application extensions**
|
||||
|
||||
1. To view the package that you want to configure, open the App-V Management Console. Select the package that you want to configure, right-click the package name and select **edit default configuration**.
|
||||
|
||||
2. To view the applications contained in the specified package, in the **Default Configuration** pane, click **Applications**. To view the shortcuts for that package, click **Shortcuts**. To view the file type associations for that package, click **File Types**.
|
||||
|
||||
3. To enable the application extensions, select **ENABLE**.
|
||||
|
||||
To enable shortcuts, select **ENABLE SHORTCUTS**. To add a new shortcut for the selected application, right-click the application in the **SHORTCUTS** pane and select **Add new shortcut**. To remove a shortcut, right-click the application in the **SHORTCUTS** pane and select **Remove Shortcut**. To edit an existing shortcut, right-click the application and select **Edit Shortcut**.
|
||||
|
||||
4. To view any other application extensions, click **Advanced** and click **Export Configuration**. Type in a filename and click **Save**. You can view all application extensions associated with the package using the configuration file.
|
||||
|
||||
5. To edit other application extensions, modify the configuration file and click **Import and Overwrite this Configuration**. Select the modified file and click **Open**. In the dialog box, click **Overwrite** to complete the process.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
264
windows/manage/appv-viewing-appv-server-publishing-metadata.md
Normal file
264
windows/manage/appv-viewing-appv-server-publishing-metadata.md
Normal file
@ -0,0 +1,264 @@
|
||||
---
|
||||
title: Viewing App-V Server Publishing Metadata (Windows 10)
|
||||
description: Viewing App-V Server Publishing Metadata
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Viewing App-V Server Publishing Metadata
|
||||
|
||||
|
||||
Use this procedure to view publishing metadata, which can help you resolve publishing-related issues. You must be using the App-V Management server to use this procedure.
|
||||
|
||||
This article contains the following information:
|
||||
|
||||
- [App-V requirements for viewing publishing metadata](#bkmk-51-reqs-pub-meta)
|
||||
|
||||
- [Syntax to use for viewing publishing metadata](#bkmk-syntax-view-pub-meta)
|
||||
|
||||
- [Query values for client operating system and version](#bkmk-values-query-pub-meta)
|
||||
|
||||
- [Definition of publishing metadata](#bkmk-whatis-pub-metadata)
|
||||
|
||||
## <a href="" id="bkmk-51-reqs-pub-meta"></a>App-V requirements for viewing publishing metadata
|
||||
|
||||
|
||||
In App-V, you must provide the following values in the address when you query the App-V Publishing server for metadata:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Value</th>
|
||||
<th align="left">Additional details</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>ClientVersion</strong></p></td>
|
||||
<td align="left"><p>If you omit the <strong>ClientVersion</strong> parameter from the query, the metadata excludes the features that were new in App-V 5.0 SP3.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>ClientOS</strong></p></td>
|
||||
<td align="left"><p>You have to provide this value only if you select specific client operating systems when you sequence the package. If you select the default (all operating systems), do not specify this value in the query.</p>
|
||||
<p>If you omit the <strong>ClientOS</strong> parameter from the query, only the packages that were sequenced to support any operating system appear in the metadata.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-syntax-view-pub-meta"></a>Query syntax for viewing publishing metadata
|
||||
|
||||
|
||||
The following table provides the syntax and query examples.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="25%" />
|
||||
<col width="25%" />
|
||||
<col width="25%" />
|
||||
<col width="25%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Version of App-V</th>
|
||||
<th align="left">Query syntax</th>
|
||||
<th align="left">Parameter descriptions</th>
|
||||
<th align="left">Example</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 5.0 SP3 and App-V</p></td>
|
||||
<td align="left"><p><code>http://<PubServer>:<Publishing Port#>/?ClientVersion=<AppvClientVersion>&ClientOS=<OSStringValue></code></p></td>
|
||||
<td align="left"><table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Parameter</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><PubServer></p></td>
|
||||
<td align="left"><p>Name of the App-V Publishing server.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><Publishing Port#></p></td>
|
||||
<td align="left"><p>Port to the App-V Publishing server, which you defined when you configured the Publishing server.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>ClientVersion=<AppvClientVersion></p></td>
|
||||
<td align="left"><p>Version of the App-V client. Refer to the following table for the correct value to use.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>ClientOS=<OSStringValue></p></td>
|
||||
<td align="left"><p>Operating system of the computer that is running the App-V client. Refer to the following table for the correct value to use.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p> </p>
|
||||
<p>To get the name of the Publishing server and the port number (http://<PubServer>:<Publishing Port#>) from the App-V Client, look at the URL configuration of the <strong>Get-AppvPublishingServer</strong> PowerShell cmdlet.</p></td>
|
||||
<td align="left"><p><code>http://pubsvr01:2718/?clientversion=5.0.10066.0&clientos=WindowsClient_6.2_x64</code></p>
|
||||
<p>In the example:</p>
|
||||
<ul>
|
||||
<li><p>A Windows Server 2012 R2 named “pubsvr01” hosts the Publishing service.</p></li>
|
||||
<li><p>The Windows client is Windows 8.1 64-bit.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 5.0 through App-V 5.0 SP2</p></td>
|
||||
<td align="left"><p><code>http://<PubServer>:<Publishing Port#>/ </code></p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p><strong>ClientVersion</strong> and <strong>ClientOS</strong> are supported only in App-V 5.0 SP3 and App-V.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
</div></td>
|
||||
<td align="left"><p>See the information for App-V 5.0 SP3 and App-V.</p></td>
|
||||
<td align="left"><p><code>http://pubsvr01:2718</code></p>
|
||||
<p>In the example, A Windows Server 2012 R2 named “pubsvr01” hosts the Management and Publishing services.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-values-query-pub-meta"></a>Query values for client operating system and version
|
||||
|
||||
|
||||
In your publishing metadata query, enter the string values that correspond to the client operating system and version that you’re using.
|
||||
|
||||
<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">Architecture</th>
|
||||
<th align="left">Operating string string value</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows 10</p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
<td align="left"><p>WindowsClient_10.0_x64</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Windows 10</p></td>
|
||||
<td align="left"><p>32-bit</p></td>
|
||||
<td align="left"><p>WindowsClient_10.0_x86</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows 8.1</p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
<td align="left"><p>WindowsClient_6.2_x64</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Windows 8.1</p></td>
|
||||
<td align="left"><p>32-bit</p></td>
|
||||
<td align="left"><p>WindowsClient_6.2_x86</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows 8</p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
<td align="left"><p>WindowsClient_6.2_x64</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Windows 8</p></td>
|
||||
<td align="left"><p>32-bit</p></td>
|
||||
<td align="left"><p>WindowsClient_6.2_x86</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows Server 2012 R2</p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
<td align="left"><p>WindowsServer_6.2_x64</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Windows Server 2012 R2</p></td>
|
||||
<td align="left"><p>32-bit</p></td>
|
||||
<td align="left"><p>WindowsServer_6.2_x86</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows Server 2012</p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
<td align="left"><p>WindowsServer_6.2_x64</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Windows Server 2012</p></td>
|
||||
<td align="left"><p>32-bit</p></td>
|
||||
<td align="left"><p>WindowsServer_6.2_x86</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows 7</p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
<td align="left"><p>WindowsClient_6.1_x64</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Windows 7</p></td>
|
||||
<td align="left"><p>32-bit</p></td>
|
||||
<td align="left"><p>WindowsClient_6.1_x86</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows Server 2008 R2</p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
<td align="left"><p>WindowsServer_6.1_x64</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Windows Server 2008 R2</p></td>
|
||||
<td align="left"><p>32-bit</p></td>
|
||||
<td align="left"><p>WindowsServer_6.1_x86</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-whatis-pub-metadata"></a>Definition of publishing metadata
|
||||
|
||||
|
||||
When packages are published to a computer that is running the App-V client, metadata is sent to that computer indicating which packages and connection groups are being published. The App-V Client makes two separate requests for the following:
|
||||
|
||||
- Packages and connection groups that are entitled to the client computer.
|
||||
|
||||
- Packages and connection groups that are entitled to the current user.
|
||||
|
||||
The Publishing server communicates with the Management server to determine which packages and connection groups are available to the requester. The Publishing server must be registered with the Management server in order for the metadata to be generated.
|
||||
|
||||
You can view the metadata for each request in an Internet browser by using a query that is in the context of the specific user or computer.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Technical Reference for App-V](appv-technical-reference.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -16,7 +16,7 @@ author: brianlic-msft
|
||||
|
||||
- Windows 10
|
||||
- Windows 10 Mobile
|
||||
- Windows Server 2016 Technical Preview
|
||||
- Windows Server 2016
|
||||
|
||||
At Microsoft, we use Windows telemetry to inform our decisions and focus our efforts in providing the most robust, most valuable platform for your business and the people who count on Windows to enable them to be as productive as possible. Telemetry gives users a voice in the operating system’s development. This guide describes the importance of Windows telemetry and how we protect that data. Additionally, it differentiates between telemetry and functional data. It also describes the telemetry levels that Windows supports. Of course, you can choose how much telemetry is shared with Microsoft, and this guide demonstrates how.
|
||||
|
||||
@ -36,7 +36,7 @@ Use this article to make informed decisions about how you might configure teleme
|
||||
|
||||
## Overview
|
||||
|
||||
In previous versions of Windows and Windows Server, Microsoft used telemetry to check for updated or new Windows Defender signatures, check whether Windows Update installations were successful, gather reliability information through the Reliability Analysis Component (RAC), and gather reliability information through the Windows Customer Experience Improvement Program (CEIP) on Windows. In Windows 10 and Windows Server 2016 Technical Preview, you can control telemetry streams by using the Privacy option in Settings, Group Policy, or MDM.
|
||||
In previous versions of Windows and Windows Server, Microsoft used telemetry to check for updated or new Windows Defender signatures, check whether Windows Update installations were successful, gather reliability information through the Reliability Analysis Component (RAC), and gather reliability information through the Windows Customer Experience Improvement Program (CEIP) on Windows. In Windows 10 and Windows Server 2016, you can control telemetry streams by using the Privacy option in Settings, Group Policy, or MDM.
|
||||
|
||||
For Windows 10, we invite IT pros to join the [Windows Insider Program](http://insider.windows.com) to give us feedback on what we can do to make Windows work better for your organization.
|
||||
|
||||
@ -159,7 +159,7 @@ Microsoft believes in and practices information minimization. We strive to gathe
|
||||
## Telemetry levels
|
||||
|
||||
|
||||
This section explains the different telemetry levels in Windows 10, Windows Server 2016 Technical Preview, and System Center. These levels are available on all desktop and mobile editions of Windows 10, with the exception of the **Security** level which is limited to Windows 10 Enterprise, Windows 10 Education, Windows 10 Mobile Enterprise, Windows 10 IoT Core (IoT Core), and Windows Server 2016 Technical Preview.
|
||||
This section explains the different telemetry levels in Windows 10, Windows Server 2016, and System Center. These levels are available on all desktop and mobile editions of Windows 10, with the exception of the **Security** level which is limited to Windows 10 Enterprise, Windows 10 Education, Windows 10 Mobile Enterprise, Windows 10 IoT Core (IoT Core), and Windows Server 2016.
|
||||
|
||||
The telemetry data is categorized into four levels:
|
||||
|
||||
@ -171,7 +171,7 @@ The telemetry data is categorized into four levels:
|
||||
|
||||
- **Full**. All data necessary to identify and help to fix problems, plus data from the **Security**, **Basic**, and **Enhanced** levels.
|
||||
|
||||
The levels are cumulative and are illustrated in the following diagram. Also, these levels apply to all editions of Windows Server 2016 Technical Preview.
|
||||
The levels are cumulative and are illustrated in the following diagram. Also, these levels apply to all editions of Windows Server 2016.
|
||||
|
||||
|
||||
|
||||
@ -216,7 +216,7 @@ The Basic level gathers a limited set of data that’s critical for understandin
|
||||
|
||||
The data gathered at this level includes:
|
||||
|
||||
- **Basic device data**. Helps provide an understanding about the types of Windows devices and the configurations and types of native and virtualized Windows Server 2016 Technical Preview in the ecosystem. Examples include:
|
||||
- **Basic device data**. Helps provide an understanding about the types of Windows devices and the configurations and types of native and virtualized Windows Server 2016 in the ecosystem. Examples include:
|
||||
|
||||
- Device attributes, such as camera resolution and display type
|
||||
|
||||
@ -306,7 +306,7 @@ We do not recommend that you turn off telemetry in your organization as valuable
|
||||
|
||||
You can turn on or turn off System Center telemetry gathering. The default is on and the data gathered at this level represents what is gathered by default when System Center telemetry is turned on. However, setting the operating system telemetry level to **Basic** will turn off System Center telemetry, even if the System Center telemetry switch is turned on.
|
||||
|
||||
The lowest telemetry setting level supported through management policies is **Security**. The lowest telemetry setting supported through the Settings UI is **Basic**. The default telemetry setting for Windows Server 2016 Technical Preview is **Enhanced**.
|
||||
The lowest telemetry setting level supported through management policies is **Security**. The lowest telemetry setting supported through the Settings UI is **Basic**. The default telemetry setting for Windows Server 2016 is **Enhanced**.
|
||||
|
||||
### Configure the operating system telemetry level
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user