- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
App Vols v4.7
Hi there
I have a query when using "On demand" rather than "classic" when using app vols.
If i create a app vol using the "classic" method i would create a desktop icon (windows environment) for the application for all users to see ...this works great . However when using "on demand" , i would do the same with the icon , but with "on demand" it also creates the desktop icon in the user profile (as the active user will have permission to do this ) . As we then use folder replication for each user , the user profile then gets icons under their profile.... this causes orphan icons if that user then uses other horizon VMs if the application is not available with in the new chosen VM
Is there anyway this could be stopped (creating icons to the users profile) when using "on demand"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Could you please share the application on which you have done this experiment?
GURU
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Review this link:
https://communities.vmware.com/t5/App-Volumes/App-Volumes-2111-Apps-on-demand/td-p/2886368
You will need to remove all shortcuts from your AppVol package and create DEM shortcuts, by following this link below.
Note: I remove the shortcuts and place them in a folder (DEM Shortcuts) in the DEM_Config share, under ...\@WorkSpace\DEM_Shortcuts\. This way I can grab all the information I need to create the DEM Shortcuts.
@StevenFurtick
VMware Docs | VMware EUC BLOG | VMware EUC Community | VMware Support |
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Overlooking at the behavior that you describe, is expected. At logon of the user, the shortcuts are created by AppVolumes in the user profile. This would be replaced by the real shortcuts of the application, at the instance of the virtualization being complete, upon launch of the respective application.
GURU