Citrix: NetScaler applet hangs at 99% “Logging in”

Written by Ingmar Verheij on November 27th, 2013. Posted in Netscaler

When a Citrix NetScaler is configured using a graphical interface a browser is used to connect to the Citrix NetScaler. Starting NetScaler release 10 a part of the configuration is migrated from Java Applets to HTML5, but most configuration are still depending on Java Applets.

When you open a more advanced configuration the Java Applet is loaded automatically., If it hangs at 1% “Downloading Applet…” you might want to read this article.If it hangs at 99% “Logging in” continue reading.

Logging in

Citrix: NetScaler hangs at Downloading Applet…

Written by Ingmar Verheij on November 27th, 2013. Posted in Netscaler

TIP: NetScaler 10.5 uses HTML5 instead or JRE for most configuration features! Hooraaayyy! – link

With the release of Java Runtime Environment (JRE) 7 update 45  new security measurements are introduced. Oracle describes the impact of the updated security baseline in this blog. While security is an important topic (especially when web applications are involved) breaking applications due to raised security could result in the opposite.

In case you’re running JRE 7u51, please read this article with an update.

Downloading applet...Citrix NetScalers are managed with a web interface which uses HTML5 and Java applets. With new security measurements these applets hang at “Downloading Applet…”

At the moment of writing there are two features that need to be disabled to enable the Java Applets of the Citrix NetScaler (as described by Barry Schiffer in this article):

  • Disable Temporary Internet Files
  • Lower Security

While this solves the problem (of not being able to administer a Citrix NetScaler) is potentially creates a new: the security level is lowered for the entire JRE. While Oracle was trying to increase the security for Java Applets with this update the opposite is achieved Sad smile.  Fortunately there is a way to lower the security for specific addresses Smile

Citrix: Import NetScaler (10.1 Build 120.13) on Hyper-V Server 2012R2 / 8.1

Written by Ingmar Verheij on November 5th, 2013. Posted in Netscaler

Hyper-V did not find virtual machines to import from locationI tried importing a Citrix NetScaler Virtual Appliance on a Windows 8.1 machine and received the error “Hyper-V did not find virtual machines to import from location”. Importing the same appliance on Windows Server 2012 did work.

The cause of this error is that the virtual machine is exported from a Windows Server 2008R2 server (running Hyper-V 2) and Microsoft deprecated the WMI root\virtualization namespace v1 in Windows Server 2012 (Hyper-V 3) and removed it Windows Server 2012 R2 (see TechNet).  There’s no support for the old WMI format.

Citrix PVS: Enabling KMS licensing on a vDisk

Written by Ingmar Verheij on August 9th, 2013. Posted in Provisioning Server

When streaming a Windows machine the Windows license can be managed by a Key Management System (KMS). Citrix describes it as follows “KMS volume licensing utilizes a centralized activation server that runs in the datacenter, and servers as a local activation point (opposed to having each system activate with Microsoft over the internet).

To ensure KMS is working correctly the Windows machine needs to be prepared for KMS, this involves setting the right license key and “re-arming” the license. Citrix has done a pretty good job describing different scenarios in CTX128276 and explaining which actions to take, but there are more steps involved.

In this article I’ll explain what steps you can take to build a PVS vDisk where licensed are managed by KMS and how to troubleshoot some known caveats.

Citrix XenApp: Sessions disconnected right after connection

Written by Ingmar Verheij on August 7th, 2013. Posted in Remote Desktop / Terminal Server, XenApp (Presentation Server)

When new sessions are started, either via Microsoft RDP of Citrix ICA, they are disconnected within seconds. This applies to normal users and users with administrative privileges. This problem is caused by a chain of events. One components crash leads to an ungraceful shutdown of other components leaving a garbage configuration, preventing new connections.