Featured Post

NetScaler Cipher Lists - 2016 Edition with ECC/ECDSA

The new NetScaler 11.1 Release (starting with Build 47.14) brings Support for ECC/ECDSA Ciphers, unfortunately only on MPX Appliances with a...

Friday, June 28, 2013

Skip vDisk Boot Menu under PVS 7.0/7.1

Under Provisioning Services 6.1 I had disabled the vDisk Boot Menu for all of my Maintenance/Test Target Devices by setting the "SkipBootMenu" DWORD Registry Key as described in the Citrix Support Article CTX135299.

After upgrading my Provisioning Servers to Version 7.x the PVS vDisk Boot Menu reappeared even though the SkipBootMenu was still present. After a quick Call with Citrix it was determined that the Registry Key has been moved from:
  • Old: HKLM\Software\Citrix\ProvisioningServices\SkipBootMenu (PVS 6.x)
  • New: HKLM\Software\Citrix\ProvisioningServices\StreamProcess\SkipBootMenu (PVS 7.x)

The correct Registry Key Location for PVS 7.0

After moving the Registry Key to the new Location and restarting the StreamService my Maintenance/Test Target Devices are now skipping the vDisk Boot Menu again. Problem solved!

Thursday, June 6, 2013

Uploads to Sharefile Storage Zone fail with 100% completed

I'm currently implementing a ShareFile Proof of Concept with On-Premise Storage (also known as Storage Center) and stumbled upon an Error while trying to upload my first Files into the On-Premise Storage Zone and thought I'd share my Solution.

When trying to upload my first Files into the On-Premise Storage Zone via the Sharefile Website the File Upload itself would continue up to 100% but then fail while completing/finishing with an Error.

In the Logfiles where the Sharefile Storage Center is installed (usually found under: C:\inetpub\wwwroot\Citrix\StorageCenter\SC\logs) I found the following Error Messages:
HE [scerr] StorageCenter Error - Unhandled exception in upload-threaded-3.aspx - 'Unable to generate a temporary class (result=1)
error CS2001: Source file 'C:\Windows\TEMP\vr2z302t.0.cs' could not be found
error CS2008: No inputs specified 
Because the ShareFile Services are running under the Network Service Account (if you haven't changed it) I had to give the Network Service Account Full Access on the C:\Windows\TEMP Folder on the Storage Center Server itself.

Wednesday, June 5, 2013

Configuring the new Storefront Monitor in NetScaler 10.1

With the new NetScaler 10.1 Release Citrix is shipping an "built-in" Storefront Monitor so you no longer have to use an https-evc Monitor (or something else) as Monitor like I described in my previous Blogpost.

UPDATE: The Problem I describe below seems to be fixed in the new NetScaler Release 10.1 Build 120.13 according to the Release Log.
Issue ID 0398327: Monitoring of StoreFront servers fails if they are part of a cluster and the StoreFront monitor is bound to the entire service group. The StoreFront monitor probe fails because individual members have different host names.

In this Example my Storefront Servers are named storefrontserver01 and storefrontserver02 and they are load balanced under the DNS Record lb-storefront.domain.local which is pointing to the Virtual IP Address (VIP) on my NetScaler responsible for load balancing the two Storefront Servers.

When configuring the new Storefront Monitor don't put the load balanced Storefront DNS Record in the Field "Host Name". Here is the Screenshot how NOT to do it:

You shouldn't use the load balanced DNS Record because as soon as your two (or more) Storefront Servers are down at the same time and therefor your Storefront Virtual Server is marked as Down too, the Storefront Monitor will never report the Storefront Services as up again even though the Storefront Servers might have recovered in the meantime. This is because the Storefront Monitor is checking the DNS Record pointing to the marked as "Down" Virtual Server load balancing your Storefront Servers which in turn is down because the Monitors are "Down" and the Monitors are "Down" because your Virtual Server is "Down"... the NetScaler is caught in a Loop.

To prevent this from happening you should instead create a separate Storefront Monitor for every Storefront Server you are going to be load balancing and put the FQDN of your Storefront Servers in the Field "Host Name". In my example this would be storefrontserver01.domain.local and in the second Monitor it would be storefrontserver02.domain.local.

You should then bind the new Monitors to their corresponding Service as shown in the Screenshot below:

If something is not understandable or my explanations are too weird feel free to let me know in the Comments :)