Filtered articles: "Presentation Server"

When I attended BriForum 2007 in Amsterdam, Juliano Maldaner (XenApp product architect) presented features in future versions of XenApp. He also talked about a very impressive change how XenApp handles policies: the plan was to integrate them into Microsoft group policies.

Two and a half years have passed and - finally - the project Parra tech preview offers a first (public) look at the new policy engine. In this article, I'll have a closer look at the user interface and the handling of policies.

Do you host your Web Interface on one or more XenApp servers? Then I recommend you heed this article before changing your setup. You may well loose your XML service when migrating the Web Interface to another server. And loosing your XML service may result in an outage of your application delivery infrastructure!

In my experience, terminal servers are not properly monitored resulting in administrators not knowing how a farm performs – neither concerning the peak performance nor the trend of the handled load. This leads to an inaccurate and often inadequate sizing of the terminal server environment because only rough estimates arise from such a negligence.

In this series of articles, I'd like to expand on the topic and stressing why monitoring is important for all environment (including terminal servers), what needs to be monitored and how is can be achieved.

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.