WSV 308 Standards Support and Interoperability in Windows

WSV 308 Standards Support and Interoperability in Windows Server 2012: Networking, Management, and Storage Jeffrey Snover Distinguished Engineer and Lead Architect for Windows Server Microsoft Corporation

server its

lots of servers connecting physical virtual on-premise off

Storage Standards and Interoperability in Networking See-Mong Tan Principal Program Mangaer Windows Networking

End-to-end Deperimeterization • Security and performance optimizations are best done end-toend • My network is wherever my users and assets happen to be Policy-based connectivity Vendor flexibility Power Friendly • Configure network connectivity through policy • Give users choice in industry standard equipment • New Silicon Architectures • Always On, Always Connected • Use hardware offloads Standards-based Interoperability Web-friendly Developer simplicity Microsoft Confidential 8

From IPv 4 to IPv 6

Hyper-V Extensible Switch Frame distribution/aggregation Failure detection Control protocol implementation Switch independent team LBFO NIC 1 NIC 2 NIC 3 Network switch Switch dependent team

Windows Server 8 Qo. S Power. Shell WMI Winsock Traffic Classification Windows Network Stack File I/O API Windows Storage Stack Up to 8 classes DCB k. RDMA LAN Miniport

Management Standards and Interoperability in Management Wojtek Kozaczynski Principal Architect Windows Server Management

Power. Shell to manage Windows and non-Windows . . . IT Pros OData to manage Windows Developers of managed services and devices Greatley simplified managment interface definition and implementation

Power. Shell MI Client API. Net MI API non-Windows MI MI Provider v 1 Classical v 1 Provider MI Provider Native MI API WMI OMI any device WS-Man Protocol Handler WS-Man

Open. Pegasus OMI Factor Requests per sec. (binary protocol) 260 20, 000 76 x Image object size 8, 000 KB 150 KB 53 x Trivial provider size 30 KB 3 KB 10 x Virtual memory size 54 MB 1. 5 MB 36 x Resident set size 8, 500 KB 17 x

. . MI Client API. Net MI API CIM Client APIs v 1 Provider v 1 Classic v 1 Provider WMI Engine Native MI API Client WS-Man Protocol Handler . v 2 Provider MI Provider . . . Power. Shell Server (D)COM Protocol Handler Client (D)COM Protocol Handler Local + Remote Server WS-Man Protocol Handler

Power. Shell CIM-Based Cmdlets CIM Cmdlets MI Client API. Net MI API CIM Client APIs Native MI API WS-Man Protocol Handler

non-Windows REST Clients Management OData Service Dispatching Layer Power. Shell CIMModule CIM Module MI Client WMI or OMI CIM Client WS-Man Protocol Handler Service Module

Management Interoperability Hardware Windows Linux

Windows Server 2012 Win 8 VM 3 Linux VM Brodcom BMC 2 1 Power. Shell Intel BMC 1 Windows managing non-Windows via WS-Man 2 Windows managing Linux running OMI 3 non-Windows managing Windows via OData

Storage Standards and Interoperability in Storage Gene Chellis Director of Program Management Windows Server Storage & Availability

De Jure and De Facto Standards

Network File System remote file protocol

Network connected remote block storage protocol i. SCSI Initiator(s) 1 Failover of i. SCSI Target connections to Node B Clustered i. SCSI Target Node A 2 3 Node B

Server Message Block remote file protocol

SNIA Storage Management Initiative Specification SMI-S Example

video demo Heterogeneous Storage Management with SMI-S Demo

#TE(sessioncode) Talk to our Experts at the TLC DOWNLOAD Windows Server 2012 Release Candidate Hands-On Labs microsoft. com/windowsserver DOWNLOAD Windows Azure Windowsazure. com/ teched

Learning Connect. Share. Discuss. Microsoft Certification & Training Resources http: //northamerica. msteched. com www. microsoft. com/learning Tech. Net Resources for IT Professionals Resources for Developers http: //microsoft. com/technet http: //microsoft. com/msdn

Complete an evaluation on Comm. Net and enter to win!

Scan the Tag to evaluate this session now on my. Tech. Ed Mobile