Ran Oelgiesser, Sr. Product Manager Praveen Vijayaraghavan, Program Manager (Virtual PC) Yigal Edery, Group Program Manager (MED-V)

Agenda The challenge of compatibility MED-V and Windows XP Mode Windows XP Mode Technology and how to setup Demo – key features MED-V Architecture and key capabilities Demo - configuring and deploying v1 System requirements Next steps and Q&A

The challenge of compatibility when upgrading to a new operating system TestTestMigrateMigrateUpgradeUpgrade

Resolving conflicts between applications, and reduces testing Good for: Creates a package of a single application Isolates from all other applications Application Virtualization Desktop vs. Application Virtualization Applications Operating System Hardware ® ® Resolving incompatibility between applications and a new OS Good for Creates a package with a full instance of Windows Desktop Virtualization

Using desktop virtualization for Application-OS Compatibility

TestTestMigrateMigrateUpgradeUpgrade

A preconfigured virtual Windows XP SP3 (32bit) environment Easy to install your applications on Windows XP and run from Windows 7 desktop Well integrated into Windows 7 Designed for small businesses and consumers Windows XP Mode Provides the Ease of Use for End Users Windows XP Mode and MED-V Deploy virtual Windows XP images and customize per user Provision and define applications and websites to users Control Virtual PC settings Maintain and Support endpoints through monitoring and troubleshooting MED-V – Application-OS compatibility for the Enterprise

Virtual PC 2007 Primary Audience: Developers / IT Typical guest OS: Multiple Guest OS Windows Virtual PC Scenario: Windows XP Compatibility for small businesses with no IT Cost: None. Virtual Windows XP is included with Windows 7 Pro Features: Seamless integration, USB device support Windows XP Mode Virtualization Technology

Windows XP Mode Requirements Windows 7 Professional, Ultimate & Enterprise Processors capable of hardware-assisted virtualization (e.g. AMD-V™, Intel® VT or VIA® VT enabled) 2 GB of RAM Recommended (~ Mb allocated for Windows XP Mode) Initial image size of ~2Gb 32 bit Guest OS Support

Windows XP Mode Setup Parent VHD (Windows XP Mode base.vhd) Parent VHD (Windows XP Mode base.vhd) User Disk Differencing Disk User Disk Differencing Disk User Disk Differencing Disk User Disk Differencing Disk User 1 User 2 Configuration File EULA Create Password WU Options Setup Full Desktop Configuration File Drive Sharing Download and install Windows Virtual PC and Windows XP Mode from

Windows XP Mode Setup Install antivirus solution in the guest, apply latest patches Enable Cleartype in the guest Remote Desktop User or Admin user

Key Features Windows 7 Shell integration Virtual Applications Folder Integration between host and guest Integration Features (Drive/Clipboard/Smartcard sharing) USB Redirection Scripting support ( us/library/dd796757(VS.85).aspx) us/library/dd796757(VS.85).aspx)

Windows XP Mode

MED-V is Part of the MDOP Subscription Translating software inventory into business intelligence Enhancing group policy through change management Dynamically streaming software as a centrally managed service Proactively managing application and operating system failures Powerful tools to accelerate desktop repair Simplifying deployment and management of Virtual PCs With Software Assurance, customers can run up to 4 virtual OS on each licensed device And what about the Windows XP license for the Virtual PC?

Centrally define Virtual PC settings (e.g. Adjust virtual PC memory allocation based on available RAM on host) Centrally monitor endpoint clients Provide helpdesk tools to diagnose and troubleshoot virtual PCs Control and Monitor MED-V v1 Key Capabilities Deploy IT-managed virtual XP environment to end users Enable customization in heterogeneous desktop environments  Automate first-time virtual PC setup (e.g. initial network setup, computer name, domain join) Application provisioning based on Microsoft Active-Directory® users/groups  Assign a virtual image and define which applications are available to the user Deploy and provision End users seamlessly use Windows XP applications on their Windows 7 desktop End users automatically see Websites that require Internet Explorer 6 in the virtual environment Enable incompatible applications

MED-V v1 Architecture

Typical Virtual Image life-cycle Create a master image Include common software, security and management tools Package the image and distribute Via existing software distribution (e.g. System Center) Image is customized and joined to domain Unique name is assigned for identification Remotely manage as any Windows XP desktop Install applications Apply patches and updates

MED-V v1 System Requirements Windows Server 2008 Standard/Enterprise (v1 SP1 will add support for Windows Server 2008 R2) Optional - IIS web server for image delivery Optional - SQL Server 2008 (any edition) or SQL Server 2005(SP2 Enterprise ) for reporting ServerServer Windows Vista SP1/2 – 32-bit (2GB RAM Recommended) Windows XP SP2/3 - 32bit (1GB RAM Recommended) Support for Windows 7 (32bit + 64bit) will be added in Q1 CY2010 via MED-V 1.0 SP1 ClientClient Virtual machine English UI, with support for localized OS: French, German, Italian, Dutch, Spanish, Portuguese (Brazil) LanguagesLanguages

Windows Client Workstation MED-V Admin Console ExportExport MED-V Admin Console Package Wizard Policy Windows Virtual PC ConfigMgr Client MED-V Client V2 - Integrated with System Center Virtual Image (optional) System Center Configuration Manager Deploy Packages

Next Steps Learn more at Virtual PC Website: Hardware-Assisted Virtualization Detection Tool Windows XP Mode Deployment guide Windows XP Mode IT Pro video, FAQs and more Learn more at Virtual PC Website: Hardware-Assisted Virtualization Detection Tool Windows XP Mode Deployment guide Windows XP Mode IT Pro video, FAQs and more

Complete an evaluation on CommNet and enter to win an Xbox 360 Elite!

© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.