Updated: September 22nd 2015
Although it has been a while since I’ve written this article there’s still a lot of interest in the subject. Pretty much nothing has changed since I released it so it’s was also still valid, until yesterday. Community hero Andrew Morgan released a long awaited update for ThreadLocker. I’ve updated the Threadlocker part of this article and the conclusion.
If you are reading this you might also be interested in part 2 of the CPU scheduling and memory optimization solutions series.
For a while now customers and colleagues are asking me which tool to use when it comes to CPU scheduling and memory optimizations. We use several management products and end up with more than one product utilizing these tasks. Choice is good but do we just enable them all and if not what’s the best way to configure this?
When you look a little bit deeper then plain and simple marketing you’ll notice that the way the different products handle CPU scheduling is totally different and combining some of them will degrade system performance or simply don’t work for example Citrix CPU management does not start when Microsoft DFSS is enabled.
Before we start I’d like to thank Andrew Morgan for allowing me to re-use some information from his ThreadLocker topic.
To start off I will first try to explain how each product works and will then summarize and see if we can work through them and work to a proper advice.
Microsoft Windows 2008 R2 Dynamic Fair Share Scheduling (DFSS)
The mystery of the missing use case for stateful VDI
Since I started doing VDI projects a couple of years ago on each project I run into cases where certain user groups demand a personal stateful VDI desktop. I have heard lots of reasons, the problem is that I haven’t heard a single good one yet!
The first thing I run into is that customers want to squeeze all of their users onto VDI while most of the times 80% of the users will have the same experience on a RDS desktop. Would we ever think of letting a user install his own applications on a RDS desktop?? I don’t think so!
So what about the 20% of the users that actually need a VDI desktop? Do they also need to install their own applications? I would say no but let’s look at some of the use cases users think of.
Citrix just released a “small” but important update for XenApp 6.5 available as XA650W2K8R2X64002. Although this is update is only 12 megs in size it adds a bunch of interesting new features!
To finish the Powershell Microsoft Active Directory blog post series here is a script which I used for a customer. The script is used for moving the Terminal Server Home Drives of all TS users to a Central Directory. The central directory is based on the ServernameShare%USERNAME% value. The TS Home Drive location was set manually and different location were used. We needed to change this to one single location. Doing this manually would take us months so we need to automate these tasks.
Here we are with already the latest part in the Powershell and Active Directory blog series. In part 3/4 we worked with getting information from AD Object attributes which are not defined in the schema. In this part we will work on modifying the settings on these attributes.
Back again with a new post in the Powershell and Active Directory series of posts. Remember when I said I will show you how to work with attributes that are not schema attributes? By default you can do a $var.schemaatrributename like $user.name or $user.DistinguishedName. This is not possible for for example the TerminalServiceHomeDrive attribute because this strange enough is not a schema attribute.