1. Virtualization Scenarios for Business Critical Applications
Tech Ed North America 2010
11/27/2018 7:13 PM
Required Slide
SESSION CODE:
VIR314
Virtualization Scenarios for Business Critical Applications
Allen Stewart
Principal Group Program Manager
Server and Cloud Division
Microsoft Corporation
© 2010 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.

2. Agenda Why Microsoft Virtualization for Microsoft Server Applications?
SQL Server Virtualization Scenarios
Consolidation, BI and HA Scenarios
Scalability Tests, Best Practices, Sizing Guidelines
SharePoint Virtualization Best Practices
Exchange Virtualization Best Practices
Links to Reference Material

3. Microsoft Virtualization: The Best Choice for Microsoft Server Applications
Microsoft Server Applications Built for Windows
Complete
Management Solution
Low Cost
Complete Solution
*A comparable solution can cost up to six times more†
*Built-in Virtualization with One-stop Support
*Deep Application Knowledge
*Large Partner Ecosystem
*Physical & Virtual Management
*Lower Ongoing Costs
Increased
Deployment Options
*Cross Platform and Hypervisor Support
Virtualization-friendly
Licensing
*Only available with Microsoft Virtualization
†Based on a comparison of Microsoft® System Center Server Management Suite Datacenter with VMware® vSphere Enterprise Plus with VMware vCenter Server.. Assumes a five host configuration, 2 processors on each host, 2 years support costs for both products, and no operating system costs included.. The Microsoft solution can use either the free Microsoft Hyper-V Server 2008 R2 hypervisor or an existing Windows Server 2008 R2 hypervisor.  Based on Microsoft estimated retail prices and published VMware prices available at as of 08/04/2009 for purchases in the United States. Actual reseller prices may vary.

4. Why Hyper-V for Business Critical Workloads
Better Flexibility
Live Migration. Moves running VMs between compatible physical hosts for performance, hardware maintenance, operating system maintenance, and power optimization without any disruption or perceived loss of service using a memory-to-memory operation using processors from the same manufacturer and family.
Hot add and removal of storage. Supports the addition or removal of VHDs or pass-through disks connected to the VMs virtual SCSI controllers while a VM is running.
Processor compatibility mode for Live Migration. Enables Live Migration across different CPU versions within the same manufacturer and processor family.

5. Why Hyper-V for Business Critical Workloads
Greater Scalability
Scalability to 64 logical processors. Hyper-V scales up to 64 logical processors on the physical system and up to four virtual processors for each VM.
Server core parking. Places processor cores into a park/sleep mode when not in use. This enables the processor to consume less power without affecting system performance.
Increased Performance
Second Level Address Translation (SLAT). The Hyper-V SLAT feature takes advantage of this advanced processor technology to further improve VM performance and to reduce the non productive processing overhead on the hypervisor.
Virtual Machine Queue (VMQ) support. Enables physical computer network interface cards (NICs) to use direct memory access (DMA) for VM memory, increasing I/O performance.

6. Dynamic Memory Hot add and remove of memory
As a virtual machine needs memory – its needs are evaluated against the needs of other virtual machines in the system, and it is given memory accordingly.
DM does not overcommit resource
DM treats memory like how we treat processor
Dynamically schedulable resource

7. How does DM work Adding Memory Removing Memory
Memory added to virtual machine in enlightened fashion
No hardware emulation
Integration with MM in the guest OS
Light Weight
Removing Memory
Ballooning

8. Dynamic Memory UI Memory Settings Memory columns
Memory Available value can be negative,
indicating VM is under memory pressure
and guest OS is paging

9. Virtualization Deployment Scenarios for
Microsoft SQL Server

10. The benefits of using Hyper-V with SQL Server include:
Close to native performance with minimal additional overhead.
Simplified SQL Server database workload consolidation for Online Transaction Processing (OLTP) workloads and Analysis Services workloads.
Deployment flexibility using core technologies such as Live Migration, virtual disk hot add and removal, in addition to flexible network configuration and optimization.
SysPrep support. Enables the creation of standardized Windows deployment images with SQL Server preinstalled.

11. SQL Server Consolidation
Currently a variety of consolidation strategies exist and are utilized.
Typically, as isolation goes up, density goes down and operation cost goes up.
Higher Isolation, Higher Costs
Higher Density, Lower Costs
IT Managed
Environment
Virtual
Machines
Instances
Databases
Schemas
MyServer
Sales_1
Marketing_1
Online_Sales
ERP_10
DB_1
DB_3
DB_2
Consolidate_1
Microsoft Confidential

