This tool offers a graphical user interface to build requests to be sent to the XML service. The response is displayed for inspection. Thus, the XmlServiceExplorer allows administrators to debug how the XML service works and what kind of information is passed to Web Interface.

Where is my XenApp 5.0 for Windows Server 2003?

A couple of weeks ago, Citrix released XenApp 5.0 to the web. Rest assured, I was really eager to be one of the first to download this new major release and immediately set up a new box with it. Of course, I wanted to know how the RTW compares to the Early Release of Project Delaware which I wrote about in Delaware Test Drive.

Suppressing Access Lists to be Exposed by the XML Service

In an earlier article about the XmlServiceExplorer, I explained how to obtain the access list of all published applications in a farm from the XML service.

As this information is offered without authentication, it can be considered a security issue. The XML service should rather offer the resulting list of published applications based on the access lists instead of the access list themselves.

Fortunately, this behaviour of the XML service can be suppressed by changing a registry key on the Presentation Server / XenApp server:

Debugging Using XmlServiceExplorer - Part 3

In the last part of this tutorial about the XmlServiceExplorer, I introduced requesting useful information from the farm as well as resolving addresses.

Now, I’d like to demonstrate how chatty the XML service is when it comes to applications and their configuration. Some pieces of information are required for Web Interface to operate while others can be regarded as compromising.

Debugging Using XmlServiceExplorer - Part 2

In the first part of my tutorial about the XmlServiceExplorer, I have explained how session management is performed by the Web Interface and how the same behaviour can be reproduced by the XmlServiceExplorer. I recommend you also read the initial article: Talking to the XML Service.

Now I’d like to introduce several requests providing useful information about a farm and its servers through the XML service.

Debugging Using XmlServiceExplorer - Part 1

After publishing the XmlServiceExplorer, I’d like to give you some ideas how to use this application to do some debugging. In this article, I will demonstrate how Web Interface manages sessions using the XML service and how the same effects are achieved using the XmlServiceExplorer.

Dialects of the XML Service

You may have noticed me taking interest in the XML service and its importance in application delivery based on Citrix products. The DTD NFuse.dtd for XML requests is updated with each version of Web Interface to reflect the current revision of the dialect used for communication. The following table contains a list of dialects (expressed as version numbers) the individual products are speaking (according to their XML requests and replies).

The (Un)Availability of CPSCOM

Inspired by Andy Zhu’s article explaining how to exclude a server from load balancing, I repeated some of the commands from my earlier article about CPSCOM to explore which interfaces are available.

Talking to the XML Service (Update)

Haven’t we all tried to figure out why a setup of Presentation Server with Web Interface and Program Neighborhood Agent is not working as it was designed to be? And haven’t we all traced the network traffic using WireShark to expose the misbehaving component? Yes, to both questions.

Shadow Keys: A Relict from Ancient Times

I have already written about shadow keys in the past explaining the TermSrvCopyKeyOnce and how they are handled on Windows x64. So far, I have only provided descriptions of technical matters concerning shadow keys. This article contains a discussion whether shadow keys are still applicable in modern application delivery infrastructures.