deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-28 13:17:23 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Content updates we've pulled together so far

Browse Source
This commit is contained in:
JanKeller1 2016-07-29 11:53:09 -07:00
parent ebd1b53c15
commit e0a796e38f
17 changed files with 935 additions and 1378 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

156
windows/manage/appv-client-configuration-settings.md
View File

@ -1,85 +1,115 @@
---
title: About Client Configuration Settings
---
title: About Client Configuration Settings (Windows 10)
description: About Client Configuration Settings
author: jamiejdt
ms.assetid: 18bb307a-7eda-4dd6-a83e-6afaefd99470
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
---
# About Client Configuration Settings
The Microsoft Application Virtualization (App-V) 5.1 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 5.1 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 5.1 see [Administering App-V 5.1 by Using PowerShell](appv-administering-appv-with-powershell.md).
## <a href="" id="---------app-v-5-1-client-configuration-settings"></a> App-V 5.1 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](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-administering-appv-with-powershell.md).
The following table displays information about the App-V 5.1 client configuration settings:
|Setting name | Setup Flag | Description | Setting Options | Registry Key Value | Disabled Policy State Keys and Values |
|-------------|------------|-------------|-----------------|--------------------|--------------------------------------|
| PackageInstallationRoot | PACKAGEINSTALLATIONROOT | Specifies directory where all new applications and updates will be installed. | String | Streaming\PackageInstallationRoot | Policy value not written (same as Not Configured) |
| PackageSourceRoot | PACKAGESOURCEROOT | Overrides source location for downloading package content. | String | Streaming\PackageSourceRoot | Policy value not written (same as Not Configured) |
| AllowHighCostLaunch | Not available. |This setting controls whether virtualized applications are launched on Windows 10 machines connected via a metered network connection (For example, 4G). | True (enabled); False (Disabled state) | Streaming\AllowHighCostLaunch | 0 |
| ReestablishmentRetries | Not available. | Specifies the number of times to retry a dropped session. | Integer (0-99) | Streaming\ReestablishmentRetries | Policy value not written (same as Not Configured) |
| ReestablishmentInterval | Not available. | Specifies the number of seconds between attempts to reestablish a dropped session. | Integer (0-3600) | Streaming\ReestablishmentInterval | Policy value not written (same as Not Configured) |
| LocationProvider | Not available. | Specifies the CLSID for a compatible implementation of the IAppvPackageLocationProvider interface. | String | Streaming\LocationProvider | Policy value not written (same as Not Configured) |
| CertFilterForClientSsl | Not available. | Specifies the path to a valid certificate in the certificate store. | String | Streaming\CertFilterForClientSsl | Policy value not written (same as Not Configured) |
| VerifyCertificateRevocationList | Not available. | Verifies Server certificate revocation status before steaming using HTTPS. | True(enabled); False(Disabled state) | Streaming\VerifyCertificateRevocationList | 0 |
| SharedContentStoreMode | SHAREDCONTENTSTOREMODE | Specifies that streamed package contents will be not be saved to the local hard disk. | True(enabled); False(Disabled state) | Streaming\SharedContentStoreMode | 0 |
| Name<br>**Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | PUBLISHINGSERVERNAME | Displays the name of publishing server. | String | Publishing\Servers\{serverId}\FriendlyName | Policy value not written (same as Not Configured) |
| URL<br>**Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | PUBLISHINGSERVERURL | Displays the URL of publishing server. | String | Publishing\Servers\{serverId}\URL | Policy value not written (same as Not Configured) |
| GlobalRefreshEnabled<br>**Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | GLOBALREFRESHENABLED | Enables global publishing refresh (Boolean) | True(enabled); False(Disabled state) | Publishing\Servers\{serverId}\GlobalEnabled | False |
| GlobalRefreshOnLogon<br>**Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | GLOBALREFRESHONLOGON | Triggers a global publishing refresh on logon. ( Boolean) | True(enabled); False(Disabled state) | Publishing\Servers\{serverId}\GlobalLogonRefresh | False |
| GlobalRefreshInterval<br>**Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | GLOBALREFRESHINTERVAL | Specifies the publishing refresh interval using the GlobalRefreshIntervalUnit. To disable package refresh, select 0. | Integer (0-744) | Publishing\Servers\{serverId}\GlobalPeriodicRefreshInterval | 0 |
| GlobalRefreshIntervalUnit <br>**Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | GLOBALREFRESHINTERVALUNI | Specifies the interval unit (Hour 0-23, Day 0-31). | 0 for hour, 1 for day | Publishing\Servers\{serverId}\GlobalPeriodicRefreshIntervalUnit | 1 |
| UserRefreshEnabled<br>**Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | USERREFRESHENABLED | Enables user publishing refresh (Boolean) | True(enabled); False(Disabled state) | Publishing\Servers\{serverId}\UserEnabled | False |
| UserRefreshOnLogon<br>**Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | USERREFRESHONLOGON | Triggers a user publishing refresh onlogon. ( Boolean)<br>Word count (with spaces): 60 | True(enabled); False(Disabled state) | Publishing\Servers\{serverId}\UserLogonRefresh | False |
| UserRefreshInterval<br>**Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | USERREFRESHINTERVAL | Specifies the publishing refresh interval using the UserRefreshIntervalUnit. To disable package refresh, select 0. | Word count (with spaces): 85<br>Integer (0-744 Hours) | Publishing\Servers\{serverId}\UserPeriodicRefreshInterval | 0 |
| UserRefreshIntervalUnit<br>**Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | USERREFRESHINTERVALUNIT | Specifies the interval unit (Hour 0-23, Day 0-31). | 0 for hour, 1 for day | Publishing\Servers\{serverId}\UserPeriodicRefreshIntervalUnit | 1 |
| MigrationMode | MIGRATIONMODE | Migration mode allows the App-V client to modify shortcuts and FTA’s for packages created using a previous version of App-V. | True(enabled state); False (disabled state) | Coexistence\MigrationMode | |
| CEIPOPTIN | CEIPOPTIN | Allows the computer running the App-V 5.1 Client to collect and return certain usage information to help allow us to further improve the application. | 0 for disabled; 1 for enabled | SOFTWARE/Microsoft/AppV/CEIP/CEIPEnable | 0 |
| EnablePackageScripts | ENABLEPACKAGESCRIPTS | Enables scripts defined in the package manifest of configuration files that should run. | True(enabled); False(Disabled state) | \Scripting\EnablePackageScripts | |
| RoamingFileExclusions | ROAMINGFILEEXCLUSIONS | Specifies the file paths relative to %userprofile% that do not roam with a user's profile. Example usage:  /ROAMINGFILEEXCLUSIONS='desktop;my pictures' | | | |
| RoamingRegistryExclusions | ROAMINGREGISTRYEXCLUSIONS | Specifies the registry paths that do not roam with a user profile. Example usage: /ROAMINGREGISTRYEXCLUSIONS=software\\classes;software\\clients | String | Integration\RoamingReglstryExclusions | Policy value not written (same as Not Configured) |
| IntegrationRootUser | Not available. | 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.| String | Integration\IntegrationRootUser | Policy value not written (same as Not Configured) |
|IntegrationRootGlobal | Not available.| 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 | String | Integration\IntegrationRootGlobal | Policy value not written (same as Not Configured) |
| VirtualizableExtensions | Not available. | 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.<br>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.<br>For more information about the **RunVirtual** parameter, see [Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md). | String | Integration\VirtualizableExtensions | Policy value not written |
| ReportingEnabled | Not available. | Enables the client to return information to a reporting server. | True (enabled); False (Disabled state) | Reporting\EnableReporting | False |
| ReportingServerURL | Not available. | Specifies the location on the reporting server where client information is saved. | String | Reporting\ReportingServer | Policy value not written (same as Not Configured) |
| ReportingDataCacheLimit | Not available. | 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. | Integer [0-1024] | Reporting\DataCacheLimit | Policy value not written (same as Not Configured) |
| ReportingDataBlockSize| Not available. | 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. | Integer [1024 - Unlimited] | Reporting\DataBlockSize | Policy value not written (same as Not Configured) |
| ReportingStartTime | Not available. | 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 5.1 client are least likely to be offline. | Integer (0 – 23) | Reporting\ StartTime | Policy value not written (same as Not Configured) |
| ReportingInterval | Not available. | Specifies the retry interval that the client will use to resend data to the reporting server. | Integer | Reporting\RetryInterval | Policy value not written (same as Not Configured) |
| ReportingRandomDelay | Not available. | 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. | Integer [0 - ReportingRandomDelay] | Reporting\RandomDelay | Policy value not written (same as Not Configured) |
| EnableDynamicVirtualization<br>**Important** This setting is available only with App-V 5.0 SP2 or later. | Not available. | Enables supported Shell Extensions, Browser Helper Objects, and Active X controls to be virtualized and run with virtual applications. | 1 (Enabled), 0 (Disabled) | HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Client\Virtualization | |
| EnablePublishingRefreshUI<br>**Important** This setting is available only with App-V 5.0 SP2. | Not available. | Enables the publishing refresh progress bar for the computer running the App-V 5.1 Client. | 1 (Enabled), 0 (Disabled) | HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Client\Publishing | |
| HideUI<br>**Important**  This setting is available only with App-V 5.0 SP2.| Not available. | Hides the publishing refresh progress bar. | 1 (Enabled), 0 (Disabled) | | |
| ProcessesUsingVirtualComponents | Not available. | 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. | String | Virtualization\ProcessesUsingVirtualComponents | Empty string. |
## App-V Client Configuration Settings: Windows PowerShell
## Got a suggestion for App-V?
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/home?forum=mdopappv).
## Related topics
[Deploying the App-V Sequencer and Client](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-deploying-the-appv-sequencer-and-client.md)
[Deploying the App-V 5.1 Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
[How to Modify App-V 5.1 Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md)
[How to Deploy the App-V Client](appv-deploy-the-appv-client.md)
 
 
[How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](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-modify-client-configuration-with-the-admx-template-and-group-policy.md)
[How to Deploy the App-V Client](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-deploy-the-appv-client.md)

60
windows/manage/appv-connection-group-file.md
View File

@ -1,8 +1,7 @@
---
title: About the Connection Group File
title: About the Connection Group File (Windows 10)
description: About the Connection Group File
author: jamiejdt
ms.assetid: 1f4df515-f5f6-4b58-91a8-c71598cb3ea4
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -39,7 +38,7 @@ ms.prod: w10
</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 5.1 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) 5.1 connection group file to configure existing App-V 5.1 connection groups.</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>
@ -61,8 +60,6 @@ ms.prod: w10
- [App-V example connection group XML file](#bkmk-50sp3-exp-cg-xml)
- [App-V 5.0 through App-V 5.0 SP2 example connection group XML file](#bkmk-50thru50sp2-exp-cg-xm)
### <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.
@ -82,7 +79,7 @@ The following table describes the parameters in the XML file that define the con
<tr class="odd">
<td align="left"><p>Schema name</p></td>
<td align="left"><p>Name of the schema.</p>
<p><strong>Applicable starting in App-V 5.0 SP3</strong>: If you want to use the new “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>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=&quot;http://schemas.microsoft.com/appv/2014/virtualapplicationconnectiongroup&quot;</code></p></td>
</tr>
<tr class="even">
@ -133,11 +130,11 @@ In the &lt;Packages&gt; section of the connection group XML file, you list the m
<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><strong>Applicable starting in App-V 5.0 SP3</strong>: If you specify <strong>“*”</strong> for the package version, the GUID of the latest available package version is dynamically inserted.</p></td>
<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><strong>Applicable starting in App-V 5.0 SP3</strong>: Parameter that enables you to make a package optional within the connection group. Valid entries are:</p>
<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>
@ -151,15 +148,30 @@ In the &lt;Packages&gt; section of the connection group XML file, you list the m
### <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 and highlights the items that are new starting in App-V 5.0 SP3.
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-50thru50sp2-exp-cg-xm"></a>App-V 5.0 through App-V 5.0 SP2 example connection group XML file
The following example connection group XML file applies to App-V 5.0 through App-V 5.0 SP2. It shows examples of the fields in the previous table, but it excludes the changes described above for App-V 5.0 SP3.
`<?xml version="1.0" encoding="UTF-16"?>``<appv:AppConnectionGroup``xmlns="http://schemas.microsoft.com/appv/2010/virtualapplicationconnectiongroup"``xmlns:appv="http://schemas.microsoft.com/appv/2010/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="C7DF4F63-5288-439C-ACEF-EF06BF401EC5"`` />`` <appv:Package`` PackageId="04220DCA-EE77-42BE-A9F5-96FD8E8593F2"`` VersionId="E15EFFE9-043D-4C01-BC52-AD2BD1E8BAFA"`` />`` </appv:Packages>`
```
<?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
@ -270,23 +282,11 @@ The virtual application Microsoft Outlook is running in virtual environment **XY
</tbody>
</table>
 
## Got a suggestion for 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/home?forum=mdopappv).
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](http://social.technet.microsoft.com/Forums/en-US/mdopappv/threads).
## Related topics
[Managing Connection Groups](appv-managing-connection-groups.md)
 
 

54
windows/manage/appv-convert-a-package-created-in-a-previous-version-of-appv.md
View File

@ -1,8 +1,7 @@
---
title: How to Convert a Package Created in a Previous Version of App-V
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: jamiejdt
ms.assetid: 3366d399-2891-491d-8de1-f8cfdf39bbab
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -18,8 +17,6 @@ You can use the package converter utility to upgrade virtual application package
**Note**  
If you are running a computer with a 64-bit architecture, you must use the x86 version of PowerShell.
 
The package converter can only directly convert packages that were created by using the App-V 4.5 sequencer or a subsequent version. Packages that were created using a version prior to App-V 4.5 must be upgraded to the App-V 4.5 or App-V 4.6 format before conversion.
The following information provides direction for converting existing virtual application packages.
@ -27,55 +24,38 @@ The following information provides direction for converting existing virtual app
**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
**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:\\.)
When you convert packages from App-V 4.6 to 5.1, the App-V 5.1 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.
Prior to App-V 5.1, the 4.6 root folder was not recognized and could not be accessed by App-V 5.0 packages. Now, App-V 5.1 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 5.1 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 5.1 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**
## 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.
2. The following cmdlets are available:
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 -?`.
- 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 the PowerShell cmdline, 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.
- 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 5.1 virtual application package file will be saved. By default, if you do not specify a new name, the old package name will be used for the App-V 5.1 filename.
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.
Additionally, the package converter optimizes performance of packages in App-V 5.1 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**&nbsp;&nbsp;Before you specify the output directory, you must create the output directory.
**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.
**Advanced Conversion Tips**
- 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`.
- Piping - 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 5.1 client.
- 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.
- Batching - The 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`.
## Have a suggestion for App-V?
- Other functionality - 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 PowerShell and can help you create advanced scenarios for the Package Converter.
**Got 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/home?forum=mdopappv).
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](http://social.technet.microsoft.com/Forums/en-US/mdopappv/threads).
## Related topics
[Operations for App-V 5.1](appv-operations.md)
 
 
[Operations for App-V](appv-operations.md)

45
windows/manage/appv-deploy-appv-databases-with-sql-scripts.md
View File

@ -1,8 +1,7 @@
---
title: How to Deploy the App-V Databases by Using SQL Scripts
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: jamiejdt
ms.assetid: 1183b1bc-d4d7-4914-a049-06e82bf2d96d
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -22,9 +21,7 @@ Use the following instructions to use SQL scripts, rather than the Windows Insta
**Note**  
If you have already deployed the App-V 5.0 SP3 database, the SQL scripts are not required to upgrade to App-V 5.1.
 
**How to install the App-V databases by using SQL scripts**
## 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.
@ -59,21 +56,11 @@ If you have already deployed the App-V 5.0 SP3 database, the SQL scripts are not
</tbody>
</table>
 
> **Caution**&nbsp;&nbsp;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.
**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**&nbsp;&nbsp;The InsertVersionInfo.sql script is not required for versions of the App-V management database later than App-V 5.0 SP3.<br>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.
 
**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**
### Updated management database README file content
``` syntax
******************************************************************
@ -138,7 +125,7 @@ Steps to install "AppVManagement" schema in SQL SERVER.
```
**Updated reporting database README file content**
### Updated reporting database README file content
``` syntax
******************************************************************
@ -163,7 +150,6 @@ Steps to install "AppVReporting" schema in SQL SERVER.
CreateReportingStoredProcs.sql
CreateStoredProcs.sql
CreateViews.sql
InsertVersionInfo.sql
Permissions.sql
ScheduleReportingJob.sql
@ -210,26 +196,19 @@ Steps to install "AppVReporting" schema in SQL SERVER.
CreateReportingStoredProcs.sql
CreateStoredProcs.sql
CreateViews.sql
InsertVersionInfo.sql
Permissions.sql
## ScheduleReportingJob.sql
```
**Got 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/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](http://social.technet.microsoft.com/Forums/en-US/mdopappv/threads).
## Related topics
<!-- Should 5.1 be put back into the titles and-or filenames of the following related topics? -->
[Deploying the App-V 5.1 Server](appv-deploying-the-appv-server.md)
[How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.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)

83
windows/manage/appv-deploy-the-appv-client.md
View File

@ -1,8 +1,7 @@
---
title: How to Deploy the App-V Client
title: How to Deploy the App-V Client (Windows 10)
description: How to Deploy the App-V Client
author: jamiejdt
ms.assetid: 981f57c9-56c3-45da-8261-0972bfad3e5b
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -12,18 +11,17 @@ ms.prod: w10
# How to Deploy the App-V Client
Use the following procedure to install the Microsoft Application Virtualization (App-V) client and Remote Desktop Services client. You must install the version of the client that matches the operating system of the target computer.
Use the following procedure to install the Microsoft Application Virtualization (App-V) 5.1 client and Remote Desktop Services client. You must install the version of the client that matches the operating system of the target computer.
**What to do before you start**
## What to do before you start
1. Review and install the software prerequisites:
Install the prerequisite software that corresponds to the version of App-V that you are installing:
- [About App-V 5.1](appv-about-appv.md)
- [About App-V](appv-about-appv.md)
- [App-V 5.1 Prerequisites](appv-prerequisites.md)
- [App-V Prerequisites](appv-prerequisites.md)
2. Review the client coexistence and unsupported scenarios, as applicable to your installation:
@ -35,17 +33,15 @@ Use the following procedure to install the Microsoft Application Virtualization
<tbody>
<tr class="odd">
<td align="left"><p>Deploying coexisting App-V clients</p></td>
<td align="left"><p>[Planning for the App-V 5.1 Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md)</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>
</tr>
<tr class="even">
<td align="left"><p>Unsupported or limited installation scenarios</p></td>
<td align="left"><p>See the client section in [App-V 5.1 Supported Configurations](appv-supported-configurations.md)</p></td>
<td align="left"><p>See the client section in [App-V Supported Configurations](appv-supported-configurations.md)</p></td>
</tr>
</tbody>
</table>
 
3. Review the locations for client registry, log, and troubleshooting information:
<table>
@ -57,7 +53,7 @@ Use the following procedure to install the Microsoft Application Virtualization
<tr class="odd">
<td align="left"><p>Client registry information</p></td>
<td align="left"><ul>
<li><p>By default, after you install the App-V 5.1 client, the client information is stored in the registry in the following registry key:</p>
<li><p>By default, after you install the App-V client, the client information is stored in the registry in the following registry key:</p>
<p><strong>HKEY_LOCAL_MACHINE \ SOFTWARE \ MICROSOFT \ APPV \ CLIENT</strong></p></li>
<li><p>When you deploy a virtualized package to a computer that is running the App-V client, the associated package data is stored in the following location:</p>
<p><strong>C: \ ProgramData \ App-V</strong></p>
@ -68,12 +64,12 @@ Use the following procedure to install the Microsoft Application Virtualization
<tr class="even">
<td align="left"><p>Client log files</p></td>
<td align="left"><ul>
<li><p>For log file information that is associated with the App-V 5.1 Client, search in the following log:</p>
<li><p>For log file information that is associated with the App-V Client, search in the following log:</p>
<p><strong>Event logs / Applications and Services Logs / Microsoft / AppV</strong></p></li>
<li><p>In App-V 5.0 SP3, some logs were consolidated and moved to the following location:</p>
<p><strong>Event logs/Applications and Services Logs/Microsoft/AppV/ServiceLog</strong></p>
<p>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#bkmk-event-logs-moved).</p></li>
<li><p>Packages that are currently stored on computers that run the App-V 5.1 Client are saved to the following location:</p>
<li><p>Packages that are currently stored on computers that run the App-V Client are saved to the following location:</p>
<p><strong>C:\ProgramData\App-V\&lt;package id&gt;\&lt;version id&gt;</strong></p></li>
</ul></td>
</tr>
@ -84,11 +80,9 @@ Use the following procedure to install the Microsoft Application Virtualization
</tbody>
</table>
 
## To install the App-V Client
**To install the App-V 5.1 Client**
1. Copy the App-V 5.1 client installation file to the computer on which it will be installed. Choose from the following client types:
1. Copy the App-V client installation file to the computer on which it will be installed. Choose from the following client types:
<table>
<colgroup>
@ -113,9 +107,7 @@ Use the following procedure to install the Microsoft Application Virtualization
</tbody>
</table>
 
2. Double-click the installation file, and click **Install**. Before the installation begins, the installer checks the computer for any missing [App-V 5.1 Prerequisites](appv-prerequisites.md).
2. Double-click the installation file, and click **Install**. Before the installation begins, the installer checks the computer for any missing [App-V Prerequisites](appv-prerequisites.md).
3. Review and accept the Software License Terms, choose whether to use Microsoft Update and whether to participate in the Microsoft Customer Experience Improvement Program, and click **Install**.
@ -132,19 +124,15 @@ Use the following procedure to install the Microsoft Application Virtualization
**Note**  
After the installation, only the .exe file can be uninstalled.
 
**To install the App-V 5.1 client using a script**
## To install the App-V client using a script
1. Install all of the required prerequisite software on the target computers. See [What to do before you start](#bkmk-clt-install-prereqs). If you install the client by using an .msi file, the installation will fail if any prerequisites are missing.
2. To use a script to install the App-V 5.1 client, use the following parameters with **appv\_client\_setup.exe**.
2. To use a script to install the App-V client, use the following parameters with **appv\_client\_setup.exe**.
**Note**  
The client Windows Installer (.msi) supports the same set of switches, except for the **/LOG** parameter.
 
<table>
<colgroup>
<col width="50%" />
@ -173,7 +161,7 @@ Use the following procedure to install the Microsoft Application Virtualization
</tr>
<tr class="even">
<td align="left"><p>/AUTOLOAD</p></td>
<td align="left"><p>Specifies how new packages will be loaded by App-V 5.1 on a specific computer. The following options are enabled: [1]; automatically load all packages [2]; or automatically load no packages [0].<strong>Example usage: /AUTOLOAD=[0|1|2]</strong></p></td>
<td align="left"><p>Specifies how new packages will be loaded by App-V on a specific computer. The following options are enabled: [1]; automatically load all packages [2]; or automatically load no packages [0].<strong>Example usage: /AUTOLOAD=[0|1|2]</strong></p></td>
</tr>
<tr class="odd">
<td align="left"><p>/SHAREDCONTENTSTOREMODE</p></td>
@ -181,7 +169,7 @@ Use the following procedure to install the Microsoft Application Virtualization
</tr>
<tr class="even">
<td align="left"><p>/MIGRATIONMODE</p></td>
<td align="left"><p>Allows the App-V 5.1 client to modify the shortcuts and FTAs that are associated with the packages that are created with a previous version. Example usage: <strong>/MIGRATIONMODE=[0|1]</strong></p></td>
<td align="left"><p>Allows the App-V client to modify the shortcuts and FTAs that are associated with the packages that are created with a previous version. Example usage: <strong>/MIGRATIONMODE=[0|1]</strong></p></td>
</tr>
<tr class="odd">
<td align="left"><p>/ENABLEPACKAGESCRIPTS</p></td>
@ -250,7 +238,7 @@ Use the following procedure to install the Microsoft Application Virtualization
<tr class="odd">
<td align="left"><p>/NORESTART</p></td>
<td align="left"><p>Prevents the computer from rebooting after the client installation.</p>
<p>The parameter prevents the end-user computer from rebooting after each update is installed and lets you schedule the reboot at your convenience. For example, you can install App-V 5.1 and then install Hotfix Package Y without rebooting after the Service Pack installation. After the installation, you must reboot before you start using App-V.</p></td>
<p>The parameter prevents the end-user computer from rebooting after each update is installed and lets you schedule the reboot at your convenience. For example, you can install App-V and then install Hotfix Package Y without rebooting after the Service Pack installation. After the installation, you must reboot before you start using App-V.</p></td>
</tr>
<tr class="even">
<td align="left"><p>/UNINSTALL</p></td>
@ -262,7 +250,7 @@ Use the following procedure to install the Microsoft Application Virtualization
</tr>
<tr class="even">
<td align="left"><p>/LAYOUT</p></td>
<td align="left"><p>Specifies the associated layout action. It also extracts the Windows Installer (.msi) and script files to a folder without installing App-V 5.1. No value is expected.</p></td>
<td align="left"><p>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.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/LAYOUTDIR</p></td>
@ -275,13 +263,11 @@ Use the following procedure to install the Microsoft Application Virtualization
</tbody>
</table>
 
**To install the App-V 5.1 client by using the Windows Installer (.msi) file**
## To install the App-V client by using the Windows Installer (.msi) file
1. Install the required prerequisites on the target computers. See [What to do before you start](#bkmk-clt-install-prereqs). If any prerequisites are not met, the installation will fail.
2. Ensure that the target computers do not have any pending restarts before you install the client using the App-V 5.1 Windows Installer (.msi) files. The Windows Installer files do not flag a pending restart.
2. Ensure that the target computers do not have any pending restarts before you install the client using the App-V Windows Installer (.msi) files. The Windows Installer files do not flag a pending restart.
3. Deploy one of the following Windows Installer files to the target computer. The file that you specify must match the configuration of the target computer.
@ -306,23 +292,22 @@ Use the following procedure to install the Microsoft Application Virtualization
<td align="left"><p>appv_client_MSI_x64.msi</p></td>
</tr>
<tr class="odd">
<td align="left"><p>You are deploying the App-V 5.1 Remote Desktop Services client</p></td>
<td align="left"><p>You are deploying the App-V Remote Desktop Services client</p></td>
<td align="left"><p>appv_client_rds_MSI_x64.msi</p></td>
</tr>
</tbody>
</table>
 
4. Using the information in the following table, select the appropriate language pack **.msi** to install, based on the desired language for the target computer. The **xxxx** in the table refers to the target locale of the language pack.
**What to know before you start:**
- The language packs are common to both the standard App-V 5.1 client and the Remote Desktop Services version of the App-V 5.1 client.
- The language packs are common to both the standard App-V client and the Remote Desktop Services version of the App-V client.
- If you install the App-V 5.1 client using the **.exe**, the installer will deploy only the language pack that matches the operating system running on the target computer.
- If you install the App-V client using the **.exe**, the installer will deploy only the language pack that matches the operating system running on the target computer.
- To deploy additional language packs on a target computer, use the procedure **To install the App-V 5.1 client by using Windows Installer (.msi) file**.
- To deploy additional language packs on a target computer, use the procedure **To install the App-V client by using Windows Installer (.msi) file**.
<table>
<colgroup>
@ -347,24 +332,14 @@ Use the following procedure to install the Microsoft Application Virtualization
</tbody>
</table>
 
## Have a suggestion for App-V?
**Got 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/home?forum=mdopappv).
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](http://social.technet.microsoft.com/Forums/en-US/mdopappv/threads).
## Related topics
[Deploying App-V 5.1](appv-deploying-appv.md)
[Deploying App-V](appv-deploying-appv.md)
[About Client Configuration Settings](appv-client-configuration-settings.md)
[How to Uninstall the App-V 5.1 Client](appv-uninstall-the-appv-client.md)
 
 
[How to Uninstall the App-V Client](appv-uninstall-the-appv-client.md)

41
windows/manage/appv-deploy-the-appv-server.md
View File

@ -1,25 +1,22 @@
---
title: How to Deploy the App-V 5.1 Server
description: How to Deploy the App-V 5.1 Server
title: How to Deploy the App-V Server (Windows 10)
description: How to Deploy the App-V Server
author: jamiejdt
ms.assetid: 4729beda-b98f-481b-ae74-ad71c59b1d69
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
---
# How to Deploy the App-V Server
# How to Deploy the App-V 5.1 Server
Use the following procedure to install the Microsoft Application Virtualization (App-V) 5.1 server. For information about deploying the App-V 5.1 Server, see [About App-V 5.1](appv-about-appv.md#bkmk-migrate-to-51).
Use the following procedure to install the Microsoft Application Virtualization (App-V) server. For information about deploying the App-V Server, see [About App-V](appv-about-appv.md#bkmk-migrate-to-51).
**Before you start:**
- Ensure that you’ve installed prerequisite software. See [App-V 5.1 Prerequisites](appv-prerequisites.md).
- Ensure that you’ve installed prerequisite software. See [App-V Prerequisites](appv-prerequisites.md).
- Review the server section of [App-V 5.1 Security Considerations](appv-security-considerations.md).
- Review the server section of [App-V Security Considerations](appv-security-considerations.md).
- Specify a port where each component will be hosted.
@ -27,11 +24,11 @@ Use the following procedure to install the Microsoft Application Virtualization
- 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 5.1 server**
**To install the App-V server**
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it.
1. Copy the App-V server installation files to the computer on which you want to install it.
2. Start the App-V 5.1 server installation by right-clicking and running **appv\_server\_setup.exe** as an administrator, and then click **Install**.
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.
@ -63,7 +60,7 @@ Use the following procedure to install the Microsoft Application Virtualization
</tr>
<tr class="even">
<td align="left"><p>Reporting server</p></td>
<td align="left"><p>Provides App-V 5.1 reporting services.</p></td>
<td align="left"><p>Provides App-V reporting services.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Reporting database</p></td>
@ -251,24 +248,16 @@ Use the following procedure to install the Microsoft Application Virtualization
Example: **http://localhost:12345/console.html**. If the installation succeeded, the App-V Management console is displayed with no errors.
**Got 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/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](http://social.technet.microsoft.com/Forums/en-US/mdopappv/threads).
## Related topics
[Deploying App-V 5.1](appv-deploying-appv.md)
[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 5.1 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)

41
windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md
View File

@ -1,8 +1,7 @@
---
title: Deploying Microsoft Office 2010 by Using App-V
title: Deploying Microsoft Office 2010 by Using App-V (Windows 10)
description: Deploying Microsoft Office 2010 by Using App-V
author: jamiejdt
ms.assetid: ae0b0459-c0d6-4946-b62d-ff153f52d1fb
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,7 +12,7 @@ ms.prod: w10
# Deploying Microsoft Office 2010 by Using App-V
You can create Office 2010 packages for Microsoft Application Virtualization (App-V) 5.1 using one of the following methods:
You can create Office 2010 packages for Microsoft Application Virtualization (App-V) using one of the following methods:
- Application Virtualization (App-V) Sequencer
@ -36,14 +35,6 @@ The following table shows the App-V versions, methods of Office package creation
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Supported App-V versions</p></td>
<td align="left"><ul>
<li><p>4.6</p></li>
<li><p>5.0</p></li>
<li><p>5.1</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>Package creation</p></td>
<td align="left"><ul>
@ -69,17 +60,17 @@ The following table shows the App-V versions, methods of Office package creation
 
## Creating Office 2010 App-V 5.1 using the sequencer
## 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 5.1. Microsoft has provided a detailed recipe through a Knowledge Base article. To create an Office 2010 package on App-V 5.1, refer to the following link for detailed instructions:
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 5.1 packages using package accelerators
## Creating Office 2010 App-V packages using package accelerators
Office 2010 App-V 5.1 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:
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)
@ -87,7 +78,7 @@ Office 2010 App-V 5.1 packages can be created through package accelerators. Micr
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 5.1
## Deploying the Microsoft Office package for App-V
You can deploy Office 2010 packages by using any of the following App-V deployment methods:
@ -101,7 +92,7 @@ You can deploy Office 2010 packages by using any of the following App-V deployme
## Office App-V package management and customization
Office 2010 packages can be managed like any other App-V 5.1 packages through known package management mechanisms. No special instructions are needed, for example, to add, publish, unpublish, or remove Office packages.
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
@ -295,18 +286,8 @@ The following table provides a full list of supported integration points for Off
**Dynamic Configuration**
[About App-V 5.1 Dynamic Configuration](appv-dynamic-configuration.md)
## Got 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/home?forum=mdopappv).
 
 
[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](http://social.technet.microsoft.com/Forums/en-US/mdopappv/threads).

117
windows/manage/appv-deploying-the-appv-server.md
View File

@ -1,82 +1,80 @@
---
title: Deploying the App-V 5.1 Server
description: Deploying the App-V 5.1 Server
title: Deploying the App-V Server (Windows 10)
description: Deploying the App-V Server
author: jamiejdt
ms.assetid: 987b61dc-00d6-49ba-8f1b-92d7b948e702
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
---
# Deploying the App-V Server
# Deploying the App-V 5.1 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).
For information about deploying the App-V Server, see [About App-V](appv-about-appv.md#bkmk-migrate-to-51).
You can install the Microsoft Application Virtualization (App-V) 5.1 server features by using different deployment configurations, which described in this topic. Before you install the server features, review the server section of [App-V 5.1 Security Considerations](appv-security-considerations.md).
> **Important**&nbsp;&nbsp;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.
For information about deploying the App-V Server, see [About App-V 5.1](appv-about-appv.md#bkmk-migrate-to-51).
## App-V Server overview
**Important**  
Before you install and configure the App-V 5.1 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.
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.
## <a href="" id="---------app-v-5-1-server-overview"></a> App-V 5.1 Server overview
**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.
- 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.
- 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 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.
## <a href="" id="---------app-v-5-1-stand-alone-deployment"></a> App-V stand-alone deployment
The App-V 5.1 Server is made up of five components. Each component serves a different purpose within the App-V 5.1 environment. Each of the five components is briefly described here:
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.
- Management Server – provides overall management functionality for the App-V 5.1 infrastructure.
[How to Deploy the App-V Server](appv-deploy-the-appv-server.md)
- Management Database – facilitates database predeployments for App-V 5.1 management.
[How to Deploy the App-V Server Using a Script](appv-deploy-the-appv-server-with-a-script.md)
- Publishing Server – provides hosting and streaming functionality for virtual applications.
## <a href="" id="---------app-v-5-1-server-distributed-deployment"></a> App-V Server distributed deployment
- Reporting Server – provides App-V 5.1 reporting services.
- Reporting Database – facilitates database predeployments for App-V 5.1 reporting.
## <a href="" id="---------app-v-5-1-stand-alone-deployment"></a> App-V 5.1 stand-alone deployment
The App-V 5.1 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 5.1 components. Therefore, you should not use this topology for larger deployments.
[How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md)
[How to Deploy the App-V 5.1 Server Using a Script](appv-deploy-the-appv-server-with-a-script.md)
## <a href="" id="---------app-v-5-1-server-distributed-deployment"></a> App-V 5.1 Server distributed deployment
The distributed deployment topology can support a large App-V 5.1 client base and it allows you to more easily manage and scale your environment. When you use this type of deployment, the App-V 5.1 Server components are deployed across multiple computers, based on the structure and requirements of the organization.
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 5.1 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)
[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 5.1
## 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.
You can also deploy the App-V 5.1 clients and packages by using an ESD without having to deploy App-V 5.1. The full capabilities for integration will vary depending on the ESD that you use.
> **Note**&nbsp;&nbsp;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 5.1 reporting server and reporting database can still be deployed alongside the ESD to collect the reporting data from the App-V 5.1 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)
 
## <a href="" id="---------app-v-5-1-server-logs"></a> App-V Server logs
[Deploying App-V 5.1 Packages by Using Electronic Software Distribution (ESD)](appv-deploying-packages-with-electronic-software-distribution-solutions.md)
## <a href="" id="---------app-v-5-1-server-logs"></a> App-V 5.1 Server logs
You can use App-V 5.1 server log information to help troubleshoot the server installation and operational events while using App-V 5.1. The server-related log information can be reviewed with the **Event Viewer**. The following line displays the specific path for Server-related events:
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**
@ -84,42 +82,27 @@ Associated setup logs are saved in the following directory:
**%temp%**
In App-V 5.0 SP3, some logs were consolidated and moved. See [About App-V 5.0 SP3](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/about-app-v-50-sp3#bkmk-event-logs-moved).
## <a href="" id="---------app-v-5-1-reporting"></a> App-V reporting
## <a href="" id="---------app-v-5-1-reporting"></a> App-V 5.1 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.
App-V 5.1 reporting allows App-V 5.1 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 5.1 client collects:
- Information about the computer that runs the App-V 5.1 client.
- Information about virtualized packages on a specific computer that runs the App-V 5.1 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 5.1 reporting server and it must be deployed separately to generate the associated 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.
Use the following link for more information [About App-V 5.1 Reporting](appv-reporting.md).
[How to Enable Reporting on the App-V 5.1 Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)
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)
[Deploying App-V 5.1](appv-deploying-appv.md)
## Got 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/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](http://social.technet.microsoft.com/Forums/en-US/mdopappv/threads).

1034
windows/manage/appv-dynamic-configuration.md
View File

File diff suppressed because it is too large Load Diff

41
windows/manage/appv-enable-the-app-v-desktop-client.md Normal file
View File

@ -0,0 +1,41 @@
---
title: Enable the App-V desktop client (Windows 10)
description: Enable the App-V desktop client
author: jamiejdt
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** &gt; **Administrative Templates** &gt; **System** &gt; **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](http://social.technet.microsoft.com/Forums/en-US/mdopappv/threads).

131
windows/manage/appv-getting-started.md
View File

@ -1,8 +1,7 @@
---
title: Getting Started with App-V 5.1
description: Getting Started with App-V 5.1
title: Getting Started with App-V (Windows 10)
description: Getting Started with App-V
author: jamiejdt
ms.assetid: 49a20e1f-0566-4e53-a417-1521393fc974
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,127 +9,71 @@ ms.prod: w10
---
# Getting Started with App-V 5.1
# Getting Started with App-V
Microsoft Application Virtualization (App-V) 5.1 enables administrators to deploy, update, and support applications as services in real time, on an as-needed basis. Individual applications are transformed from locally installed products into centrally managed services and are available wherever you need, without the need to preconfigure computers or to change operating system settings.
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.
App-V consists of the following elements:
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 [App-V Administrator's Guide](appv-microsoft-application-virtualization-administrators-guide.md).
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Element</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>App-V Management Server</p></td>
<td align="left"><ul>
<li><p>Provides a central location for managing the App-V infrastructure, which delivers virtual applications to both the App-V Desktop Client and the Remote Desktop Services (formerly Terminal Services) Client.</p></li>
<li><p>Uses Microsoft SQL Server® for its data store, where one or more App-V Management servers can share a single SQL Server data store.</p></li>
<li><p>Authenticates requests and provides security, metering, monitoring, and data gathering. The server uses Active Directory and supporting tools to manage users and applications.</p></li>
<li><p>Has a management site that lets you configure the App-V infrastructure from any computer. You can add and remove applications, manipulate shortcuts, assign access permissions to users and groups, and create connection groups.</p></li>
<li><p>Enables communication between the App-V Web Management Console and the SQL Server data store. These components can all be installed on a single server computer, or on one or more separate computers, depending on the required system architecture.</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>App-V Publishing Server</p></td>
<td align="left"><ul>
<li><p>Provides App-V Clients with entitled applications for the specific user</p></li>
<li><p>Hosts the virtual application package for streaming.</p></li>
</ul></td>
</tr>
<tr class="odd">
<td align="left"><p>App-V Desktop Client</p></td>
<td align="left"><ul>
<li><p>Retrieves virtual applications</p></li>
<li><p>Publishes the applications on the clients</p></li>
<li><p>Automatically sets up and manages virtual environments at runtime on Windows endpoints.</p></li>
<li><p>Stores user-specific virtual application settings, such as registry and file changes, in each user's profile.</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>App-V Remote Desktop Services (RDS) Client</p></td>
<td align="left"><p>Enables Remote Desktop Session Host servers to use the capabilities of the App-V Desktop Client for shared desktop sessions.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>App-V Sequencer</p></td>
<td align="left"><ul>
<li><p>Is a wizard-based tool that you use to transform traditional applications into virtual applications.</p></li>
<li><p>Produces the application “package,” which consists of:</p>
<ol>
<li><p>a sequenced application (APPV) file</p></li>
<li><p>a Windows Installer file (MSI) that can be deployed to clients configured for stand-alone operation</p></li>
<li><p>Several XML files including Report.XML, PackageName_DeploymentConfig.XML, and PackageName_UserConfig.XML. The UserConfig and DeploymentConfig XML files are used to configure custom changes to the default behavior of the package.</p></li>
</ol></li>
</ul></td>
</tr>
</tbody>
</table>
If you’re already using App-V 5.1, 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-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 more information about these elements, see [High Level Architecture for App-V 5.1](appv-high-level-architecture.md).
For information about previous versions of App-V, see [MDOP Information Experience](https://technet.microsoft.com/itpro/mdop/index).
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 more information about Microsoft training opportunities, see the Microsoft Training Overview at <http://go.microsoft.com/fwlink/p/?LinkId=80347>.
## Getting started with App-V for Windows 10 (new installations)
**Note**  
A downloadable version of this administrator’s guide is not available. However, you can learn about a special mode of the TechNet Library that allows you to select articles, group them in a collection, and print them or export them to a file at <http://go.microsoft.com/fwlink/?LinkId=272491> (http://go.microsoft.com/fwlink/?LinkId=272491).
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.
 
| 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 | 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](enable-the-app-v-desktop-client.md). |
| App-V Remote Desktop Services (RDS) Client | . | . |
| 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). |
This section of the App-V 5.1 Administrator’s Guide includes high-level information about App-V 5.1 to provide you with a basic understanding of the product before you begin the deployment planning.
<!-- The link above to enable-the-app-v-desktop-client.md does not correspond with a topic-file yet. -->
## Getting started with App-V 5.1
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 5.1](appv-about-appv.md)
- [About App-V](appv-about-appv.md)
Provides a high-level overview of App-V 5.1 and how it can be used in your organization.
Provides a high-level overview of App-V and how it can be used in your organization.
- [Evaluating App-V 5.1](appv-evaluating-appv.md)
- [Evaluating App-V](appv-evaluating-appv.md)
Provides information about how you can best evaluate App-V 5.1 for use in your organization.
Provides information about how you can best evaluate App-V for use in your organization.
- [High Level Architecture for App-V 5.1](appv-high-level-architecture.md)
- [High Level Architecture for App-V](appv-high-level-architecture.md)
Provides a description of the App-V 5.1 features and how they work together.
Provides a description of the App-V features and how they work together.
- [Accessibility for App-V 5.1](appv-accessibility.md)
- [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
- [Microsoft Application Virtualization 5.1 Administrator's Guide](appv-microsoft-application-virtualization-administrators-guide.md)
- [Microsoft Application Virtualization Administrator's Guide](appv-microsoft-application-virtualization-administrators-guide.md)
- [Planning for App-V 5.1](appv-planning-for-appv.md)
- [Planning for App-V](appv-planning-for-appv.md)
- [Deploying App-V 5.1](appv-deploying-appv.md)
- [Deploying App-V](appv-deploying-appv.md)
- [Operations for App-V 5.1](appv-operations.md)
- [Troubleshooting App-V 5.1](appv-troubleshooting.md)
- [Technical Reference for App-V 5.1](appv-technical-reference.md)
## Got 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/home?forum=mdopappv).
 
 
- [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](http://social.technet.microsoft.com/Forums/en-US/mdopappv/threads).

45
windows/manage/appv-high-level-architecture.md
View File

@ -1,8 +1,7 @@
---
title: High Level Architecture for App-V 5.1
description: High Level Architecture for App-V 5.1
title: High Level Architecture for App-V (Windows 10)
description: High Level Architecture for App-V
author: jamiejdt
ms.assetid: 90406361-55b8-40b7-85c0-449436789d4c
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,15 +9,15 @@ ms.prod: w10
---
# High Level Architecture for App-V 5.1
# High Level Architecture for App-V
Use the following information to help you simplify you Microsoft Application Virtualization (App-V) 5.1 deployment.
Use the following information to help you simplify you Microsoft Application Virtualization (App-V) deployment.
## Architecture Overview
A typical App-V 5.1 implementation consists of the following elements.
A typical App-V implementation consists of the following elements.
<table>
<colgroup>
@ -33,49 +32,45 @@ A typical App-V 5.1 implementation consists of the following elements.
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>App-V 5.1 Management Server</p></td>
<td align="left"><p>The App-V 5.1 Management server provides overall management functionality for the App-V 5.1 infrastructure. Additionally, you can install more than one instance of the management server in your environment which provides the following benefits:</p>
<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 5.1 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 5.1 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>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 5.1 Publishing Server</p></td>
<td align="left"><p>The App-V 5.1 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>
<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 5.1 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>
<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 5.1 Reporting Server</p></td>
<td align="left"><p>The App-V 5.1 Reporting server enables authorized users to run and view existing App-V 5.1 reports and ad hoc reports that can help them manage the App-V 5.1 infrastructure. The Reporting server requires a connection to the App-V 5.1 reporting database. You can also help increase App-V 5.1 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>
<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 5.1 Client</p></td>
<td align="left"><p>The App-V 5.1 client enables packages created using App-V 5.1 to run on target computers.</p></td>
<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 5.1 with Electronic Software Distribution (ESD) you are not required to use the App-V 5.1 Management server, however you can still utilize the reporting and streaming functionality of App-V 5.1.
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?
## Got 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/home?forum=mdopappv).
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](http://social.technet.microsoft.com/Forums/en-US/mdopappv/threads).
## Related topics
[Getting Started with App-V 5.1](appv-getting-started.md)
[Getting Started with App-V](appv-getting-started.md)
 

120
windows/manage/appv-install-the-sequencer.md
View File

@ -1,8 +1,7 @@
---
title: How to Install the Sequencer
description: How to Install the Sequencer
title: Install the App-V Sequencer (Windows 10)
description: Install the App-V Sequencer
author: jamiejdt
ms.assetid: 5e8f1696-9bc0-4f44-8cb7-b809b2daae10
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,101 +9,50 @@ ms.prod: w10
---
# How to Install the Sequencer
# 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/en-us/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. On the screen pictured below, select **Microsoft Application Virtualization (App-V) Sequencer** and then click or press **Install**.
Use the following procedure to install the Microsoft Application Virtualization (App-V) 5.1 sequencer. The computer that will run the sequencer must not be running any version of the App-V 5.1 client.
![Selecting APP-V features in ADK](images/appv-adk-select-appv-feature.png)
Upgrading a previous installation of the App-V sequencer is not supported.
3. To open the Sequencer, from the **Start** menu, select **Microsoft Application Virtualization Sequencer** .
**Important**  
For a full list of the sequencer requirements see sequencer sections of [App-V 5.1 Prerequisites](appv-prerequisites.md) and [App-V 5.1 Supported Configurations](appv-supported-configurations.md).
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 5.1 sequencer. The following list displays information about options for installing the sequencer using the command line and **appv\_sequencer\_setup.exe**:
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**:
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Command</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>/INSTALLDIR</p></td>
<td align="left"><p>Specifies the installation directory.</p></td>
</tr>
<tr class="even">
<td align="left"><p>/CEIPOPTIN</p></td>
<td align="left"><p>Enables participation in the Microsoft Customer Experience Improvement Program.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/Log</p></td>
<td align="left"><p>Specifies where the installation log will be saved, the default location is <strong>%Temp%</strong>. For example, <strong>C:\ Logs \ log.log</strong>.</p></td>
</tr>
<tr class="even">
<td align="left"><p>/q</p></td>
<td align="left"><p>Specifies a quiet or silent installation.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/Uninstall</p></td>
<td align="left"><p>Specifies the removal of the sequencer.</p></td>
</tr>
<tr class="even">
<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>
<tr class="odd">
<td align="left"><p>/LAYOUT</p></td>
<td align="left"><p>Specifies the associated layout action. It also extracts the Windows Installer (.msi) and script files to a folder without installing App-V 5.1. 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. Requires a string value. Example usage: <strong>/LAYOUTDIR=”C:\Application Virtualization Client”</strong>.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/? Or /h or /help</p></td>
<td align="left"><p>Displays associated help.</p></td>
</tr>
</tbody>
</table>
| **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
**To install the App-V 5.1 sequencer**
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**.
1. Copy the App-V 5.1 sequencer installation files to the computer on which it will be installed. Double-click **appv\_sequencer\_setup.exe** and then click **Install**.
## Have a suggestion for App-V?
2. On the **Software License Terms** page, you should review the license terms. To accept the license terms select **I accept the license terms.** 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 from running select **I don’t want to use Microsoft Update**. Click **Next**.
4. On the **Customer Experience Improvement Program** page, to participate in the program select **Join the Customer Experience Improvement Program**. This will allow information to be collected about how you are using App-V 5.1. If you don’t want to participate in the program select **I don’t want to join the program at this time**. Click **Install**.
5. To open the sequencer, click **Start** and then click **Microsoft Application Virtualization Sequencer**.
**To troubleshoot the App-V 5.1 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**.
**Got 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/home?forum=mdopappv).
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](http://social.technet.microsoft.com/Forums/en-US/mdopappv/threads).
## Related topics
[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
 
 

58
windows/manage/appv-planning-folder-redirection-with-appv.md
View File

@ -1,19 +1,16 @@
---
title: Planning to Use Folder Redirection with App-V
title: Planning to Use Folder Redirection with App-V (Windows 10)
description: Planning to Use Folder Redirection with App-V
author: jamiejdt
ms.assetid: 6bea9a8f-a915-4d7d-be67-ef1cca1398ed
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) 5.1 supports the use of folder redirection, a feature that enables users and administrators to redirect the path of a folder to a new location.
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:
@ -46,7 +43,7 @@ This topic contains the following sections:
<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 5.0 SP2 or later client:</p>
<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>
@ -58,30 +55,7 @@ This topic contains the following sections:
<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 as follows:</p>
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">App-V version</th>
<th align="left">Scenario description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>In App-V 5.0 through App-V 5.0 SP2 plus hotfixes</p></td>
<td align="left"><p>This failure will occur regardless of whether Offline Files is enabled.</p></td>
</tr>
<tr class="even">
<td align="left"><p>In App-V 5.0 SP3 and later</p></td>
<td align="left"><p>If the unavailable network share has been enabled for Offline Files, the App-V application will start successfully.</p></td>
</tr>
</tbody>
</table>
<p> </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>
@ -121,13 +95,7 @@ The following table describes how folder redirection works when %AppData% is red
<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>
<div class="alert">
<strong>Note</strong>  
<p>The App-V client folder redirection sometimes fails to move files from %AppData% to %LocalAppData%. See [Release Notes for App-V 5.0 SP2](appv-release-notes-for-appv-for-windows.md#bkmk-folderredirection).</p>
</div>
<div>
 
</div></td>
</td>
</tr>
<tr class="even">
<td align="left"><p>When the virtual environment shuts down</p></td>
@ -173,18 +141,6 @@ The following table describes how folder redirection works when %AppData% is red
</tbody>
</table>
 
## Got 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/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](http://social.technet.microsoft.com/Forums/en-US/mdopappv/threads).

71
windows/manage/appv-planning-for-high-availability-with-appv.md
View File

@ -1,8 +1,7 @@
---
title: Planning for High Availability with App-V 5.1
description: Planning for High Availability with App-V 5.1
title: Planning for High Availability with App-V 5.1 Server
description: Planning for High Availability with App-V 5.1 Server
author: jamiejdt
ms.assetid: 1f190a0e-10ee-4fbe-a602-7e807e943033
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,8 +9,7 @@ ms.prod: w10
---
# Planning for High Availability with App-V 5.1
# Planning for High Availability with App-V 5.1 Server
Microsoft Application Virtualization (App-V) 5.1 system configurations can take advantage of options that maintain a high level of available service.
@ -43,54 +41,50 @@ Review the following for more information about configuring IIS and Network Load
- Provides information about configuring Internet Information Services (IIS) 7.0.
[Achieving High Availability and Scalability - ARR and NLB](http://go.microsoft.com/fwlink/?LinkId=316369) (http://go.microsoft.com/fwlink/?LinkId=316369)
[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](http://go.microsoft.com/fwlink/?LinkId=316370) (http://go.microsoft.com/fwlink/?LinkId=316370).
[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 Server 2012 R2 Preview and Windows Server 2012](http://go.microsoft.com/fwlink/?LinkId=316371) (http://go.microsoft.com/fwlink/?LinkId=316371).
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
## <a href="" id="bkmk-clusterscsmode"></a>Support for clustered file servers when running (SCS) mode
Running App-V 5.1 in Share Content Store (SCS) mode with clustered file servers is supported.
Running App-V 5.1 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 5.1 to run in client SCS mode. For more information about configuring App-V 5.1 SCS mode, see [How to Install the App-V 5.1 Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md).
- 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 both the Microsoft Server 2012 scale out mode and pre **2012** mode with a virtual SAN.
- 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 5.1 client and open an application.
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 fail-over works correctly.
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:
- [Checklist: Create a Clustered File Server](http://go.microsoft.com/fwlink/?LinkId=316372) (http://go.microsoft.com/fwlink/?LinkId=316372).
- [Create a Failover Cluster](https://technet.microsoft.com/library/dn505754(v=ws.11).aspx).
- [Use Cluster Shared Volumes in a Windows Server 2012 Failover Cluster](http://go.microsoft.com/fwlink/?LinkId=316373) (http://go.microsoft.com/fwlink/?LinkId=316373).
- [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 5.1 management server database is mirrored utilizing two SQL Server instances, for App-V 5.1 management server databases is supported.
Review the following for more information about configuring Microsoft SQL Server Mirroring:
- [How to: Prepare a Mirror Database for Mirroring (Transact-SQL)](http://go.microsoft.com/fwlink/?LinkId=316375) (http://go.microsoft.com/fwlink/?LinkId=316375)
- [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)](http://go.microsoft.com/fwlink/?LinkId=316377) (http://go.microsoft.com/fwlink/?LinkId=316377)
- [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:
@ -100,14 +94,13 @@ The following steps can be used to validate the configuration:
3. Verify that the App-V 5.1 management server continues to function as expected after the failover.
The connection string on the management server can be modified to include **failover partner = &lt;server2&gt;**. This will only help when the primary on the mirror has failed over to the secondary and the computer running the App-V 5.1 client is doing a fresh connection (say after reboot).
The connection string on the management server can be modified to include **failover partner = &lt;server2&gt;**. 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 = &lt;server2&gt;**:
**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**.
@ -118,40 +111,24 @@ This topic describes how to change the Windows registry by using Registry Editor
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 with Microsoft SQL Server 2012.
 
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:
- [How to: Prepare a Mirror Database for Mirroring (Transact-SQL)](http://go.microsoft.com/fwlink/?LinkId=394235) (http://go.microsoft.com/fwlink/?LinkId=394235).
- [Prepare a Mirror Database for Mirroring (SQL Server)](https://technet.microsoft.com/library/ms189053.aspx).
- [How to: Configure a Database Mirroring Session (SQL Server Management Studio)](http://go.microsoft.com/fwlink/?LinkId=394236) (http://go.microsoft.com/fwlink/?LinkId=394236).
- [Establish a Database Mirroring Session Using Windows Authentication (SQL Server Management Studio)](https://technet.microsoft.com/library/ms188712(v=sql.130).aspx).
- [Establish a Database Mirroring Session Using Windows Authentication (SQL Server Management Studio)](http://go.microsoft.com/fwlink/?LinkId=394237) (http://go.microsoft.com/fwlink/?LinkId=394237).
- [Deprecated Database Engine Features in SQL Server 2012](http://go.microsoft.com/fwlink/?LinkId=394238) (http://go.microsoft.com/fwlink/?LinkId=394238).
- [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 5.1 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).
The App-V 5.1 management server database supports deployments to computers running Microsoft SQL Server with the **Always On** configuration.
## Have a suggestion for App-V?
## Got 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/home?forum=mdopappv).
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](http://social.technet.microsoft.com/Forums/en-US/mdopappv/threads).
## Related topics
[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
 
 

111
windows/manage/appv-planning-for-using-appv-with-office.md
View File

@ -1,8 +1,7 @@
---
title: Planning for Using App-V with Office
title: Planning for Using App-V with Office (Windows 10)
description: Planning for Using App-V with Office
author: jamiejdt
ms.assetid: e7a19b43-1746-469f-bad6-8e75cf4b3f67
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -12,8 +11,7 @@ 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) 5.1. This article includes:
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)
@ -25,8 +23,7 @@ Use the following information to plan how to deploy Office by using Microsoft Ap
## <a href="" id="bkmk-lang-pack"></a>App-V support for Language Packs
You can use the App-V 5.1 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.
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.
@ -44,12 +41,10 @@ The following table lists the versions of Microsoft Office that App-V supports,
<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">Supported App-V Versions</th>
<th align="left">Package Creation</th>
<th align="left">Supported Licensing</th>
<th align="left">Supported Deployments</th>
@ -63,13 +58,6 @@ The following table lists the versions of Microsoft Office that App-V supports,
<li><p>Visio Pro for Office 365</p></li>
<li><p>Project Pro for Office 365</p></li>
</ul></td>
<td align="left"><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>
<li><p>App-V 5.1</p></li>
</ul></td>
<td align="left"><p>Office Deployment Tool</p></td>
<td align="left"><p>Subscription</p></td>
<td align="left"><ul>
@ -86,13 +74,6 @@ The following table lists the versions of Microsoft Office that App-V supports,
<li><p>Visio Professional 2013</p></li>
<li><p>Project Professional 2013</p></li>
</ul></td>
<td align="left"><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>
<li><p>App-V 5.1</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>
@ -110,7 +91,7 @@ The following table lists the versions of Microsoft Office that App-V supports,
## <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 5.1. However, using Office coexistence is not recommended by Microsoft.
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.
@ -295,72 +276,8 @@ The Office 2013 App-V package supports the following integration points with the
<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](http://go.microsoft.com/fwlink/p/?LinkId=331361).</p></td>
</tr>
<tr class="odd">
<td align="left"><p>   Groove.SiteClient</p></td>
<td align="left"><p>Active X Control</p></td>
</tr>
<tr class="even">
<td align="left"><p>   PortalConnect.PersonalSite</p></td>
<td align="left"><p>Active X Control</p></td>
</tr>
<tr class="odd">
<td align="left"><p>   SharePoint.openDocuments</p></td>
<td align="left"><p>Active X Control</p></td>
</tr>
<tr class="even">
<td align="left"><p>   SharePoint.ExportDatabase</p></td>
<td align="left"><p>Active X Control</p></td>
</tr>
<tr class="odd">
<td align="left"><p>   SharePoint.SpreadSheetLauncher</p></td>
<td align="left"><p>Active X Control</p></td>
</tr>
<tr class="even">
<td align="left"><p>   SharePoint.StssyncHander</p></td>
<td align="left"><p>Active X Control</p></td>
</tr>
<tr class="odd">
<td align="left"><p>   SharePoint.DragUploadCtl</p></td>
<td align="left"><p>Active X Control</p></td>
</tr>
<tr class="even">
<td align="left"><p>   SharePoint.DragDownloadCtl</p></td>
<td align="left"><p>Active X Control</p></td>
</tr>
<tr class="odd">
<td align="left"><p>   Sharepoint.OpenXMLDocuments</p></td>
<td align="left"><p>Active X Control</p></td>
</tr>
<tr class="even">
<td align="left"><p>   Sharepoint.ClipboardCtl</p></td>
<td align="left"><p>Active X control</p></td>
</tr>
<tr class="odd">
<td align="left"><p>   WinProj.Activator</p></td>
<td align="left"><p>Active X Control</p></td>
</tr>
<tr class="even">
<td align="left"><p>   Name.NameCtrl</p></td>
<td align="left"><p>Active X Control</p></td>
</tr>
<tr class="odd">
<td align="left"><p>   STSUPld.CopyCtl</p></td>
<td align="left"><p>Active X Control</p></td>
</tr>
<tr class="even">
<td align="left"><p>   CommunicatorMeetingJoinAx.JoinManager</p></td>
<td align="left"><p>Active X Control</p></td>
</tr>
<tr class="odd">
<td align="left"><p>   LISTNET.Listnet</p></td>
<td align="left"><p>Active X Control</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>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>
@ -381,18 +298,6 @@ The Office 2013 App-V package supports the following integration points with the
</tbody>
</table>
 
## Got 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/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](http://social.technet.microsoft.com/Forums/en-US/mdopappv/threads).

105
windows/manage/appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md Normal file
View File

@ -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: jamiejdt
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 5.1 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](http://social.technet.microsoft.com/Forums/en-US/mdopappv/threads).