![]() ![]()
As mentioned for our test scenario I am going to log into my Horizon View environment using a test account. With the Writable Volumes up and running it is time to see what they can do. One other thing to point out, each of the VMDK’s are Thin-Provisioned and configured with a maximum size of 10GB per VMDK by default:īack in the AppVolumes Manager dashboard we can see each of the volumes that were created and their current status:Īnd just like that we are ready to give the volumes a test. Browsing the Datastore you can see the four unique VMDK’s created per use (notice the VMDK file names). The last option is when you select the type of Writable Volumes template to use:ĭuring the creation process I popped over to my vCenter connection and as you can see below the tasks to create the new VMDK’s finished. I selected to use my VSAN Datastore and the default destination path to hold the Writable Volumes. With the Active Directory group selected additional AppVolumes options are available. From the output you can see the three Active Directory groups I have created, one for each type of Writable Volumes templates:įor this post I will be using the Template_profile_only Writable template so I selected the corespondng Active Directory group, AppVolumes_Writable_Profile. Since I will be creating Writable Volumes for a group of users I entered AppVolumes_Writable in the Search field. Finally click on the Create Writable button: With the assumption that you have already logged into the AppVolumes Manager Dashboard, select the Volumes menu context and click on the Writables tab.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |