Brian Madden TV
The upcoming server version of Windows 7 will be released as "Windows Server 2008 R2" late this year or early next year. Microsoft is planning several improvements to the terminal server capabilities. Back in BMTV Episode 4, we looked at the changes that Microsoft is making for the RDP protocol in Windows 7. In this week's show we'll look at the changes and new features of Terminal Server itself.
We'll also take a look at Microsoft's plans for VDI in Windows Server 2008 R2. They're building a Windows 7 client plus Hyper-V plus RDP 7 capability that will let anyone use pure Microsoft products to build a basic VDI environment.
This week's show includes demos and conversations with several people from Microsoft, including:
- Ashwin Palekar, discussing Microsoft's terminal server and VDI strategy and plans for Windows 7.
- George Zhu, demoing the creation of a VDI instance in Windows 7.
- Ido Ben-Shachar, explaining how the Start Menu application integration will work.
- Olga Ivanova, demoing several new features of Terminal Server, including per-user MSI installations, session- or application-based IP addresses, and "fair share" kernel-based processor utilization protection.
And new this week: our "vendor of the week" segment.
Last month we wrote that there are more than 100 vendors in the desktop and application virtualization space. Some of them are very popular, and some of them are more obscure. All of them are worth at least knowing about. To that end, we're creating a new segment on the show for our "vendor of the week." We (Gabe) put all the vendors' names into a hat, and we'll draw one at random each week. Then we'll learn about that vendor and arrange some interviews during the week, and we'll do a short segment on them the following week.
We close Episode 6 with the random drawing for next week's vendor, and that vendor is....... (you have to watch to find out. ;)
(Note: You must be logged in to post a comment.)
If you log in and nothing happens, delete your cookies from BrianMadden.com and try again. Sorry about that, but we had to make a one-time change to the cookie path when we migrated web servers.