Published Applications

Last Modified: Dec 22, 2023 @ 5:02 am

267 Comments

Navigation

💡 = Recently Updated

Change Log

RDSH Application Testing

Installing apps on Remote Desktop Session Host (Virtual Apps or XenApp) is more complicated than installing apps on a single-user operating system (virtual desktop). Here are some RDSH-specific considerations that must be tested before integrating a new application into RDSH. These considerations usually don’t apply to virtual desktops.

  •  Multi-user Capable – can the application run multiple times on the same machine by different users? Most applications don’t have a problem, but a few do, especially applications that put temporary files or other writable files in global locations. For example, the first user of an app could write temporary files to C:\Temp. The second user writes to the same location, overwriting the temp files needed by the first user. Test the app with multiple users running the app on the same RDSH machine.
  • Lockdown to prevent one user from affecting another – What restrictions are needed to prevent one user from affecting another? For example, if an app’s configuration files are stored in a global location, you don’t want one user to edit the configuration file, and thus affect a different user. Test the app with multiple users running the app on the same RDSH machine.
  • Permission Relaxations – what relaxations (e.g. NTFS) are needed to allow non-administrators and GPO locked-down users to run the application? Test the application as a non-administrator with GPO lock down policies applied.
  • First Time Use – when a user launches an application the first time, the application should be automatically fully configured with default settings (e.g. back-end server connections). Use group policy to apply application settings. Automated FTU also helps with a user whose profile is reset. Test the RDSH app with a user that has a new (clean) profile.
  • Roaming – users could connect to a different RDSH machine every day, and thus user settings need to roam across machines. Test running the app on one RDSH, make changes, then login to a different RDSH machine to ensure the changes are still there.
  • Application Licensing – if an application requires licensing, can licensed and non-licensed users connect to the same machine? Can it be guaranteed that non-licensed users can’t run the application that requires licensing? Adobe Acrobat is an example of a challenging application because of the global .pdf file-type association, and the global PDF printer.
  • Client Devices (USB, printers, COM ports) – the client device mapping capabilities on RDSH are not as extensive as virtual desktops. For example, generic USB wasn’t added until Windows Server 2012 R2. When the application prints, does it show printers from every user, instead of just the user running the app? Does the app need COM port mapping?
  • Shared IP – does the app have any problems with multiple users sharing the same IP address? If so, you might have to configure RDS IP Virtualization.
  • Fair Sharing of Hardware Resources– does the app sometimes consume a disproportionate amount of hardware resources? For example, can the app be used to launch a task that consumes 100% CPU for some time? One option is to put this app on its own Delivery Group. Or you can use Citrix Workspace Environment Manager to ensure fair sharing of hardware resources.
  • Published Application – can the app run as a published application that doesn’t have Explorer running in the background? Does the app (e.g. Internet Explorer web apps) need RunOnce.exe /AlternateShellStartup to fully initialize before it will run correctly as a published application? Some apps work without issue in a published desktop, but don’t work properly as published applications. When testing a published app, test it with a user that has a new (clean) profile. Connecting to the published desktop once will cause Active Setup to run, changing the user’s profile, thus distorting the published app testing results.
  • Integration Testing – when installing a new app on a RDSH server, don’t forget to test the other apps already on the RDSH server, because the new app might have broken the other apps. The more apps you put on an RDSH server, the longer it takes to perform integration testing.

Also see MSDN Remote Desktop Services programming guidelines.

Some of the issues in this list can be overcome by using an application virtualization tool (e.g. Microsoft App-V) that runs apps in isolated bubbles.

Application Groups

Citrix Blog Post Introducing Application Groups in XenApp and XenDesktop 7.9

Citrix Virtual Apps and Desktops and XenApp 7.9 and newer has an Application Group feature. This feature lets you group published apps together so you can more easily apply properties to every app in the group. Today, you can do the following:

  • Control visibility of every app in the app group (Users page).
  • Publish every app on the same Delivery Groups.
  • Prevent or allow apps in different Application Groups from running in the same session.
  • With one published app icon, test users launch from test Delivery Group, while production users launch from production Delivery Group.

To create an Application Group:

  1. In Citrix Studio, right-click Applications, and click Create Application Group.

    1. In the Getting Started page, click Next.
    2. In the Delivery Groups page, select the delivery groups you want these apps published from.
    3. In the Users page, select the users that can see the apps in this app group.
    4. Note: there are three levels of authorization. An app is only visible to a user if the user is assigned to all of the following:
      • Delivery Group
      • Application Group
      • Individual Published Apps in the Application Group
    5. Click Next.
    6. In the Applications page, publish applications like normal. The Existing option lets you select an app that’s already been published to a different Application Group or Delivery Group. Click Next.
    7. In the Summary page,  give the Application Group a name, and click Finish.
  2. In the Applications node in Studio, there’s a new Application Groups section.
  3. If you highlight your Application Group, on the right is the list of apps in the group. You can edit each of these published apps like normal.
  4. You can drag applications into an Application Group.

  5. However, this more of a copy than a move. To actually move the app exclusively into the Application Group, edit the individual app, and on the Groups page, remove all Delivery Groups (or other Application Groups). The app will instead inherit the Delivery Groups from the app group.
  6. If you edit the Application Group:
  7. The Settings page has an option for session sharing between Application Groups. Clearing this checkbox allows you to force applications in different Application Groups to run in different sessions.
  8. The Delivery Groups tab lets you set Delivery Group priority. If priority is identical, then sessions are load balanced. If priorities are different, then sessions are launched on Delivery Groups in priority order.
  9. The checkbox for Restrict launches to machines with tag lets you restrict the apps to only run on VDAs with the selected tag.
  10. In Citrix Virtual Apps and Desktops and XenApp/XenDesktop 7.13 and newer, you can use PowerShell to cause an Application Group to launch multiple app instances in separate sessions. Citrix Blog Post XenApp and XenDesktop 7.13: Launching an Application in Multiple Sessions.

Limit Icon Visibility

For Published Applications, there are three levels of application authorization: Delivery Group, Application Groups, and Published App Limit Visibility. A published app icon is only visible if the user is added to all three levels.

  1. Delivery Group (Users page). If the user is not assigned to the Delivery Group, then the user won’t see any application or desktop icon published from that Delivery Group.

  2. Limit Visibility – You can use the published app’s Limit Visibility page to restrict an icon to a subset of Delivery Group users.

  3. In Citrix Virtual Apps and Desktops (CVAD) and XenApp/XenDesktop 7.9 and newer, you can use Application Groups to restrict access to published icons.

  4. App Icons won’t appear unless users are added to all three of the above locations.

