Today’s post comes to us from David Trupkin, Sr Product Manager for App-V and MED-V
One of the ways I can tell it’s going to be a good day at work is when I look at my calendar in the morning and see that I’ve got some sort of IT Pro related activity on my schedule. As the product manager for Microsoft Application Virtualization (App-V) and Microsoft Enterprise Desktop Virtualization (MED-V), I find your feedback particularly valuable. Considering my own background as an IT Pro, I enjoy helping you solve business problems.
A recurring message I hear from the community is that you want choice. If you’re responsible for desktop or application deployment in your organization, it’s likely that you have some sort of infrastructure in place dedicated to this task. It may be Microsoft infrastructure such as the Microsoft Deployment Toolkit (MDT) 2010 or System Center Configuration Manager 2007, or it may be a third party tool. Many of you have told me you want to use these systems to deploy and manage App-V and MED-V, but didn’t think it was possible. I’ve even seen third party information that implies that you absolutely must use a dedicated App-V Management Server before you can use App-V in your environment. The truth is that App-V and MED-V work with your existing management systems – no dedicated infrastructure required!
Today we’ve posted a new video series for App-V and MED-V that will help you get started. The first videos are about App-V. If you’re using MDT 2010, have a look at Deploying App-V with the Microsoft Deployment Toolkit. If you’re using System Center Configuration Manager, you’ll want to review Deploying App-V with System Center Configuration Manager. If you want deeper, hands-on experience with App-V and System Center Configuration Manager, you can review the TechNet Hands-on Lab.
Of course, if you’d like to use the App-V Management Server, we have you covered. This new video will step you through the process of Setting up the App-V Management Server on Windows Server 2008 R2.
The next set of videos covers MED-V. MED-V 2.0 eschews dedicated server infrastructure, allowing you to manage its application compatibility workspaces just as you would any other Windows endpoint in your environment. You can Deploy MED-V Workspace Packages with the Microsoft Deployment Toolkit, or Deploy MED-V Workspace Packages with System Center Configuration Manager. For deeper technical information on deploying MED-V 2.0 the new whitepaper, Deployment Guidance for Microsoft Enterprise Desktop Virtualization 2.0 (I know, who thinks up the titles for these things?), is just what you’re looking for.
Thank you for all of your valuable feedback, and please keep it coming! I look forward to meeting you at events in the coming year. Please visit the Desktop Virtualization zone on Springboard, and the App-V TechCenter for more information on App-V and MED-V.