Recently I spent lots of time to check how to improve PVS 7.* server performance to reduce the vDisk loading time.
And it seems on the internet there are lots of articles talking about tuning storage (both storage server and PVS server) to enable ‘oplock’.
But I found that almost all these articles are based on PVS 5.* and windows 2003/2008.
So do we still need to tuning storage/SMB for PVS servers?
Citrix has a good article to answer this quetion:
Just check the summary part:
Using file share storage for vDisks is still a valid and recommended approach, if sufficient capacity and high availability is in place. Especially in environments without redundant resp. highly available file services, I’d rather recommend local replicated vDisk stores instead of using just a single file server that definitely constitutes a single point of failure. And no one needs to invest in expensive file clustering solutions if its only purpose would be to provide file shares for vDisk storage.
Caching will help to significantly reduce the load on file servers or filers. Unlike earlier versions, there are no tuning requirements, neither for the PVS servers, nor for file servers. The defaults are perfectly fine. Sizing guidelines for PVS server memory (RAM) from past articles still apply.
Consider the caching behavior of the SMB redirector. There is a chance that shutting down all target devices connected to a particular vDisk will also remove the vDisk’s cache entries and the cache will need to be warmed up again on the next boot.
Leverage the latest SMB protocol if possible, at the time or writing this article it’s SMB 3.1.1. Not only Windows file servers support SMB3, but also modern filers such as NetApp, and even my home lab Synology is able to support SMB3.
Leasing is key for caching, so don’t use SMB 1.x or 2.0 (in fact you shouldn’t even enable the optional SMB 1.x feature on your PVS servers), and forget about any ‘oplock tuning’. Anything from SMB 2.1 onwards is fine with its defaults, but SMB 3.x brings added features that might be beneficial for you, such as ODX when taking copies of a vDisk file.
So it seems the only thing we need to do is to disable SMB 1.0 on PVS server. How to do it? Here is the link:
I’m using Chinese input layout in my VDI, so usually I delete all other input layout.
And I found that every time when I login to my VDI via company’s laptop, my VDI’s default keyboard input layout will be changed to English (US), and I have to remove it again and again.
At beginning I thought it’s a windows bug, so I spent lots of time to check MS article to fix the problem…No fix…
And today I found that this issue is caused by Citrix not by Windows… Citrix introduced a new feature named “keyboard layout synchronization” in version 7.16. You can refer to below link:
To disable this feature,
On client: use local keyboard layout. Receiver side: select Advanced Preferences > Local keyboard layout setting > No
On VDA disable the keyboard layout sync feature.
For this open registry editor and navigate to HKLM\Software\Citrix\ICA\IcaIme
Add a new DWORD key called DisableKeyboardSync and set the value to <span style="color: #ff0000;">1</span> and reboot the VDA
In Firefox, type ‘about:config’ in the address bar
If prompted, accept any warnings
search for ‘security.enterprise_roots.enabled‘ as the Name
Set the value to ‘true’
Press Control + F to launch the find window. Search for “Creative Cloud Files”, uncheck the Keys and Values boxes and click Find Next. The first result should be within a directory that begins with HKEY_CLASSES_ROOT\CLSID. Below is a screenshot of what it looks like. If you do not see this screen, keep pushing the F3 key until you find it.
Once you’ve located the directory, look for a DWORD value on the right named System.IsPinnedToNameSpaceTree.
Double click it and change the “Value data” from 1 to 0. Finally, click OK to save the new value.
Best practices is always to upgrade vCenter before your ESXi hosts. Download the ISO and upload to your Datastore.
Attach the ISO to the vCenter VM.
Use Putty to connect to your VCSA and run the following command:
software-packages install --iso --acceptEulas
Update ESXi – Fast Method
This is the fastest way, but requires a decent internet connection.
Shut down all your running VM’s and enter Maintenance Mode.
Use Putty to connect to your ESXi host and run the following command:
esxcli network firewall ruleset set -e true -r httpClient
esxcli software sources profile list -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
esxcli software profile update -p ESXi-6.0.0-20160104001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
With daylight-saving time beginning at week’s end (March 8 at 2am), we got some issues that can occur with PVS delivered desktops and XenApp servers.
Some of the issues that occur as a result of the time change are:
Time not showing correctly in the Desktop or XenApp server,
Desktop failure to register with DDCs,
User inability to log on due to domain trust relationship issues caused by the VM/Domain time difference.
Open up your PVS delivered image(s) in read/write mode after the time change has occurred on Sunday.
Run “w32tm /resync /nowait” at the command prompt.
Set the image(s) back to read only, following your normal image preparation procedures.
Remember, you must reboot all PVS delivered desktops and servers after you make the above changes to ensure they receive the updated version.
Being proactive will help ensure a smooth Monday morning for all of your users!
More information on this issue can be viewed here: http://support.citrix.com/article/CTX200058