12. Consolidation Considerations
Multiple SQL Instances
Multiple Virtual Machines (VM)
Isolation
Shared Windows instance
Dedicated Windows instance
CPU Resources
Number of CPUs visible to Windows instance
Up to 4 virtual CPUs
CPU over-commit is supported
Memory
Server Limit
Dynamic(max server memory)
Statically allocated to VM (Offline changes only)
64GB limit per VM
2 TB Limit per Host
Storage
SQL Data Files with standard storage options
SQL Data Files using
Passthrough or Virtual Hard Disks exposed to VM
Resource Management
Windows System Resource Manager(process level)
SQL Server Resource Governor
Hyper-V guest VM
Number of instances 50
Practical number of VMs supported is limited by the hardware resources only.
Note that there is a 384 VM limit and a 50 VM limit for clustering.
High Availability
Clustering, Database Mirroring, Log Shipping, Replication
Live Migration, Guest Clustering, Database Mirroring, Log Shipping, Replication
Performance
Good
Comparable with multiple instances, acceptable overhead
Support
SQL Server 2005 to SQL Server 2008 Enterprise Edition

13. Virtual Memory & Second-Level Translation
With Virtualization an additional level of mapping is required
SLAT improves VM performance by reducing the hypervisor overhead from upwards of 10 percent down to 2 percent, and by reducing memory overhead. This improves the scalability significantly because it enables more VMs to run concurrently on a single host server.
The Virtual / Process view
The Physical / real view
Virtual Machine 1
Physical Memory Pages
Virtual Machine 3
Virtual Machine 1
Hyper Visor
Operating System

14. SQL Server Consolidation Scalability
Results:
Increased throughput with consolidation
Near linear scale in throughput with no CPU over-commit
Improved performance with Windows Server 2008 R2 and SLAT processor architecture
Configuration:
OS: Microsoft® Windows Server® 2008 R2 Hyper-V™
Hardware:
HP DL585 (16 core) with SLAT
HP EVA 8000 storage
Virtual Machines: 4 virtual processors and 7 GB RAM per virtual machine; Fixed size VHD )
Throughput
(Batch requests/sec)
% CPU
Almost Linear Scale
No CPU over-commit
CPU over-commit
Heavy
Load
Moderate
Load
Low
Load
Relative Throughput for Windows Server 2008

15. Virtualization for SQL Server Business Intelligence
Scenario Description:
Business Intelligence (BI) components with lower resource requirements such as Data Mart (DM), OLAP Cube, Reporting Servers are good candidates for scale out and ideal for virtualization
Operational Data Store (ODS), Data Warehouse (DW), SQL Server® Integration Services could be physical or virtual depending on scale up requirements
If virtual, put SSIS and Data Warehouse on the same Virtual Machine (VM)
Virtualization Benefits:
Increase agility by rapidly provisioning and scaling-out BI components on demand
Reduce the number of physical servers, save on power and space VM
External
ERP
Web
Legacy
Reporting
Server
Data Mart &
OLAP Cube 1
SQL Server® Integration Services (SSIS)
Data Warehouse (DW)
Operational
Data Store
Reporting
Server
Data Mart &
OLAP Cube 2
Click Here For More Information

16. Remote Site Consolidation with DB Mirroring
Scenario Description:
Help protect from data loss with SQL Server® Database Mirroring. Automatically, failover from primary to standby using witness.
Consolidate mirrored database servers on standby site with virtualization
Use mirrored databases with database snapshots for reporting
Ensure there is enough CPU capacity at the standby site to provide acceptable SLA upon failover VM
SQL Server Database Mirroring 1
Reporting Server
(DB Snapshot) 2
Virtualization Benefits:
Better server utilization on standby site due to consolidation
Cost effective disaster recovery solution without using costly specialized hardware
Management efficiency based on SQL Server and System Center management tools 3 2
SQL Server Database Mirroring
Click Here For More Information

