HI
We have a requirement from the customer that they will be using writable volumes for OST and Indexing. Since it will not have any data stored they would like to have the writable volumes size to 1 GB.
I tried to follow the steps from VMware blogs for custumizing the appstack size and pointed to the writable volume template. The
Creating a Customized App Volumes AppStack Template VMDK - VMware End-User Computing Blog - VMware
Will reducing the writable volumes size reduce the log on time.
We have the base image + Base App stack 20 GB+ Autocad 10 GB + Writable volume 10 GB and the log on time is 1 min. I would like to know the possibility of speeding the log on .
we have already added the registry not to block user on logon as per VMware recommendation.
Please Advice
Hey.
The setting volwaittimeout will not work if you have the 2.11 version because it will not apply the settings in your writable volume if you are using UIA + Profile. If you only use UIA then this setting will work.
And what we did to create a larger (or smaller, whatever you would like to use) is to copy the disk and resize it while attached to a machine and then use the following procedure to rename the disk.
This should do the trick.
Hey nevgeo,
Changing the size of the wtritable volume will not speed up the logon process. What Appvolumes version are you using?
It depends on what version of Appvolumes you are using if you are able to speed up the logon process.
The best option is to change the VolWAitTimeout value to something like 5 (seconds that is) but when you have a writable and are using 2.11 you cannot use this setting because your writable settings will not be applied, even if they are attached.
Did you check the svservice.log file to see why it takes about 1 minute?
We have currently upgraded to Esxi update 2 and found the attachment of app stacks are 40-50 seconds.But VMware support has also enabled the registry and we have writable volumes and we can see the writable volumes attached and indexing is redirected to the writable volumes and working fine. Which setting did you mention in the previous comment which will not work if writable volumes are used.
We are using 2.11.
Thank you for the response
Ray,
Also I would like to know the possibility of reducing the default 10 Gb to 1 Gb as this will be just used for indexing
Please Advise
Hey.
The setting volwaittimeout will not work if you have the 2.11 version because it will not apply the settings in your writable volume if you are using UIA + Profile. If you only use UIA then this setting will work.
And what we did to create a larger (or smaller, whatever you would like to use) is to copy the disk and resize it while attached to a machine and then use the following procedure to rename the disk.
This should do the trick.
We are using the UIA template so we didn't face any issue.But I would like to know the iops created by writable volumes is there any default value available. Which I can share it with the Customer.
Thank you
No there isn't. The thing is that it will merge it prelogon and after that it depends on how much you do on the VDI and how much the writable contains.
In normal behaviour a Windows machine takes up to 40 to 50 IOPS so my guess is it wont be any different for the writable.
And for VDI to work properly you will need some sort of Flash storage to begin with. Just pick a good one (enough to choose from, we use Tintri) that delivers the IOPS. If you need to juggle around with these numbers my guess is your lost to begin with
.
