Windows 8.1 VDI Optimization Guide

Posted: 4th March 2014 by neil in Citrix XenDesktop

Citrix have released a Windows 8.1 Optimization Guide for VDI which is a very useful read.  The savings encountered by performing these optimisations are considerable.  In summary the savings vs a non optimised image are below.  You can find a link to the download here – http://blogs.citrix.com/2014/03/03/new-windows-8-and-8-1-optimization-guide/?utm_source=feedburner&utm_medium=email&utm_campaign=Feed%3A+CitrixBlogs+%28Citrix+Blogs%29

Metric Default Optimized % Gain
Hypervisor Level Total CPU % Run Time 55% 42% 24%
Context Switches 201,000 177,000 12%
Disk MB Total/Sec 9.6 8.4 13%
Disk Transfers/sec 634 595 6%
VM Network Traffic (Mbps) 120 92 23%
VN Level Available memory (MB( 458 644 40%
Memory Pages/Sec 19.4 15.2 22%

By default you can only connect to Citrix StoreFront using HTTPS.  If you are in a corporate environment which has a PKI Infrastructure that is perfectly fine.  But if like me you run a small test lab there is a work around which you can do to enable you to use http instead. 

image

1) When you configure StoreFront make sure you select the transport method of HTTP

2) On the Citrix Receiver client configure the following registry entries:

  1. Under HKLM\Software\Citrix\Dazzle, set AllowAddStore value to A in order to allow users to add non-secure stores.
  2. Under HKLM\Software\Citrix\Dazzle, set AllowSavePwd value to A in order to allow users to save their passwords for non-secure stores.
  3. To be able to add a store that is configured in StoreFront with a TransportType of HTTP, add the following key value under HKLM\Software\Citrix\AuthManager : ConnectionSecurityMode (REG_SZ type) and set it to Any.

3) After configuring those registry entires you should be able to connect using HTTP

image

On a recent XenDesktop 7 deployment I encountered this error when attempting to configure XenDesktop. The error message received was “There was no suitable service to perform operation”.  Luckily the fix for this is simple, just reboot your server, launch Desktop Studio and you will see the configuration has actually succeeded successfully.

image

image