1.  Ram Cherala Principal Program Manager Microsoft Corporation TL37

2. Dev ChallengesHow Lab Management addresses them – Demo!!Build workflowArchitectureLab Management in a nut shellQ & A

3. TesterDeveloper

4. Bug “ping-pong”Expensive context switches“Double-hop” issuesSlow turnaround – How can we be Agile? Please use this format when talking about FUTURE products, services or features.

9. Action and video log System information Event logs, historic debugging and lab environment Rich bug Group of Virtual Machines with an identity which can be rapidly provisioned Can be copied, check pointed, shared Lab Environment Developer has access to tester’s environment Direct access to test machines makes debugging easy!! Network fencing enables you to run a copy of the environment Dev Access to Environment

10. Compile Code Deploy Application Run Tests

11. Compile Code Restore Environ- ment Deploy Application Take Checkpoint Run Tests

12. Team Foundation Server (TFS) Lab ManagementTest Case managementBuild managementWork Item TrackingSource Control System Center Management Stack Operations Manager Virtual Machine Manager Virtualization Platform Hyper-VESX

13. Along with historic debugging support, makes “No-Repro” bugs a thing of the past!! Easily revert to a baseline configuration Improves Productivity Self-service library of machines Reduces significant setup time Scheduled build/test cycle on steroids Improves Efficiency Share your environment with others Network fencing comes to the rescue!! Enables Parallelism Please use this format when talking about FUTURE products, services or features.

14. Get familiar with virtualization – any virtualization!! Try Visual Studio Team System hands on labsTell your test buddies about Lab Management Please use this format when talking about FUTURE products, services or features.

15. HOL CodeTitle TLHOL07VSTS 2010: Project Planning, Management, and Design TLHOL08VSTS 2010: Architecture Tools TLHOL09VSTS 2010: Team Foundation Server TLHOL10VSTS 2010: Software Quality TLHOL11VSTS 2010: Diagnostics and Performance

16. Please submit session evaluation form at http://microsoftpdc.com Feedback/questions, email to vslmpdc@microsoft.com

17. Please fill out your evaluation for this session at: This session will be available as a recording at: www.microsoftpdc.com

19. © 2008 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.

21. IISDB 10.10.1.510.10.1.6 172.22.48.15 172.22.48.16 Copy 1 IISDB 10.10.1.510.10.1.6 172.22.48.17 172.22.48.18 Copy 2 Fence network (Internal) Lab network (External) What Create multiple copies of environment They can run in parallel without conflicts No application reconfiguration How Internal fence network is created for all VMs A VM gets the same MAC & IP address, and computer name in all copies VMs are also connected to the external lab network