Published Desktops have separate authorization configuration:

  1. Citrix Virtual Apps and Desktops (CVAD) and XenApp/XenDesktop 7.8 and newer have a Desktops page in Delivery Group properties where you can publish multiple desktops and restrict access to those individual published desktops.

  2. In XenApp/XenDesktop prior to version 7.8, if a desktop is published from the Delivery Group, by default, every user assigned to the Delivery Group can see the icon. You can use the PowerShell command Set-BrokerEntitlementPolicyRule to limit the desktop icon to a subset of the users assigned to the Delivery Group.
    1. Run asnp citrix.*
    2. Run Get-BrokerEntitlementPolicyRule to see the published desktops.
    3. Then run Set-BrokerEntitlementPolicyRule to set the IncludedUsers or ExcludedUsers filters.

Published Content

Citrix Virtual Apps and Desktops (CVAD) and XenApp 7.11 and newer have Published Content where you can publish URLs that are opened in the user’s local browser. You can also publish UNC paths, which are opened with local Explorer or local application.

It’s not possible to publish content using Citrix Studio. Instead, use PowerShell.

The New-BrokerApplication cmdlet requires you to specify a Delivery Group which must have at least one registered machine in it. However, the published content does not actually launch from the Delivery Group since the URLs and/or UNCs open locally.

First run asnp citrix.*

Then run New-BrokerApplication -ApplicationType PublishedContent. Here is a sample PowerShell command:

New-BrokerApplication -Name "CitrixHomePage" -PublishedName "Citrix Home Page" -ApplicationType PublishedContent -CommandLineExecutable https://www.citrix.com -DesktopGroup RDSH12R2

Instead of publishing to a Delivery Group, you can publish to an Application Group by using the -ApplicationGroup switch. The Application Group must have Delivery Group(s) assigned to it.

Once the Published Content is created, you can see it in Citrix Studio. You can also edit it from Citrix Studio, including Limit Visibility and Groups (to move it to an Application Group).

Published Content can be placed in Application Groups, which supports properties to restrict access to the shortcut.

It does not appear to be possible to set the icon from Studio, but you can do it using PowerShell. See Citrix Blog Post @XDtipster – Changing Delivery Group Icons Revisited (XD7) for instructions to convert an icon to a base64 string, and import to Citrix Virtual Apps or XenApp using New-BrokerIcon -EnCodedIconData "Base64 String".  Then you can link the icon to the Published Content using Set-BrokerApplication "App Name" -IconUid.

In StoreFront 3.7, you can click the icon and URLs will open in a new browser tab.

