Provisioning applications on physical system using VMware App Volumes

Introduction

In few of my earlier blogs on VMware App Volumes, I demonstrated how you can leverage VMware App Volumes to provision applications real time in a VMware virtualized environment. But what if an organization is looking for a solution to provision applications on to a physical target machine or on a non-VMware virtualized environment. An organization can leverage VMware App Volumes to provision applications on to a physical target machine or on a non-VMware virtualized environment using in-Guest Operations mode. An organization can use in-Guest connection type to assign AppStacks and Writable Volumes to the virtual machines running on third-party unsupported hypervisors or to the physical computers. In an in-Guest operations mode, AppStacks and writable volumes are stored on a standard Common Internet File System (CIFS) file share in VHD file format and attached to the target computer using operating system functionality.

In this post, I will be covering the steps to configure an App Volume manager in in-Guest Operations mode post installing VMware App Volumes manager.

You can also refer to my previous blogs for

Demo

Procedure

2. Integrate Active Directory

3. Choose in-Guest as Operations Mode under Machine Manager tab.

4. Add the CIFS Share & choose CIFS share as storage location for AppStacks or Writable Volumes under Storage Tab.

Post configuration you can create an AppStack and assign that to the user.

Conclusion

This concludes the configuration of VMware App Volumes Manager in a in-Guest Operation mode to provision applications on to physical target machines or on virtual machines running on a third-party unsupported hypervisor. Hope this will be informative for you. Thanks for Reading!!!. Be social and share if you find worth sharing it.