Description |
+Stores package documents that are available to users on the machine, when packages are added and published. However, if a package is “global” at publishing time, the integrations are available to all users. +If a package is non-global, the integrations are published only for specific users, but there are still global resources that are modified and visible to anyone on the client computer (e.g., the package directory is in a shared disk location). +If a package is available to a user on the computer (global or non-global), the manifest is stored in the Machine Catalog. When a package is published globally, there is a Dynamic Configuration file, stored in the Machine Catalog; therefore, the determination of whether a package is global is defined according to whether there is a policy file (UserDeploymentConfiguration file) in the Machine Catalog. |
+
Default storage location |
+
This location is not the same as the Package Store location. The Package Store is the golden or pristine copy of the package files. |
+
Files in the machine catalog |
+
|
+
Additional machine catalog location, used when the package is part of a connection group |
+The following location is in addition to the specific package location mentioned above: +
|
+
Additional files in the machine catalog when the package is part of a connection group |
+
|
+
Description |
+Created during the publishing process. Contains information used for publishing the package, and also used at launch to ensure that a package is provisioned to a specific user. Created in a roaming location and includes user-specific publishing information. +When a package is published for a user, the policy file is stored in the User Catalog. At the same time, a copy of the manifest is also stored in the User Catalog. When a package entitlement is removed for a user, the relevant package files are removed from the User Catalog. Looking at the user catalog, an administrator can view the presence of a Dynamic Configuration file, which indicates that the package is entitled for that user. +For roaming users, the User Catalog needs to be in a roaming or shared location to preserve the legacy App-V behavior of targeting users by default. Entitlement and policy are tied to a user, not a computer, so they should roam with the user once they are provisioned. |
+
Default storage location |
+
|
+
Files in the user catalog |
+
|
+
Additional user catalog location, used when the package is part of a connection group |
+The following location is in addition to the specific package location mentioned above: +
|
+
Additional file in the machine catalog when the package is part of a connection group |
+
|
+
Registry.dat from Package Store |
+> |
+%ProgramData%\Microsoft\AppV\Client\Vreg\{VersionGuid}.dat |
+
Location |
+Description |
+
COW |
+
|
+
Package |
+
|
+
Native |
+
|
+
Location |
+Description |
+
COW |
+
|
+
Package |
+
|
+
Native |
+
|
+
| Policy | +Description | +
|---|---|
AllowHighCostLaunch |
+On Windows 8 and later, it allows streaming over 3G and cellular networks |
+
AutoLoad |
+Specifies the Background Load setting: +0 - Disabled +1 – Previously Used Packages only +2 – All Packages |
+
PackageInstallationRoot |
+The root folder for the package store in the local machine |
+
PackageSourceRoot |
+The root override where packages should be streamed from |
+
SharedContentStoreMode |
+Enables the use of Shared Content Store for VDI scenarios |
+
| Scenario | +Description | +
|---|---|
Applications that are run as standard users |
+When a standard user launches an App-V application, both HKLM and HKCU for App-V applications are stored in the HKCU hive on the machine. This presents as two distinct paths: +
The locations are enabled for roaming based on the operating system settings. |
+
Applications that are run with elevation |
+When an application is launched with elevation: +
In this scenario, these settings are not roamed with normal operating system roaming configurations, and the resulting registry keys and values are stored in the following location: +
|
+
| VFS directory in package | +Mapped location of backing store | +
|---|---|
ProgramFilesX86 |
+C:\users\jsmith\AppData\Local\Microsoft\AppV\Client\VFS\<GUID>\ProgramFilesX86 |
+
SystemX86 |
+C:\users\jsmith\AppData\Local\Microsoft\AppV\Client\VFS\<GUID>\SystemX86 |
+
Windows |
+C:\users\jsmith\AppData\Local\Microsoft\AppV\Client\VFS\<GUID>\Windows |
+
appv_ROOT |
+C:\users\jsmith\AppData\Local\Microsoft\AppV\Client\VFS\<GUID>\appv_ROOT |
+
AppData |
+C:\users\jsmith\AppData\Roaming\Microsoft\AppV\Client\VFS\<GUID>\AppData |
+
| VFS directory in package | +Mapped location of backing store | +
|---|---|
ProgramFilesX86 |
+C:\users\jsmith\AppData\Local\Microsoft\AppV\Client\VFS\<GUID>\ProgramFilesX86 |
+
SystemX86 |
+C:\users\jsmith\AppData\Local\Microsoft\AppV\Client\VFS\<GUID>\SystemX86 |
+
Windows |
+C:\users\jsmith\AppData\Local\Microsoft\AppV\Client\VFS\<GUID>\Windows |
+
appv_ROOT |
+C:\users\jsmith\AppData\Local\Microsoft\AppV\Client\VFS\<GUID>\appv_ROOT |
+
AppData |
+\\Fileserver\users\jsmith\roaming\Microsoft\AppV\Client\VFS\<GUID>\AppData |
+
| Task type | +Applicable rule | +
|---|---|
User-based task, e.g., publishing a package to a user |
+The pending task will be performed after the user logs off and then logs back on. |
+
Globally based task, e.g., enabling a connection group globally |
+The pending task will be performed when the computer is shut down and then restarted. |
+
| User-based or globally based task | +Where the registry key is generated | +
|---|---|
User-based tasks |
+KEY_CURRENT_USER\Software\Microsoft\AppV\Client\PendingTasks |
+
Globally based tasks |
+HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Client\PendingTasks |
+
| Task | +Details | +
|---|---|
Add the package to the computer |
+This task is computer specific and you can perform it at any time by completing the steps in the Package Add section above. |
+
Publish the package |
+See the Package Publishing section above for steps. This process requires that you update extension points on the system. End users cannot be using the application when you complete this task. |
+
| Scenario | +Requirements | +
|---|---|
App-V package is not in use when you try to upgrade |
+None of the following components of the package can be in use: virtual application, COM server, or shell extensions. +The administrator publishes a newer version of the package and the upgrade works the next time a component or application inside the package is launched. The new version of the package is streamed and run. Nothing has changed in this scenario in App-V 5 SP2 from previous releases of App-V 5. |
+
App-V package is in use when the administrator publishes a newer version of the package |
+The upgrade operation is set to pending by the App-V Client, which means that it is queued and carried out later when the package is not in use. +If the package application is in use, the user shuts down the virtual application, after which the upgrade can occur. +If the package has shell extensions (Office 2013), which are permanently loaded by Windows Explorer, the user cannot be logged in. Users must log off and the log back in to initiate the App-V package upgrade. |
+
| Handler | +Description | +
|---|---|
Context menu handler |
+Adds menu items to the context menu. It is called before the context menu is displayed. |
+
Drag-and-drop handler |
+Controls the action upon right-click drag-and-drop and modifies the context menu that appears. |
+
Drop target handler |
+Controls the action after a data object is dragged-and-dropped over a drop target such as a file. |
+
Data object handler |
+Controls the action after a file is copied to the clipboard or dragged-and-dropped over a drop target. It can provide additional clipboard formats to the drop target. |
+
Property sheet handler |
+Replaces or adds pages to the property sheet dialog box of an object. |
+
Infotip handler |
+Allows retrieving flags and infotip information for an item and displaying it inside a popup tooltip upon mouse- hover. |
+
Column handler |
+Allows creating and displaying custom columns in Windows Explorer Details view. It can be used to extend sorting and grouping. |
+
Preview handler |
+Enables a preview of a file to be displayed in the Windows Explorer Preview Pane. |
+
| Virtual Extension | +Requires target OS Sequencing | +Requires Global Publishing | +
|---|---|---|
Shortcut |
++ | + |
File Type Association |
++ | + |
URL Protocols |
+X |
++ |
AppPaths |
+X |
++ |
COM Mode |
++ | + |
Software Client |
+X |
++ |
Application Capabilities |
+X |
+X |
+
Context Menu Handler |
+X |
+X |
+
Drag-and-drop Handler |
+X |
++ |
Data Object Handler |
+X |
++ |
Property Sheet Handler |
+X |
++ |
Infotip Handler |
+X |
++ |
Column Handler |
+X |
++ |
Shell Extensions |
+X |
++ |
Browser Helper Object |
+X |
+X |
+
Active X Object |
+X |
+X |
+
| Task | +More Information | +
|---|---|
Determine Application Scope |
+Depending on the applications to be virtualized, the App-V 5.1 infrastructure can be set up in different ways. The first task is to define what applications you want to virtualize. |
+
Determine Location Scope |
+Location scope refers to the physical locations (for example, enterprise-wide or a specific geographic location) where you plan to run the virtualized applications. It can also refer to the user population (for example, a single department) who will run the virtual applications. You should obtain a network map that includes the connection paths as well as available bandwidth to each location and the number of users using virtualized applications and the WAN link speed. |
+
| Factors impacting round trip response time | +More Information | +
|---|---|
The number of publishing servers simultaneously requesting package metadata refreshes. |
+
+
|
+
The number of connection groups configured on the management server. + |
+
+
|
+
The number of access groups configured on the management server. + |
+
+
|
+
| Scenario | +Variation | +Number of connection groups | +Number of access groups | +Number of publishing servers | +Network connection type publishing server / management server | +Round trip response time on the publishing server (in seconds) | +CPU utilization on management server | +
|---|---|---|---|---|---|---|---|
Publishing servers simultaneously contacting management server for publishing metadata. |
+Number of publishing servers |
+
+
|
+
+
|
+
+
|
+
+
|
+
+
|
+
+
|
+
Publishing metadata contains connection groups |
+Number of connection groups |
+
+
|
+
+
|
+
+
|
+
+
|
+
+
|
+
+
|
+
Publishing metadata contains access groups |
+Number of access groups |
+
+
|
+
+
|
+
+
|
+
+
|
+
+
|
+
+
|
+
| Scenario | +Variation | +Number of connection groups | +Number of access groups | +Number of publishing servers | +Network connection type publishing server / management server | +Round trip response time on the publishing server (in seconds) | +CPU utilization on management server | +
|---|---|---|---|---|---|---|---|
Network connection between the publishing server and management server |
+1.5 Mbps Slow link Network |
+
+
|
+
+
|
+
+
|
+
+
|
+
+
|
+
+
|
+
Network connection between the publishing server and management server |
+LAN / WIFI Network |
+
+
|
+
+
|
+
+
|
+
+
|
+
+
|
+
+
|
+
| Scenario | +Summary | +
|---|---|
Multiple App-V 5.1 clients send reporting information to the reporting server simultaneously. |
+
+
|
+
Requests per second processed by the reporting server. + |
+
+
|
+
Reporting Database. + |
+
+
|
+
| Scenario | +Summary | +
|---|---|
Multiple App-V 5.1 clients connect to a single publishing server simultaneously. |
+
+
|
+
Number of packages in each refresh. + |
+
+
|
+
Network between the App-V 5.1 client and the publishing server. + |
+
+
|
+
| Scenario | +Variation | +Number of App-V 5.1 clients | +Number of packages | +Processor configuration on the publishing server | +Network connection type publishing server / App-V 5.1 client | +Round trip time on the App-V 5.1 client (in seconds) | +CPU utilization on publishing server (in %) | +
|---|---|---|---|---|---|---|---|
App-V 5.1 client sends publishing refresh request & receives response, each request containing 120 packages |
+Number of clients |
+
+
|
+
+
|
+
+
|
+
+
|
+
+
|
+
+
|
+
Multiple packages in each refresh |
+Number of packages |
+
+
|
+
+
|
+
+
|
+
+
|
+
+
|
+
+
|
+
Network between client and publishing server |
+1.5 Mbps Slow link network |
+
+
|
+
+
|
+
+
|
+
+
|
+
+
|
++ |
| Scenario | +Summary | +
|---|---|
Multiple App-V 5.1 clients stream applications from a single streaming server simultaneously. |
+
+
|
+
Size of the package being streamed. + |
+
+
|
+
Network between the App-V 5.1 client and the streaming server. + |
+
+
|
+
| Scenario | +Variation | +Number of App-V 5.1 clients | +Size of each package | +Network connection type streaming server / App-V 5.1 client | +Round trip time on the App-V 5.1 client (in seconds) | +
|---|---|---|---|---|---|
Multiple App-V 5.1 clients streaming virtual application packages from a streaming server. |
+Number of clients. |
+
+
|
+
+
|
+
+
|
+
+
|
+
Size of each package being streamed. |
+Size of each package. |
+
+
|
+
+
|
+
+
|
+
+ 33 +83 + +100 +160 |
+
Network connection between client and App-V 5.1 streaming server. |
+1.5 Mbps Slow link network. |
+
+
|
+
+
|
+
+
|
+
+ 102 + +121 |
+
**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
**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
**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
**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
**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
**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
**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
**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)
Word count (with spaces): 60 | True(enabled); False(Disabled state) | Publishing\Servers\{serverId}\UserLogonRefresh | False | +| UserRefreshInterval
**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
Integer (0-744 Hours) | Publishing\Servers\{serverId}\UserPeriodicRefreshInterval | 0 | +| UserRefreshIntervalUnit
**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.
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](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.
**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
**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
**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
**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. | + +## 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). + +## Related topics + + +[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) + + + + + + + + + diff --git a/windows/manage/appv-configure-access-to-packages-with-the-management-console.md b/windows/manage/appv-configure-access-to-packages-with-the-management-console.md new file mode 100644 index 0000000000..23ac67cc7f --- /dev/null +++ b/windows/manage/appv-configure-access-to-packages-with-the-management-console.md @@ -0,0 +1,73 @@ +--- +title: How to Configure Access to Packages by Using the Management Console +description: How to Configure Access to Packages by Using the Management Console +author: jamiejdt +ms.assetid: 4fd39bc2-d814-46de-a108-1c21fa404e8a +ms.pagetype: mdop, appcompat, virtualization +ms.mktglfcycl: deploy +ms.sitesec: library +ms.prod: w10 +--- + + +# How to Configure Access to Packages by Using the Management Console + + +Before you deploy an App-V 5.1 virtualized package, you must configure the Active Directory Domain Services (AD DS) security groups that will be allowed to access and run the applications. The security groups may contain computers or users. Entitling a package to a computer group publishes the package globally to all computers in the group. + +Use the following procedure to configure access to virtualized packages. + +**To grant access to an App-V 5.1 package** + +1. Find the package you want to configure: + + 1. Open the App-V 5.1 Management console. + + 2. To display the **AD ACCESS** page, right-click the package to be configured, and select **Edit active directory access**. Alternatively, select the package and click **EDIT** in the **AD ACCESS** pane. + +2. Provision a security group for the package: + + 1. Go to the **FIND VALID ACTIVE DIRECTORY NAMES AND GRANT ACCESS** page. + + 2. Using the format **mydomain** \\ **groupname**, type the name or part of the name of an Active Directory group object, and click **Check**. + + **Note** + Ensure that you provide an associated domain name for the group that you are searching for. + + + +3. To grant access to the package, select the desired group and click **Grant Access**. The newly added group is displayed in the **AD ENTITIES WITH ACCESS** pane. + +4. + + To accept the default configuration settings and close the **AD ACCESS** page, click **Close**. + + To customize configurations for a specific group, click the **ASSIGNED CONFIGURATIONS** drop-down and select **Custom**. To configure the custom configurations, click **EDIT**. After you grant access, click **Close**. + +**To remove access to an App-V 5.1 package** + +1. Find the package you want to configure: + + 1. Open the App-V 5.1 Management console. + + 2. To display the **AD ACCESS** page, right-click the package to be configured, and select **Edit active directory access**. Alternatively, select the package and click **EDIT** in the **AD ACCESS** pane. + +2. Select the group you want to remove, and click **DELETE**. + +3. To close the **AD ACCESS** page, click **Close**. + + **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). + +## Related topics + + +[Operations for App-V 5.1](appv-operations.md) + + + + + + + + + diff --git a/windows/manage/appv-configure-connection-groups-to-ignore-the-package-version.md b/windows/manage/appv-configure-connection-groups-to-ignore-the-package-version.md new file mode 100644 index 0000000000..442a0585ce --- /dev/null +++ b/windows/manage/appv-configure-connection-groups-to-ignore-the-package-version.md @@ -0,0 +1,108 @@ +--- +title: How to Make a Connection Group Ignore the Package Version +description: How to Make a Connection Group Ignore the Package Version +author: jamiejdt +ms.assetid: db16b095-dbe2-42c7-863d-b0d5d91b2f4c +ms.pagetype: mdop, appcompat, virtualization +ms.mktglfcycl: deploy +ms.sitesec: library +ms.prod: w10 +--- + + +# How to Make a Connection Group Ignore the Package Version + + +Microsoft Application Virtualization (App-V) 5.1 lets you configure a connection group to use any version of a package, which simplifies package upgrades and reduces the number of connection groups you need to create. + +To upgrade a package in some earlier versions of App-V, you had to perform several steps, including disabling the connection group and modifying the connection group’s XML definition file. + +
| Task description with App-V 5.1 | +How to perform the task with App-V 5.1 | +||||||
|---|---|---|---|---|---|---|---|
You can configure a connection group to accept any version of a package, which enables you to upgrade the package without having to disable the connection group. +How the feature works: +
|
+
|
+
Connection group purpose |
+A connection group is an App-V feature that enables you to group packages together to create a virtual environment in which the applications in those packages can interact with each other. +Example: You want to use plug-ins with Microsoft Office. You can create a package that contains the plug-ins, and create another package that contains Office, and then add both packages to a connection group to enable Office to use those plug-ins. |
+
How the connection group file works |
+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. |
+
Example file path |
+%APPDATA%\Microsoft\AppV\Client\Catalog\PackageGroups\{6CCC7575-162E-4152-9407-ED411DA138F4}\{4D1E16E1-8EF8-41ED-92D5-8910A8527F96}. |
+
| Field | +Description | +
|---|---|
Schema name |
+Name of the schema. +Applicable starting in App-V 5.0 SP3: 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: +
|
+
AppConnectionGroupId |
+Unique GUID identifier for this connection group. The connection group state is associated with this identifier. Specify this identifier only when you create the connection group. +You can create a new GUID by typing: [Guid]::NewGuid(). |
+
VersionId |
+Version GUID identifier for this version of the connection group. +When you update a connection group (for example, by adding or updating a new package), you must update the version GUID to reflect the new version. |
+
DisplayName |
+Display name of the connection group. |
+
Priority |
+Optional priority field for the connection group. +“0” - indicates the highest priority. +If a priority is required, but has not been configured, the package will fail because the correct connection group to use cannot be determined. |
+
| Field | +Description | +
|---|---|
PackageId |
+Unique GUID identifier for this package. This GUID doesn’t change when newer versions of the package are published. |
+
VersionId |
+Unique GUID identifier for the version of the package. +Applicable starting in App-V 5.0 SP3: If you specify “*” for the package version, the GUID of the latest available package version is dynamically inserted. |
+
IsOptional |
+Applicable starting in App-V 5.0 SP3: Parameter that enables you to make a package optional within the connection group. Valid entries are: +
See [How to Use Optional Packages in Connection Groups](appv-use-optional-packages-in-connection-groups.md). |
+
| Configuration | +Example scenario | +||||||
|---|---|---|---|---|---|---|---|
An. exe file and plug-in (.dll) |
+
|
+||||||
An. exe file and a middleware application |
+
|
+||||||
An. exe file and an .exe file |
+You have an application that relies on another application, and you want to keep the packages separate for operational efficiencies, licensing restrictions, or rollout timelines. +Example: +If you are deploying Microsoft Lync 2010, you can use three packages: +
You can manage the deployment using the following connection groups: +
When the deployment has completed, you can either create a single new Microsoft Office 2010 + Microsoft Lync 2010 package, or keep and maintain them as separate packages and deploy them by using a connection group. |
+
| Package A | +Package B | +
|---|---|
C:\Windows\System32 |
+C:\Windows\System32 |
+
C:\AppTest |
+C:\AppTest |
+
| Unsupported scenarios and potential issues | +Result | +
|---|---|
You cannot include user-published packages in globally entitled connection groups. |
+The connection group will fail. |
+
If you publish a package globally and then create a user-published connection group in which you’ve made that package non-optional, you can still run Unpublish-AppvClientPackage <package> -global to unpublish the package, even when that package is being used in another connection group. |
+If any other connection groups are using that package, the package will fail in those connection groups. +To avoid inadvertently unpublishing a non-optional package that is being used in another connection group, we recommend that you track the connection groups in which you’ve used a non-optional package. |
+
| Handler | +Description | +
|---|---|
Context menu handler |
+Adds menu items to the context menu. It is called before the context menu is displayed. |
+
Drag-and-drop handler |
+Controls the action where right-click, drag and drop and modifies the context menu that appears. |
+
Drop target handler |
+Controls the action after a data object is dragged and dropped over a drop target such as a file. |
+
Data object handler |
+Controls the action after a file is copied to the clipboard or dragged and dropped over a drop target. It can provide additional clipboard formats to the drop target. |
+
Property sheet handler |
+Replaces or adds pages to the property sheet dialog box of an object. |
+
Infotip handler |
+Allows retrieving flags and infotip information for an item and displaying it inside a pop-up tooltip upon mouse hover. |
+
Column handler |
+Allows creating and displaying custom columns in Windows Explorer Details view. It can be used to extend sorting and grouping. |
+
Preview handler |
+Enables a preview of a file to be displayed in the Windows Explorer Preview pane. |
+
| Database | +Location of Readme.txt file to use | +
|---|---|
Management database |
+ ManagementDatabase subfolder |
+
Reporting database |
+ ReportingDatabase subfolder |
+
| Method | +Description | +
|---|---|
Functionality provided by a third-party ESD |
+Use the functionality in a third-party ESD. |
+
Stand-alone Windows Installer |
+Install the application on the target client computer by using the associated Windows Installer (.msi) file that is created when you initially sequence an application. The Windows Installer file contains the associated App-V 5.1 package file information used to configure a package and copies the required package files to the client. |
+
PowerShell |
+Use PowerShell cmdlets to deploy virtualized applications. 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). |
+
Deploying coexisting App-V clients |
+ [Planning for the App-V 5.1 Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md) |
+
Unsupported or limited installation scenarios |
+ See the client section in [App-V 5.1 Supported Configurations](appv-supported-configurations.md) |
+
Client registry information |
+
|
+
Client log files |
+
|
+
Client installation troubleshooting information |
+See the error log in the %temp% folder. To review the log files, click Start, type %temp%, and then look for the appv_ log. |
+
| Client type | +File to use | +
|---|---|
Standard version of the client |
+ appv_client_setup.exe |
+
Remote Desktop Services version of the client |
+ appv_client_setup_rds.exe |
+
/INSTALLDIR |
+ Specifies the installation directory. Example usage: /INSTALLDIR=C:\Program Files\AppV Client |
+
/CEIPOPTIN |
+ Enables participation in the Customer Experience Improvement Program. Example usage: /CEIPOPTIN=[0|1] |
+
/MUOPTIN |
+ Enables Microsoft Update. Example usage: /MUOPTIN=[0|1] |
+
/PACKAGEINSTALLATIONROOT |
+ Specifies the directory in which to install all new applications and updates. Example usage: /PACKAGEINSTALLATIONROOT='C:\App-V Packages' |
+
/PACKAGESOURCEROOT |
+ Overrides the source location for downloading package content. Example usage: /PACKAGESOURCEROOT='http://packageStore' |
+
/AUTOLOAD |
+ 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].Example usage: /AUTOLOAD=[0|1|2] |
+
/SHAREDCONTENTSTOREMODE |
+ Specifies that streamed package contents will be not be saved to the local hard disk. Example usage: /SHAREDCONTENTSTOREMODE=[0|1] |
+
/MIGRATIONMODE |
+ 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: /MIGRATIONMODE=[0|1] |
+
/ENABLEPACKAGESCRIPTS |
+ Enables the scripts that are defined in the package manifest file or configuration files that should run. Example usage: /ENABLEPACKAGESCRIPTS=[0|1] |
+
/ROAMINGREGISTRYEXCLUSIONS |
+ Specifies the registry paths that will not roam with a user profile. Example usage: /ROAMINGREGISTRYEXCLUSIONS=software\classes;software\clients |
+
/ROAMINGFILEEXCLUSIONS |
+ Specifies the file paths relative to %userprofile% that do not roam with a user's profile. Example usage: /ROAMINGFILEEXCLUSIONS 'desktop;my pictures' |
+
/S[1-5]PUBLISHINGSERVERNAME |
+ Displays the name of the publishing server. Example usage: /S2PUBLISHINGSERVERNAME=MyPublishingServer |
+
/S[1-5]PUBLISHINGSERVERURL |
+ Displays the URL of the publishing server. Example usage: /S2PUBLISHINGSERVERURL=\\pubserver |
+
/S[1-5]GLOBALREFRESHENABLED - |
+ Enables a global publishing refresh. Example usage: /S2GLOBALREFRESHENABLED=[0|1] |
+
/S[1-5]GLOBALREFRESHONLOGON |
+ Initiates a global publishing refresh when a user logs on. Example usage: /S2LOGONREFRESH=[0|1] |
+
/S[1-5]GLOBALREFRESHINTERVAL - |
+ Specifies the publishing refresh interval, where 0 indicates do not periodically refresh. Example usage: /S2PERIODICREFRESHINTERVAL=[0-744] |
+
/S[1-5]GLOBALREFRESHINTERVALUNIT |
+ Specifies the interval unit (Hours[0], Days[1]). Example usage: /S2GLOBALREFRESHINTERVALUNIT=[0|1] |
+
/S[1-5]USERREFRESHENABLED |
+ Enables user publishing refresh. Example usage: /S2USERREFRESHENABLED=[0|1] |
+
/S[1-5]USERREFRESHONLOGON |
+ Initiates a user publishing refresh when a user logs on. Example usage: /S2LOGONREFRESH=[0|1] |
+
/S[1-5]USERREFRESHINTERVAL - |
+ Specifies the publishing refresh interval, where 0 indicates do not periodically refresh. Example usage: /S2PERIODICREFRESHINTERVAL=[0-744] |
+
/S[1-5]USERREFRESHINTERVALUNIT |
+ Specifies the interval unit (Hours[0], Days[1]). Example usage: /S2USERREFRESHINTERVALUNIT=[0|1] |
+
/Log |
+ Specifies a location where the log information is saved. The default location is %Temp%. Example usage: /log C:\logs\log.log |
+
/q |
+ Specifies an unattended installation. |
+
/REPAIR |
+ Repairs a previous client installation. |
+
/NORESTART |
+ Prevents the computer from rebooting after the client installation. +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. |
+
/UNINSTALL |
+ Uninstalls the client. |
+
/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 5.1. No value is expected. |
+
/LAYOUTDIR |
+ Specifies the layout directory. Requires a string value. Example usage: /LAYOUTDIR=”C:\Application Virtualization Client”. |
+
/?, /h, /help |
+ Requests help about the previous installation parameters. |
+
| Type of deployment | +Deploy this file | +
|---|---|
Computer is running a 32-bit Microsoft Windows operating system |
+ appv_client_MSI_x86.msi |
+
Computer is running a 64-bit Microsoft Windows operating system |
+ appv_client_MSI_x64.msi |
+
You are deploying the App-V 5.1 Remote Desktop Services client |
+ appv_client_rds_MSI_x64.msi |
+
| Type of deployment | +Deploy this file | +
|---|---|
Computer is running a 32-bit Microsoft Windows operating system |
+ appv_client_LP_xxxx_ x86.msi |
+
Computer is running a 64-bit Microsoft Windows operating system |
+ appv_client_LP_xxxx_ x64.msi |
+
To Install the Management server and Management database on a local machine. |
+ To use the default instance of Microsoft SQL Server, use the following parameters: +
To use a custom instance of Microsoft SQL Server, use the following parameters: +
Using a custom instance of Microsoft SQL Server example: +/appv_server_setup.exe /QUIET +/MANAGEMENT_SERVER +/MANAGEMENT_ADMINACCOUNT=”Domain\AdminGroup” +/MANAGEMENT_WEBSITE_NAME=”Microsoft AppV Management Service” +/MANAGEMENT_WEBSITE_PORT=”8080” +/DB_PREDEPLOY_MANAGEMENT +/MANAGEMENT_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName” +/MANAGEMENT_DB_NAME=”AppVManagement” |
+
To Install the Management server using an existing Management database on a local machine. |
+ To use the default instance of Microsoft SQL Server, use the following parameters: +
To use a custom instance of Microsoft SQL Server, use these parameters: +
Using a custom instance of Microsoft SQL Server example: +/appv_server_setup.exe /QUIET +/MANAGEMENT_SERVER +/MANAGEMENT_ADMINACCOUNT=”Domain\AdminGroup” +/MANAGEMENT_WEBSITE_NAME=”Microsoft AppV Management Service” +/MANAGEMENT_WEBSITE_PORT=”8080” +/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL +/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE =”SqlInstanceName” +/EXISTING_MANAGEMENT_DB_NAME =”AppVManagement” |
+
To install the Management server using an existing Management database on a remote machine. |
+ To use the default instance of Microsoft SQL Server, use the following parameters: +
To use a custom instance of Microsoft SQL Server, use these parameters: +
Using a custom instance of Microsoft SQL Server example: +/appv_server_setup.exe /QUIET +/MANAGEMENT_SERVER +/MANAGEMENT_ADMINACCOUNT=”Domain\AdminGroup” +/MANAGEMENT_WEBSITE_NAME=”Microsoft AppV Management Service” +/MANAGEMENT_WEBSITE_PORT=”8080” +/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME=”SqlServermachine.domainName” +/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE =”SqlInstanceName” +/EXISTING_MANAGEMENT_DB_NAME =”AppVManagement” |
+
To Install the Management database and the Management Server on the same computer. |
+ To use the default instance of Microsoft SQL Server, use the following parameters: +
To use a custom instance of Microsoft SQL Server, use these parameters: +
Using a custom instance of Microsoft SQL Server example: +/appv_server_setup.exe /QUIET +/DB_PREDEPLOY_MANAGEMENT +/MANAGEMENT_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName” +/MANAGEMENT_DB_NAME=”AppVManagement” +/MANAGEMENT_SERVER_MACHINE_USE_LOCAL +/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount” |
+
To install the Management database on a different computer than the Management server. |
+ To use the default instance of Microsoft SQL Server, use the following parameters: +
To use a custom instance of Microsoft SQL Server, use these parameters: +
Using a custom instance of Microsoft SQL Server example: +/appv_server_setup.exe /QUIET +/DB_PREDEPLOY_MANAGEMENT +/MANAGEMENT_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName” +/MANAGEMENT_DB_NAME=”AppVManagement” +/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT=”Domain\MachineAccount” +/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount” |
+
To Install the publishing server. |
+ To use the default instance of Microsoft SQL Server, use the following parameters: +
Using a custom instance of Microsoft SQL Server example: +/appv_server_setup.exe /QUIET +/PUBLISHING_SERVER +/PUBLISHING_MGT_SERVER=”http://ManagementServerName:ManagementPort” +/PUBLISHING_WEBSITE_NAME=”Microsoft AppV Publishing Service” +/PUBLISHING_WEBSITE_PORT=”8081” |
+
To Install the Reporting server and Reporting database on a local machine. |
+ To use the default instance of Microsoft SQL Server, use the following parameters: +
To use a custom instance of Microsoft SQL Server, use these parameters: +
Using a custom instance of Microsoft SQL Server example: +
|
+
To Install the Reporting server and using an existing Reporting database on a local machine. |
+ To use the default instance of Microsoft SQL Server, use the following parameters: +
To use a custom instance of Microsoft SQL Server, use these parameters: +
Using a custom instance of Microsoft SQL Server example: +/appv_server_setup.exe /QUIET +/REPORTING_SERVER +/REPORTING_WEBSITE_NAME=”Microsoft AppV Reporting Service” +/REPORTING_WEBSITE_PORT=”8082” +/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL +/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE=”SqlInstanceName” +/EXITING_REPORTING_DB_NAME=”AppVReporting” |
+
To Install the Reporting server using an existing Reporting database on a remote machine. |
+ To use the default instance of Microsoft SQL Server, use the following parameters: +
To use a custom instance of Microsoft SQL Server, use these parameters: +
Using a custom instance of Microsoft SQL Server example: +/appv_server_setup.exe /QUIET +/REPORTING_SERVER +/REPORTING_WEBSITE_NAME=”Microsoft AppV Reporting Service” +/REPORTING_WEBSITE_PORT=”8082” +/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME=”SqlServerMachine.DomainName” +/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE=”SqlInstanceName” +/EXITING_REPORTING_DB_NAME=”AppVReporting” |
+
To install the Reporting database on the same computer as the Reporting server. |
+ To use the default instance of Microsoft SQL Server, use the following parameters: +
To use a custom instance of Microsoft SQL Server, use these parameters: +
Using a custom instance of Microsoft SQL Server example: +/appv_server_setup.exe /QUIET +/DB_PREDEPLOY_REPORTING +/REPORTING_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName” +/REPORTING_DB_NAME=”AppVReporting” +/REPORTING_SERVER_MACHINE_USE_LOCAL +/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount” |
+
To install the Reporting database on a different computer than the Reporting server. |
+ To use the default instance of Microsoft SQL Server, use the following parameters: +
To use a custom instance of Microsoft SQL Server, use these parameters: +
Using a custom instance of Microsoft SQL Server example: +/appv_server_setup.exe /QUIET +/DB_PREDEPLOY_REPORTING +/REPORTING_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName” +/REPORTING_DB_NAME=”AppVReporting” +/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT=”Domain\MachineAccount” +/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount” |
+
| Parameter | +Information | +
|---|---|
/QUIET |
+ Specifies silent install. |
+
/UNINSTALL |
+ Specifies an uninstall. |
+
/LAYOUT |
+ Specifies layout action. This extracts the MSIs and script files to a folder without actually installing the product. No value is expected. |
+
/LAYOUTDIR |
+ Specifies the layout directory. Takes a string. For example, /LAYOUTDIR=”C:\Application Virtualization Server” |
+
/INSTALLDIR |
+ Specifies the installation directory. Takes a string. E.g. /INSTALLDIR=”C:\Program Files\Application Virtualization\Server” |
+
/MUOPTIN |
+ Enables Microsoft Update. No value is expected |
+
/ACCEPTEULA |
+ Accepts the license agreement. This is required for an unattended installation. Example usage: /ACCEPTEULA or /ACCEPTEULA=1. |
+
| Parameter | +Information | +
|---|---|
/MANAGEMENT_SERVER |
+ Specifies that the management server will be installed. No value is expected |
+
/MANAGEMENT_ADMINACCOUNT |
+ Specifies the account that will be allowed to Administrator access to the management server This account can be an individual user account or a group. Example usage: /MANAGEMENT_ADMINACCOUNT=”mydomain\admin”. If /MANAGEMENT_SERVER is not specified, this will be ignored. Specifies the account that will be allowed to Administrator access to the management server. This can be a user account or a group. For example, /MANAGEMENT_ADMINACCOUNT="mydomain\admin". |
+
/MANAGEMENT_WEBSITE_NAME |
+ Specifies name of the website that will be created for the management service. For example, /MANAGEMENT_WEBSITE_NAME=”Microsoft App-V Management Service” |
+
MANAGEMENT_WEBSITE_PORT |
+ Specifies the port number that will be used by the management service will use. For example, /MANAGEMENT_WEBSITE_PORT=82. |
+
| Parameter | +Information | +
|---|---|
/DB_PREDEPLOY_MANAGEMENT |
+ Specifies that the management database will be installed. You must have sufficient database permissions to complete this installation. No value is expected |
+
/MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT |
+ Indicates that the default SQL instance should be used. No value is expected. |
+
/MANAGEMENT_DB_ CUSTOM_SQLINSTANCE |
+ Specifies the name of the custom SQL instance that should be used to create a new database. Example usage: /MANAGEMENT_DB_ CUSTOM_SQLINSTANCE=”MYSQLSERVER”. If /DB_PREDEPLOY_MANAGEMENT is not specified, this will be ignored. |
+
/MANAGEMENT_DB_NAME |
+ Specifies the name of the new management database that should be created. Example usage: /MANAGEMENT_DB_NAME=”AppVMgmtDB”. If /DB_PREDEPLOY_MANAGEMENT is not specified, this will be ignored. |
+
/MANAGEMENT_SERVER_MACHINE_USE_LOCAL |
+ Indicates if the management server that will be accessing the database is installed on the local server. Switch parameter so no value is expected. |
+
/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT |
+ Specifies the machine account of the remote machine that the management server will be installed on. Example usage: /MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT=”domain\computername” |
+
/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT |
+ Indicates the Administrator account that will be used to install the management server. Example usage: /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT =”domain\alias” |
+
| Parameter | +Information | +
|---|---|
/PUBLISHING_SERVER |
+ Specifies that the Publishing Server will be installed. No value is expected |
+
/PUBLISHING_MGT_SERVER |
+ Specifies the URL to Management Service the Publishing server will connect to. Example usage: http://<management server name>:<Management server port number>. If /PUBLISHING_SERVER is not used, this parameter will be ignored |
+
/PUBLISHING_WEBSITE_NAME |
+ Specifies name of the website that will be created for the publishing service. For example, /PUBLISHING_WEBSITE_NAME=”Microsoft App-V Publishing Service” |
+
/PUBLISHING_WEBSITE_PORT |
+ Specifies the port number used by the publishing service. For example, /PUBLISHING_WEBSITE_PORT=83 |
+
| Parameter | +Information | +
|---|---|
/REPORTING_SERVER |
+ Specifies that the Reporting Server will be installed. No value is expected |
+
/REPORTING_WEBSITE_NAME |
+ Specifies name of the website that will be created for the Reporting Service. E.g. /REPORTING_WEBSITE_NAME="Microsoft App-V ReportingService" |
+
/REPORTING_WEBSITE_PORT |
+ Specifies the port number that the Reporting Service will use. E.g. /REPORTING_WEBSITE_PORT=82 |
+
| Parameter | +Information | +
|---|---|
/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL |
+ Indicates that the Microsoft SQL Server is installed on the local server. Switch parameter so no value is expected. |
+
/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME |
+ Specifies the name of the remote computer that SQL Server is installed on. Takes a string. E.g. /EXISTING_REPORTING_DB_ REMOTE_SQL_SERVER_NAME="mycomputer1" |
+
/EXISTING_ REPORTING _DB_SQLINSTANCE_USE_DEFAULT |
+ Indicates that the default SQL instance is to be used. Switch parameter so no value is expected. |
+
/EXISTING_ REPORTING_DB_CUSTOM_SQLINSTANCE |
+ Specifies the name of the custom SQL instance that should be used. Takes a string. E.g. /EXISTING_REPORTING_DB_ CUSTOM_SQLINSTANCE="MYSQLSERVER" |
+
/EXISTING_ REPORTING _DB_NAME |
+ Specifies the name of the existing Reporting database that should be used. Takes a string. E.g. /EXISITING_REPORTING_DB_NAME="AppVReporting" |
+
| Parameter | +Information | +
|---|---|
/DB_PREDEPLOY_REPORTING |
+ Specifies that the Reporting Database will be installed. DBA permissions are required for this installation. No value is expected |
+
/REPORTING_DB_SQLINSTANCE_USE_DEFAULT |
+ Specifies the name of the custom SQL instance that should be used. Takes a string. E.g. /REPORTING_DB_ CUSTOM_SQLINSTANCE="MYSQLSERVER" |
+
/REPORTING_DB_NAME |
+ Specifies the name of the new Reporting database that should be created. Takes a string. E.g. /REPORTING_DB_NAME="AppVMgmtDB" |
+
/REPORTING_SERVER_MACHINE_USE_LOCAL |
+ Indicates that the Reporting server that will be accessing the database is installed on the local server. Switch parameter so no value is expected. |
+
/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT |
+ Specifies the machine account of the remote machine that the Reporting server will be installed on. Takes a string. E.g. /REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT = "domain\computername" |
+
/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT |
+ Indicates the Administrator account that will be used to install the App-V Reporting Server. Takes a string. E.g. /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT = "domain\alias" |
+
| Parameter | +Information | +
|---|---|
/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL |
+ Indicates that the SQL Server is installed on the local server. Switch parameter so no value is expected.If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored. |
+
/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME |
+ Specifies the name of the remote computer that SQL Server is installed on. Takes a string. E.g. /EXISTING_MANAGEMENT_DB_ REMOTE_SQL_SERVER_NAME="mycomputer1" |
+
/EXISTING_ MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT |
+ Indicates that the default SQL instance is to be used. Switch parameter so no value is expected. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored. |
+
/EXISTING_MANAGEMENT_DB_ CUSTOM_SQLINSTANCE |
+ Specifies the name of the custom SQL instance that will be used. Example usage /EXISTING_MANAGEMENT_DB_ CUSTOM_SQLINSTANCE=”AppVManagement”. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored. |
+
/EXISTING_MANAGEMENT_DB_NAME |
+ Specifies the name of the existing management database that should be used. Example usage: /EXISITING_MANAGEMENT_DB_NAME=”AppVMgmtDB”. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored. + +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). |
+
| Component | +Description | +
|---|---|
Management server |
+ Provides overall management functionality for the App-V infrastructure. |
+
Management database |
+ Facilitates database predeployments for App-V management. |
+
Publishing server |
+ Provides hosting and streaming functionality for virtual applications. |
+
Reporting server |
+ Provides App-V 5.1 reporting services. |
+
Reporting database |
+ Facilitates database predeployments for App-V reporting. |
+
| Method | +What you need to do | +
|---|---|
You are using a custom Microsoft SQL Server instance. |
+ Select Use the custom instance, and type the name of the instance. +Use the format INSTANCENAME. The assumed installation location is the local computer. +Not supported: A server name using the format ServerName\INSTANCE. |
+
You are using a custom database name. |
+ Select Custom configuration and type the database name. +The database name must be unique, or the installation will fail. |
+
| Method | +What you need to do | +
|---|---|
You are using a custom Microsoft SQL Server instance. |
+ Select Use the custom instance, and type the name of the instance. +Use the format INSTANCENAME. The assumed installation location is the local computer. +Not supported: A server name using the format ServerName\INSTANCE. |
+
You are using a custom database name. |
+ Select Custom configuration and type the database name. +The database name must be unique, or the installation will fail. |
+
| Item to configure | +Description and examples | +
|---|---|
Type the AD group with sufficient permissions to manage the App-V environment. |
+ Example: MyDomain\MyUser +After installation, you can add additional users or groups by using the Management console. However, global security groups and Active Directory Domain Services (AD DS) distribution groups are not supported. You must use Domain local or Universal groups are required to perform this action. |
+
Website name: Specify the custom name that will be used to run the publishing service. |
+ If you do not have a custom name, do not make any changes. |
+
Port binding: Specify a unique port number that will be used by App-V. |
+ Example: 12345 +Ensure that the port specified is not being used by another website. |
+
| Item to configure | +Description and examples | +
|---|---|
Specify the URL for the management service. |
+ Example: http://localhost:12345 |
+
Website name: Specify the custom name that will be used to run the publishing service. |
+ If you do not have a custom name, do not make any changes. |
+
Port binding: Specify a unique port number that will be used by App-V. |
+ Example: 54321 +Ensure that the port specified is not being used by another website. |
+
| Item to configure | +Description and examples | +
|---|---|
Website name: Specify the custom name that will be used to run the Reporting Service. |
+ If you do not have a custom name, do not make any changes. |
+
Port binding: Specify a unique port number that will be used by App-V. |
+ Example: 55555 +Ensure that the port specified is not being used by another website. |
+
| Supported item | +Level of support | +
|---|---|
Supported App-V versions |
+
|
+
Package creation |
+
|
+
Supported licensing |
+Volume Licensing |
+
Supported deployments |
+
|
+
| Extension Point | +Description | +Office 2010 | +
|---|---|---|
Lync meeting Join Plug-in for Firefox and Chrome |
+User can join Lync meetings from Firefox and Chrome |
++ |
Sent to OneNote Print Driver |
+User can print to OneNote |
+Yes |
+
OneNote Linked Notes |
+OneNote Linked Notes |
++ |
Send to OneNote Internet Explorer Add-In |
+User can send to OneNote from IE |
++ |
Firewall Exception for Lync and Outlook |
+Firewall Exception for Lync and Outlook |
++ |
MAPI Client |
+Native apps and add-ins can interact with virtual Outlook through MAPI |
++ |
SharePoint Plugin for Firefox |
+User can use SharePoint features in Firefox |
++ |
Mail Control Panel Applet |
+User gets the mail control panel applet in Outlook |
+Yes |
+
Primary Interop Assemblies |
+Support managed add-ins |
++ |
Office Document Cache Handler |
+Allows Document Cache for Office applications |
++ |
Outlook Protocol Search handler |
+User can search in outlook |
+Yes |
+
Active X Controls: |
+For more information on ActiveX controls, refer to [ActiveX Control API Reference](http://go.microsoft.com/fwlink/p/?LinkId=331361). |
++ |
Groove.SiteClient |
+Active X Control |
++ |
PortalConnect.PersonalSite |
+Active X Control |
++ |
SharePoint.openDocuments |
+Active X Control |
++ |
SharePoint.ExportDatabase |
+Active X Control |
++ |
SharePoint.SpreadSheetLauncher |
+Active X Control |
++ |
SharePoint.StssyncHander |
+Active X Control |
++ |
SharePoint.DragUploadCtl |
+Active X Control |
++ |
SharePoint.DragDownloadCtl |
+Active X Control |
++ |
Sharpoint.OpenXMLDocuments |
+Active X Control |
++ |
Sharepoint.ClipboardCtl |
+Active X control |
++ |
WinProj.Activator |
+Active X Control |
++ |
Name.NameCtrl |
+Active X Control |
++ |
STSUPld.CopyCtl |
+Active X Control |
++ |
CommunicatorMeetingJoinAx.JoinManager |
+Active X Control |
++ |
LISTNET.Listnet |
+Active X Control |
++ |
OneDrive Pro Browser Helper |
+Active X Control] |
++ |
OneDrive Pro Icon Overlays |
+Windows explorer shell icon overlays when users look at folders OneDrive Pro folders |
++ |
| Information to review | +Description | +
|---|---|
[Planning for Using App-V with Office](appv-planning-for-using-appv-with-office.md#bkmk-office-vers-supp-appv) |
+
|
+
[Planning for Using App-V with Office](appv-planning-for-using-appv-with-office.md#bkmk-plan-coexisting) |
+Considerations for installing different versions of Office on the same computer |
+
| Task | +Requirement | +
|---|---|
Packaging |
+
|
+
Publishing |
+
|
+
Deploying any of the following products to a shared computer, for example, by using Remote Desktop Services: +
|
+You must enable [shared computer activation](http://technet.microsoft.com/library/dn782860.aspx). +You don’t use shared computer activation if you’re deploying a volume licensed product, such as: +
|
+
| Task | +Details | +
|---|---|
Use the ExcludeApp setting when you create the package by using the Office Deployment Tool. |
+
|
+
Modify the DeploymentConfig.xml file |
+
|
+
| Prerequisite | +Description | +
|---|---|
Prerequisite software |
+.Net Framework 4 |
+
Supported operating systems |
+
|
+
| Input | +Description | +Example | +
|---|---|---|
Add element |
+ Specifies the products and languages to include in the package. |
+ N/A |
+
OfficeClientEdition (attribute of Add element) |
+ Specifies the edition of Office 2013 product to use: 32-bit or 64-bit. The operation fails if OfficeClientEdition is not set to a valid value. |
+ OfficeClientEdition="32" +OfficeClientEdition="64" |
+
Product element |
+ Specifies the application. Project 2013 and Visio 2013 must be specified here as an added product to be included in the applications. |
+
|
+
Language element |
+ Specifies the language supported in the applications |
+
|
+
Version (attribute of Add element) |
+ Optional. Specifies a build to use for the package +Defaults to latest advertised build (as defined in v32.CAB at the Office source). |
+
|
+
SourcePath (attribute of Add element) |
+ Specifies the location in which the applications will be saved to. |
+
|
+
\\server\Office2013 |
+ is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml. |
+
Setup.exe |
+ is the Office Deployment Tool. |
+
/download |
+ downloads the Office 2013 applications that you specify in the customConfig.xml file. These bits can be later converted in an Office 2013 App-V package with Volume Licensing. |
+
\\server\Office2013\Customconfig.xml |
+ passes the XML configuration file required to complete the download process, in this example, customconfig.xml. After using the download command, Office applications should be found in the location specified in the configuration xml file, in this example \\Server\Office2013. |
+
| Product ID | +Volume Licensing | +Subscription Licensing | +
|---|---|---|
Office 2013 |
+ProPlusVolume |
+O365ProPlusRetail |
+
Office 2013 with Visio 2013 |
+ProPlusVolume +VisioProVolume |
+O365ProPlusRetail +VisioProRetail |
+
Office 2013 with Visio 2013 and Project 2013 |
+ProPlusVolume +VisioProVolume +ProjectProVolume |
+O365ProPlusRetail +VisioProRetail +ProjectProRetail |
+
| Parameter | +What to change the value to | +||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SourcePath |
+ Point to the Office applications downloaded earlier. |
+ ||||||||||||
ProductID |
+ Specify the type of licensing, as shown in the following examples: +
|
+ ||||||||||||
ExcludeApp (optional) |
+ Lets you specify Office programs that you don’t want included in the App-V package that the Office Deployment Tool creates. For example, you can exclude Access and InfoPath. |
+ ||||||||||||
PACKAGEGUID (optional) |
+ By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use PACKAGEGUID to specify a different package ID for each package, which allows you to publish multiple App-V packages, created by the Office Deployment Tool, and manage them by using the App-V Server. +An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2013 for some users, and create another package with Office 2013 and Visio 2013 for another set of users. +
+ Note
+
+ Even if you use unique package IDs, you can still deploy only one App-V package to a single device. +
+
+ |
+
\\server\Office2013 |
+ is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml. |
+
Setup.exe |
+ is the Office Deployment Tool. |
+
/packager |
+ creates the Office 2013 App-V package with Volume Licensing as specified in the customConfig.xml file. |
+
\\server\Office2013\Customconfig.xml |
+ passes the configuration XML file (in this case customConfig) that has been prepared for the packaging stage. |
+
\\server\share\Office 2013AppV |
+ specifies the location of the newly created Office App-V package. |
+
| Prerequisite or requirement | +Details | +
|---|---|
Enable PowerShell scripting on the App-V clients |
+To publish Office 2013 packages, you must run a script. +Package scripts are disabled by default on App-V clients. To enable scripting, run the following PowerShell command: + |
+
Publish the Office 2013 package globally |
+Extension points in the Office App-V package require installation at the computer level. +When you publish at the computer level, no prerequisite actions or redistributables are needed, and the Office 2013 package globally enables its applications to work like natively installed Office, eliminating the need for administrators to customize packages. |
+
| Task | +Details | +||||||
|---|---|---|---|---|---|---|---|
How do I package and publish Visio 2013 and Project 2013 with Office? |
+You must include Visio 2013 and Project 2013 in the same package with Office. +If you aren’t deploying Office, you can create a package that contains Visio and/or Project, as long as you follow the [Virtualizing Microsoft Office 2013 for Application Virtualization (App-V) 5.0](../solutions/virtualizing-microsoft-office-2013-for-application-virtualization--app-v--50-solutions.md#bkmk-pkg-pub-reqs). |
+||||||
How can I deploy Visio 2013 and Project 2013 to specific users? |
+Use one of the following methods: +
|
+
| + | Task | +References | +Notes | +
|---|---|---|---|
 |
+Complete the planning phase to prepare the computing environment for App-V 5.1 deployment. |
+[App-V 5.1 Planning Checklist](appv-planning-checklist.md) |
++ |
|
+Review the App-V 5.1 supported configurations information to make sure selected client and server computers are supported for App-V 5.1 feature installation. |
+[App-V 5.1 Supported Configurations](appv-supported-configurations.md) |
++ |
|
+Run App-V 5.1 Setup to deploy the required App-V 5.1 features for your environment. +
+Note
+
+Keep track of the names of the servers and associated URL’s created during installation. This information will be used throughout the installation process. +
+
+ |
+
+
|
++ |
User Configuration .xml file |
+
Deployment Configuration .xml file |
+
Package Manifest |
+
| Script Execution Time | +Can be specified in Deployment Configuration | +Can be specified in User Configuration | +Can run in the Virtual Environment of the package | +Can be run in the context of a specific application | +Runs in system/user context: (Deployment Configuration, User Configuration) | +
|---|---|---|---|---|---|
AddPackage |
+X |
++ | + | + | (SYSTEM, N/A) |
+
PublishPackage |
+X |
+X |
++ | + | (SYSTEM, User) |
+
UnpublishPackage |
+X |
+X |
++ | + | (SYSTEM, User) |
+
RemovePackage |
+X |
++ | + | + | (SYSTEM, N/A) |
+
StartProcess |
+X |
+X |
+X |
+X |
+(User, User) |
+
ExitProcess |
+X |
+X |
++ | X |
+(User, User) |
+
StartVirtualEnvironment |
+X |
+X |
+X |
++ | (User, User) |
+
TerminateVirtualEnvironment |
+X |
+X |
++ | + | (User, User) |
+
| Parameter in the example file | +Description | +
|---|---|
|
+Name of the event trigger for which you are running a script, such as adding a package or publishing a package. |
+
|
+The script launcher application that is installed as part of the App-V client installation. +
+Note
+
+Although ScriptRunner.exe is installed as part of the App-V client, the location of the App-V client must be in %path% or ScriptRunner will not run. ScriptRunner.exe is typically located in the C:\Program Files\Microsoft Application Virtualization\Client folder. +
+
+ |
+
|
+
|
+
|
+Waits for overall completion of ScriptRunner.exe. +Set the timeout value for the overall runner to be greater than or equal to the sum of the timeout values on the individual scripts. +If any individual script reported an error and rollbackonerror was set to |
+
| Setting | +Description | +
|---|---|
ReportingEnabled |
+ Enables the client to return information to a reporting server. This setting is required for the client to collect the reporting data on the client. |
+
ReportingServerURL |
+ Specifies the location on the reporting server where client information is saved. For example, http://<reportingservername>:<reportingportnumber>. +
+ Note
+
+ This is the port number that was assigned during the Reporting Server setup +
+
+ |
+
Reporting Start Time |
+ This is set to schedule the client to automatically send the data to the server. This setting will indicate the hour at which the reporting data will start to send. It is in the 24 hour format and will take a number between 0-23. |
+
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. |
+
ReportingInterval |
+ Specifies the retry interval that the client will use to resend data to the reporting server. |
+
ReportingDataCacheLimit |
+ 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. |
+
ReportingDataBlockSize |
+ 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. |
+
| Element | +Description | +
|---|---|
App-V Management Server |
+
|
+
App-V Publishing Server |
+
|
+
App-V Desktop Client |
+
|
+
App-V Remote Desktop Services (RDS) Client |
+Enables Remote Desktop Session Host servers to use the capabilities of the App-V Desktop Client for shared desktop sessions. |
+
App-V Sequencer |
+
|
+
| Element | +More information | +
|---|---|
App-V 5.1 Management Server |
+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: +
|
+
App-V 5.1 Publishing Server |
+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: +
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. |
+
App-V 5.1 Reporting Server |
+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. |
+
App-V 5.1 Client |
+The App-V 5.1 client enables packages created using App-V 5.1 to run on target computers. |
+
| Command | +Description | +
|---|---|
/INSTALLDIR |
+Specifies the installation directory. |
+
/CEIPOPTIN |
+Enables participation in the Microsoft Customer Experience Improvement Program. |
+
/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 5.1. 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. |
+
| Requirement | +Details | +||||||
|---|---|---|---|---|---|---|---|
Users can run App-V Server cmdlets only if you grant them access by using one of the following methods: |
+
|
+||||||
Cmdlets that require an elevated command prompt |
+
|
+||||||
Cmdlets that end users can run, unless you configure them to require an elevated command prompt |
+
To configure these cmdlets to require an elevated command prompt, use one of the following methods: +
|
+
| App-V component | +Command to type | +
|---|---|
App-V Server |
+Import-Module AppvServer |
+
App-V Sequencer |
+Import-Module AppvSequencer |
+
App-V Client |
+Import-Module AppvClient |
+
| Format | +Description | +||||||||
|---|---|---|---|---|---|---|---|---|---|
As a downloadable module |
+To download the latest help after downloading the cmdlet module: +
|
+||||||||
On TechNet as web pages |
+See the App-V node under [Microsoft Desktop Optimization Pack Automation with Windows PowerShell](http://technet.microsoft.com/library/dn520245.aspx). |
+
| Publishing method | +Cmdlet and example | +
|---|---|
Publishing to the user |
+Cmdlet: Publish-AppvClientPackage +Example: Publish-AppvClientPackage “ContosoApplication” |
+
Publishing globally |
+Cmdlet: Publish-AppvClientPackage +Example: Publish-AppvClientPackage “ContosoApplication” -Global |
+
Cmdlet |
+Set-AppvClientConfiguration |
+
Parameter |
+-RequirePublishAsAdmin +Parameter values: +
Example:: Set-AppvClientConfiguration –RequirePublishAsAdmin1 |
+
| Cmdlet output item | +Description | +
|---|---|
UserPending |
+Indicates whether the listed package has a pending task that is being applied to the user: +
|
+
GlobalPending |
+Indicates whether the listed package has a pending task that is being applied globally to the computer: +
|
+
| Task type | +Applicable rule | +
|---|---|
User-based task, e.g., publishing a package to a user |
+The pending task will be performed after the user logs off and then logs back on. |
+
Globally based task, e.g., enabling a connection group globally |
+The pending task will be performed when the computer is shut down and then restarted. |
+
| Cmdlet | +Examples | +
|---|---|
Enable-AppVClientConnectionGroup |
+ Enable-AppVClientConnectionGroup “ConnectionGroupA” -UserSID S-1-2-34-56789012-3456789012-345678901-2345 |
+
Disable -AppVClientConnectionGroup |
+ Disable -AppVClientConnectionGroup “ConnectionGroupA” -UserSID S-1-2-34-56789012-3456789012-345678901-2345 |
+
| Cmdlet | +Parameter and values | +Example | +
|---|---|---|
Set-AppvClientConfiguration |
+ –RequirePublishAsAdmin +
|
+ Set-AppvClientConfiguration –RequirePublishAsAdmin1 |
+
[About the Connection Group Virtual Environment](appv-connection-group-virtual-environment.md) |
+Describes the connection group virtual environment. |
+
[About the Connection Group File](appv-connection-group-file.md) |
+Describes the connection group file. |
+
[How to Create a Connection Group](appv-create-a-connection-group.md) |
+Explains how to create a new connection group. |
+
[How to Create a Connection Group with User-Published and Globally Published Packages](appv-create-a-connection-group-with-user-published-and-globally-published-packages.md) |
+Explains how to create a new connection group that contains a mix of packages that are published to the user and published globally. |
+
[How to Delete a Connection Group](appv-delete-a-connection-group.md) |
+Explains how to delete a connection group. |
+
[How to Publish a Connection Group](appv-publish-a-connection-group.md) |
+Explains how to publish a connection group. |
+
| New in App-V 5.1 | +Prior to App-V 5.1 | +
|---|---|
New .xml files are created corresponding to the .osd files associated with a package; these files include the following information: +
You can now choose to add information from a subset of the .osd files in the source directory to the package using the |
+Registry information and scripts included in .osd files associated with a package were not included in package converter output. +The package converter would populate the new package with information from all of the .osd files in the source directory. |
+
| These Source directory files… | +…are converted to these Destination directory files… | +…and will contain these items | +Description | +
|---|---|---|---|
|
+
|
+
|
+Each .osd file is converted to a separate, corresponding .xml file that contains the items listed here in App-V 5.1 deployment configuration format. These items can then be copied from these .xml files and placed in the deployment configuration or user configuration files as desired. +In this example, there are three .xml files, corresponding with the three .osd files in the source directory. Each .xml file contains the environment variables, shortcuts, file type associations, registry information, and scripts in its corresponding .osd file. |
+
|
+
|
+
|
+The information from the .osd files specified in the In this example, environment variables, shortcuts, and file type associations included in X.osd and Y.osd were converted and placed in the App-V package, and some of this information was also included in the deployment configuration and user configuration files. X.osd and Y.osd were used because they were included as arguments to the |
+
| Issue | +Workaround | +
|---|---|
Virtual packages using DSC are not linked after conversion. |
+Link the packages using connection groups. See [Managing Connection Groups](appv-managing-connection-groups.md). |
+
Environment variable conflicts are detected during conversion. |
+Resolve any conflicts in the associated .osd file. |
+
Hard-coded paths are detected during conversion. |
+Hard-coded paths are difficult to convert correctly. The package converter will detect and return packages with files that contain hard-coded paths. View the file with the hard-coded path, and determine whether the package requires the file. If so, it is recommended to re-sequence the package. |
+
| Task | +More Information | +
|---|---|
Upgrade your environment to the latest version of App-V 4.6 |
+[Application Virtualization Deployment and Upgrade Considerations](../appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy.md). |
+
Install the App-V 5.1 client with co-existence enabled. |
+[How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer](appv-deploy-the-appv-46x-and-the-appv--51-client-on-the-same-computer.md). |
+
Sequence and roll out App-V 5.1 packages. As needed, unpublish App-V 4.6 packages. |
+[How to Sequence a New Application with App-V 5.1](appv-sequence-a-new-application.md). |
+
| Task | +More Information | +
|---|---|
Upgrade your environment to the latest version of App-V 4.6. |
+[Application Virtualization Deployment and Upgrade Considerations](../appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy.md). |
+
Deploy App-V 5.1 version of the client. |
+[How to Deploy the App-V Client](appv-deploy-the-appv-client.md). |
+
Install App-V 5.1 server. |
+[How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md). |
+
Migrate existing packages. |
+See the Converting packages created using a prior version of App-V section of this article. |
+
|
+Non-Persistent VDI or RDSH. |
+
|
+User Experience Virtualization (UE-V), other UPM solutions or User Profile Disks (UPD). |
+
|
+User Experience Virtualization (UE-V) with the App-V user state template enabled or User Profile Management (UPM) software. Non-UE-V UPM software must be capable of triggering on Login or Process/Application Start and Logoff. |
+
|
+App-V Shared Content Store (SCS) is configured or can be configured. |
+
|
+Admin may need to update the VM base image regularly to ensure optimal performance or Admin may need to manage multiple images for different user groups. |
+
| Optimized for Performance | +Optimized for Storage | +
|---|---|
To provide the most optimal user experience, this approach leverages the capabilities of a UPM solution and requires additional image preparation and can incur some additional image management overhead. +The following describes many performance improvements in stateful non-persistent deployments. For more information, see the Sequencing Steps to Optimize Packages for Publishing Performance and reference to App-V Sequencing Guide in the See Also section of this document. |
+The general expectations of the previous scenario still apply here. However, keep in mind that VM images are typically stored in very costly arrays; a slight alteration has been made to the approach. Do not pre-configure user-targeted virtual application packages in the base image. +The impact of this alteration is detailed in the User Experience Walkthrough section of this document. |
+
| Optimized for Performance | +Optimized for Storage | +
|---|---|
+
|
+
+
|
+
| Configuration Setting | +What does this do? | +How should I use it? | +
|---|---|---|
Shared Content Store (SCS) Mode +
|
+When running the shared content store only publishing data is maintained on hard disk; other virtual application assets are maintained in memory (RAM). +This helps to conserve local storage and minimize disk I/O per second (IOPS). |
+This is recommended when low-latency connections are available between the App-V Client endpoint and the SCS content server, SAN. |
+
PreserveUserIntegrationsOnLogin +
|
+If you have not pre-configured (Add-AppvClientPackage) a specific package and this setting is not configured, the App-V Client will de-integrate* the persisted user integrations, then re-integrate*. +For every package that meets the above conditions, effectively twice the work will be done during publishing/refresh. |
+If you don’t plan to pre-configure every available user package in the base image, use this setting. |
+
MaxConcurrentPublishingRefresh +
|
+This setting determines the number of users that can perform a publishing refresh/sync at the same time. The default setting is no limit. |
+Limiting the number of concurrent publishing refreshes prevents excessive CPU usage that could impact computer performance. This limit is recommended in an RDS environment, where multiple users can log in to the same computer at the same time and perform a publishing refresh sync. +If the concurrent publishing refresh threshold is reached, the time required to publish new applications and make them available to end users after they log in could take an indeterminate amount of time. |
+
| Optimized for Performance | +Optimized for Storage | +
|---|---|
After implementing this approach in the VDI/RDSH environment, on first login, +
On subsequent logins: +
¹ The publishing operation (Publish-AppVClientPackage) adds entries to the user catalog, maps entitlement to the user, identifies the local store, and finishes by completing any integration steps. |
+After implementing this approach in the VDI/RDSH environment, on first login, +
On subsequent logins: +
|
+
| Outcome | +Outcome | +
|---|---|
+
|
+Because the add/refresh must re-configure all the virtual applications to the VM, the publishing refresh time on every login will be extended. |
+
| Step | +Consideration | +Benefits | +Tradeoffs | +
|---|---|---|---|
No Feature Block 1 (FB1, also known as Primary FB) |
+No FB1 means the application will launch immediately and stream fault (application requires file, DLL and must pull down over the network) during launch.If there are network limitations, FB1 will: +
|
+Stream faulting decreases the launch time. |
+Virtual application packages with FB1 configured will need to be re-sequenced. |
+
| Step | +Considerations | +Benefits | +Tradeoffs | +
|---|---|---|---|
No SXS Install at Publish (Pre-Install SxS assemblies) |
+Virtual Application packages do not need to be re-sequenced. SxS Assemblies can remain in the virtual application package. |
+The SxS Assembly dependencies will not install at publishing time. |
+SxS Assembly dependencies must be pre-installed. |
+
| Step | +Considerations | +Benefits | +Tradeoffs | +
|---|---|---|---|
Selectively Employ Dynamic Configuration files |
+The App-V 5.1 client must parse and process these Dynamic Configuration files. +Be conscious of size and complexity (script execution, VREG inclusions/exclusions) of the file. +Numerous virtual application packages may already have User- or computer–specific dynamic configurations files. |
+Publishing times will improve if these files are used selectively or not at all. |
+Virtual application packages would need to be reconfigured individually or via the App-V server management console to remove associated Dynamic Configuration files. |
+
| Step | +Considerations | +Benefits | +Tradeoffs | +
|---|---|---|---|
Account for Synchronous Script Execution during Package Lifecycle. |
+If script collateral is embedded in the package, Add (Powershell) may be significantly slower. +Running of scripts during virtual application launch (StartVirtualEnvironment, StartProcess) and/or Add+Publish will impact the perceived performance during one or more of these lifecycle operations. |
+Use of Asynchronous (Non-Blocking) Scripts will ensure that the lifecycle operations complete efficiently. |
+This step requires working knowledge of all virtual application packages with embedded script collateral, which have associated dynamic configurations files and which reference and run scripts synchronously. |
+
Remove Extraneous Virtual Fonts from Package. |
+The majority of applications investigated by the App-V product team contained a small number of fonts, typically fewer than 20. |
+Virtual Fonts impact publishing refresh performance. |
+Desired fonts will need to be enabled/installed natively. For instructions, see Install or uninstall fonts. |
+
| + | Task | +References | +Notes | +
|---|---|---|---|
|
+Review the getting started information about App-V 5.1 to gain a basic understanding of the product before beginning deployment planning. |
+[Getting Started with App-V 5.1](appv-getting-started.md) |
++ |
|
+Plan for App-V 5.1 1.0 Deployment Prerequisites and prepare your computing environment. |
+[App-V 5.1 Prerequisites](appv-prerequisites.md) |
++ |
|
+If you plan to use the App-V 5.1 management server, plan for the required roles. |
+[Planning for the App-V 5.1 Server Deployment](appv-planning-for-appv-server-deployment.md) |
++ |
|
+Plan for the App-V 5.1 sequencer and client so you to create and run virtualized applications. |
+[Planning for the App-V 5.1 Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md) |
++ |
|
+If applicable, review the options and steps for migrating from a previous version of App-V. |
+[Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md) |
++ |
|
+Plan for running App-V 5.1 clients using in shared content store mode. |
+[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) |
++ |
Requirements |
+To use %AppData% folder redirection, you must: +
|
+||||||
Unsupported scenarios |
+
|
+
| Virtual environment state | +Action that occurs | +
|---|---|
When the virtual environment starts |
+The virtual file system (VFS) AppData folder is mapped to the local AppData folder (%LocalAppData%) instead of to the user’s roaming AppData folder (%AppData%). +
+Note
+
+The App-V client folder redirection sometimes fails to move files from %AppData% to %LocalAppData%. See [Release Notes for App-V 5.0 SP2](release-notes-for-app-v-50-sp2.md#bkmk-folderredirection). +
+
+ |
+
When the virtual environment shuts down |
+The local cached data in AppData (roaming) is zipped up and copied to the “real” roaming AppData folder in %AppData%. A time stamp, which indicates the last known upload, is simultaneously saved as a registry key under: +
To provide redundancy, App-V keeps the three most recent copies of the compressed data under %AppData%. |
+
Purpose |
+Enables end users to work with files, which have been redirected to another folder, as if the files still existed on the local drive. |
+
Description |
+Folder redirection allows users and administrators to redirect the path of a folder to a network location. The documents in the folder are available to the user from any computer on the network. +
|
+
Usage example |
+You can redirect the Documents folder, which is usually stored on the computer's local hard disk, to a network location. The user can access the documents in the folder from any computer on the network. |
+
More resources |
+[Folder redirection overview](http://technet.microsoft.com/library/cc778976.aspx) |
+
| Server Type | +Protocols | +External Features Needed | +Reporting | ++ |
|---|---|---|---|---|
IIS server |
+HTTP +HTTPS |
+This server-protocol combination requires a mechanism to synchronize the content between the Management Server and the Streaming Server. When using HTTP or HTTPS, use an IIS server and a firewall to protect the server from exposure to the Internet. |
+Internal |
++ |
File |
+SMB |
+This server-protocol combination requires support to synchronize the content between the Management Server and the Streaming Server. Use a client computer with file sharing or streaming capability. |
+Internal |
++ |
| App-V 4.6.x client type | +App-V 5.1 client type | +
|---|---|
App-V 4.6 SP2 |
+App-V 5.1 |
+
App-V 4.6 SP2 RDS |
+App-V 5.1 RDS |
+
App-V 4.6 SP3 |
+App-V 5.1 |
+
App-V 4.6 SP3 RDS |
+App-V 5.1 RDS |
+
| App-V version | +Link to download the client | +Link to TechNet documentation | +
|---|---|---|
App-V 4.6 SP2 |
+[Microsoft Application Virtualization 4.6 Service Pack 2](http://www.microsoft.com/download/details.aspx?id=35513) |
+[About Microsoft Application Virtualization 4.6 SP2](http://technet.microsoft.com/library/jj680847.aspx) |
+
App-V 4.6 SP3 |
+[Microsoft Application Virtualization 4.6 Service Pack 3](http://www.microsoft.com/download/details.aspx?id=41187) |
+[About Microsoft Application Virtualization 4.6 SP3](http://technet.microsoft.com/library/dn511019.aspx) |
+
| Supported Office Version | +Supported App-V Versions | +Package Creation | +Supported Licensing | +Supported Deployments | +
|---|---|---|---|---|
Office 365 ProPlus +Also supported: +
|
+
|
+Office Deployment Tool |
+Subscription |
+
|
+
Office Professional Plus 2013 +Also supported: +
|
+
|
+Office Deployment Tool |
+Volume Licensing |
+
|
+
| Office version | +Link to guidance | +
|---|---|
Office 2013 |
+[Information about how to use Office 2013 suites and programs (MSI deployment) on a computer that is running another version of Office](http://support.microsoft.com/kb/2784668) |
+
Office 2010 |
+[Information about how to use Office 2010 suites and programs on a computer that is running another version of Office](http://support.microsoft.com/kb/2121447) |
+
| + | Mode in which App-V can sequence this version of Office | +
|---|---|
Office 2007 |
+Always non-integrated. App-V does not offer any operating system integrations with a virtualized version of Office 2007. |
+
Office 2010 |
+Integrated and non-integrated mode. |
+
Office 2013 |
+Always integrated. Windows operating system integrations cannot be disabled. |
+
| Extension Point | +Description | +
|---|---|
Lync meeting Join Plug-in for Firefox and Chrome |
+User can join Lync meetings from Firefox and Chrome |
+
Sent to OneNote Print Driver |
+User can print to OneNote |
+
OneNote Linked Notes |
+OneNote Linked Notes |
+
Send to OneNote Internet Explorer Add-In |
+User can send to OneNote from IE |
+
Firewall Exception for Lync and Outlook |
+Firewall Exception for Lync and Outlook |
+
MAPI Client |
+Native apps and add-ins can interact with virtual Outlook through MAPI |
+
SharePoint Plug-in for Firefox |
+User can use SharePoint features in Firefox |
+
Mail Control Panel Applet |
+User gets the mail control panel applet in Outlook |
+
Primary Interop Assemblies |
+Support managed add-ins |
+
Office Document Cache Handler |
+Allows Document Cache for Office applications |
+
Outlook Protocol Search handler |
+User can search in outlook |
+
Active X Controls: |
+For more information on ActiveX controls, refer to [ActiveX Control API Reference](http://go.microsoft.com/fwlink/p/?LinkId=331361). |
+
Groove.SiteClient |
+Active X Control |
+
PortalConnect.PersonalSite |
+Active X Control |
+
SharePoint.openDocuments |
+Active X Control |
+
SharePoint.ExportDatabase |
+Active X Control |
+
SharePoint.SpreadSheetLauncher |
+Active X Control |
+
SharePoint.StssyncHander |
+Active X Control |
+
SharePoint.DragUploadCtl |
+Active X Control |
+
SharePoint.DragDownloadCtl |
+Active X Control |
+
Sharepoint.OpenXMLDocuments |
+Active X Control |
+
Sharepoint.ClipboardCtl |
+Active X control |
+
WinProj.Activator |
+Active X Control |
+
Name.NameCtrl |
+Active X Control |
+
STSUPld.CopyCtl |
+Active X Control |
+
CommunicatorMeetingJoinAx.JoinManager |
+Active X Control |
+
LISTNET.Listnet |
+Active X Control |
+
OneDrive Pro Browser Helper |
+Active X Control] |
+
OneDrive Pro Icon Overlays |
+Windows Explorer shell icon overlays when users look at folders OneDrive Pro folders |
+
Shell extensions |
++ |
Shortcuts |
++ |
Windows Search |
++ |
| Deployment requirement or option | +Description | +
|---|---|
The App-V Management server, Management database, and Publishing server are not required. |
+These functions are handled by the implemented ESD solution. |
+
You can deploy the App-V Reporting server and Reporting database side by side with the ESD. |
+The side-by-side deployment lets you to collect data and generate reports. +If you enable the App-V client to send report information, and you are not using the App-V Reporting server, the reporting data is stored in associated .xml files. |
+
| Operating system | +Prerequisite description | +
|---|---|
Windows 10 |
+All of the prerequisite software is already installed. |
+
Windows 8.1 |
+All of the prerequisite software is already installed. +
+Note
+
+If you are running Windows 8, upgrade to Windows 8.1 before using App-V 5.1. +
+
+ |
+
Windows Server 2012 |
+The following prerequisite software is already installed: +
|
+
Windows 7 |
+The prerequisite software is not already installed. You must install it before you can install App-V. |
+
Account for installing the App-V Server |
+The account that you use to install the App-V Server components must have: +
|
+
Port and firewall |
+
|
+
Web Distributed Authoring and Versioning (WebDAV) |
+WebDAV is automatically disabled for the Management Service. |
+
Supported deployment scenarios |
+
|
+
Unsupported deployment scenarios |
+
|
+
| Prerequisites and required settings | +Details | +
|---|---|
Supported version of SQL Server |
+For supported versions, see [App-V 5.1 Supported Configurations](appv-supported-configurations.md). |
+
[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773) |
++ |
[Windows PowerShell 3.0](http://www.microsoft.com/download/details.aspx?id=34595) |
+Installing PowerShell 3.0 requires a restart. |
+
Download and install [KB2533623](http://support.microsoft.com/kb/2533623) |
+Applies to Windows 7 only. |
+
[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784) |
++ |
64-bit ASP.NET registration |
++ |
Windows Server Web Server Role |
+This role must be added to a server operating system that is supported for the Management server. |
+
Web Server (IIS) Management Tools |
+Click IIS Management Scripts and Tools. |
+
Web Server Role Services |
+Common HTTP Features: +
Application Development: +
Security: +
Management Tools: +
|
+
Default installation location |
+%PROGRAMFILES%\Microsoft Application Virtualization Server |
+
Location of the Management database |
+SQL Server database name, SQL Server database instance name, and database name. |
+
Management console and Management database permissions |
+A user or group that can access the Management console and database after the deployment is complete. Only these users or groups will have access to the Management console and database unless additional administrators are added by using the Management console. |
+
Management service website name |
+Name for the Management console website. |
+
Management service port binding |
+Unique port number for the Management service. This port cannot be used by another process on the computer. |
+
| Prerequisites and required settings | +Details | +
|---|---|
[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773) |
++ |
[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784) |
++ |
Default installation location |
+%PROGRAMFILES%\Microsoft Application Virtualization Server |
+
Custom SQL Server instance name (if applicable) |
+Format to use: INSTANCENAME +This format is based on the assumption that the installation is on the local computer. +If you specify the name with the format SVR\INSTANCE, the installation will fail. |
+
Custom database name (if applicable) |
+Unique database name. +Default: AppVManagement |
+
Management server location |
+Machine account on which the Management server is deployed. +Format to use: Domain\MachineAccount |
+
Management server installation administrator |
+Account used to install the Management server. +Format to use: Domain\AdministratorLoginName |
+
Microsoft SQL Server Service Agent |
+Configure the Management database computer so that the Microsoft SQL Server Agent service is restarted automatically. For instructions, see [Configure SQL Server Agent to Restart Services Automatically](http://technet.microsoft.com/magazine/gg313742.aspx). |
+
| Prerequisites and required settings | +Details | +||||||
|---|---|---|---|---|---|---|---|
[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773) |
++ | ||||||
[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784) |
++ | ||||||
64-bit ASP.NET registration |
++ | ||||||
Windows Server Web Server Role |
+This role must be added to a server operating system that is supported for the Management server. |
+||||||
Web Server (IIS) Management Tools |
+Click IIS Management Scripts and Tools. |
+||||||
Web Server Role Services |
+Common HTTP Features: +
Application Development: +
Security: +
Management Tools: +
|
+||||||
Default installation location |
+%PROGRAMFILES%\Microsoft Application Virtualization Server |
+||||||
Management service URL |
+URL of the App-V Management service. This is the port with which the Publishing server communicates. +
+ |
+||||||
Publishing service website name |
+Name for the Publishing website. |
+||||||
Publishing service port binding |
+Unique port number for the Publishing service. This port cannot be used by another process on the computer. |
+
| Prerequisites and required settings | +Details | +
|---|---|
Supported version of SQL Server |
+For supported versions, see [App-V 5.1 Supported Configurations](appv-supported-configurations.md). |
+
[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773) |
++ |
[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784) |
++ |
64-bit ASP.NET registration |
++ |
Windows Server Web Server Role |
+This role must be added to a server operating system that is supported for the Management server. |
+
Web Server (IIS) Management Tools |
+Click IIS Management Scripts and Tools. |
+
Web Server Role Services |
+To reduce the risk of unwanted or malicious data being sent to the Reporting server, you should restrict access to the Reporting Web Service per your corporate security policy. +Common HTTP Features: +
Application Development: +
Security: +
Management Tools: +
|
+
Default installation location |
+%PROGRAMFILES%\Microsoft Application Virtualization Server |
+
Reporting service website name |
+Name for the Reporting website. |
+
Reporting service port binding |
+Unique port number for the Reporting service. This port cannot be used by another process on the computer. |
+
| Prerequisites and required settings | +Details | +
|---|---|
[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773) |
++ |
[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784) |
++ |
Default installation location |
+%PROGRAMFILES%\Microsoft Application Virtualization Server |
+
Custom SQL Server instance name (if applicable) |
+Format to use: INSTANCENAME +This format is based on the assumption that the installation is on the local computer. +If you specify the name with the format SVR\INSTANCE, the installation will fail. |
+
Custom database name (if applicable) |
+Unique database name. +Default: AppVReporting |
+
Reporting server location |
+Machine account on which the Reporting server is deployed. +Format to use: Domain\MachineAccount |
+
Reporting server installation administrator |
+Account used to install the Reporting server. +Format to use: Domain\AdministratorLoginName |
+
Microsoft SQL Server Service and Microsoft SQL Server Service Agent |
+Configure these services to be associated with user accounts that have access to query AD DS. |
+
| Prerequisite | +Details | +
|---|---|
[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773) |
++ |
[Windows PowerShell 3.0](http://www.microsoft.com/download/details.aspx?id=34595) + |
+Installing PowerShell 3.0 requires a restart. |
+
[KB2533623](http://support.microsoft.com/kb/2533623) |
+Applies to Windows 7 only: Download and install the KB. |
+
[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784) |
++ |
| Prerequisite | +Details | +
|---|---|
[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773) |
++ |
[Windows PowerShell 3.0](http://www.microsoft.com/download/details.aspx?id=34595) + |
+Installing PowerShell 3.0 requires a restart. |
+
[KB2533623](http://support.microsoft.com/kb/2533623) |
+Applies to Windows 7 only: Download and install the KB. |
+
[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784) |
++ |
| Prerequisite | +Details | +
|---|---|
[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773) |
++ |
[Windows PowerShell 3.0](http://www.microsoft.com/download/details.aspx?id=34595) + |
+Installing PowerShell 3.0 requires a restart. |
+
[KB2533623](http://support.microsoft.com/kb/2533623) |
+Applies to Windows 7 only: Download and install the KB. |
+
| Question | +More Information | +
|---|---|
What is the frequency that reporting information is sent to the reporting database? |
+The frequency depends on how the reporting task is configured on the computer running the App-V 5.1 client. You must configure the frequency / interval for sending the reporting data. App-V 5.1 Reporting is not enabled by default. |
+
What information is stored in the reporting server database? |
+The following list displays what is stored in the reporting database: +
|
+
What is the average volume of information that is sent to the reporting server? |
+It depends. The following list displays the three sets of the data sent to the reporting server: +
|
+
Can reporting be scheduled? |
+Yes. Besides manually sending reporting using PowerShell Cmdlets (Send-AppvClientReport), the task can be scheduled so it will happen automatically. There are two ways to schedule the reporting: +
|
+
| Client Information | +Package Information | +Application Usage | +
|---|---|---|
Host Name |
+Package Name |
+Start and End Times |
+
App-V 5.1 Client Version |
+Package Version |
+Run Status |
+
Processor Architecture |
+Package Source |
+Shutdown State |
+
Operating System Version |
+Percent Cached |
+Application Name |
+
Service Pack Level |
++ | Application Version |
+
Operating System Type |
++ | Username |
+
| + | + | Connection Group |
+
| With a Reporting Server | +Without a Reporting Server | +
|---|---|
If you have an existing App-V 5.1 reporting Server, create a customized scheduled task or script. Specify that the client send the data to the specified location with the desired frequency. |
+If you do not have an existing App-V 5.1 reporting Server, use the –URL parameter to send the data to a specified share. For example: +
The previous example will send the reporting data to \\MyShare\MyData\ location indicated by the -URL parameter. After the data has been sent, the cache is cleared. +
+Note
+
+If a location other than the Reporting Server is specified, the data is sent using .xml format with no additional processing. +
+
+ |
+
| App-V version | +Supported publishing methods | +
|---|---|
App-V 5.0 SP3 and App-V 5.1 |
+Published globally or to the user |
+
App-V 5.0 through App-V 5.0 SP2 |
+Published globally only |
+
| Package publishing method | +Where to create the registry key | +
|---|---|
Published globally |
+ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual +Example: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual\MyApp.exe |
+
Published to the user |
+ HKEY_CURRENT_USER\SOFTWARE\Microsoft\AppV\Client\RunVirtual +Example: HKEY_CURRENT_USER \SOFTWARE\Microsoft\AppV\Client\RunVirtual\MyApp.exe |
+
Connection group can contain: +
|
+ Either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER key, but all of the following must be true: +
|
+
| Group name | +Details | +
|---|---|
App-V Management Admin group |
+Used to manage the App-V 5.1 management server. This group is created during the App-V 5.1 Management Server installation. +
+Important
+
+There is no method to create the group using the management console after you have completed the installation. +
+
+ |
+
Database read/write for Management Service account |
+Provides read/write access to the management database. This account should be created during the App-V 5.1 management database installation. |
+
App-V Management Service install admin account +
+Note
+
+This is only required if management database is being installed separately from the service. +
+
+ |
+Provides public access to schema-version table in management database. This account should be created during the App-V 5.1 management database installation. |
+
App-V Reporting Service install admin account +
+Note
+
+This is only required if reporting database is being installed separately from the service. +
+
+ |
+Public access to schema-version table in reporting database. This account should be created during the App-V 5.1 reporting database installation. |
+
| Application type | +Description | +
|---|---|
Standard |
+ Creates a package that contains an application or a suite of applications. This is the preferred option for most application types. |
+
Add-on or plug-in |
+ Creates a package that extends the functionality of a standard application, for example, a plug-in for Microsoft Excel. Additionally, you can use plug-ins for natively installed applications, or for another package that is linked by using connection groups. |
+
Middleware |
+ Creates a package that is required by a standard application, for example, Java. Middleware packages are used for linking to other packages by using connection groups. |
+
| Operating system | +Service Pack | +System architecture | +
|---|---|---|
Microsoft Windows Server 2012 R2 |
++ | 64-bit |
+
Microsoft Windows Server 2012 |
++ | 64-bit |
+
Microsoft Windows Server 2008 R2 |
+SP1 |
+64-bit |
+
| SQL Server version | +Service pack | +System architecture | +
|---|---|---|
Microsoft SQL Server 2014 |
++ | 32-bit or 64-bit |
+
Microsoft SQL Server 2012 |
+SP2 |
+32-bit or 64-bit |
+
Microsoft SQL Server 2008 R2 |
+SP3 |
+32-bit or 64-bit |
+
| Operating system | +Service Pack | +System architecture | +
|---|---|---|
Microsoft Windows Server 2012 R2 |
++ | 64-bit |
+
Microsoft Windows Server 2012 |
++ | 64-bit |
+
Microsoft Windows Server 2008 R2 |
+SP1 |
+64-bit |
+
| Operating system | +Service Pack | +System architecture | +
|---|---|---|
Microsoft Windows Server 2012 R2 |
++ | 64-bit |
+
Microsoft Windows Server 2012 |
++ | 64-bit |
+
Microsoft Windows Server 2008 R2 |
+SP1 |
+64-bit |
+
| SQL Server version | +Service pack | +System architecture | +
|---|---|---|
Microsoft SQL Server 2014 |
++ | 32-bit or 64-bit |
+
Microsoft SQL Server 2012 |
+SP2 |
+32-bit or 64-bit |
+
Microsoft SQL Server 2008 R2 |
+SP3 |
+32-bit or 64-bit |
+
| Operating system | +Service pack | +System architecture | +
|---|---|---|
Microsoft Windows 10 |
++ | 32-bit or 64-bit |
+
Microsoft Windows 8.1 |
++ | 32-bit or 64-bit |
+
Microsoft Windows 8 |
++ | 32-bit or 64-bit |
+
Windows 7 |
+SP1 |
+32-bit or 64-bit |
+
| Operating system | +Service Pack | +System architecture | +
|---|---|---|
Microsoft Windows Server 2012 R2 |
++ | 64-bit |
+
Microsoft Windows Server 2012 |
++ | 64-bit |
+
Microsoft Windows Server 2008 R2 |
+SP1 |
+64-bit |
+
| Operating system | +Service pack | +System architecture | +
|---|---|---|
Microsoft Windows Server 2012 R2 |
++ | 64-bit |
+
Microsoft Windows Server 2012 |
++ | 64-bit |
+
Microsoft Windows Server 2008 R2 |
+SP1 |
+64-bit |
+
Microsoft Windows 10 |
++ | 32-bit and 64-bit |
+
Microsoft Windows 8.1 |
++ | 32-bit and 64-bit |
+
Microsoft Windows 8 |
++ | 32-bit and 64-bit |
+
Microsoft Windows 7 |
+SP1 |
+32-bit and 64-bit |
+
| App-V Version | +System Center Configuration Manager 2007 | +System Center 2012 Configuration Manager | +System Center 2012 Configuration Manager SP1 | +System Center 2012 R2 Configuration Manager | +System Center 2012 R2 Configuration Manager SP1 | +System Center 2012 Configuration Manager SP2 | +System Center Configuration Manager Version 1511 | +
|---|---|---|---|---|---|---|---|
App-V 4.5 |
+R2 |
+No |
+No |
+No |
+No |
+No |
+No |
+
App-V 4.5 CU1 |
+R2 |
+No |
+No |
+No |
+No |
+No |
+No |
+
App-V 4.5 SP1 |
+R2 |
+No |
+No |
+No |
+No |
+No |
+No |
+
App-V 4.5 SP2 |
+R2 |
+No |
+No |
+No |
+No |
+No |
+No |
+
App-V 4.6 |
+R2, SP1 |
+No |
+No |
+No |
+No |
+No |
+No |
+
App-V 4.6 SP1 |
+R2, R3, SP2 |
+Yes |
+Yes |
+Yes |
+No |
+No |
+No |
+
App-V 4.6 SP2 |
+R2, R3, SP2 |
+Yes |
+Yes |
+Yes |
+No |
+No |
+No |
+
App-V 4.6 SP3 |
+R2, R3, SP2 |
+No |
+Yes |
+Yes |
+No |
+Yes |
+Yes |
+
App-V 5.0 |
+MSI-Wrapper-Only |
+No |
+Yes |
+Yes |
+Yes |
+Yes |
+Yes |
+
App-V 5.0 SP1 |
+MSI-Wrapper Only |
+No |
+Yes |
+Yes |
+Yes |
+Yes |
+Yes |
+
App-V 5.0 SP2 |
+MSI-Wrapper Only |
+No |
+2012 SP1 CU4 +App-V 5.0 HF5 or later |
+2012 R2 CU1 +App-V 5.0 HF5 or later |
+Yes |
+With App-V 5.0 SP2 HF5 or later |
+With App-V 5.0 SP2 HF5 or later |
+
App-V 5.0 SP2 HF4 |
+MSI-Wrapper Only |
+No |
+2012 SP1 CU4 +App-V 5.0 HF5 or later |
+2012 R2 CU1 +App-V 5.0 HF5 or later |
+Yes |
+Requires HF5 or later |
+Requires HF5 or later |
+
App-V 5.0 SP3 |
+MSI-Wrapper Only |
+No |
+2012 SP1 CU4 |
+2012 R2 CU1 |
+Yes |
+Yes |
+Yes |
+
App-V 5.1 |
+MSI-Wrapper Only |
+No |
+2012 SP1 CU4 |
+2012 R2 CU1 |
+Yes |
+Yes |
+Yes |
+
| Link to instructions | +Task | +
|---|---|
[Use one connection group, with optional packages, for multiple users who have different packages entitled to them](#bkmk-apps-plugs-optional) |
+Use a single connection group to make different groups of applications and plug-ins available to different end users. +For example, you want to distribute Microsoft Office to all end users, but distribute different plug-ins to different subsets of users. |
+
[Unpublish or delete an optional package, or unpublish an optional package and republish it later, without changing the connection group](#bkmk-unpub-del-optl-pkg) |
+Unpublish, delete, or republish an optional package without having to disable, remove, edit, add, and re-enable the connection group on the App-V Client. +You can also unpublish the optional package and republish it later without having to disable or republish the connection group. |
+
| Task description | +How to perform the task | +||||||||
|---|---|---|---|---|---|---|---|---|---|
With App-V 5.0 SP3 and App-V 5.1 +You can add optional packages to connection groups, which enables you to provide different combinations of applications and plug-ins to different end users. +Example: You want to distribute Microsoft Office to your end users, but enable a certain plug-in for only a subset of users. +To do this, create a connection group that contains a package with Office, and another package with Office plug-ins, and then make the plug-ins package optional. +End users who are not entitled to the plug-in package will still be able to run Office. |
+
|
+||||||||
With versions earlier than App-V 5.0 SP3 |
+You had to create many connection groups to make specific application and plug-in combinations available to specific users. |
+
| Task description | +How to perform the task | +||||||
|---|---|---|---|---|---|---|---|
With App-V 5.0 SP3 and App-V 5.1 +You can unpublish, delete, or republish an optional package, which is in a connection group, without having to disable or re-enable the connection group on the App-V Client. +You can also unpublish an optional package and republish it later without having to disable or republish the connection group. +Example: If you publish an optional package that contains a Microsoft Office plug-in, and you want to remove the plug-in, you can unpublish the package without having to disable the connection group. |
+
|
+||||||
With versions earlier than App-V 5.0 SP3 |
+You had to: +
|
+
| Requirement | +Details | +
|---|---|
Connection groups must contain at least one non-optional package. |
+
|
+
|
+Globally published connection groups must contain packages that are published globally to ensure that the packages will be available when starting the connection group’s virtual environment. +If you try to add or enable globally published connection groups that contain user-published packages, the connection group will fail. |
+
You must publish all non-optional packages before publishing the connection group that contains those packages. |
+A connection group’s virtual environment cannot start if any non-optional packages are missing. +The App-V Client fails to add or enable a connection group if any non-optional packages have not been published. |
+
Before you unpublish a globally published package, ensure that the connection groups that are entitled to all the users on that computer no longer require the package. |
+The system does not check whether the package is part of another user’s connection group. Unpublishing a global package will make it unavailable to every user on that computer, so make sure that each user’s connection groups no longer contain the package, or alternatively make the package optional. |
+
| Tab | +Description | +
|---|---|
Overview |
+The Overview tab contains the following elements: +
|
+
Virtual Apps |
+The VIRTUAL APPS tab displays all of the packages that have been published to the user. You can also click a specific package and see all of the applications that are part of that package. This displays information about packages that are currently in use and how much of each package has been downloaded to the computer. You can also start and stop package downloads. Additionally, you can repair the user state. A repair will delete all user data that is associated with a package. + |
+
App Connection Groups |
+The APP CONNECTION GROUPS tab displays all of the connection groups that are available to the current user. Click a specific connection group to see all of the packages that are part of the selected group. This displays information about connection groups that are already in use and how much of the connection group contents have been downloaded to the computer. Additionally, you can start and stop connection group downloads. You can use this section to initiate a repair. A repair will remove all of the user state that is associated a connection group. +(Associated PowerShell cmdlets: Download - Mount-AppvClientConnectionGroup. Repair -AppvClientConnectionGroup.) + |
+
| Value | +Additional details | +
|---|---|
ClientVersion |
+If you omit the ClientVersion parameter from the query, the metadata excludes the features that were new in App-V 5.0 SP3. |
+
ClientOS |
+You have to provide this value only if you select specific client operating systems when you sequence the package. If you select the default (all operating systems), do not specify this value in the query. +If you omit the ClientOS parameter from the query, only the packages that were sequenced to support any operating system appear in the metadata. |
+
| Version of App-V | +Query syntax | +Parameter descriptions | +Example | +||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
App-V 5.0 SP3 and App-V 5.1 |
+
|
+
+ To get the name of the Publishing server and the port number (http://<PubServer>:<Publishing Port#>) from the App-V Client, look at the URL configuration of the Get-AppvPublishingServer PowerShell cmdlet. |
+
In the example: +
|
+||||||||||
App-V 5.0 through App-V 5.0 SP2 |
+
+Note
+
+ClientVersion and ClientOS are supported only in App-V 5.0 SP3 and App-V 5.1. +
+
+ |
+See the information for App-V 5.0 SP3 and App-V 5.1. |
+
In the example, A Windows Server 2012 R2 named “pubsvr01” hosts the Management and Publishing services. |
+
| Operating system | +Architecture | +Operating string string value | +
|---|---|---|
Windows 10 |
+64-bit |
+WindowsClient_10.0_x64 |
+
Windows 10 |
+32-bit |
+WindowsClient_10.0_x86 |
+
Windows 8.1 |
+64-bit |
+WindowsClient_6.2_x64 |
+
Windows 8.1 |
+32-bit |
+WindowsClient_6.2_x86 |
+
Windows 8 |
+64-bit |
+WindowsClient_6.2_x64 |
+
Windows 8 |
+32-bit |
+WindowsClient_6.2_x86 |
+
Windows Server 2012 R2 |
+64-bit |
+WindowsServer_6.2_x64 |
+
Windows Server 2012 R2 |
+32-bit |
+WindowsServer_6.2_x86 |
+
Windows Server 2012 |
+64-bit |
+WindowsServer_6.2_x64 |
+
Windows Server 2012 |
+32-bit |
+WindowsServer_6.2_x86 |
+
Windows 7 |
+64-bit |
+WindowsClient_6.1_x64 |
+
Windows 7 |
+32-bit |
+WindowsClient_6.1_x86 |
+
Windows Server 2008 R2 |
+64-bit |
+WindowsServer_6.1_x64 |
+
Windows Server 2008 R2 |
+32-bit |
+WindowsServer_6.1_x86 |
+