To choose whether to “Import volumes in the background” or “Import volumes immediately”
In my lab environment I configured both to use the VSAN Datastore:Ĭonfirm the Storage Settings to proceed. In the Storage tab we are configuring the location of where the Appstacks and Writeable volumes that are created will be stored.
I also provided my ESXi hosts root account and password to enable the “Mount on host” setting. I am using the “vCenter Server”, as I am assuming most folks will, and the service account I created assigned to the “App Volumes User” vCenter Role I created. Next up is the Hypervisor Credentials tab. For lab use I added my Domain Admins group. Click “ Next” to continue:Ĭonfigure the Active Directory group that will be added to the App Volumes Admin Group. I provided a service account that I created for both Active Directory and vCenter permissions. Provide the details for your domain, domain controllers (if you want to specify) and user with “Read” access to your directory. Second tab displayed is for the configuration Active Directory.
One thing to point out, when using the trial version of the software only a single Appstack can be attached per user. As I am using the trial version of the software we don’t have much to do here. The first tab that is displayed is the “License Information”. It provides an overview of the tasks that can be completed and initiated App Volumes Manager. Launch the App Volumes Manager desktop icon:Ī “Welcome to App Volumes Manager” webpage will be displayed. With the completion of the installation we have to run through a quick “setup” process to configure VMware App Volumes Manager. Once the installation completes click “Finish” to exit the installer:
Click ‘”Install “ to proceed:ĭuring my install this screen was accurate, it took about 8 minutes to complete the installation: Click “Next” to continue:Īt this point we are ready for the actual installation. I left the default Destination Location unchanged. I had no need to change the default HTTP and HTTPS ports. For this example I am using an existing remote SQL Server Database:įill in the needed Database Server connectivity details and click “Next” when ready: Click “Next” to continue:Ĭhoose if you wish to have setup program install/configure a copy of SQL Server Express or utilize an existing SQL Server Database. The “App Volumes Manager Installation Wizard” dialog will be displayed.
Click “Next” on the Installation Wizard dialog:Īccept the the licensing agreement and click “Next” to continue:Ĭhoose the “Install App Volumes Manager” radial and click “Install” to continue:
Mount the VMware App Volumes ISO to the “VMware App Volumes Manager” server and execute the installer.
With all this goodness in hand, this first post in the series will cover the installation and configuration of the brains for App Volumes, the App Volumes Manager. Additionally, with the use of “Writable Volumes” user settings and changes can be captured and saved. Shown in the picture below you can see with the use of the “CloudVolumes agent” the application stacks are decoupled from the operating system. Fast forward to earlier this month and VMware officially released the product under the App Volumes name and made the software available to customers (as a standalone product or part of the Horizon View Enterprise bundle) as well as trial bits to give folks the chance to kick the tires.Īpp Volumes allows for the creation of containers or “AppStacks” for the delivery of a single application or multiple applications within a single stack. During VMworld 2014 it was announced that VMware was purchasing Cloud Volumes, an upstart for application virtualization technology.