Thursday, March 28, 2013

CTX126704 - Registry Entries Used by XenDesktop 5.x Broker Service - Citrix Knowledge Center

CTX126704 - Registry Entries Used by XenDesktop 5.x Broker Service - Citrix Knowledge Center
Read More ->>

Wednesday, March 13, 2013

Provisioning: How to avoid failover delay

Note: Installing Provisioning Services affects the following registry key:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\OplocksDisabled. Changing this registry key disables Windows Opportunity Locking, providing the fastest possible failover time when contact with the active Provisioning Server is lost. Without this change, failover times can take up to one minute. During this time, Windows does not allow access to the vDisk file that was in use by the failed Provisioning Server. By disabling Windows Opportunity Locking on Provisioning Servers, the Stream Service can have immediate access to vDisk files. However, this reduces caching of remote vDisk data for the entire Provisioning Server.
OplocksDisabled REG_DWORD 0 or 1
Default: 0 (not disabled)
OplocksDisabled REG_DWORD 0 or 1
Default: 1 (disabled)
Read More ->>

xendesktop trust xml service

Note: If you intend to use SmartAcces
s endpoint analysis, pass-through authentication, or smart card authentication with XenDesktop, you must configure XenDesktop to trust XML services. To do this, run the following Powershell SDK command:

Set-BrokerSite -TrustRequestsSentToTheXmlServicePort $true
Read More ->>

Wednesday, March 6, 2013

XS - Multipathing



Firstly Check true multipath status (XenCentre can report it incorrectly). You should see two paths in Round Robin for each Storage Repository

Multipath –ll


If this reports two per SR as expected then we simply need to tell XenCentre to update/refresh its view this is accomplished by running the below command, give it a minute and XenCentre should then report the correct number of connections.

/opt/xensource/sm/mpathcount.py


If the multipath –ll doesn’t report as expected the quickest and simplest way to resolve is to put the host in maintenance mode, disable multipathing wait 2 minutes and then re-enable multipathing. Wait a couple of minutes and then check the multipath status as per above. Once happy you can leave maintenance mode.  This seems to sort the problem 9/10 times.  Failing that if you may need to restart the open-iscsi service, command below;  

Service open-iscsi restart
Read More ->>