If VPrefer fails to launch the selected application, then it would fall back to the KEYWORDS:Prefer option (if also configured for the app). If both methods have been configured, the VPrefer method will take precedence. Customers have a choice as to which method to employ. Administrators are still able to control published app launch behavior using the existing KEYWORDS:Prefer=“application” tag in Citrix Studio. The VPrefer feature and KEYWORDS:Prefer feature can essentially be configured to create the same resultant behavior that is, to have a local app will launch instead of the published app equivalent.The VPrefer feature works only with native Receiver launches of published apps – it cannot be used to launch an app locally if the published app is launched through the StoreFront site in a web browser.Ĭonsiderations when using the VPrefer feature.The VPrefer feature requires a minimum of StoreFront 3.14, Citrix Receiver for Windows 4.11, and Delivery Controller 7.17.It is not currently available in the Citrix Studio graphical interface This option is available only through PowerShell.The application's ApplicationType value must be HostedOnDesktop.Limitations of the VPrefer feature When configuring an application launch behavior with the Admins can check the current LocalLaunchDisabled property value for each published app by using the Get-BrokerApplication cmdlet.If the LocalLaunchDisabled property is set to $true, the published app will always launch, no matter what the Receiver for Windows VPrefer policy is configured to.By default, the LocalLaunchDisabled property is set to $false, which means that by default, the Receiver for Windows VPrefer policy can successfully allow local installs of an app to launch instead of the published app equivalent.A new LocalLaunchDisabled property has been added to the Set-BrokerApplication and New-BrokerApplication cmdlets.The XML data in the app launch request incorporates the VPrefer tags and data:ĭelivery Controller (PowerShell) The Delivery Controller 7.17 Broker includes PowerShell support for the new VPrefer feature: StoreFront The new StoreFront 3.14 version released with XenApp and XenDesktop 7.17 includes support for the VPrefer setting: The behavior configured using Receiver for Windows VPrefer policy operates in conjunction with a new PowerShell cmdlet property (described later in this article).When the Enable VPrefer policy is set to “Not Configured”, the default behavior is:.AllowNetworkApps: The published app will always launch.excluding local Win32 apps) will launch locally instead of the equivalent published app AllowInstalledApps: Only additionally installed local apps (i.e.AllowAllApps: The app will launch locally instead of the equivalent published app.AllowApps Options (only configurable when VPrefer policy is set to Enabled):.The VPrefer feature simplifies local app launches in published desktop sessions and provides precise control through a combination of Receiver policy and PowerShell.Ī new Receiver for Windows 4.11 policy setting controls the overall behavior: Purpose/Benefit Double-hop published application launch control has historically required the use of the KEYWORDS:Prefer tag along with some complex workarounds by customers to achieve certain use cases. Code changes to Receiver for Windows, StoreFront, and the Delivery Controller have been introduced to support this feature.In addition, a new PowerShell cmdlet property controls, on an app-by-app basis, whether the published app will launch or the VDA installed equivalent. When a user attempts to launch a published app from a published desktop session, a Receiver for Windows policy controls whether the app will launch the locally installed version of the app on the VDA instead.This feature was designed to control how published applications are treated when launched from a published desktop session (double-hop scenario).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |