VirtualizationAdmin.com has a new article by David Davis titled: 5 things Microsoft must do to stay in the virtualization game. I think the article has some fairly weak arguments and certainly a couple of claims that are just wrong. VirtualizationAdmin doesn’t provide a way to comment on articles, so I’ll break this down in an article of my own.

The document Hotfixes and Security Updates included in Windows 7 and Windows Server 2008 R2 Service Pack 1 Beta has the complete list of what’s fixed in SP1. RemoteFX might steal the show, however I’m specifically interested in what fixes there are for Terminal Server or Remote Desktop Session Host as it’s now called.

There are currently several versions of App-V 4.x available for deployment, although it is highly recommended that you deploy or migrate to 4.6 SP2. For the full list of available versions and hotfixes for all App-V components see the spread sheet at the end of this post.

If you’re configuring the Remote Desktop Virtualization Host (RDVH) and RemoteFX roles on a Hyper-V box, you may see the following message and will need to configure a license server:

Microsoft App-V is available in two flavours: for desktops (this includes laptops and virtual desktops – essentially anything that will run Windows XP, Windows Vista or Windows 7) and for Remote Desktop Services (RDS).

Wikipedia describes application virtualization as: