Hey,
First off a small introduction might be a good idea (other than raeding installation documentation and user guides and stuff
)
What AppVolumes does is create a VMDK file which holds information and when logging in it attaches these VMDK to a running machine based on user or computer (depends were you attach it to).
When installaing it you copy 1 template VMDK for apps and 3 for writable volumes to your datastore. What you need at least to create appstacks is a VCenter where Appvolumes can talk to because it needs to attach the VMDK to a machine, a Windows 7 or 8 virtual machine within this VCenter to do the sequencing with and an Appvolumes manager to create the actual appstacks. It would not suggest using anything other than this to create appstacks. Appstacks are read only VMDK's (which are made read only by AppVolumes manager) and writable volumes are read write.
So if you would like to create Appstacks in a test environment and then use it in production just by copying the file it would be possible. Writable volumes i would just create at production because they are read/write. But for appstacks to be created you will need to have a fully functional AppVolumes environment.
If you have more questions feel free to ask
The more people in the community, the merrier ![]()