Month: July 2016

Nice Citrix AppDNA 7.9 vid’

If you happen to be lucky enough to be a Citrix Platinum level customer will be lucky enough to have AppDNA in your toolkit.

Nice video covering the piece’s. Interesting product as its uses extend far beyond the application virtualization space. For example if you have a separate Application Packaging team covering desktop-based apps will still have the same obvious benefits. Definitely one of Citrix’s best acquisitions.

 

Advertisements

Nifty new MS cluster feature (2016 Server tech) – configure your own witness in the cloud

An interesting feature within W2k16 within the clustering framework is the cloud witness. Quorum maintenance being one of the most important parts of any cluster design. With DR can be a design challenge as MS recommend that the quorum is located in a 3rd data center. As a lot of companies operate using 2 data centers this can pose a problem.

With the tech preview edition of 2016 it introduces a new feature called the cloud witness that looks to address this problem.

Creating one is simple and via the usual means to create a quorum using the Cluster Quorum wizard. The pre-requisites are straightforward enough too. Need:

i) An active Azure subscription

ii) Storage account

To launch the wizard:

i) Right-click the server in the Failover Cluster Manager

ii) Point to More Actions

iii) Select Configure Cluster Quorum Settings

iv) Select the Quorum Witness option

v) Select the Configure a Cloud Witness option

vi) On the next page provide the name of your Azure storage account, copy the key from the Azure Portal to the clipboard and type the Azure service endpoint

When the wizard is completed you’ll see the cloud witness displayed in the Cluster Core Resources pane in the Failover Configuration Manager snap-in.

 

Citrix HDX Flash redirection tip: how to disable player version check

Been testing various thin clients lately and one thing that appears same across them all is when testing HDX flash offloading by default they will fail due to the flash player being that bit older than perhaps what your VDI image/published desktop has installed.

Example message below:

flash check message

 

If you do come across this message on every VDA/XenApp need to add the below entry in the registry.

•For a 32-bit operating system: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\HdxMediaStreamForFlash\Server\PseudoServer
Add the entry named FlashPlayerVersionComparisonMask with a DWORD value = 00000000

•For a 64-bit operating system: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\HdxMediaStreamForFlash\Server\PseudoServer
Add the entry named FlashPlayerVersionComparisonMask with a DWORD value = 00000000

ESXi tip: Recommended lockdown mode configurations

As you can probably guess by its name lockdown mode is used to increase the security of your ESXi hosts. When enabled no users other than vpxuser have permissions to logon nor can they perform activities against the host directly.

Essentially forces all operations to be performed through vCenter.

Enclosed is a handy table showing the recommended configuration based on setup

https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.security.doc%2FGUID-B23B1360-8838-4FF2-B074-71643C4CB040.html

Applicable to later editions too.