HTTP/HTTPS Published Content should open in Receiver. Other URLs (e.g. file:// or UNC path) will probably show an error message.

You can override this restriction by enabling the group policy setting Allow/Prevent users to publish unsafe content at Computer Configuration | Policies | Administrative Templates | Citrix Components | Citrix Receiver | SelfService. This assumes you’ve installed the Receiver .admx files. (h/t David Prows at CUGC forums).

Application Usage Limits

In Citrix Virtual Apps and Desktops (CVAD) and XenApp/XenDesktop 7.7 or newer, if you edit an application’s Properties, on the Delivery page, you can restrict the number of concurrent instances of the application. You can also Limit to one instance per user.

Citrix Virtual Apps and Desktops (CVAD) 1808 and newer support limiting the number of application instances per machine. This setting is configured using PowerShell. See Configure application limits at Citrix Docs.

asnp citrix.*
Set-BrokerApplication MyApplication -MaxPerMachineInstances 2

To revert to unlimited per-machine instances of the published application, set MaxPerMachineInstances to 0.

Keywords for StoreFront

In a published application’s Properties, on the Identification page, in the Description and keywords field, you can enter KEYWORDS to control how the app behaves when displayed by StoreFront.

  • Enter KEYWORDS:Mandatory or KEYWORDS:Auto to cause the application to automatically be subscribed or favorited in Citrix Receiver.
    • In StoreFront 3.0 and newer, the user can go to the Apps tab, click an App’s Details button, and mark the app as a Favorite. 
    • In the older StoreFront interface, users subscribe to applications by clicking the plus icon to add the application to the middle of the screen. 
    • Mandatory means the app can’t be removed from Favorites or unsubscribed.
    • Auto means the app is automatically favorited or subscribed, and can be un-favorited or unsubscribed by the user.
  • Enter KEYWORDS:Featured to make the application show up in the Featured list.
  • You can separate multiple keywords with a space. KEYWORDS:Mandatory Featured.
  • See the StoreFront 3.7 Keywords documentation at Citrix Docs for more information.

Users will have a better experience with StoreFront if applications are published into folders. The folder name is specified in the Delivery page in the Category field. Note: Add shortcut to user’s desktop works in newer versions of Receiver assuming the app is marked as a Favorite.

Secure Browser

Citrix has a deployment guide for publishing a browser from XenApp. Here’s an overview of the configuration:

  • Install Chrome on an RDSH VDA.
  • In Studio, publish IE and/or Chrome in Kiosk Mode to anonymous users.
    • Create a different published app for each website.
  • In StoreFront, create a Store for Unauthenticated Users.
  • In StoreFront, enable Receiver for HTML5.
  • In StoreFront, enable web links so you can link to the published browser from a different website.

When a user launches the published browser, the HTML5 client opens the published app in a local browser tab. The published browser runs in kiosk mode so that the published browser’s user interface is hidden. It looks like the website is running on the local browser but actually it’s running from a published browser.

App-V

App-V GPO ADMX templates

The latest GPO ADMX templates for App-V can be downloaded from Microsoft Desktop Optimization Pack Group Policy Administrative Templates.

App-V and Logon Times

Links:

App-V Dual Admin

In Dual Admin mode, you configure Citrix Studio to connect to App-V Management Server(s) and Publishing Server(s).

See Citrix Blog Post Load Balancing Microsoft App-V Servers with a Citrix Virtual Apps deployment for supported App-V server load balancing configurations.

  • Connecting to Management Servers using a load balancing VIP is not supported.
    • Use DNS Round Robin instead. Or use Citrix PowerShell to specify multiple Management Servers.
  • You can connect to Publishing Servers load balanced through a VIP, but Studio will show an error. Just ignore it.

App-V Single Admin

Citrix Virtual Apps and Desktops (CVAD) and XenApp 7.8 no longer requires App-V management infrastructure and can instead pull the App-V packages directly from an SMB share as detailed at App Packages at Citrix Docs.

The computer accounts for Delivery Controllers and VDAs must have read access to the share. An easy method is to add Domain Computers. See CTX221296 Citrix App-V Integration Minimum Permission Requirements.

In CVAD 2311 or newer, in Web Studio, go to App Packages to add App-V packages. See Publish packaged applications on single-session or shared desktop VDAs at Citrix Docs.

In older Citrix Studio, go to Configuration > Hosting, right-click App-V Publishing, click Add Packages, and browse to the .appv file.

Citrix Virtual Apps and Desktops (CVAD) and XenApp 7.11 adds an Isolation Groups tab.

Once App-V packages are added to Citrix Studio, you can publish an app, and select App-V from the drop-down.

The App-V apps show up as AppLibrary App-V and support the same options as other published applications.

Make sure the App-V Components are installed on your VDA. It’s not checked by default in 7.12 and newer.

On your VDA Windows 10/2016 or newer, in PowerShell, run Enable-Appv. For older OS, install the App-V client.

There appears to be some limitations to the package share method as detailed by Joe Robinson at Citrix Discussions:

Joe Robinson provided a script to force the App-V client to sync before launching the user’s App-V application.

If you run Citrix Workspace app inside a VDA machine and attempt to launch an App-V published app, it will launch from a different VDA session instead of the VDA session you’re already connected to.

Launch App Inside App-V Bubble

From Citrix Blog Post Process Launching in an App-V V5 Virtual Environment:

  • On any executable, add the /appvve:<PackageID>_<VersionID> of the package in which one would like the executable to run
  • If the App-V process is already running then use the /appvpid:<ProcessId> to inject into a running App-V virtual environment
  • If you want something more permanent, you can set the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual\<YourApplicationName> with a default REG_SZ key that has the executable name in it.

Also see Microsoft Knowledgebase article How to launch processes inside the App-V 5.0 virtualized environment.

AppDisks

See https://www.carlstalhood.com/appdisks/

Change Published Desktop Icon

Citrix Blog Post Changing Delivery Group Icons Revisited (XD7) has instructions on how to use PowerShell to import a Base-64 icon and then link it to the published desktop.

StoreFront overrides custom desktop icons. Run the following PowerShell commands to restore custom desktop icons: (h/t CTP Sam Jacobs)

& 'C:\Program Files\Citrix\Receiver StoreFront\Scripts\ImportModules.ps1'

$store = Get-STFStoreService /Citrix/Store
Set-STFStoreService -StoreService $store -SubstituteDesktopImage $false -Confirm:$false

Other Published App Tips

CTX209199 Published 64 bit Aps Can’t Be Started With %ProgramFiles% in Command Line If It’s Not the first Application to Start: You can try the following methods to address this issue:

  1. Use the absolute path to publish the application.
    2. Use %ProgramW6432% for 64-bit applications instead of %ProgramFiles%.

Google Chrome

Links detailing installation, configuration, roaming profiles, and publishing.

CTX132057 Google Chrome Becomes Unresponsive when Started as Published Application: add the parameters --allow-no-sandbox-job --disable-gpu in the published app command line. According to Dennis Span, this is no longer needed in Chrome 58 and newer.

CTX205876 Non-published Google Chrome browser on XenApp server, called and launched from any published app, is seen in black/grey screen: The command line parameter has to be added to registry shell open command for the Chrome browser:

  1. In Regedit, navigate to HKEY_CLASSES_ROOT\http\shell\open\command
  2. Edit the Default value as follows:
    "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --allow-no-sandbox-job --disable-gpu -- "%1"

Disable Application and Hide It

  1. In Studio, you can disable a published application by right-clicking it, and clicking Disable.
  2. In older versions of XenApp/XenDesktop, when you disable the application, it leaves the application visible but it is grayed out thus preventing users from launching it. In 7.8, the disabled app is automatically hidden (no longer shown in the apps list).
  3. If desired, you can hide or unhide the disabled application icon by running a PowerShell command: 
    asnp citrix.*
Set-BrokerApplication MyApp -Visible $false

  4. When you re-enable the application, Visibility is automatically set back to true.

Browser Content Redirection

Browser Content Redirection prevents the rendering of whitelisted webpages on the VDA side, and instead renders them on the client side. Only the browser viewport is redirected. The intent of this feature is to redirect HTML5 Video (e.g .youtube).

Browser Content Redirection requirements:

  • Citrix Virtual Apps and Desktops (CVAD) or XenApp/XenDesktop 7.16 and newer
  • Receiver 4.10 or newer
  • Chrome support is available in Citrix Virtual Apps and Desktops (CVAD) 1808 and newer
    • In the VDA, install the Chrome Browser Extension named Browser Content Redirection Extension. You can use Google Chrome Group Policy templates to force installation of the extension. See Browser content redirection Chrome extension at Citrix Docs.
    • You do not need any client software other than Workspace app 1809 or newer. The client-side rendering engine is included in Workspace app 1809 and newer.
      • HDX Browser Content Redirection feature will not work with Citrix Workspace app for Windows 1912 LTSR due to removal of the embedded browser from LTSR versions. But it does work in Workspace app 2006.
  • Internet Explorer 11– IE 11 on both the VDA, and on the client.
    • On the VDA, Enhanced Protected Mode must be disabled under Internet Explorer: Internet Options > Advanced
    • On the VDA, an IE 11 Browser Helper Object (BHO) named Citrix HDXJsInjector facilitates the redirection.
    • In Internet Explorer > Tools > Internet Options > Advanced > Browsing, ensure that Enable third-party browser extensions is checked. Source = Content Browser Redirection at Citrix Discussions.
  • Internet access from Client – By default, the client (Receiver) tries to fetch the redirected content. If client is not able to fetch, then the content falls back to server rendering.
  • When redirection is working, the client machine has a HdxBrowser.exe process.

    • See Kasper Johansen Citrix Xenapp And Desktop 7.16 Browser Content Redirection for some videos of this feature.
    • Kasper and Rasmus detail client-side registry keys to enable HdxBrowser.exe to use client-side GPU. These keys/values might already be configured in Receiver 4.11 and newer.
      • HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_GPU_RENDERING
        • HdxBrowser.exe (DWORD) = 1
      • HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION
        • HDXBrowser.exe (DWORD) = 11000 (Decimal)
      • HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_GPU_RENDERING
        • HdxBrowser.exe (DWORD) = 1
      • HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION
        • HDXBrowser.exe (DWORD) = 11000 (Decimal)
    • Rasmus Raun-Nielsen at Browser Content Redirection?! at LinkedIn has some CPU analysis, including client-side GPU.

Browser Content Redirection is configured using Citrix Policies, in the User half, under the Multimedia category.

Browser Content Redirection is enabled by default, but only for the specified whitelist URLs (ACL Configuration). Note that wildcards can be used in the path, but not in the DNS name. To configure Microsoft Teams and GoToMeeting, see CTX238236 Browser Content Redirection: whitelisting websites.

Citrix Virtual Apps and Desktops (CVAD)  and XenDesktop 7.18 and newer have a setting named Browser Content Redirection Authentication Sites. Add URLs that are redirected from the main ACL URL. To configure Microsoft Teams and GoToMeeting, see CTX238236 Browser Content Redirection: whitelisting websites. Also see See CTX230052 How to Troubleshoot Browser Content Redirection.

Citrix Virtual Apps and Desktops (CVAD) and XenDesktop 7.17 and newer have a Blacklist setting. Any address added here will not be redirected to the client. You typically configure this setting to override the ACL setting (e.g. ACL setting has a generic URL, but the Blacklist has a more specific URL)

7.18 adds a Browser Content Redirection Authentication Sites setting. Configure a list of URLs that sites redirected via Browser Content Redirection can use to authenticate a user. E.g. iDP URLs.

Registry keys for Browser Content Redirection are detailed at Browser content redirection policy settings at Citrix Docs.

Bidirectional Content Redirection

You can redirect URLs from client to a published browser, or from VDA to the client. See Bidirectional content redirection policy settings at Citrix Docs for requirements and limitations.

  1. Make sure Local App Access is not enabled on the VDAs.
  2. Make sure a browser is published. Chrome and Edge require Workspace app 2106 and newer connecting to VDA 2106 and newer.
  3. Edit a GPO that applies to VDA users.
  4. Go to User Config | Policies | Citrix Policies and edit a Citrix Policy.
  5. Find the setting Allow Bidirectional Content Redirection and enable it (Allowed).

  6. In CVAD 2311 and newer, use the setting Bidirectional content redirection configuration to insert a JSON string containing the list of URLs to redirect from client or VDA. The older setting for Allowed URLs has been deprecated. See Bidirectional content redirection at Citrix Docs.


  7. Prior to CVAD 2311, also configure the Allowed URLs policy settings (VDA to client, or client to VDA) to indicate which URLs should be redirected in either direction.

    • VDA 2206 adds support for wildcards in the Allowed URLs to be redirected to Client policy setting, but not from Client to VDA.
    • VDA 2206 adds support for custom protocols other than HTTP and HTTPS in the Allowed URLs to be redirected to Client policy setting. These custom protocols don’t work from Edge/Chrome.
    • More details at Citrix Docs.
  8. In CVAD 2311 and newer, it is no longer necessary to configure Bidirectional Content Redirection on the client side. For older CVAD:
    1. Copy the receiver.admx file from Receiver 4.7 or newer to PolicyDefinitions (SYSVOL or C:\Windows\PolicyDefinitions).
    2. Edit a GPO that applies to client devices (endpoints).
    3. Go to User Configuration | Policies | Administrative Templates | Citrix Workspace | User experience.
    4. Double-click the setting Bidirectional Content Redirection.
    5. Enable the setting.
    6. In the Published Application field, enter the name of the Internet Explorer published application.
    7. In the Allowed URLs fields, configure the URLs you want to redirect in either direction.
  9. On the VDA, run one or more the following commands to register the browser add-on. Chrome and Edge require Workspace app 2106 and newer connecting to VDA 2106 and newer. 
    "C:\Program Files (x86)\Citrix\System32\VDARedirector.exe" /regIE
"C:\Program Files (x86)\Citrix\System32\VDARedirector.exe" /regChrome
"C:\Program Files (x86)\Citrix\System32\VDARedirector.exe" /regEdge
"C:\Program Files (x86)\Citrix\System32\VDARedirector.exe" /regall

  10. CTX232277 Unable to Logoff When Bidirectional Content Redirection is Configured says that the following registry value should be configured on the VDA. If you already have LogoffCheckSysModules, then add the below processes names to the existing value.
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
      • LogoffCheckSysModules (REG_SZ) = wfcrun32.exe,Concentr.exe,SelfServicePlugin.exe,redirector.exe
  11. In Workspace app 2106 and newer connecting to VDA 2106 and newer, do the following to enable redirection for Chrome and/or Edge: 
    "%ProgramFiles(x86)%\Citrix\ICA Client\redirector.exe" /regChrome /verbose

  12. Chrome might display an Error indicating New extension added.

  13. For Internet Explorer, do the following: 
    "C:\Program Files (x86)\Citrix\ICA Client\redirector.exe" /regIE

  14. When you run Internet Explorer on the VDA or client device, you’ll be prompted to enable the add-on. You can configure a GPO to enable this add-on automatically. Redirection won’t work unless the add-on is enabled.

Host to client Redirection

This feature causes Citrix VDA to redirect http links in applications to the client machine, so they are opened using the client’s browser. The feature is disabled by default.

James Rankin at Using host-to-client redirection in Citrix XenApp explains the feature in detail, including:

  • Limitations of the feature
  • Registry values to control the URL Schemes that can be redirect to the client
  • Group Policy and XML file to handle the File Type Associations in Windows 2012 and newer

Local App Access

Some applications are not suitable for centralization and instead should run on endpoint devices. These applications include: phone software, applications needing peripherals, etc. Citrix Local App Access lets you access these endpoint-installed applications from inside a published desktop. This is sometimes called Reverse Seamless.

Local App Access has three modes of functionality:

  • User-managed local applications. Any shortcuts in the endpoint’s local Start Menu and local Desktop are made available from inside the published desktop.
  • Administrator-managed local applications. Use Studio to publish a local application, which is created as a shortcut inside the published desktop. When the shortcut is launched, it is actually running from the endpoint device (reverse seamless) instead of the centralized desktop. If you enable administrator-managed local applications then user-managed local applications are disabled.
  • URL Redirection. Administrators define some URLs that should be opened in a local endpoint browser instead of a VDA browser, and then display the local browser inside the published desktop (reverse seamless).

Local App Access requires Platinum Licensing.

Do the following to configure Local App Access:

  1. In a Citrix Policy that applies to the VDAs, enable the Allow local app access policy setting. It’s in the Computer Half.
  2. The URL redirection black list setting lets you define a list of URLs that should be opened on the endpoint’s browser instead of the VDA browser. Alternatively, you can instead configure Bidirectional Content Redirection.
  3. On the Endpoints, install Receiver using the ALLOW_CLIENTHOSTEDAPPSURL=1 switch. Feel to add /includeSSON too. Run the installer from an elevated (Administrator) command prompt. This switch automatically enables both Local App Access and URL Redirection. Note: the URL Redirection code does not install on VDAs so URL Redirection might not work if your endpoint has VDA software for Remote PC.
  4. After installation of Receiver, launch Internet Explorer. You should see a prompt to enable the Citrix URL-Redirection Helper add-on.
  5. You can also go to Tools > Manage Add-ons to verify the Browser Helper Object.
  6. By default, Local App Access redirects the endpoint’s Start Menu and Desktop. You can control which folders are redirected by editing the endpoint’s registry at HKCU\Software\Citrix\ICA Client\CHS. You might have to create the CHS key. Create the Multi-String Values named ProgramsFolders and DesktopFolders, and point them to folders containing shortcuts that you want to make available from inside the published desktop.

  7. When you connect to a published desktop, by default, there will be a Local Programs folder in the Start Menu containing shortcuts to programs on the endpoint’s Start Menu. These are user-managed shortcuts. Note: Windows 8 and newer only supports one level of Start Menu folders. This means that all local shortcuts are placed into the single Local Programs folder without any subfolders.
  8. On the VDA Desktop there will be a Local Desktop folder containing shortcuts from the endpoint’s desktop. These are user-managed shortcuts.
  9. Note: the following doesn’t seem to work in LTSR 7.15. The VDA seems to overwrite these registry values.
    1. The Local Desktop and Local Programs folders on the VDA can be renamed by editing the VDA’s registry at HKCU\Software\Citrix\Local Access Apps. You might have to create the Local App Access registry key. Create String values ProgramsCHSFolderName and DesktopCHSFolderName as detailed at Citrix Docs.

  10. To enable administrator-managed local applications, login to a machine that has Citrix Studio installed, and edit the registry. Go to HKLM\Software\Wow6432Node\Citrix\DesktopStudio, and create the DWORD value named ClientHostedAppsEnabled, and set it to 1.
  11. When you open Studio, and right-click the Applications node, there is a new entry Add Local App Access Application.

    1. In the Getting Started with Local Access Applications page, click Next.
    2. In the Groups page, select the Delivery Group or Application Group whose published desktop will receive the shortcut, and click Next.
    3. In the Location page, enter the path to the executable. This is the path on the endpoint. Also enter a Working Directory. You can get this information from the properties of the shortcut on the endpoint device. Click Next.
    4. In the Identification page, enter a name for the shortcut, and click Next.
    5. In the Delivery page, these options work as expected. Click Next.
    6. In the Summary page, click Finish.
    7. If you open the Properties of the Local App, there’s a Limit Visibility page.
  12. When you login to the desktop, you’ll see the administrator-managed local application. If any administrator-managed Client Hosted Applications are delivered to the user, then the default Local Programs and Local Desktop folders no longer appear.
  13. To enable URL Redirection, login to the VDA, and run "C:\Program Files (x86)\Citrix\System32\VDARedirector.exe" /regall. This registers the browser helpers.

  14. In Internet Explorer, if you go to Tools > Manage Add-ons, you’ll see the Citrix VDA-URL-Redirection Helper add-on.
  15. From inside the published desktop, if you go to a website on the blacklist, the VDA browser will close and a local browser will open in Reverse Seamless mode. If you then go to a website that is not on the blacklist, the local browser will close and the VDA browser will open again.

Citrix TV – Local App Access in XenDesktop 7

Anonymous Apps

Citrix Virtual Apps and Desktops (CVAD) and XenApp 7.6 and newer supports publishing apps to anonymous users. Edit the Delivery Group, and on the Users page, check the box next to Give access to unauthenticated (anonymous) users.

Anonymous Users are managed differently than regular Domain Users. See VDA Anon instructions for adding anon accounts, configuring session timeouts, and configuring local group policy.

Anonymous published apps should show up for all authenticated users. However, you can also create a StoreFront store that does not require any authentication.

Export/Import Published Applications

If your destination CVAD farm is version 2212 or newer with Web Studio, then you can use Citrix’s Automated Configuration Tool to export and import the configuration. See Citrix Docs PoC Guide: Automated Configuration Tool – On-Premises to On-Premises Migration

Links:

Related Topics

267 thoughts on “Published Applications”

  1. hi Carl,
    In my XenDesktop 7.5 enviroment when i’m trying to restrict users for published desktop with “Set-BrokerEntitlementPolicyrule” poweshell command, it’s not happening?
    Set-BrokerEntitlementPolicyRule – Name “My Delivery Group_1” -AddIncludedUsers “MyDomain\User” -IncludedUserFilterEnabled $true

    Reply

  2. hey carl , i tried to publish a URL with the commands in the mentioned Publish Application section and it worked, BUT when i try to publish UNC path it is getting published but after launching it blank tab get opened . I have checked all the permissions on the folder .

    Reply

    1. I haven’t been able to get a UNC path to work. But others seems to have success. Maybe depends on the browser and security settings.

      Reply

  3. Thank you Carl,

    As always, this is a very well organized and highly informative article. I foind the information very useful when analyzing hosted application compatibility with Citrix VDA and remote desktop services.

    Keep uo the good work!

    Reply

  4. is there a way to hide a app from showing at favorites yet its subscribed?
    Note: i just need 1 single app yet published to be hidden not the entire favorites/app tab.

    reason is due to outlook unable to open .msg files hence i have to publish two outlook. 1 for launching outlook and the other for .msg files.

    Reply

    1. addon… am using 7.11

      Also, if there is a way to open outlook and open save .msg files without the need to add /f let me know too. thank you v much

      Reply

  5. Hi Carl,
    My IT guys have installed only XenDesktop 7.9 which they said is a combination of XenApp and XenDesktop server. Do i need to install XenApp 7.9 separately for citrix studio to serve applications my end point devices?

    Apparanly, I am able to access virtual desktops from my citrix WebStore interface but cannot start any app as i said earlier.
    Thanks,
    Sriram

    Reply

    1. It is two names for one product. Only one install.

      You’re using App-V? Can you publish a non-App-V app?

      Reply

  6. Carl,

    Like many others, I really appreciate your site.

    I have an issue with published content on 7.11. When trying to launch them from the desktop client, I get an error that the application can’t be launched. However, they work fine from the web client. I have tried both websites and files. Any thoughts?

    Thanks,

    Dave

    Reply

  7. Is there any way to hide the LocalApps desktop and start menu folders entirely? I want the user ONLY to see my published local app, not any of the other apps available on their PC….

    I have everything working, except still get the bloody folder on the desktop.

    Reply

    1. If you publish a local app from Studio, the automatic local apps should be ignored. Are you saying that’s not the case?

      Reply

  8. hi Carl,

    Currently experiencing app-v launch issues when using Mandatory profiles in non-persistent RDS workers. I have created some app-v packages and published them but they won’t launch (just give error starting application), I see the cache has the package on the XenApp server and in %localappdata% i can find the app-v app and the icons appear on the desktop for the applications. Do you have any experience or any articles on using app-v packages with XenApp when using Mandatory profiles?

    When not using mandatory profiles and using roaming profiles the app-v packages will launch fine.

    Thanks,
    Steve

    Reply

  11. Hi Carl,

    first of all, i’d like to thank you for your great work here and at the ctx forum.
    Helped me a lot in the last years.

    Now to my Problem:

    We have got a little Problem with starting a second Published app quickly after the first one.
    When a user launches the first Citrix Application, it fails to quickly launch a second one if its on the same Server / Deployment Group. The User receives the Message “The App cannot be started. Please contact your helpdesk”.
    When he waits round about 30 seconds after the first start, the second start has no problem and the program comes up. (You have to wait again if you want to start a third Program).

    The User are already working over a published Desktop.

    We got 2 Messages in the Event Viewer of the Storefront:

    Warning:
    … The Citrix XML-Service gives back der Error: ‘no-available-workstation’ back ..

    Error:
    … there is no availabe Ressource for the User ‘Domain\User’ found. This Massage was given by the Citrix XML-Service.

    Any Solutions here? Timeouts or Something?

    Thanks and greetings,
    Olaf

    Reply

    2. Hello Carl.. we are facing exactly the same issue as mentioned by Olaf. The same 2 errors in SF. VDA versions on Workers / DC are v7.15 . I have also made changes recommended by Citrix about Bypass duration to 1 minute and with other connectionattempts and connectiontimeouts with enable socket pooling. Not sure where the issue seems to be ?
      Please help.

      Reply

  12. Hi Carl

    Great documentation..!!!

    I am unable to edit Delivery group properties though I am added as delivery group admin. Please can you suggest any possibilities?

    Reply

      1. We have created a role with Delivery group Admin access specifically. But unable to modify DG properties being in that role. Full admin has all rights to administer the console.

        Reply

        1. You use the built-in role? Or did you create a role? If you created a role, what permissions did you assign?

          When you added the administrator, what scope did you use? Is the Delivery Group in the scope?

          It’s working for me with the built-in DG Admin role.

          Reply

  13. Hello Carl
    You can make “local app access” with integrated file type association?
    In my environment XenApp 7.6, Excel is not installed, Excel and need to be moved from my endpoint was the virtual XenApp session.
    But I have not found a way that when run an Excel file .xls or .xslx in the virtual session is automatically opened with Excel integrated as “local app access”

    Reply

      1. The file is in my documents VDA OS Server.
        Excel is displayed as an icon published on the desktop VDA OS Server
        But when I go to run the file .xslx appears:
        How do you want to open this type of file? and not load with published Excel “local App Access”

        Reply

  15. Very insightful,
    If you have XA farms, 6.5 and 7.6 can you hide visibility to apps from one farm (6.5) for some users using the same URL with combined STAs?

    Our options are place icons from the farms in different folders or provide separate URLs.

    Reply

    1. Are you asking if you can only show icons from an entire farm if the icon is in a specific group? In that case, there’s StoreFront User Mapping (StoreFront 3.5 > Store > Manage Delivery Controllers, on bottom is User Mapping.

      Reply

  16. Hi Carl, I’m trying to setup a Citrix Studio install to run as a published app from a non-delivery controller server. I’m running into an issue where it asks for the delivery controller address every time. Do you know if there is a config file I can add an entry to or a reg key I can set to have the MMC snap-in pick up the delivery controller fqdn? Thanks in advance!

    Reply

  17. I’ve recently setup a new XenDesktop 7.8 Environment testing with our 2008 R2 image
    We are not using storefront but using Juniper client to talk directly to the DDC’s.
    When testing out published applications they are launching correctly, however when you launch a subsequent application all published apps disconnect (and I see the session go disconnected in studio) and then when then the new app launches and the previously opened apps also pop up on screen.

    Obviously I don’t think this is expected behavior but not sure if anyone else has seen something like that or is it most likely the juniper. Don’t want to waste time setting up storefront if its something else.

    Reply

  18. Hi Carl,

    do you know if it’s possible to publish an application on a network share like this:
    PATH: \\share\folder\appl.exe
    DIR: \\share\folder\

    Thanks

    Reply

    1. I think there have been issues in some versions of XenApp. The easiest way is to create a .cmd file that launches the program using the start command and then publish the .cmd file.

      Reply

  19. Hi Carl I have XenApp7.7 Platinum. Cant seems to be able to set up the local App redirection. I can see the local App in controller and I set up the Citrix policy applied to my desktop delivery group and on local PC I installed receiver with the =1. When I login to desktop I cant see me local shortcuts. Did I miss anything?

    Reply

    1. You can only do one or the other. If you publish Local Apps, then automatic visibility of local apps won’t work. You have to stop publishing local apps to cause the local apps to automatically display.

      Reply

      1. I want to set only two local applications that’s why I need to publish them. But when I do it doesn’t work ;o( I had set this up on demo while ago was fine there but I might missed something this time.

        Reply

      2. Hi Carl I had to set up only one application hence the Local app publishing in studio. I opened case with Citrix now as I just wonder if having two controllers or changing the gateway slightly might have disable this function. I had set this up just now on different domain with one controller and default gateway setting and all working fine there.

        Reply

        1. I found why this doesn’t work for my client. On demo I disabled Desktop Viewer Tool bar in my config file on SF and my Local App redirection stop working. Seems that the black menu need to be set to true for it to work..

          Reply

          1. That’s the default so I don’t think I mentioned that. Maybe I should?

            The docs also say full screen is required but it seems to work in a window too.

  20. Hi Carl,
    thanks for the great information.
    One question:
    To get back custom desktop icons, we need to run the command

    Disable-DSStoreSubstituteDesktopImage -SiteId 1 -VirtualPath /Citrix/Store

    Is there also an “enable…” command to switch this back to the default settings?

    Thanks for your help,
    best regards,
    Stefan

    Reply

    1. Did you try it? I see Enable-DSStoreSubstituteDesktopImage as an available cmdlet.

      You can run Get-Command *DSStoreSubstituteDesktopImage* to see the available commands.

      Reply

  21. Carl that fixed it, I forgot I had the ICA only box checked. Along with that: I assume that because I need 2 delivery groups to pull this off, I will also need a set of servers in each delivery group, one group for inside access and one for gateway access, because I can’t publish apps by servers like xenapp 6.5? Thanks for your help, I will look for you at Synergy.

    Reply

  22. Carl thanks for answering my question on April 1 about limiting access to a published app from Netscaler gateway. My issue now is, when I check the box for Connections through Netscaler Gateway, the icon does not show at all, and when I check the box for All connections not through Netscaler Gateway, the icon shows when logged into the gateway, and a login without the gateway. There is also a Storefront button on the left that I left at default, does this need to coincide with the check boxes, and point to the Storefront server connected to the gateway? Thanks.

    Reply

  23. Carl, What is the option add shortcut to user desktop inside of the delivery group option for? From everything I read and done, we had to use the PutShortcutsOnDesktop = true. ? Will this check do this as well for only certain apps? like the web interface days?

    Reply

  24. Hi Carl,
    I have a problem in my Storefront 3.x xenapp 7.6 (and 6.5) shared environment.
    I am trying to disable session sharing with no luck. I need the user(s) to be able to launch the same app (receiver 4.4) and connect to different sessions. Is this possible?

    Reply

      1. When I try to run the set-broker command on storefront, the command is not found. Using get-command after importing Citrix modules does not show the command either. Am I missing something?

        Reply

        1. You should be running that on your Delivery Controller or any machine with Studio installed.

          Reply

          1. I was running on SF 3.01 with studio installed. I tried on DC same issue.
            Both Get-BrokerAppEntitlementPolicyRule and Set-BrokerAppEntitlementPolicyRule not recognized

            Here’s output from powershell.
            PS C:\> cd “C:\Program Files\Citrix\Receiver StoreFront\Scripts”
            PS C:\Program Files\Citrix\Receiver StoreFront\Scripts> .\ImportModules.ps1
            Adding snapins
            Importing modules > all modules loaded
            PS C:\Program Files\Citrix\Receiver StoreFront\Scripts> Set-BrokerAppEntitlementPolicyRule Rel15 -SessionReconnection SameEndpointOnly
            Set-BrokerAppEntitlementPolicyRule : The term ‘Set-BrokerAppEntitlementPolicyRule’ is not recognized as the name of a
            cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify
            that the path is correct and try again.
            At line:1 char:1
            + Set-BrokerAppEntitlementPolicyRule Rel15 -SessionReconnection SameEndpointO …
            + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
            + CategoryInfo : ObjectNotFound: (Set-BrokerAppEntitlementPolicyRule:String) [], CommandNotFoundException
            + FullyQualifiedErrorId : CommandNotFoundException

          2. Those cmdlets come from Studio, not StoreFront. Run Asnp Citrix.* And then you’ll see them.

  25. Hi Carl, why the delivery option is not available for APP-V applications in XA 7.8 but for locally installed apps?

    Reply

  26. Carl, in Xenapp 6.5 AppCenter you can control access to an application from Access Gateway, by checking the box, Allow connections made through Access Gateway Advanced Edition, and by a similar box called Allow all other connections. We use this to control access to applications from the outside. I don’t see a way to do that with Xenapp 7, did I overlook it? Thanks.

    Reply

    1. Yes, but only at the Delivery Group level. Edit the Delivery Group and there’s an Access Control page.

      Reply

  27. Hi Carl

    I have a strange one
    XenDesktop/XenApp 7.7
    Single Delivery Group containing a Single 2008 R2 Server with VDA 7.7.
    PVS 7.7 streamed Image (this issue is replicated with multiple identical servers in the DG also)
    User A Assigned to DG
    User A Assigned to 2 individual applications

    I have two applications assigned to the delivery group. I can only launch one of them at a time. Weirdly, if i Launch App A, i get my application, i then launch App B, and nothing happens. Client doesn’t see the second application launch in the receiver connection centre, however the Broker (via powershell and the GUI) will see both Apps as active. If I launch App B first, i cant launch App A.

    Director will see two applications launched under the 1 server, however if you select the session list that contains both apps, you will only see one actually running. Eventually App 2 will die off

    No errors on the Broker, Client, Server – everything clean.

    This works perfectly fine in XA 6.5, just when i move to 7.7, it breaks and i am a little lost

    This also seems to work perfectly fine on a delivery group in 7.7 that has non streamed Servers in the mix. I can launch as many apps as i like and everything will work as expected.

    Are there any gotchas around the VDA Installation and PVS that i might be missing?

    Thanks

    J

    Reply

    1. Do the two apps normally run side-by-side?

      Same problem on VDA 7.8? That VDA has bug fixes. Otherwise you might have to call Support.

      Reply

      1. Hey Carl,

        Thanks for taking the time to reply

        I just cracked it – turns out there appears to be issues if you add the app via studio manually and your app runs from say “C:\Program Files\LocationA”, Studio Auto changes this to variable based…%ProgramFiles%\LocationA.

        In my case
        App 1 = “C:\Program Files\LocationA”
        App 2 = “C:\Program Files\LocationB”

        Studio Changes this to %ProgramFiles%\LocationA or B respectively and my apps wouldn’t run side by side. Change it back to the physical path and delete the variable, and things start working perfectly 🙂

        I changed both the App path, and the working directory so not 100% sure which value sorted it

        James

        Reply

  28. Hi,
    In Xenapp 7.6 How do you publish individual server as publish desktop for the NOC team to verify / test the individual server are working correctly.

    Thanks,

    Javed

    Reply

    1. It’s not possible. I would have to be in it’s own Delivery Group. You could remove the machine from the prod delivery group and add it to a different delivery group.

      Reply

  29. Hi Carl
    I want to know if it is possible after logging off from citrix receiver the webpage (whether after time out or or a manyual logoff) if the apps can stay open. right now when a user logs off, all the apps close? thanks

    Reply

    1. In StoreFront, adjust the Workspace Control settings. The process varies depending on the version of StoreFront.

      Reply

  30. I have installed XA 7.6 and trying to configure the APP-V with it. My App-V server is working fine and I was able to deliver applications using the App-V Client.
    The issue which I am facing is how can I get the Citrix Studio to recognize the applications coming from App-V.

    I have added the App-V server on the studio and even installed the VDA Agent on one of the server which has application delivered by app-v. Could you please let me know how I need to configure it?

    Reply

  31. Hi Carl,

    I have a question about Applications in XA7.7….
    In 6.x, Apps were enumerated via XML brokers…etc. How is this done in 7.7?

    Do you know of any in-depth doc that discusses how Applications are delivered to users in XA 7.7?
    (I don’t mean how to setup the delivery group…etc to deliver/publish an App. I am looking for the backend logical flow and components that do what XML brokers used to do in 6.x).

    Thanks
    HK

    Reply

    1. In 7.x, the Controllers are the XML Brokers.

      VDAs register with Controllers to inform them that the VDA is available for connections.

      StoreFront authenticates the user and retrieves the users group. StoreFront sends this info to Controller and Controller sends back a list of icons. StoreFront creates a web page from the icons.

      When user launches app, StoreFront sends XML query to Controller to ask for an available VDA. Controller sends back the IP address of the VDA.

      Reply

  32. Is it possible to enable session sharing in XD between published app (using app-v) and desktop mode?

    Requirements:
    1. To integrate app-v on XD so all app runs as like a native app in full desktop mode.
    2. To publish all apps through SF.
    3. Enable smooth roaming experience. (To launch individual apps directly from SF and the same need to be reconnected within the XD desktop session as a local instance)

    When it comes to app-v and XD desktop integration below are the options i evaluated.

    1. Enable app-v client to sync at every logon (few sec delay in enumerating start menu but good that we have options to enable progress bar for sync)

    2. Publish all globally and limit the icon visibility using ABE shares. (No wait time but end users can still launch the app if they know the actual path)

    3. Publish through Receiver so it can auto reconnect and bring all apps within desktop or to use Keywords to prefer local instance. But this will not enable session sharing instead will result in duplicate sessions for above scenario.

    Any other thoughts?

    Thanks,
    Manikandan

    Reply

    1. Keywords:prefer should launch in the same desktop session. If launching in a new session then your keywords:prefer is not working.

      7.8 is supposed to have some App-V enhancements. Not sure if published app-v apps are displayed inside a published desktop and launched in the desktop session.

      Most reliable option is to publish App-V globally and hide icons users shouldn’t see (e.g. NTFS permissions). However, now you have to maintain both published apps and an icon hiding method (e.g. Group Policy Preferences).

      Reply

  33. Hi,

    Is it possible to let some specified users forced login on one citrix server, so i can do testing for applications only on that server ?

    thanks
    rolf

    Reply

    1. Only if it’s in its own Delivery Group.

      This is a frequent request. Please call Citrix Support and ask them to bring back this feature.

      Reply

  34. I have eleven XenApp 7.6 servers, all in the same delivery group, all running the same PVS image. There is one application published on all these servers – One icon that opens on any of the eleven servers. I would like to also publish this application individually on each server. So, there would be eleven icons, each corresponding to one specific server. Is this possible, since I only have all the servers in one delivery group?

    Reply

    1. That’s not possible in a single Delivery Group today. I suggest calling Citrix Support and tell them to bring back this feature (enhancement request).

      Reply

  35. Had a question regarding assigning users a specific published application in XenApp 6.5. I’m much more familiar with XD so just wondering how XA works in comparison. I know in XD when you assign a user explicit rights to a desktop, it takes precedence over them being assigned a different desktop via AD security groups they are a member of.

    How does XenApp handle a similar situation, where a user is granted access to a specific published application (server desktop), and they are also in a security group thats got access to a different published application (server desktop)??

    Reply

    1. In either case, the user sees all icons the user is granted access to. I’m not sure what you mean by “precedence”.

      XenDesktop has two levels of authorization: first at the Delivery Group and again in the published app’s Limit Visibility page.

      XenApp 6.5 only has a single level of authorization; simply grant the user access to the published app/desktop and the user can see it.

      Reply

  36. Hello Carl

    We are seeing a behavior in our Xendesktop 7.6 where our support applications (multiple application per tuser) get pinned on one box. This result on the box getting oversubscribe for resource.

    We are looking for a way we can force to load these multiple support apps for a single user; to run on multiple servers on a LBG or a workaround that will give us similar behavior.

    Thanks
    Edgar

    Reply

      1. Disable session sharing is not a supported feature in XD76; we opened a call with Citrix and after waiting for 3 mos got an answer.

        XD76 by default will load balance users (due to session sharing) not apps among servers in a MC; the only way we can ensure that a user that launches same apps have these apps on different servers; is to create 2 DG against a MC and spread servers on this DG’s.
        Then assign same users and app on these DG’s when a user launches APPa on DG1 and launches same app APPb from DG2.

        Applications will be then be spread out on separate servers.

        Reply

  37. Hi Carl,

    Is it possible to do anything with with Published Desktop icons like you can with apps, like moving them in to sub folders under the + icon?

    Reply

    1. There is a TreatAsApp KEYWORD you can add to the Delivery Group Description. Not sure if you can specify a category. If not in GUI then check PowerShell.

      The XenApp Tech Preview had some enhancements for published desktops. Not sure if this was one of them.

      Reply

  38. Good afternoon!

    Carl,

    Congratulations on the excellent blog, is a shaking in a database.

    I seek your aid when public Apps gives the following error message: Cannot start app “app name”. What are the possible reasons for this error?

    I’m waiting your reply.

    Thank you

    Reply

    1. The event viewer on the Controller usually tells you the reason. Not registered. Not enough machines. Published app file path not found. Licensing issues. Etc.

      Reply

  39. Carl, can you verify this is accurate: “If there are multiple Delivery Groups with identical priorities then connections will be load balanced across them.”

    This is not the behavior we are seeing, connections all go to the first delivery group and there is no apparent load balancing.

    Reply

      1. I know no one knows for sure, but has Citrix given any indication of the release time frame for 7.7 (i.e. 1Q 2016)? I know the TP has been out for a while. Thanks.

        Reply

  40. Does this work with Windows 8.1 and Server 2008 R2 or Windows 8.1 and Server 2012? I have it working with a client on Windows 7 and shared desktop on server 2008 R2. Only the local desktop folder works if i connect from a windows 8 laptop.

    Reply

    1. Local App Access? I just tried Windows 10 to Windows 10 and it seems to work. It creates the shortcuts on both Desktop and Start Menu.

      Reply

  41. Thank you for your blog. I’m a new Citrix admin and this has answered every question I’ve had without going through the process of pulling teeth from the Citrix support reps

    Reply

  42. When I made Local App Access available to users, when they logged in, the screen stayed “Black”. In order to let them access their desktops I had to revert and restart many times the computers…

    Is there something I could forget?

    Reply

  43. Thanks Carl. We recently upgraded from 5.0 to 7.6. We had several IE shortcuts that redirected to the users local desktop using the locally installed browser. The old “Content” type of deployment. Is there a new way to do this with only XenApp? We are not deploying XenDesktop VDA’s.

    Reply

  44. I have aquestion. Currently I have a XenApp 6.5 farm with some siloed servers which publish GIS apps. Users get a published desktop from the normal farm servers and from an icon on the desktop which runs a ICA file get there GIS apps from the siloed servers. This set up is required so that the resource hungery GIS apps do not affect the normal published desktops.
    As XenApp 7 dosn’t support ICA files how can you achive the same end result?

    Reply

  45. Hi Carl,

    As usual great information. One question:

    if limit the desktop icon is used to hide the icon , would appliance site still automatically launch the desktop without user intervention in IE kiosk mode even if applications are published to that same user but visible ?

    Thanks.

    Reply

    1. I suspect that if the desktop icon is not visible to the user then there’s nothing to auto-launch. Otherwise you’ll have to try it in a lab.

      Reply

      1. Hi Carl,
        Is there a way to prevent the icons published on xenapp 6 with “KEYWORDS: Auto” via storefront are hidden when disabled?
        If I disable application, this automatically hide from users and there is a problem.
        Thanks

        Reply

      2. Thank’s Carl.
        do you think there is an alternative way to see the icons on the desktop automatically to users with storefront and xenapp 6? (without “KEYWORDS:Auto”)

        Reply

  46. Hi Carl,

    Great article.

    I have a question regarding Delivery Groups relating to my new XA 7.6 deployment. I have 5x VDAs within a Delivery Group where 2x VDAs host the same ‘standard’ applications but also host specialised applications due to licensing constraints.

    When a user connects to a VDA hosting only ‘standard’ applications, then attempts to access a ‘specialised’ application hosted on other 2x VDAs, there is no activity and no connection is attempted. Is this by design as all VDAs should host the identical applications? therefore, I should remove the 2x VDAs hosting the specialised applications into a separate Delivery Group?

    Thanks in Advance.

    Reply

    1. In 7.x, it is assumed that all members of a Delivery Group are identical. If they are not identical then they should be in separate delivery groups.

      Reply

  47. Hi Carl,

    Excellent article, it has helped me tremendously! Much appreciated.

    I have 5 VDAs in a delivery group and 2 of the VDAs (in my case, server 1 and server 2) have a ‘specialised’ applications installed due to licensing constraints (i.e. MS Visio 2013). So not all of the 5 VDAs have identical applications installed.

    My issue is that when a user connects to a standard published application on server 3 then attempts to connect to the specialised application on server 1. The connection is unsuccessful. Is this by design ? If so, I’m assuming I need to remove the 2 VDAs from the existing delivery group and move them to a new delivery group? Can you please confirm ?

    Thanks in Advance.

    Reply

  48. Hi carl, I have setup an Lab environment with xenapp 7.6 with evaluation license. i can publish the app. but when user try to open the application from the app dashboard. i am getting constent Event viewer error : The Desktop Window Manager has exited with code (0xd00002fe) ID: 9009.

    App server dont have Remote Desktop License server.

    Its Server 2012 r2.

    I really need your help mate.

    Thanks
    James

    Reply

    1. When creating the Delivery Group, select the Desktop or Desktop and Applications type. If you’ve already created the Delivery Group then you can go to its properties and change it to one of the Desktop types.

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *