In Part 3, we completed the Agent and View Broker installation. In this part 4, we are now ready to configure AppStacks.
Go back the Windows VM where you install your App Volumes Manager. If you remember, we left at the screen in Part 2. There is no AppStack created yet. Click the Create AppStack button.
You get the following screen. To create AppStack, just need to specify the name, datastore, etc. Click the Create button.
It is not instant, and the status changes to Creating.
Wait for the above process to complete. Once completed, the status will change to Unprovisioned. Click on the Provision button. Notice it’s giving you a hint on the next step, which is Select Provisioning VM.
Remember the MS AD integration requirement? This is where it comes in handy. You need to find the computer. In my case, I just typed “volume“, clicked Search button, and it found my Provisioning VM.
I selected it, and clicked on the Provision button.
The AppStack status is now changed to Provisioning. Again, it’s giving you a hint on the next step, which is to install applications on the provisioning computer.
My plan is to create >1 AppStacks so I can evaluate cross AppStacks integration and see the experience in managing multiple AppStacks. I created these 3 AppStacks
- Core Apps:
- Basic and mandatory apps, like Java, Flash, Chrome, FF.
- The reason for including browsers is browsers typically needs plugins.
- MS Office, Adobe Reader
- Admin Tools
- SSH, BitVise, vSphere C# Client, vSphere Web Client, etc.
This what it looks like after I created 3 AppStacks. The next step is to choose a Provisioning VM.
A Provisioning VM can be used for >1 AppStack, but not at the same time. If you do not manually unassign it, you get an error message like the following:
The next step is to install application. I will use a separate post to mark the separation, as the work is done on another place (the Provisioning VM). You can find it on Part 5.