VMware App Volumes and UEM battling each other
I was talking to my colleague Sven Huisman this morning and the discussion got to App volumes and VMware UEM. We both are running some PoC’s right now and are experiencing some rather interesting facts about both products.
There is one feature that I experienced before that I thought should be shared with you out there. It’s something they need to work on, it’s fairly simple but if it’s not implemented in UEM soon, the combination with App volumes is rather useless.
Let me explain myself…
UEM is implemented to control what application a user will see in his/her desktop, this among other user profile controlling features is the core business of UEM.
App volumes is implemented to stop the image sprawl so you don’t need 10 VDI golden images to conquer your ever demanding organization, you built one and add AppStack per department.
The marriage took place the minute VMware acquired VMware UEM, both products suddenly are bonded, in good and in bad times until death do us part.
So what happens when you have a desktop that is controlled by UEM and you add an AppStack? Let me walk you through this.
- You logon to the desktop
- UEM kicks in and setup your desktop following the configuration you created
- App Volumes integration with the Connection server kicks in and connects to AppStack to your desktop
- You see all you apps that are installed in the image and all other settings like printers and drive mappings.
You won’t however see your AppStack applications, they are there but UEM is still blocking them. The logon task of VMware UEM is happening before the AppStack is connected, the integration with the connection broker works for App Volumes but not yet for VMware UEM.
Can be tune this?
I’ve been playing around with it and there are a few way to get your applications available. One option is to click refresh yourself but that is of course the last option you want to give your users.
There are a few trigger available that you could use;
There is however no trigger for added AppStack and and haven’t yet found a way to create something to run after logon that would do a refresh.
I created a unlock task that runs on the unlock trigger and chose UEM Refresh there. That one works for instantly after I unlock my desktop the apps are there.
I also added a scheduled task to do a refresh but again it’s not really the way to go.
I think that VMware needs to add a little bit of integration here and ask the guys from Immidio to add a trigger called AppStackArrival.
I you found a great manageable way to do this, please let me know.. looking forward to it.
p.s. without UEM, App volumes will show you the applications instantly, just when you add UEM you add management on a different level that for now hurts me.
Update 5th June 2015 11:02: My co-worker Sven Huisman was digging a bit deeper and focused on AppVolumes to solve this issue. He found another workaround to solve this, this is a more workable workaround. Read about it here.
It does not solve it, the integration has to come from UEM detecting the AppStack or AppVolumes notifying UEM that it is doing something. It’s at least a workable solution for now, now it’s up to VMware.