Before we can test the AppStack, we need to assign it first. AppStacks can be assigned to all kind of active directory objects like Users, Groups, Computers and OU’s, and you have the possibility to attach the AppStack at next login or reboot or immediately. Because App Volumes provides just-in-time application delivery you can literally publish hundreds of application on the user’s desktop in just a few seconds!
In the next steps I’m going to assign an AppStack immediately to the desktop and show you the integration with the local system. (Note: If you choose immediately, make sure the user is logged into the desktop)
How to: Assign an AppStack
- In the App Volumes Manager, select the AppStack and click Assign.
- Search for the Active Director object. Select the user, computer, OU or user group to assign the AppStack to. Click Assign.
- Choose to assign the AppStack immediately, and click Assign.
- Switch to the client desktop, and you will notice that the Notepad ++ icon is published to the desktop.
- Open the application to see if it starts without any errors.
- To see the really cool integration with the local system. Go to Start > Control Panel > Programs and Features, and notice that the application looks like it’s locally installed.
- As said before, App Volumes does not use any isolation. So your applications are not written to any kind of cache folder on your local drive. For example Microsoft App-V uses c:\programdata\app–v as a cache folder for all packages. When you open a browser and browse to the C:\Program Files folder you will see the Notepad ++ folder.
If you followed all steps you should now have an AppStack with working application(s). In the next chapter I will show you how to unassign an AppStack.
VMware App Volumes and AppStacks:
– Chapter one: Create an AppStack
– Chapter two: Provision an AppStack
– Chapter three: Capture an application
– Chapter four: Edit an AppStack
– Chapter five: Assign an AppStack
– Chapter six: Unassign an AppStack
– Chapter seven: Update an AppStack