17. SQL Server with Live Migration
Scenario Description:
Manage high availability with multipathing and live migration for planned downtime situations, such as hardware and software maintenance
Failover individual virtual machines (VMs) to other hosts within a cluster by using Cluster Shared Volume (in Windows Server® 2008 R2)
Use Microsoft ® System Center Virtual Machine Manager for migrations. System Center VMM can perform host compatibility checks before migrations and manage multiple Live Migrations with queues.
Nodes in cluster can be active-active
Ensure there is enough CPU capacity for the failover nodes in cluster VM
Live
Migration 1 1 2 2
Virtualization Benefits:
No loss of service during failover with live migration. Migration is completely transparent to the user
Improve availability with less complexity
Better server utilization due to consolidation
Easier set up and management through System Center VMM
Host cluster
Shared Storage
iSCSI, SAS, Fibre
Click Here For More Information

18. Performance & Resource Optimization

19. PRO Pack Technologies Virtual Machine Manager PRO Packs Partner
PRO Technology
Brocade
Monitor IO performance from the server to the data in the SAN
Dell
The “PRO-enabled” Dell Management Pack ensures that host machines operate under normal power and temperature thresholds. Other PRO alerts include memory, storage controller, and disk remediation.
Citrix
Workflows can be initiated to automatically start or provision VMs based on an entity’s health and automatically update NetScaler load balancing rules
Emulex
Monitor I/O rates across the HBA relative to maximum available bandwidth HP
Monitor the following attributes of their servers: hard drive, array controller, power, temperature, processor, memory, fans, and alert on degradation or critical errors providing the appropriate recommended resolution
Quest Software
For non-Windows Operating Systems and non-Microsoft application technologies, the solution enables intelligent virtual machine tuning
Secure Vantage
Extends the native capabilities of Security Management providing users the ability to mitigate risk and remediate policy violations across virtual environments
For complete list, visit

20. Hyper-V Configuration Guidelines
New SP1 behavior to better protect the parent partition from rampaging virtual machines
New registry key in place
Allows you to reserve static memory for the parent partition
May result in less memory being available for VMs
Hyper-V Root Configuration
Plan for 1GB+ memory reserve for the management OS in the root partition
Plan for one dedicated NIC for management purposes
Plan (ideally) for one dedicated NIC for live migration and CSV
Separate LUNs/Arrays for management OS, guest OS VHDs and VM storage
Management OS and VHD LUNs should employ RAID to provide data protection and performance
Challenge for blades with 2 physical disks
Hyper-V Guest Configuration
Fixed-sized VHDs for Virtual OS
Need to account for page file consumption in addition to OS requirements OS VHD Size (minimum 15GB) + VM Memory Size = Minimum VHD size
Account for space needed by additional files by VM
Example for SQL: OS VHD Size + (VM Memory Size) + Data Files + Log Files

21. I/O and disk latency for dedicated pass-through disks versus VHDs

22. SQL Server Best Practices
Guest virtual machines are limited to 4 CPU cores
Best performance if VMs are not over-committed for CPU
Maintain 8 virtual CPU to core ratio
Test Network intensive applications for acceptable SLAs
Use multi-pathing on host or within the VM to ensure maximum throughput and high availability for VM workloads
Utilize either pass-through disk or fixed-size VHD for guest virtual machines
Avoid using emulated devices. Instead, ensure integration components are installed and synthetic devices are being used.

23. Microsoft Office SharePoint Server
Virtualization Deployment Scenarios for
Microsoft Office SharePoint Server

24. What is a SharePoint Farm?
A collection of one or more SharePoint Servers and SQL Servers® providing a set of basic SharePoint services bound together by a single configuration database in SQL Server
Key Components:
Web Front End (WFE) Servers:
Windows® SharePoint Services
Web Application Service
Application Servers:
Office SharePoint Server Search Service (Index or Query)
Document Conversion Launcher Service
Document Conversion Load Balancer Service
Excel Calculation Services
SQL Server

25. SharePoint Roles & Virtualization Considerations
Decision
Considerations and Requirements
Web Role
Render Content
Ideal
Easily provision additional servers for load balancing and fault tolerance
Query Role
Process Search Queries
For large indexes, use physical volume over dynamic expanding VHD
Requires propagated copy of local index
Application Role
Excel Forms Services
Provision more servers as resource requirements for individual applications increase
Index Role
Crawl Index
Consider
Environments where significant amount of content is not crawled
Requires enough drive space to store the index corpus
Database Role
Environments with lower resource usage requirements
Implement SQL Server® alias for the farm required

