The Microsoft Global MVP Summit is this week. What should we ask Microsoft?

The Microsoft MVP Summit is upon us again. This is the few days where all of the Microsoft MVPs in the world are invited back to the motherland to meet with the product teams to share feedback and discuss ideas about current and future products.

The Microsoft MVP Summit is upon us again. (This is the few days where all of the Microsoft MVPs in the world are invited back to the motherland to meet with the product teams to share feedback and discuss ideas about current and future products.) And like past years, the Remote Desktop Services product group (formerly known as the “Terminal Server” product group) asked all of us MVPs to give a presentation to them about what we’d like to see in future versions of Remote Desktop Services.

Last year we presented the team with some very bold ideas. We basically told them that what we wanted was a drastically different architecture for the “user personality” of Windows, complete with full separation of applications, settings, user state, and data. The team was generally receptive to our idea, although they’ve really gone no where with it.

This is not because the Remote Desktop group doesn’t care. It’s more because it’s the wrong group. Like it or not, the Remote Desktop product group is “just” responsible for the Remote Desktop Services-related capabilities of Windows. So when we present them with these broad and deep sweeping changes that we’d like to see in Windows, their basic response is, “Um, yeah, we’d love that too. But that’s about fifteen levels above our heads. How can we specifically help you with Terminal Services?”

So until we can get a meeting with Ray Ozzie, I guess we’re going to have to limit ourselves to Remote Desktop-related requests and questions.

We have a pretty good list so far (which we’ll share with you later this week), but if anyone else has any ideas, questions, or suggestions for Microsoft’s Remote Desktop Services product group, now’s the time to ask.

Brian Madden TV – this week from Seattle

We’ll be recording another episode of Brian Madden TV this week (to be released on Thursday). Much of the content of this week’s meetings will be covered by NDA, so we won’t be able to report on everything. However, we’ll use the opportunity to leverage (a) the large number of MVPs in one place, and (b) the large number of Microsoft folks to have some interesting conversations and to record some cool demos.

In addition to the specific questions and feedback that we’ll take to Microsoft, are there any questions you’d like to ask the MVPs? What about demos? Anything from Microsoft you’d like us to show you?

And finally, Shawn Bass is an MVP

There’s been a running joke about Shawn that he’s the one of the guys who most deserved to be an MVP that never was. And I’m most known for putting my foot in my mouth about that, often saying things to Shawn like “Don’t you remember at the MVP Summit when…” And of course he’s like, “No, dumbass, I’m not an MVP, remember?”

But this year Shawn was recognized as an MVP, and he’s here at the Summit. A bunch of us met in the lobby, and Shawn asked “Where is the actual kick off?” I told him it was in the convention center, just like last year. But he didn’t remember. It’s ok. He’s still my hero.

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

(Copy from TV epsisode 2)

While you Brian are in MS MVP meeting could you ask about VDI (VECD) licensing? I ask about year ago how to license Virtual Vista when you use WinCE terminal at work, WinXP at your laptop and Apple Mac at home (1 user). And i am still waiting; i have read VECD licensing whitepaper many times but there is no answer to this question. I think MS should change their desktop operating system licensing from per client to per user (like in Terminal Server).

Also licensing is not clear if we use client hypervisors, how many licenses you need if you run XP, Vista and W7 in same computer.



I can answer the second question...  For the client side Hypervisor, you need and OS Cal for each OS instance you run on the client.



I'm trying to verify the below Q/A from the Microsoft Windows 2008 Licensing Guide

Q: If I move an instance of Windows 2003 to run as a virtual instance on a server with Windows Server 2008 Enterprise running in the physical operating system environment. Can I use Windows Server 2003 CALs to access the virtual instance of Windows Server 2003?

A: No. Because the virtual instance of Windows Server 2003 runs on a Windows Server 2008 license, the user or device accessing the virtual instance of Windows Server 2003 needs a  Windows Server 2008 CAL.

Does this mean I would need to upgrade all my Windows Server 2003 CAL's for any Windows Server 2003 instance that I virtualize on Windows Server 2008 running Hyper-V?  Also, would this include TS CAL's for Citrix XenApp servers on Windows Server 2003 that might be virtualized on Windows Server 2008 Hyper-V?

I suspect this is the most overlooked licesning quirk by end-users and VAR's.  Many VAR's I spoke with weren't even aware of this in Windows/Hyper-V licensing.


Well if you're limited to just terminal services and bout aggregating multiple TS servers into one sharepoint site - cleanly. (ala WebInterface) or just about any other third party vendor?


Ask them about their Virtualization Strategy, also regarding their role and partnership with Citrix !

...if they have a good answer, i would be very surprised.


Ask them "Why won't you support and work with VMWare"?