Webcast Series about Installable Feature in Windows Server 2008 R2
Published on 02 Nov 2009My colleague Nicki Wruck (@CommunityGuide) has started a huge series of short videos about the features in Windows Server 2008 R2 - in German.
My colleague Nicki Wruck (@CommunityGuide) has started a huge series of short videos about the features in Windows Server 2008 R2 - in German.
I held a talk about VDI at the IT-Administrator Workshop in Böblingen. Please download the slide deck here.
Watch me explain “Netzwerklastenausgleich” in Video #26.
Watch all videos here.
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! When XenApp is installed on a server running the Internet Information Services (IIS), the installer offers to activate port sharing between the XML service and IIS. What this actually means is that the XML service is not setup as a system service but as a DLL inside IIS.
While writing the previous article about monitoring the performance of the physical disk, I realized that I should also explain why memory management and disk activity are closely connected. As this section started to get rather lengthy, I decided to publish the topic in a separate article.
In the last two articles of this series about performance monitoring, I have introduced how to monitor the characteristics of the memory subsystem and the processor subsystem. Now, I’d like to explain why the physical disk is of importance to performance monitoring and how it relates to the memory subsystem.
The famous German IT magazine c’t has recently published an article about creating your own and modifying existing ribbons in Office 2007. Not again, you may be thinking. But the article shows how a simple DLL helps without any knowledge of programming.
In the last posts of this series I gave an overview why performance monitoring is important and that it is not a trivial subject, that terminal servers are an entirely different matter and they require special attention and, in the last post, how to monitor the processor and related corners of the operating system. Continuing my way through the operating system, I’d like to take an extensive look at the memory subsystem in this post.
As Windows Server 2008 R2 is now RTM and is only available as x64 edition, you need to ask yourself how Windows x64 effects application delivery because sooner or later you will succumb. Although a general adoption of x64 is still a long way gone, many companies are beginning to actively pursue evaluating Windows x64 and testing applications on it. But considering Windows Server 2008 x64 on a very high level, there are pitfalls you need to be aware of.
After the introductory articles about the importance of performance monitoring and the characteristics of terminal servers in that area, I finally dive into the first and most obvious subsystem of an operating system – the processor. The processor or rather the processor cores are the workhorses of the system. They are collectively responsible for executing commands for each of the active processes. But they also switch the context between running processes to reflect the priorities assigned to each process by the operating system. In this article, I will introduce the well-known as well as some rarely used metrics to monitor the load put on the processor subsystem.