26. Production Farm – Physical & Virtual Mix
Scenario Description:
Optimized scenario for high-end production is mixed physical and virtual
Index and database roles on dedicated physical servers to provide very high scalability
Virtual web, query, and application roles
All servers managed by System Center Suite VM
DEV
TEST
Virtualization Benefits:
Unified management: physical and virtual
Dynamic data center: scale dynamically and on- demand provisioning
Failover Server
Shared Storage
iSCSI, SAS, Fibre
PRODUCTION
Index
Click Here for More Information

27. Partner Evidence: SharePoint Virtualization
DESCRIPTION
Deployment with mix of physical & virtual servers
Web, Query and Application roles are deployed virtual; database role is deployed physical
Maintains resource optimization with PRO
RESULTS
Average response time of under 3-5 seconds with 1% concurrency with a heavy user load profile of over 300K user capacity
VIRTUAL MACHINE SPECIFICATIONS
1 Index server dedicated for crawling: 4 CPUs, 6 GB RAM per VM
10 Web Front End & Query servers: 4 CPUs, 4 GB RAM per VM
2 Application servers: 2 CPUs, 2 GB RAM per VM
2 Domain controllers: 2 CPUs, 2 GB RAM per VM
Click here for more information
Source: EMC Virtual Architecture for Microsoft Office SharePoint Server 2007 Enabled by Hyper-V (whitepaper)

28. SharePoint Virtualization Best Practices
Best Practices and Recommendations
CPU
Configure a 1-to-1 mapping of virtual processor to logical processors for best performance
Be aware of “CPU bound” issues
Memory
Ensure enough memory is allocated to each virtual machine
Disk
Be aware of underlying disk read write contention between different virtual machines to their virtual hard disks
Ensure SAN is configured correctly
Network
Use VLAN tagging for security
Associate SharePoint® virtual machines to the same virtual switch
Others
Ensure that integration components are installed on the virtual machine
Do not use other host roles (use server core)
Avoid single point of failure: load balance your virtual machines across hosts and cluster virtual machines

29. Microsoft Exchange Server
Virtualization Deployment Scenarios for
Microsoft Exchange Server

30. Deployment Recommendations
Exchange application is not ‘virtualization aware’
Core Exchange Design Principles Still Apply
Design for Performance, Reliability and Capacity
Design for Usage Profiles (CAS/MBX)
Design for Message Profiles (Hub/Edge)
Virtualization Design Principles Now Apply
Virtual machines should be sized specific to the Exchange role (EDGE, HUB, CAS, MBX, multi-role)
Hosts should be sized to accommodate the guests that they will support

31. Exchange 2010 Sizing Guidance
Role
Physical Deployment
Virtual Deployment
Notes
Maximum Processor Cores
Memory Sizing
Processor Core : MBX Ratio
Maximum Virtual Processors
Standard VM
Standard VM Ratio
Edge/
Hub
12 processor cores
1 GB per processor core
1:5 with Anti-Virus
1:7 with no AV
4 virtual processors
4 VPs + 4GB
1 HUB VM : 5 MBX VMs
To accommodate peak I/O (e.g. processing queue) locate Transport DB + Logs on separate spindles
CAS
2GB per processor core
3:4
2 GB per processor core
4 VPs + 8GB
3 CAS VMs : 4 MBX VMs
Detailed guidance to be available by early Dec
CAS/ Hub Multi-Role
1:1
1 CAS/HUB VM : 1 MBX VM
Simplifies core ratio. Better balanced workloads on typical servers which have 8, 16 or 24 core counts.
MBX
4GB MB per MBX
N/A
4 VPs GB
Adjust for number of mailboxes and database cache for send/receive profile
8 cores
16 cores
24 cores
CAS / HUB Multi-Role Server

32. Mailbox Server Guidelines
Database Cache requirements are the same for physical and virtual deployments
Virtual Processor ≠ Logical Processor
Hypervisor and the Virtualization Stack consume CPU
Reduce recommended MBX count by ~10%
Total Send + Receive
(75k message size)
Database Cache
Per Mailbox (MB) 50 3
100 6
150 9
200 12
250 15
300 18
350 21
400 24
450 27
500 30
Total Send + Receive
(75k message size)
Users Per Core
Physical MBX Role
Users Per VP
Virtual MBX Role 50
1000
900
100
810
150
800
720
200
700
630
250
600
540
300
500
450
350
400
360
270

33. Mailbox Storage Configuration
Virtual SCSI (passthrough or fixed disk)
Recommended configuration for database and log volumes
iSCSI
Standard best practice for iSCSI connected storage apply (dedicated NIC, jumbo frames, offload, etc.)
iSCSI initiator in the guest is supported but need to account for reduced performance

