- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
App Volumes On Demand not working
Hi,
Every time we create a package for use on On Demand, it ends up show as Delivery as Classic when completed. So, our test app is always mounted when we log on...
Has anyone been successful with this?
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, it sounds like you remove the application shortcuts from the package. Is this the case?
If so, you can't use on demand.
@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
no, we have not removed the shortcut from the desktop.
When we log on, the application is already in the control panel...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm pretty sure you will see the application in control panel, but is not installed on your HD.
Do you see the shortcut for your application? Open the properties of the shortcut, you should see a AppVol string in the target path.
You mentioned that if you look in AVM console the package is saying it is classic, not OnD.
Can you give some screenshots of the package details in AVM console, shortcut properties, and Add/Remove Programs?
@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
When we create a package on demand, the package changes to classic with this message:
Package 'AppPackage <#72 Chrome on Demand {38bb2691-629f-449a-a91b-ceaa2294aece}>' is not capable of on-demand, updated its delivery mode to 'Classic'
I will get you some screen shots, but the error above seems to be a telling one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The properties of the application on the desktop was as expected.
The application was already in the control panel.
The attachments show how we created the package to be on demand but it changed back to classic... and we saw the error in the error log - Package 'AppPackage <#72 Chrome on Demand {38bb2691-629f-449a-a91b-ceaa2294aece}>' is not capable of on-demand, updated its delivery mode to 'Classic'
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What version is your templates? It looks like they are 4.0.1 and needs to be 4.4.4 or greater.
Make your templates and agents are up to the latest version of AVM.
Looks like the provisioning VM agent is at 4.5.0.77
@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
Great Michael, Thanks.
I see that our templates are from February of 2022... I am trying to figure out how to tell what the version they are.
- Agent Version: 4.5.0.77R (agent), 4.0 (capture) - what is this capture 4.0?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Look in your image you set us. There is a field for the Template and version used.
@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
You need to update your AppVol agent on the provisioning VM.
You have an agent version that does not support OnD.
@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
ok I am now using 4.5.1.10 ... that seems to be the latest. I am packaging on a machine that has that version but it is not working. The package changes back to classic after we package it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You will need to place a SR with GSS. Make sure you state the resolution here after working out the issue.
@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
any luck with this issue? We seem to have the same issue ... whenever I click update app -> change for onD -> it reverts back to Calssic after finished the packaging.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You cannot "update" an existing "classic" AppStack to a "OnDemand" Appstack.
You need to create a new AppStack based on the latest version of the templates and choose "OnDemand" when creating the AppStack.
Regards,
Mickeybyte (ITPro blog)
If you found this comment useful or an answer to your question, please mark as 'Solved' and/or click the 'Kudos' button, please ask follow-up questions if you have any.