diff --git a/windows/manage/appv-accessing-the-client-management-console.md b/windows/manage/appv-accessing-the-client-management-console.md index f0dc7f3a54..0f3b5f139e 100644 --- a/windows/manage/appv-accessing-the-client-management-console.md +++ b/windows/manage/appv-accessing-the-client-management-console.md @@ -8,42 +8,30 @@ 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**   +> [!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. -  - Use the following procedure to access the client management console. **To access the client management console** 1. On the computer running the App-V client, click **Start** and select **Microsoft Application Virtualization Client**. - **Note**   - For computers running the App-V Remote Desktop Services client version, to access client management console follow step 1 of this procedure on the server running the client. + > [!NOTE] + > For computers running the App-V Remote Desktop Services client version, to access client management console follow step 1 of this procedure on the server running the client.   2. When the App-V client management console is displayed, click the tab you want to review and perform any required tasks. For more information about the client management console tasks see, [Using the App-V Client Management Console](appv-using-the-client-management-console.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). +## 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) - -  - -  - - - - - +- [Operations for App-V](appv-operations.md) diff --git a/windows/manage/appv-application-publishing-and-client-interaction.md b/windows/manage/appv-application-publishing-and-client-interaction.md index eb72830c2d..eea437ac5a 100644 --- a/windows/manage/appv-application-publishing-and-client-interaction.md +++ b/windows/manage/appv-application-publishing-and-client-interaction.md @@ -14,31 +14,7 @@ ms.prod: w10 This article provides technical information about common App-V client operations and their integration with the local operating system. -- [App-V package files created by the Sequencer](#bkmk-appv-pkg-files-list) - -- [What’s in the appv file?](#bkmk-appv-file-contents) - -- [App-V client data storage locations](#bkmk-files-data-storage) - -- [Package registry](#bkmk-pkg-registry) - -- [App-V package store behavior](#bkmk-pkg-store-behavior) - -- [Roaming registry and data](#bkmk-roaming-reg-data) - -- [App-V client application lifecycle management](#bkmk-clt-app-lifecycle) - -- [Integration of App-V packages](#bkmk-integr-appv-pkgs) - -- [Dynamic configuration processing](#bkmk-dynamic-config) - -- [Side-by-side assemblies](#bkmk-sidebyside-assemblies) - -- [Client logging](#bkmk-client-logging) - -For additional reference information, see [Microsoft Application Virtualization (App-V) Documentation Resources Download Page](http://www.microsoft.com/download/details.aspx?id=27760). - -## App-V package files created by the Sequencer +## App-V package files created by the Sequencer The Sequencer creates App-V packages and produces a virtualized application. The sequencing process creates the following files: @@ -93,7 +69,7 @@ The Sequencer creates App-V packages and produces a virtualized application. The For information about sequencing, see [Application Virtualization Sequencing Guide](http://go.microsoft.com/fwlink/?LinkID=269810). -## What’s in the appv file? +## What’s in the appv file? The appv file is a container that stores XML and non-XML files together in a single entity. This file is built from the AppX format, which is based on the Open Packaging Conventions (OPC) standard. @@ -102,139 +78,40 @@ To view the appv file contents, make a copy of the package, and then rename the The appv file contains the following folder and files, which are used when creating and publishing a virtual application: - ----- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription

Root

File folder

Directory that contains the file system for the virtualized application that is captured during sequencing.

[Content_Types].xml

XML File

List of the core content types in the appv file (e.g. DLL, EXE, BIN).

AppxBlockMap.xml

XML File

Layout of the appv file, which uses File, Block, and BlockMap elements that enable location and validation of files in the App-V package.

AppxManifest.xml

XML File

Metadata for the package that contains the required information for adding, publishing, and launching the package. Includes extension points (file type associations and shortcuts) and the names and GUIDs associated with the package.

FilesystemMetadata.xml

XML File

List of the files captured during sequencing, including attributes (e.g., directories, files, opaque directories, empty directories,and long and short names).

PackageHistory.xml

XML File

Information about the sequencing computer (operating system version, Internet Explorer version, .Net Framework version) and process (upgrade, package version).

Registry.dat

DAT File

Registry keys and values captured during the sequencing process for the package.

StreamMap.xml

XML File

List of files for the primary and publishing feature block. The publishing feature block contains the ICO files and required portions of files (EXE and DLL) for publishing the package. When present, the primary feature block includes files that have been optimized for streaming during the sequencing process.

+| Name | Type | Description | +| - | - | - | +| Root | File folder | Directory that contains the file system for the virtualized application that is captured during sequencing. | +| [Content_Types].xml | XML File | List of the core content types in the appv file (e.g. DLL, EXE, BIN). | +| AppxBlockMap.xml | XML File | Layout of the appv file, which uses File, Block, and BlockMap elements that enable location and validation of files in the App-V package.| +| AppxManifest.xml | XML File | Metadata for the package that contains the required information for adding, publishing, and launching the package. Includes extension points (file type associations and shortcuts) and the names and GUIDs associated with the package.| +| FilesystemMetadata.xml | XML File | List of the files captured during sequencing, including attributes (e.g., directories, files, opaque directories, empty directories,and long and short names). | +| PackageHistory.xml | XML File | Information about the sequencing computer (operating system version, Internet Explorer version, .Net Framework version) and process (upgrade, package version).| +| Registry.dat | DAT File | Registry keys and values captured during the sequencing process for the package.| +| StreamMap.xml | XML File | List of files for the primary and publishing feature block. The publishing feature block contains the ICO files and required portions of files (EXE and DLL) for publishing the package. When present, the primary feature block includes files that have been optimized for streaming during the sequencing process.|   -## App-V client data storage locations - +## App-V client data storage locations The App-V client performs tasks to ensure that virtual applications run properly and work like locally installed applications. The process of opening and running virtual applications requires mapping from the virtual file system and registry to ensure the application has the required components of a traditional application expected by users. This section describes the assets that are required to run virtual applications and lists the location where App-V stores the assets. - ----- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameLocationDescription

Package Store

%ProgramData%\App-V

Default location for read only package files

Machine Catalog

%ProgramData%\Microsoft\AppV\Client\Catalog

Contains per-machine configuration documents

User Catalog

%AppData%\Microsoft\AppV\Client\Catalog

Contains per-user configuration documents

Shortcut Backups

%AppData%\Microsoft\AppV\Client\Integration\ShortCutBackups

Stores previous integration points that enable restore on package unpublish

Copy on Write (COW) Roaming

%AppData%\Microsoft\AppV\Client\VFS

Writeable roaming location for package modification

Copy on Write (COW) Local

%LocalAppData%\Microsoft\AppV\Client\VFS

Writeable non-roaming location for package modification

Machine Registry

HKLM\Software\Microsoft\AppV

Contains package state information, including VReg for machine or globally published packages (Machine hive)

User Registry

HKCU\Software\Microsoft\AppV

Contains user package state information including VReg

User Registry Classes

HKCU\Software\Classes\AppV

Contains additional user package state information

- -  +| Name | Location | Description | +| - | - | - | +| Package Store | %ProgramData%\App-V| Default location for read only package files| +| Machine Catalog | %ProgramData%\Microsoft\AppV\Client\Catalog| Contains per-machine configuration documents| +| User Catalog | %AppData%\Microsoft\AppV\Client\Catalog| Contains per-user configuration documents| +| Shortcut Backups | %AppData%\Microsoft\AppV\Client\Integration\ShortCutBackups| Stores previous integration points that enable restore on package unpublish| +| Copy on Write (COW) Roaming | %AppData%\Microsoft\AppV\Client\VFS| Writeable roaming location for package modification| +| Copy on Write (COW) Local | %LocalAppData%\Microsoft\AppV\Client\VFS| Writeable non-roaming location for package modification| +| Machine Registry | HKLM\Software\Microsoft\AppV| Contains package state information, including VReg for machine or globally published packages (Machine hive)| +| User Registry | HKCU\Software\Microsoft\AppV| Contains user package state information including VReg| +| User Registry Classes | HKCU\Software\Classes\AppV| Contains additional user package state information| Additional details for the table are provided in the section below and throughout the document. ### Package store -The App-V Client manages the applications assets mounted in the package store. This default storage location is `%ProgramData%\App-V`, but you can configure it during or after setup by using the `Set-AppVClientConfiguration` PowerShell command, which modifies the local registry (`PackageInstallationRoot` value under the `HKLM\Software\Microsoft\AppV\Client\Streaming` key). The package store must be located at a local path on the client operating system. The individual packages are stored in the package store in subdirectories named for the Package GUID and Version GUID. +The App-V Client manages the applications assets mounted in the package store. This default storage location is `%ProgramData%\App-V`, but you can configure it during or after setup by using the `Set-AppVClientConfiguration` Windows PowerShell cmdlet, which modifies the local registry (`PackageInstallationRoot` value under the `HKLM\Software\Microsoft\AppV\Client\Streaming` key). The package store must be located at a local path on the client operating system. The individual packages are stored in the package store in subdirectories named for the Package GUID and Version GUID. Example of a path to a specific application: @@ -248,8 +125,8 @@ To change the default location of the package store during setup, see [How to De If the App-V Client is configured in Shared Content Store mode, no data is written to disk when a stream fault occurs, which means that the packages require minimal local disk space (publishing data). The use of less disk space is highly desirable in VDI environments, where local storage can be limited, and streaming the applications from a high performance network location (such as a SAN) is preferable. For more information on shared content store mode, see . -**Note**   -The machine and package store must be located on a local drive, even when you’re using Shared Content Store configurations for the App-V Client. +> [!NOTE] +> The machine and package store must be located on a local drive, even when you’re using Shared Content Store configurations for the App-V Client.   @@ -322,7 +199,7 @@ The App-V Client manages the following two file-based locations:

Default storage location

-

ppdata\roaming\Microsoft\AppV\Client\Catalog\Packages\PkgGUID\VerGUID

+

appdata\roaming\Microsoft\AppV\Client\Catalog\Packages\PkgGUID\VerGUID

Files in the user catalog

@@ -355,7 +232,7 @@ The Package Store contains a pristine copy of the package files that have been s ### COW roaming -The COW Roaming location described above stores changes to files and directories that are targeted to the typical %AppData% location or \\Users\\{username}\\AppData\\Roaming location. These directories and files are then roamed based on the operating system settings. +The COW Roaming location described above stores changes to files and directories that are targeted to the typical %AppData% location or \\Users\\**\\AppData\\Roaming location. These directories and files are then roamed based on the operating system settings. ### COW local @@ -368,21 +245,7 @@ Before an application can access the package registry data, the App-V Client mus When a new package is added to the App-V Client, a copy of the REGISTRY.DAT file from the package is created at `%ProgramData%\Microsoft\AppV\Client\VREG\{Version GUID}.dat`. The name of the file is the version GUID with the .DAT extension. The reason this copy is made is to ensure that the actual hive file in the package is never in use, which would prevent the removal of the package at a later time. - ----- - - - - - - - -

Registry.dat from Package Store

 > 

%ProgramData%\Microsoft\AppV\Client\Vreg\{VersionGuid}.dat

- +**Registry.dat from Package Store ** > **%ProgramData%\Microsoft\AppV\Client\Vreg\{VersionGuid}.dat**   When the first application from the package is launched on the client, the client stages or copies the contents out of the hive file, re-creating the package registry data in an alternate location `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\Packages\PackageGuid\Versions\VersionGuid\REGISTRY`. The staged registry data has two distinct types of machine data and user data. Machine data is shared across all users on the machine. User data is staged for each user to a userspecific location `HKCU\Software\Microsoft\AppV\Client\Packages\PackageGuid\Registry\User`. The machine data is ultimately removed at package removal time, and the user data is removed on a user unpublish operation. @@ -509,10 +372,10 @@ The following locations are configured as pass-through locations by default: The purpose of Pass-through keys is to ensure that a virtual application does not write registry data in the VReg that is required for non-virtual applications for successful operation or integration. The Policies key ensures that Group Policy based settings set by the administrator are utilized and not per package settings. The AppModel key is required for integration with Windows Modern UI based applications. It is recommend that administers do not modify any of the default pass-through keys, but in some instances, based on application behavior may require adding additional pass-through keys. -## App-V package store behavior +## App-V package store behavior -App-V 5 manages the Package Store, which is the location where the expanded asset files from the appv file are stored. By default, this location is stored at %ProgramData%\\App-V, and is limited in terms of storage capabilities only by free disk space. The package store is organized by the GUIDs for the package and version as mentioned in the previous section. +App-V manages the Package Store, which is the location where the expanded asset files from the appv file are stored. By default, this location is stored at %ProgramData%\\App-V, and is limited in terms of storage capabilities only by free disk space. The package store is organized by the GUIDs for the package and version as mentioned in the previous section. ### Add packages @@ -524,7 +387,7 @@ Packages can be explicitly loaded using the PowerShell `Mount-AppVClientPackage` ### Streaming packages -The App-V Client can be configured to change the default behavior of streaming. All streaming policies are stored under the following registry key: `HKEY_LOCAL_MAcHINE\Software\Microsoft\AppV\Client\Streaming`. Policies are set using the PowerShell cmdlet `Set-AppvClientConfiguration`. The following policies apply to Streaming: +The App-V Client can be configured to change the default behavior of streaming. All streaming policies are stored under the following registry key: `HKEY_LOCAL_MAcHINE\Software\Microsoft\AppV\Client\Streaming`. Policies are set using the Windows PowerShell cmdlet `Set-AppvClientConfiguration`. The following policies apply to Streaming: @@ -540,7 +403,7 @@ The App-V Client can be configured to change the default behavior of streaming. - + @@ -588,10 +451,6 @@ App-V packages can be configured with a primary feature block during sequencing. After the initial stream of any publishing data and the primary feature block, requests for additional files perform stream faults. These blocks of data are downloaded to the package store on an as-needed basis. This allows a user to download only a small part of the package, typically enough to launch the package and run normal tasks. All other blocks are downloaded when a user initiates an operation that requires data not currently in the package store. -For more information on App-V Package streaming visit: . - -Sequencing for streaming optimization is available at: . - ### Package upgrades App-V Packages require updating throughout the lifecycle of the application. App-V Package upgrades are similar to the package publish operation, as each version will be created in its own PackageRoot location: `%ProgramData%\App-V\{PkgGUID}\{newVerGUID}`. The upgrade operation is optimized by creating hard links to identical- and streamed-files from other versions of the same package. @@ -603,7 +462,7 @@ The behavior of the App-V Client when packages are removed depends on the method ## Roaming registry and data -App-V 5 is able to provide a near-native experience when roaming, depending on how the application being used is written. By default, App-V roams AppData that is stored in the roaming location, based on the roaming configuration of the operating system. Other locations for storage of file-based data do not roam from computer to computer, since they are in locations that are not roamed. +App-V is able to provide a near-native experience when roaming, depending on how the application being used is written. By default, App-V roams AppData that is stored in the roaming location, based on the roaming configuration of the operating system. Other locations for storage of file-based data do not roam from computer to computer, since they are in locations that are not roamed. ### Roaming requirements and user catalog data storage @@ -615,8 +474,8 @@ App-V stores data, which represents the state of the user’s catalog, in the fo Together, these files and registry settings represent the user’s catalog, so either both must be roamed, or neither must be roamed for a given user. App-V does not support roaming %AppData%, but not roaming the user’s profile (registry), or vice versa. -**Note**   -The **Repair-AppvClientPackage** cmdlet does not repair the publishing state of packages, where the user’s App-V state under `HKEY_CURRENT_USER` is missing or mismatched with the data in %appdata%. +> [!NOTE] +> The **Repair-AppvClientPackage** cmdlet does not repair the publishing state of packages, where the user’s App-V state under `HKEY_CURRENT_USER` is missing or mismatched with the data in %appdata%.   @@ -671,84 +530,23 @@ A typical package has several locations mapped in the user’s backing store for The following table shows local and roaming locations, when folder redirection has not been implemented. -

AllowHighCostLaunch

On Windows 8 and later, it allows streaming over 3G and cellular networks

Allows streaming over 3G and cellular networks

AutoLoad

---- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
VFS directory in packageMapped location of backing store

ProgramFilesX86

C:\users\jsmith\AppData\Local\Microsoft\AppV\Client\VFS\<GUID>\ProgramFilesX86

SystemX86

C:\users\jsmith\AppData\Local\Microsoft\AppV\Client\VFS\<GUID>\SystemX86

Windows

C:\users\jsmith\AppData\Local\Microsoft\AppV\Client\VFS\<GUID>\Windows

appv_ROOT

C:\users\jsmith\AppData\Local\Microsoft\AppV\Client\VFS\<GUID>\appv_ROOT

AppData

C:\users\jsmith\AppData\Roaming\Microsoft\AppV\Client\VFS\<GUID>\AppData

- -  - -  +| VFS directory in package | Mapped location of backing store | +| - | - | +| ProgramFilesX86 | C:\Users\Local\AppData\Local\Microsoft\AppV\Client\VFS\\ProgramFilesX86 | +| SystemX86 | C:\Users\username\AppData\Local\Microsoft\AppV\Client\VFS\\SystemX86 | +| Windows | C:\Users\username\AppData\Local\Microsoft\AppV\Client\VFS\\Windows | +| appv\_ROOT | C:\Users\username\AppData\Local\Microsoft\AppV\Client\VFS\\appv_ROOT| +| AppData | C:\Users\username\AppData\Local\Microsoft\AppV\Client\VFS\\AppData | The following table shows local and roaming locations, when folder redirection has been implemented for %AppData%, and the location has been redirected (typically to a network location). - ---- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
VFS directory in packageMapped location of backing store

ProgramFilesX86

C:\users\jsmith\AppData\Local\Microsoft\AppV\Client\VFS\<GUID>\ProgramFilesX86

SystemX86

C:\users\jsmith\AppData\Local\Microsoft\AppV\Client\VFS\<GUID>\SystemX86

Windows

C:\users\jsmith\AppData\Local\Microsoft\AppV\Client\VFS\<GUID>\Windows

appv_ROOT

C:\users\jsmith\AppData\Local\Microsoft\AppV\Client\VFS\<GUID>\appv_ROOT

AppData

\\Fileserver\users\jsmith\roaming\Microsoft\AppV\Client\VFS\<GUID>\AppData

- -  - +| VFS directory in package | Mapped location of backing store | +| - | - | +| ProgramFilesX86 | C:\Users\Local\AppData\Local\Microsoft\AppV\Client\VFS\\ProgramFilesX86 | +| SystemX86 | C:\Users\Local\AppData\Local\Microsoft\AppV\Client\VFS\\SystemX86 | +| Windows | C:\Users\Local\AppData\Local\Microsoft\AppV\Client\VFS\\Windows | +| appv_ROOT | C:\Users\Local\AppData\Local\Microsoft\AppV\Client\VFS\\appv\_ROOT | +| AppData | \\Fileserver\users\Local\roaming\Microsoft\AppV\Client\VFS\\AppData |   The current App-V Client VFS driver cannot write to network locations, so the App-V Client detects the presence of folder redirection and copies the data on the local drive during publishing and when the virtual environment starts. After the user closes the App-V application and the App-V Client closes the virtual environment, the local storage of the VFS AppData is copied back to the network, enabling roaming to additional machines, where the process will be repeated. The detailed steps of the processes are: @@ -797,14 +595,14 @@ This completes the successful roaming of application settings that are present i This process will re-create both the local and network locations for AppData and remove the registry record of the timestamp. -## App-V client application lifecycle management +## App-V client application lifecycle management In an App-V Full Infrastructure, after applications are sequenced they are managed and published to users or computers via the App-V Management and Publishing servers. This section details the operations that occur during the common App-V application lifecycle operations (Add, publishing, launch, upgrade, and removal) and the file and registry locations that are changed and modified from the App-V Client perspective. The App-V Client operations are performed as a series of PowerShell commands initiated on the computer running the App-V Client. This document focuses on App-V Full Infrastructure solutions. For specific information on App-V Integration with Configuration Manager 2012 visit: . -The App-V application lifecycle tasks are triggered at user login (default), machine startup, or as background timed operations. The settings for the App-V Client operations, including Publishing Servers, refresh intervals, package script enablement, and others, are configured during setup of the client or post-setup with PowerShell commands. See the How to Deploy the Client section on TechNet at: [How to Deploy the App-V Client](appv-deploy-the-appv-client.md) or utilize the PowerShell: +The App-V application lifecycle tasks are triggered at user login (default), machine startup, or as background timed operations. The settings for the App-V Client operations, including Publishing Servers, refresh intervals, package script enablement, and others, are configured during setup of the client or post-setup with PowerShell commands. See [How to enable the App-V Client](appv-enable-the-appv-desktop-client.md) or use Windows PowerShell: ``` syntax get-command *appv* @@ -834,7 +632,7 @@ Adding an App-V package to the client is the first step of the publishing refres **How to add an App-V package** -1. Manual initiation via PowerShell or Task Sequence initiation of the Publishing Refresh process. +1. Manual initiation via Windows PowerShell or Task Sequence initiation of the Publishing Refresh process. 1. The App-V Client makes an HTTP connection and requests a list of applications based on the target. The Publishing refresh process supports targeting machines or users. @@ -880,8 +678,8 @@ Adding an App-V package to the client is the first step of the publishing refres 5. Remove objects that are not published to the target (user or machine). - **Note**   - This will not perform a package deletion but rather remove integration points for the specific target (user or machine) and remove user catalog files (machine catalog files for globally published). + > [!NOTE] + > This will not perform a package deletion but rather remove integration points for the specific target (user or machine) and remove user catalog files (machine catalog files for globally published).   @@ -889,8 +687,8 @@ Adding an App-V package to the client is the first step of the publishing refres 7. Packages that already have publishing information for the machine or user are immediately restored. - **Note**   - This condition occurs as a product of removal without unpublishing with background addition of the package. + > [!NOTE]    + > This condition occurs as a product of removal without unpublishing with background addition of the package.   @@ -957,7 +755,7 @@ After the Publishing Refresh process, the user launches and subsequently re-laun ### Upgrading an App-V package -The App-V 5 package upgrade process differs from the older versions of App-V. App-V supports multiple versions of the same package on a machine entitled to different users. Package versions can be added at any time as the package store and catalogs are updated with the new resources. The only process specific to the addition of new version resources is storage optimization. During an upgrade, only the new files are added to the new version store location and hard links are created for unchanged files. This reduces the overall storage by only presenting the file on one disk location and then projecting it into all folders with a file location entry on the disk. The specific details of upgrading an App-V Package are as follows: +The App-V package upgrade process differs from the older versions of App-V. App-V supports multiple versions of the same package on a machine entitled to different users. Package versions can be added at any time as the package store and catalogs are updated with the new resources. The only process specific to the addition of new version resources is storage optimization. During an upgrade, only the new files are added to the new version store location and hard links are created for unchanged files. This reduces the overall storage by only presenting the file on one disk location and then projecting it into all folders with a file location entry on the disk. The specific details of upgrading an App-V Package are as follows: **How to upgrade an App-V package** @@ -973,13 +771,13 @@ The App-V 5 package upgrade process differs from the older versions of App-V. Ap 4. Perform integration tasks. - - Integrate extensions points (EP) from the Manifest and Dynamic Configuration files. + 1. Integrate extensions points (EP) from the Manifest and Dynamic Configuration files. - 1. File based EP data is stored in the AppData folder utilizing Junction Points from the package store. + 2. File based EP data is stored in the AppData folder utilizing Junction Points from the package store. - 2. Version 1 EPs already exist when a new version becomes available. + 3. Version 1 EPs already exist when a new version becomes available. - 3. The extension points are switched to the Version 2 location in machine or user catalogs for any newer or updated extension points. + 4. The extension points are switched to the Version 2 location in machine or user catalogs for any newer or updated extension points. 5. Run scripts targeted for publishing timing. @@ -987,124 +785,42 @@ The App-V 5 package upgrade process differs from the older versions of App-V. Ap ### Upgrading an in-use App-V package -**Starting in App-V 5 SP2**: If you try to upgrade a package that is in use by an end user, the upgrade task is placed in a pending state. The upgrade will run later, according to the following rules: +If you try to upgrade a package that is in use by an end user, the upgrade task is placed in a pending state. The upgrade will run later, according to the following rules: - ---- - - - - - - - - - - - - - - - - -
Task typeApplicable rule

User-based task, e.g., publishing a package to a user

The pending task will be performed after the user logs off and then logs back on.

Globally based task, e.g., enabling a connection group globally

The pending task will be performed when the computer is shut down and then restarted.

- -  +| Task type | Applicable rule | +| - | - | +| User-based task, e.g., publishing a package to a user | The pending task will be performed after the user logs off and then logs back on. | +| Globally based task, e.g., enabling a connection group globally | The pending task will be performed when the computer is shut down and then restarted. | When a task is placed in a pending state, the App-V client also generates a registry key for the pending task, as follows: - ---- - - - - - - - - - - - - - - - - -
User-based or globally based taskWhere the registry key is generated

User-based tasks

KEY_CURRENT_USER\Software\Microsoft\AppV\Client\PendingTasks

Globally based tasks

HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Client\PendingTasks

- -  +| User-based or globally based task | Where the registry key is generated | +| - | - | +| User-based tasks | HKEY\_CURRENT\_USER\Software\Microsoft\AppV\Client\PendingTasks | +| Globally based tasks | HKEY\_LOCAL\_MACHINE\Software\Microsoft\AppV\Client\PendingTasks | The following operations must be completed before users can use the newer version of the package: - ---- - - - - - - - - - - - - - - - - -
TaskDetails

Add the package to the computer

This task is computer specific and you can perform it at any time by completing the steps in the Package Add section above.

Publish the package

See the Package Publishing section above for steps. This process requires that you update extension points on the system. End users cannot be using the application when you complete this task.

- -  +| Task | Details | +| - | - | +| Add the package to the computer | This task is computer specific and you can perform it at any time by completing the steps in the Package Add section above. | +| Publish the package | See the Package Publishing section above for steps. This process requires that you update extension points on the system. End users cannot be using the application when you complete this task. | Use the following example scenarios as a guide for updating packages. - ---- - - - - - - - - - - - - - - - - -
ScenarioRequirements

App-V package is not in use when you try to upgrade

None of the following components of the package can be in use: virtual application, COM server, or shell extensions.

-

The administrator publishes a newer version of the package and the upgrade works the next time a component or application inside the package is launched. The new version of the package is streamed and run. Nothing has changed in this scenario in App-V 5 SP2 from previous releases of App-V 5.

App-V package is in use when the administrator publishes a newer version of the package

The upgrade operation is set to pending by the App-V Client, which means that it is queued and carried out later when the package is not in use.

-

If the package application is in use, the user shuts down the virtual application, after which the upgrade can occur.

-

If the package has shell extensions (Office 2013), which are permanently loaded by Windows Explorer, the user cannot be logged in. Users must log off and the log back in to initiate the App-V package upgrade.

+| Scenario | Requirements | +| - | - | +| App-V package is not in use when you try to upgrade | None of the following components of the package can be in use: virtual application, COM server, or shell extensions.

The administrator publishes a newer version of the package and the upgrade works the next time a component or application inside the package is launched. The new version of the package is streamed and ran. | +| App-V package is in use when the administrator publishes a newer version of the package | The upgrade operation is set to pending by the App-V Client, which means that it is queued and carried out later when the package is not in use.

If the package application is in use, the user shuts down the virtual application, after which the upgrade can occur.

If the package has shell extensions, which are permanently loaded by Windows Explorer, the user cannot be logged in. Users must log off and the log back in to initiate the App-V package upgrade.|   - ### Global vs user publishing App-V Packages can be published in one of two ways; User which entitles an App-V package to a specific user or group of users and Global which entitles the App-V package to the entire machine for all users of the machine. Once a package upgrade has been pended and the App-V package is not in use, consider the two types of publishing: - **Globally published**: the application is published to a machine; all users on that machine can use it. The upgrade will happen when the App-V Client Service starts, which effectively means a machine restart. -- **User published**: the application is published to a user. If there are multiple users on the machine, the application can be published to a subset of the users. The upgrade will happen when the user logs in or when it is published again (periodically, ConfigMgr Policy refresh and evaluation, or an App-V periodic publishing/refresh, or explicitly via PowerShell commands). +- **User published**: the application is published to a user. If there are multiple users on the machine, the application can be published to a subset of the users. The upgrade will happen when the user logs in or when it is published again (periodically, ConfigMgr Policy refresh and evaluation, or an App-V periodic publishing/refresh, or explicitly via Windows PowerShell commands). ### Removing an App-V package @@ -1112,9 +828,9 @@ Removing App-V applications in a Full Infrastructure is an unpublish operation, ### Repairing an App-V package -The repair operation is very simple but may affect many locations on the machine. The previously mentioned Copy on Write (COW) locations are removed, and extension points are de-integrated and then re-integrated. Please review the COW data placement locations by reviewing where they are registered in the registry. This operation is done automatically and there is no administrative control other than initiating a Repair operation from the App-V Client Console or via PowerShell (Repair-AppVClientPackage). +The repair operation is very simple but may affect many locations on the machine. The previously mentioned Copy on Write (COW) locations are removed, and extension points are de-integrated and then re-integrated. Please review the COW data placement locations by reviewing where they are registered in the registry. This operation is done automatically and there is no administrative control other than initiating a Repair operation from the App-V Client Console or via Windows PowerShell (Repair-AppVClientPackage). -## Integration of App-V packages +## Integration of App-V packages The App-V Client and package architecture provides specific integration with the local operating system during the addition and publishing of packages. Three files define the integration or extension points for an App-V Package: @@ -1172,7 +888,7 @@ From the package manifest and dynamic configuration XML files, the path to a spe ``` syntax - [{Common Desktop}]\Adobe Reader 9.lnk + [{Common Desktop}]\Adobe Reader.lnk [{AppVPackageRoot}]\Reader\AcroRd32.exe [{Windows}]\Installer\{AC76BA86-7AD7-1033-7B44-A94000000001}\SC_Reader.ico @@ -1217,7 +933,7 @@ The App-V Client manages the local operating system File Type Associations durin [{AppVPackageRoot}]\Reader\AcroRd32.exe Read - Open with Adobe Reader 9 + Open with Adobe Reader "[{AppVPackageRoot}]\Reader\AcroRd32.exe" "%1" @@ -1255,52 +971,16 @@ Shell extensions are embedded in the package automatically during the sequencing The following table displays the supported shell extensions. - ---- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
HandlerDescription

Context menu handler

Adds menu items to the context menu. It is called before the context menu is displayed.

Drag-and-drop handler

Controls the action upon right-click drag-and-drop and modifies the context menu that appears.

Drop target handler

Controls the action after a data object is dragged-and-dropped over a drop target such as a file.

Data object handler

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.

Property sheet handler

Replaces or adds pages to the property sheet dialog box of an object.

Infotip handler

Allows retrieving flags and infotip information for an item and displaying it inside a popup tooltip upon mouse- hover.

Column handler

Allows creating and displaying custom columns in Windows Explorer Details view. It can be used to extend sorting and grouping.

Preview handler

Enables a preview of a file to be displayed in the Windows Explorer Preview Pane.

+| Handler | Description | +| - | - | +| Context menu handler | Adds menu items to the context menu. It is called before the context menu is displayed. | +| Drag-and-drop handler | Controls the action upon right-click drag-and-drop and modifies the context menu that appears. | +| Drop target handler | Controls the action after a data object is dragged-and-dropped over a drop target such as a file.| +| Data object handler| 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.| +| Property sheet handler| Replaces or adds pages to the property sheet dialog box of an object.| +| Infotip handler| Allows retrieving flags and infotip information for an item and displaying it inside a popup tooltip upon mouse- hover.| +| Column handler| Allows creating and displaying custom columns in Windows Explorer *Details view*. It can be used to extend sorting and grouping.| +| Preview handler| Enables a preview of a file to be displayed in the Windows Explorer Preview Pane.|   @@ -1501,7 +1181,7 @@ App-V Packages contain the Manifest file inside of the appv package file, which ### Example for dynamic configuration files -The example below shows the combination of the Manifest, Deployment Configuration and User Configuration files after publishing and during normal operation. These examples are abbreviated examples of each of the files. The purpose is show the combination of the files only and not to be a complete description of the specific categories available in each of the files. For more information review the App-V 5 Sequencing Guide at: +The example below shows the combination of the Manifest, Deployment Configuration and User Configuration files after publishing and during normal operation. These examples are abbreviated examples of each of the files. The purpose is show the combination of the files only and not to be a complete description of the specific categories available in each of the files. For more information review the App-V Sequencing Guide at: [http://go.microsoft.com/fwlink/?LinkID=269810](http://go.microsoft.com/fwlink/?LinkID=269810). **Manifest** @@ -1569,10 +1249,10 @@ The example below shows the combination of the Manifest, Deployment Configuratio ``` -## Side-by-side assemblies +## Side-by-side assemblies -App-V supports the automatic packaging of side-by-side (SxS) assemblies during sequencing and deployment on the client during virtual application publishing. App-V 5 SP2 supports capturing SxS assemblies during sequencing for assemblies not present on the sequencing machine. And for assemblies consisting of Visual C++ (Version 8 and newer) and/or MSXML run-time, the Sequencer will automatically detect and capture these dependencies even if they were not installed during monitoring. The Side by Side assemblies feature removes the limitations of previous versions of App-V, where the App-V Sequencer did not capture assemblies already present on the sequencing workstation, and privatizing the assemblies which limited to one bit version per package. This behavior resulted in deployed App-V applications to clients missing the required SxS assemblies, causing application launch failures. This forced the packaging process to document and then ensure that all assemblies required for packages were locally installed on the user’s client operating system to ensure support for the virtual applications. Based on the number of assemblies and the lack of application documentation for the required dependencies, this task was both a management and implementation challenge. +App-V supports the automatic packaging of side-by-side (SxS) assemblies during sequencing and deployment on the client during virtual application publishing. App-V supports capturing SxS assemblies during sequencing for assemblies not present on the sequencing machine. And for assemblies consisting of Visual C++ (Version 8 and newer) and/or MSXML run-time, the Sequencer will automatically detect and capture these dependencies even if they were not installed during monitoring. The Side by Side assemblies feature removes the limitations of previous versions of App-V, where the App-V Sequencer did not capture assemblies already present on the sequencing workstation, and privatizing the assemblies which limited to one bit version per package. This behavior resulted in deployed App-V applications to clients missing the required SxS assemblies, causing application launch failures. This forced the packaging process to document and then ensure that all assemblies required for packages were locally installed on the user’s client operating system to ensure support for the virtual applications. Based on the number of assemblies and the lack of application documentation for the required dependencies, this task was both a management and implementation challenge. Side by Side Assembly support in App-V has the following features. @@ -1588,25 +1268,16 @@ Side by Side Assembly support in App-V has the following features. During publishing of an App-V package with SxS assemblies the App-V Client will check for the presence of the assembly on the machine. If the assembly does not exist, the client will deploy the assembly to the machine. Packages that are part of connection groups will rely on the Side by Side assembly installations that are part of the base packages, as the connection group does not contain any information about assembly installation. -**Note**   -UnPublishing or removing a package with an assembly does not remove the assemblies for that package. +> [!NOTE] +> Unpublishing or removing a package with an assembly does not remove the assemblies for that package.   -## Client logging +## Client logging The App-V client logs information to the Windows Event log in standard ETW format. The specific App-V events can be found in the event viewer, under Applications and Services Logs\\Microsoft\\AppV\\Client. -**Note**   -In App-V 5.0 SP3, some logs were consolidated and moved to the following location: - -`Event logs/Applications and Services Logs/Microsoft/AppV/ServiceLog` - -For a list of the moved logs, see [About App-V 5.0 SP3](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/about-app-v-50-sp3.md#bkmk-event-logs-moved). - -  - There are three specific categories of events recorded described below. **Admin**: Logs events for configurations being applied to the App-V Client, and contains the primary warnings and errors. @@ -1617,14 +1288,4 @@ There are three specific categories of events recorded described below. ## 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). - -  - -  - - - - - diff --git a/windows/manage/appv-deploying-appv.md b/windows/manage/appv-deploying-appv.md index 996e0d13b6..c5ca765eed 100644 --- a/windows/manage/appv-deploying-appv.md +++ b/windows/manage/appv-deploying-appv.md @@ -8,13 +8,11 @@ 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. -Microsoft Application Virtualization (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 +## App-V Deployment Information - [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md) @@ -46,14 +44,4 @@ Microsoft Application Virtualization (App-V) supports a number of different depl ## 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). - -  - -  - - - - - diff --git a/windows/manage/appv-deploying-the-appv-sequencer-and-client.md b/windows/manage/appv-deploying-the-appv-sequencer-and-client.md index 9acd316d23..7eec53e3c3 100644 --- a/windows/manage/appv-deploying-the-appv-sequencer-and-client.md +++ b/windows/manage/appv-deploying-the-appv-sequencer-and-client.md @@ -1,5 +1,5 @@ --- -title: Deploying the App-V Sequencer and Client (Windows 10) +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 @@ -11,19 +11,17 @@ ms.prod: w10 # Deploying the App-V Sequencer and Client +The App-V Sequencer and client enable administrators to virtualize and run virtualized applications. -The Microsoft Application Virtualization (App-V) Sequencer and client enable administrators to virtualize and run virtualized applications. - -## Deploy the client +## 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. -[How to Deploy the App-V Client](appv-deploy-the-appv-client.md) +> [!NOTE] +> In Windows 10, version 1607, App-V is included with the OS. You only need to enable it. -[How to Uninstall the App-V Client](appv-uninstall-the-appv-client.md) - -[How to Deploy the App-V 4.6.x and the App-V Client on the Same Computer](appv-deploy-the-appv-46x-and-the-appv--51-client-on-the-same-computer.md) +[Enable the App-V desktop client](appv-enable-the-appv-desktop-client.md) ## Client Configuration Settings @@ -34,19 +32,14 @@ The App-V client stores its configuration in the registry. You can gather some u ## 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. -You can use the Microsoft ADMX template to configure the client settings for the App-V client and the Remote Desktop Services client. The ADMX template manages common client configurations by using an existing Group Policy infrastructure and it includes settings for the App-V client configuration. -**Important**   -You can obtain the App-V ADMX template from the Microsoft Download Center. - -  - -After you download and install the ADMX template, perform the following steps on the computer that you will use to manage Group Policy. This is typically the Domain Controller. +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>** +2. Save the **.adml** file to the following directory: **Windows \\ PolicyDefinitions \\ ** After you have completed the preceding steps, you can manage the App-V client configuration settings with the **Group Policy Management** console. @@ -56,13 +49,10 @@ The App-V client also stores its configuration in the registry. You can gather s ## 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. - -  +> [!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. @@ -70,26 +60,27 @@ The SCS mode is helpful in the following scenarios: - Virtual desktop infrastructure (VDI) deployments -- Remote desktop services (RDS) 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 PowerShell command on the computer that runs the App-V client: +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** +``` +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 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 PowerShell commands. The package would not stream across the network because it would be locally stored. +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 +## 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: @@ -98,21 +89,9 @@ You can use the App-V Sequencer log information to help troubleshoot the Sequenc ## Other resources for deploying the Sequencer and client - -[Deploying App-V](appv-deploying-appv.md) - -[Planning for App-V](appv-planning-for-appv.md) +- [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). - -  - -  - - - - - diff --git a/windows/manage/appv-deploying-the-appv-server.md b/windows/manage/appv-deploying-the-appv-server.md index 431a5ff0f0..38fa2690b4 100644 --- a/windows/manage/appv-deploying-the-appv-server.md +++ b/windows/manage/appv-deploying-the-appv-server.md @@ -10,28 +10,28 @@ ms.prod: w10 # Deploying the App-V Server -You can install the Microsoft Application Virtualization (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). +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#bkmk-migrate-to-51). +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. -> **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 Server overview +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. -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 an 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. +- **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](appv-deploy-the-appv-server.md) for more information about the management database. +- **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** for more information about configuring the publishing server. +- **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** for more information about the reporting capabilities in App-V. +- **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. +- **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: @@ -41,38 +41,34 @@ In large organizations, you might want to install more than one instance of the - Scalability to support a high load. For example, you can install additional servers behind a network load balancer. -## App-V stand-alone deployment +## 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](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 Server Using a Script](appv-deploy-the-appv-server-with-a-script.md) - -## App-V Server distributed deployment +## 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) +- [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. +> [!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 +## 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: @@ -82,7 +78,7 @@ Associated setup logs are saved in the following directory: **%temp%** -## App-V reporting +## 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: @@ -101,7 +97,7 @@ For more information, see [About App-V Reporting](appv-reporting.md) and [How t ## Other resources for the App-V server -[Deploying App-V](appv-deploying-appv.md) +- [Deploying App-V](appv-deploying-appv.md) ## Have a suggestion for App-V? diff --git a/windows/manage/appv-deployment-checklist.md b/windows/manage/appv-deployment-checklist.md index 4ca2362a57..546da027a6 100644 --- a/windows/manage/appv-deployment-checklist.md +++ b/windows/manage/appv-deployment-checklist.md @@ -12,12 +12,10 @@ ms.prod: w10 # App-V Deployment Checklist -This checklist can be used to help you during Microsoft Application Virtualization (App-V) deployment. +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. - -  +> [!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. @@ -52,7 +50,7 @@ This checklist outlines the recommended steps and a high-level list of items to

Run App-V Setup to deploy the required App-V features for your environment.

Note   -

Keep track of the names of the servers and associated URL’s created during installation. This information will be used throughout the installation process.

+

Keep track of the names of the servers and associated URLs created during installation. This information will be used throughout the installation process.

  @@ -68,8 +66,6 @@ This checklist outlines the recommended steps and a high-level list of items to
-  - ## Have a suggestion for App-V? @@ -77,14 +73,4 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros ## Related topics - [Deploying App-V](appv-deploying-appv.md) - -  - -  - - - - - diff --git a/windows/manage/appv-evaluating-appv.md b/windows/manage/appv-evaluating-appv.md index 9969ccc381..7e24c6ea2f 100644 --- a/windows/manage/appv-evaluating-appv.md +++ b/windows/manage/appv-evaluating-appv.md @@ -12,11 +12,10 @@ ms.prod: w10 # Evaluating App-V -Before you deploy Microsoft Application Virtualization (App-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. +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 @@ -27,7 +26,7 @@ Use the following links for information about setting up the App-V sequencer and - [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md) -### Configuring the App-V Server +### Configuring the App-V Server Use the following links for information about setting up the App-V server in your lab environment. @@ -39,25 +38,14 @@ Use the following links for information about setting up the App-V server in you Use the following link for more information about creating and managing virtualized packages in your lab environment. -- [How to Deploy the App-V Client](appv-deploy-the-appv-client.md) +- [Enable the App-V Desktop Client](appv-enable-the-appv-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) - -  - -  - - - - - +- [Getting Started with App-V](appv-getting-started.md) diff --git a/windows/manage/appv-planning-checklist.md b/windows/manage/appv-planning-checklist.md index b94901557c..91d7f0fe4e 100644 --- a/windows/manage/appv-planning-checklist.md +++ b/windows/manage/appv-planning-checklist.md @@ -12,12 +12,10 @@ ms.prod: w10 # App-V Planning Checklist -This checklist can be used to help you plan for preparing your computing environment for Microsoft Application Virtualization (App-V) deployment. +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 into a spreadsheet program and customize it for your use. - -  +> [!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. @@ -74,23 +72,10 @@ This checklist outlines the recommended steps and a high-level list of items to
-  - ## 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) - -  - -  - - - - - diff --git a/windows/manage/appv-prerequisites.md b/windows/manage/appv-prerequisites.md index 1ed485c04d..b8b112eea4 100644 --- a/windows/manage/appv-prerequisites.md +++ b/windows/manage/appv-prerequisites.md @@ -12,7 +12,7 @@ ms.prod: w10 # App-V Prerequisites -Before installing Microsoft Application Virtualization (App-V), ensure that you have installed all of the following required prerequisite software. +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). @@ -56,7 +56,7 @@ The following table indicates the software that is already installed for differe

  • Windows PowerShell 3.0

    Note   -

    Installing PowerShell 3.0 requires a restart.

    +

    Installing Windows PowerShell 3.0 requires a restart.

      @@ -148,7 +148,7 @@ Install the required prerequisite software for the App-V Server components.

    [Windows PowerShell 3.0](http://www.microsoft.com/download/details.aspx?id=34595)

    -

    Installing PowerShell 3.0 requires a restart.

    +

    Installing Windows PowerShell 3.0 requires a restart.

    Download and install [KB2533623](http://support.microsoft.com/kb/2533623)

    @@ -217,12 +217,8 @@ Install the required prerequisite software for the App-V Server components. -  - -**Important**   -JavaScript must be enabled on the browser that opens the Web Management Console. - -  +> [!IMPORTANT] +> JavaScript must be enabled on the browser that opens the Web Management Console. ### Management server database prerequisite software @@ -309,7 +305,7 @@ The Management database is required only if you are using the App-V Management s

    -

    Windows Server Web Server Role

    +

    Web Server Role

    This role must be added to a server operating system that is supported for the Management server.

    @@ -528,6 +524,9 @@ The Reporting database is required only if you are using the App-V Reporting ser Install the following prerequisite software for the App-V client. +> [!NOTE] +> This is not required on Windows 10, version 1607. + @@ -629,7 +628,7 @@ Install the following prerequisite software for the App-V Remote Desktop Service - + @@ -638,7 +637,6 @@ Install the following prerequisite software for the App-V Remote Desktop Service

    [Windows PowerShell 3.0](http://www.microsoft.com/download/details.aspx?id=34595)

    Installing PowerShell 3.0 requires a restart.

    Installing Windows PowerShell 3.0 requires a restart.

    [KB2533623](http://support.microsoft.com/kb/2533623)
    -  ## Have a suggestion for App-V? @@ -647,10 +645,8 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros ## Related topics - -[Planning for App-V](appv-planning-for-appv.md) - -[App-V Supported Configurations](appv-supported-configurations.md) +- [Planning for App-V](appv-planning-for-appv.md) +- [App-V Supported Configurations](appv-supported-configurations.md)   diff --git a/windows/manage/appv-supported-configurations.md b/windows/manage/appv-supported-configurations.md index b8f6027e0a..67662f89bd 100644 --- a/windows/manage/appv-supported-configurations.md +++ b/windows/manage/appv-supported-configurations.md @@ -12,18 +12,17 @@ ms.prod: w10 # App-V Supported Configurations -This topic specifies the requirements to install and run Microsoft Application Virtualization (App-V) in your environment. +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 Microsoft Windows Server Core. +- 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. @@ -37,10 +36,6 @@ The App-V Server does not support the following scenarios: The following table lists the operating systems that are supported for the App-V Management server installation. -**Note**   -Microsoft provides support for the current service pack and, in some cases, the immediately preceding service pack. To find the support timelines for your product, see the [Lifecycle Supported Service Packs](http://go.microsoft.com/fwlink/p/?LinkId=31975). See [Microsoft Support Lifecycle Support Policy FAQ](http://go.microsoft.com/fwlink/p/?LinkId=31976) for more information. - -  @@ -57,6 +52,11 @@ Microsoft provides support for the current service pack and, in some cases, the + + + + + @@ -76,12 +76,12 @@ Microsoft provides support for the current service pack and, in some cases, the   -**Important**   -Deployment of the Management server role to a computer with Remote Desktop Sharing (RDS) enabled is not supported. +> [!IMPORTANT] +> Deployment of the Management server role to a computer with Remote Desktop Services enabled is not supported.   -### Management server hardware requirements +### Management server hardware requirements - Processor—1.4 GHz or faster, 64-bit (x64) processor @@ -146,6 +146,11 @@ The following table lists the operating systems that are supported for the App-V + + + + + @@ -165,7 +170,7 @@ The following table lists the operating systems that are supported for the App-V   -### Publishing server hardware requirements +### Publishing server hardware requirements App-V adds no additional requirements beyond those of Windows Server. @@ -194,6 +199,11 @@ The following table lists the operating systems that are supported for the App-V + + + + + @@ -213,7 +223,7 @@ The following table lists the operating systems that are supported for the App-V   -### Reporting server hardware requirements +### Reporting server hardware requirements App-V adds no additional requirements beyond those of Windows Server. @@ -261,11 +271,14 @@ The following table lists the SQL Server versions that are supported for the App   -## App-V client system requirements +## 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. +

    Microsoft Windows Server 2016

    64-bit

    Microsoft Windows Server 2012 R2

    64-bit

    Microsoft Windows Server 2016

    64-bit

    Microsoft Windows Server 2012 R2

    64-bit

    Microsoft Windows Server 2016

    64-bit

    Microsoft Windows Server 2012 R2

    64-bit

    @@ -281,22 +294,27 @@ The following table lists the operating systems that are supported for the App-V - - - - - - + - + - + + + + + + + + + + + @@ -313,7 +331,7 @@ The following App-V client installation scenarios are not supported, except as n - The App-V Remote Desktop services client is supported only for RDS-enabled servers -### App-V client hardware requirements +### App-V client hardware requirements The following list displays the supported hardware configuration for the App-V client installation. @@ -343,6 +361,11 @@ The following table lists the operating systems that are supported for App-V Rem + + + + + @@ -630,16 +653,5 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros ## Related topics - -[Planning to Deploy App-V](appv-planning-to-deploy-appv.md) - -[App-V Prerequisites](appv-prerequisites.md) - -  - -  - - - - - +- [Planning to Deploy App-V](appv-planning-to-deploy-appv.md) +- [App-V Prerequisites](appv-prerequisites.md)

    Microsoft Windows 10

    32-bit or 64-bit

    Microsoft Windows 8.1

    Windows 10, version 1511

    32-bit or 64-bit

    Microsoft Windows 8

    Windows 10, version 1507

    32-bit or 64-bit

    Windows 7

    Windows 8.1

    32-bit or 64-bit

    Windows 8

    32-bit or 64-bit

    Windows /p>

    SP1

    32-bit or 64-bit

    Microsoft Windows Server 2016

    64-bit

    Microsoft Windows Server 2012 R2

    64-bit