34. Exchange 2010 High Availability
Database Availability Group (DAG)
A group of up to 16 Exchange Server 2010 Mailbox servers that provide automatic database-level recovery
Uses continuous log replication and a subset of Windows Failover Clustering technologies
Can extend across multiple datacenters/AD sites
Benefits of Exchange Native Data Protection
Protection from database, server or network failure
Automatic failover protection and manual switchover control is provided at the mailbox database level instead of at the server level.
Support for up to 16 copies, support for lag copies

35. Host Based Failover Clustering
Host Based Failover Clustering HA
Using Host Based Failover Clustering and automatically failing VMs to an alternate cluster node in the event of a critical hardware issue (virtualization platform independent)
What you need to be aware of:
Not an Exchange Aware Solution
Only protects against server hardware/network failure
No HA in the event of storage failure / data corruption
Trend is larger mailboxes = larger database sizes = longer time to recover from data loss = DAG
Not supported for MBX VMs that are members of a DAG

36. Live Migration and Exchange 2010
Physical Computer Maintenance
Operating System/Application Updates
Hardware Maintenance
Rebalancing Workloads
Dynamic Redistribution of VM’s to optimize workload on physical hardware
Green IT
‘Off Peak’ Virtual Machine Consolidation

37. Supportability Quick Reference Exchange 2010
Supported
Root: Hyper-V or any virtualization platform in SVVP
Guest:
Exchange 2010
Windows 2008 SP2 or R2
Mailbox, Client Access, Hub Transport, Edge roles
Meets basic Exchange system requirements
Storage is fixed VHD, SCSI pass through, or iSCSI
Not Supported
Combination of Exchange Mailbox HA (i.e. Mailbox servers in a DAG) and any host/hypervisor-based clustering or migration technologies (e.g. Microsoft Live Migration, VMware V-Motion, etc.)
Snapshots, differencing/delta disks
Unified Messaging role
Virtual/logical processor ratio greater than 2:1
Applications running in root partition (excluding AV)

38. Partner Evidence: Exchange Virtualization
HP recommended configurations for Exchange 2010 virtualization using Hyper-V R2
Sizing for 20,000 users, 512 MB mailboxes
All roles virtualized and Live Migration for MBX servers
Hardware: HP ProLiant BL460c G6 (BL460c G6) server blade and HP StorageWorks 8400 Enterprise Virtual Array (EVA8400) storage systems
Sizing for 5,000 users, 256 MB mailboxes
Hardware: HP ProLiant BL460c G6 (BL460c G6) server blades and HP LeftHand P4500 (P4500) storage systems

39. Required Slide
Track PMs will supply the content for this slide, which will be inserted during the final scrub.
Tech Ed North America 2010
11/27/2018 7:13 PM
Track Resources
Microsoft:
Hyper-V on TechNet:
Virtualization Team Blog:
Virtual PC Guy:
© 2010 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.

40. Resources Learning Required Slide www.microsoft.com/teched
Tech Ed North America 2010
11/27/2018 7:13 PM
Required Slide
Resources
Learning
Sessions On-Demand & Community
Microsoft Certification & Training Resources
Resources for IT Professionals
Resources for Developers
© 2010 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.

41. Required Slide
Speakers, please list the Breakout Sessions, Interactive Sessions, Labs and Demo Stations that are related to your session.
Tech Ed North America 2010
11/27/2018 7:13 PM
Related Content
Breakout Sessions: VIR402- Virtualization FAQ, Tips, and Tricks
Interactive Sessions: VIR09-INT – Virtualization Round Table Discussion
Hands-on Labs: VIR04-HOL – Config and Managing Windows Server 2008 R2 Hyper-V
VIR07-HOL – Introduction to Windows Server 2008 R2 Hyper-V
Product Demo Stations: TLC-35 – Server Virtualization
© 2010 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.

42. Complete an evaluation on CommNet and enter to win!
Tech Ed North America 2010
11/27/2018 7:13 PM
Required Slide
Complete an evaluation on CommNet and enter to win!
© 2010 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.

43. Tech Ed North America 2010 11/27/2018 7:13 PM
© 2010 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.
© 2010 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.

44. Required Slide Tech Ed North America 2010 11/27/2018 7:13 PM
© 2010 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.