I had to troubleshoot a case where it suddenly was not possible any more to connect via ICA/HDX to freshly installed Windows 7 VDI machines. As it turned out, the root cause was a combination of Microsoft disabling legacy technologies and Citrix relying on them.

Analyzing slow boots is a difficult task. You need to install software like XPerf and master its far-from-intuitive command-line options to generate a trace file that you can then analyze. Once you find a possible cause for the long startup duration you never know if it is specific to the machine you analyzed or if it affects other PCs, too. In other words: XPerf, although powerful, is difficult to master. And it does not scale. uberAgent does. And it is super-easy to use.

I just had a situation where I was facing an empty desktop with no way to logoff, start a program or do anything else. The only thing left to do was to log the session off from an admin session. This got me thinking: how many ways are there to create such a situation? I am writing down all the ways I know of and ask everybody to contribute. Can you come up with a way to end up with a completely empty desktop I and no one else thought of before?

There are situations when you have VMs on disk, but vCenter does not know about them - i.e. they are not in the inventory. While it is fairly easy to add a single machine to the inventory, doing so for dozens or hundreds or VMs is too tedious to do manually. This script automates the process.

Do you know the maximum number of users each of your terminal servers can host with acceptable performance? You may have found out the hard way how many are too many - but how many are just right? Farm sizing and server capacity planning are typical tasks for consultants who often have a hard time fighting the peculiarities of perfmon and logman trying to get the data they need for their calculations. It can be so much easier at no additional cost. The 60-day Enterprise Trial version of Splunk in conjunction with an evaluation license of uberAgent give all the information you need in much less time. Here is how.

When you move users from a physical PC to a VDI environment you may find that they are not too happy with their new machine’s performance - it happened to me. To quantify things I took a series of measurements comparing the old PCs we migrated away from with both VDI machines and the new PCs available to some.

Let use take a look at some graphs I created with Windows Performance Analyzer (WPA), showing a typical corporate laptop boot Windows 7. Detailed information on creating such a trace can be found in my earlier article Analyzing a Slow Boot with Windows Performance Recorder & Analyzer.

In the last five years Xperf has gained popularity as an administrator’s secret weapon for battling all kinds of performance issues. But just when it was on the brink of becoming as mainstream as such a tool can be, Microsoft superseded it by something else: Windows Performance Recorder.

Today it is still as common as it was in the 90s to go for a coffee after switching on the PC in the morning, only to find it still booting when coming back several minutes later. SSDs have not arrived in the average office yet, and even they can only cure some of the diseases that cause computers to start up agonizingly slowly.

When you buy a new HP server it comes with the BIOS setting HP Power Profile set to Balanced Power and Performance. That sounds good but is bad - at least for CPU performance in a VDI environment.

The days are long gone when a browser was just another application. Modern websites are applications of their own, and the browser is their operating system. That has consequences for monitoring. It is no longer sufficient to gather performance data for the browser as a whole. When, for example, Internet Explorer’s CPU usage is high, Administrators need to understand what caused that. Is it the business-critical ERP site or are people just watching fun videos on YouTube?

Windows Explorer is an end user, a consumer product. It creates a reality distortion field that hides part of what is really there and makes you see things that do not exist. That is OK for its intended customer base, but as an administrator you cannot afford to live in a dream world.

Considering the importance of fast logons for a good user experience there is surprisingly little information on the subject. Windows does not even record the total logon time, let alone where it is spent. Administrators wishing to analyze their users’ logons are left in the dark. But that can be changed.

Even if you only have a moderately sized VDI deployment chances are high you will face the problem of getting USB smart card readers to work on the virtual desktops. Given that this is such a basic requirement it is astonishingly hard to implement correctly. To save you the pain of having to start from scratch here is my description of how to do it.

This is a collection of bugs, errors and problems I encountered working with Offline Files, along with possible solutions or at least workarounds. For more information about Offline Files see also my other articles about this topic.

uberAgent has been pretty good at monitoring applications for some time. It is capable of auto-grouping processes to applications and showing IOPS and other stats per application in addition to per process. All this gets even better today: beta 2, available now, adds application usage metering to the feature list.

If you have ever used Sysinternals’ Process Monitor, chances are high you were a little intimidated when you looked at your first capture: it probably contained hundreds of thousands of registry and file system events, generated in a minute or less. That amount of activity must surely indicate high system load - but strangely, very often it does not. Looking at the hard disk LED you will only see an occasional flickering, even though thousands of file system events are captured per second. How is that possible? Read on to find out.

Know this problem? You try to start a XenDesktop session, Desktop Viewer opens … and closes. Then nothing. When you look at the machine in Desktop Studio you find that everything looks good: it is registered with the DDC and it is not in maintenance mode. However, you find an event with the following properties in the application event log:

The beta version of uberAgent for Splunk is available. Official announcement uberAgent’s website Download

Getting Login VSI to launch sessions on multiple RD session hosts is possible with the connection type Custom command line with CSV, but it is more difficult than it should be - especially if you want to launch the RDP sessions in windowed rather than full screen mode.

Who said that end users get all the pretty UIs? Administrators are as happy as anyone to replace ugly consoles with good-looking HTML5 that runs on a smartphone just as well as on a PC.

A little known fact about the Windows Offline Files functionality is it slows down network operations considerably. Here is how and why. Test Results The following tests were performed with a set of 1,114 files of a total size of 408 MB. In the copy test the files were copied from a Windows 7 client machine to a file server over a 100 MBit LAN connection. In the delete test the files were deleted on the file server. No antivirus or other security products were running on either side. Each test was run twice, the table lists the average.

uberAgent for Splunk monitors Windows machines. It does not try to display as much data as possible but focuses on visualizing what is actually going on instead. In the last post we gave you a glimpse of the information it can display about user sessions and logon times. Today we are going to talk about machines, processes and applications.

Client Hyper-V was one of the things I was most looking forward to when I upgraded to Windows 8. I immediately added the Hyper-V feature and went to installing Server 2008 R2 in the first virtual machine. That went well enough and nothing extraordinary happened until I tried to run Windows Update in the new VM. Try as I might, Windows Update would always fail with the error code 80072EFE. Sometimes it chose to fail with 80072EE2, though.