Microsoft Systems Architecture

1. Microsoft Systems Architecture Technical Overview Presented by: Šarūnas Končius, Microsoft

2. Overview • The Problem Space • MSA Approach • The Guidance and Using It • MSA v2.0 Architectural Overview • Review

3. Enterprise Problems • IT not aligned with enterprise business objectives • Can’t make quick and high confidence decisions due to a lack of enterprise information • Ad-hoc and informal growth of applications and servers leading to a proliferation of custom solutions

4. Technology Problems Piecemeal growth, proliferation of services and complex service provision….. …unmanageable, slow and expensive to adapt

5. MSA Defined • Technology Architecture for the enterprise “MSA is enterprise-class architectural blueprints and implementation guidance that are tested and proven in the lab with hardware partners”

6. Extranet Corporate Enterprise Internet Branch Office Department Storage Servers Networking Software MSA Approach Together with our partners we build and test data center configurations in our labs and optimize them for Windows We document these configurations both as entire data centers and as modules, supporting specific computing functions MSA incorporates all technologies required to build corporate data centers

7. MSA Design Goals

8. Employees Partners Customers Microsoft Systems Architecture v1.5 • Internet Data Center (IDC) • Enterprise Data Center (EDC)

9. MSA v1.5 Deliverables • Reference: blue prints and documentation • Corporate and Internet Scenarios • Architectural design guides • Prescriptive: documentation (Microsoft & partners) • Proof-of-concept configurations for each scenario • Deployment guides, tools and scripts • More prescriptive configurations through partnerships • Platform for Microsoft Solution Offerings • Lab instantiations for each configuration • Test tools for solution validation and deployment • Infrastructure for other Microsoft Solutions • Qualification program for partner-led prescriptive architectures

10. MSA v1.5 IDC Reference Architecture

11. MSA v1.5 IDC Prescriptive Architecture

12. Partner-led Prescriptive Solutions • Internet Data Center • Dell, EMC2, Brocade, Nortel, Avanade (released June’02) • Unisys, EMC2, Brocade, Nortel, Avanade (released June’02) • NEC Japan (Dec’02 for Japan/Far East market) • Enterprise Data Center • Dell, EMC2, Brocade, CommVault and Nortel • Unisys, EMC2, Brocade and Nortel • Fujitsu/Siemens (for EMEA market)

13. Business Architecture Functional Requirements Operational Requirements Conceptual Conceptual Application Architecture Technology Architecture Logical Logical Implementation Implementation Application Development Instantiation of IT Infrastructure Deployment of Packages patterns & practices patterns & practices Network of Devices MSA v2.0 Architectural Approach

14. Employees Partners Customers The MSA Logical Enterprise • Logical Separation • Focus on the needs of employees, partners and customers • At the core is the role of the IT Professional

15. Enterprise Scenarios • Corporate Services • Provision of core services to the enterprise • Departmental Services • Logical separation (HR, Legal), LOB Apps. • Branch Office Services • Satellite Office fully leveraging corporate services • Branch office with local services (e.g. File/Print) • Extranet Services • B2B. Exchange, share and collaborate • Internet Services • B2C. Large volume Internet based business

16. The Guidance • Scenario focus in terms of unique requirements • Service focus for more intuitive consumption • Consume as you need

17. MSF IT Life Cycle MSA Envisioning Reference Architecture Kit Plan Planning Program Documents Developing Service Blueprints Stabilizing Build Architecture Blueprints Deploying Implementation Kit MOF Deploy Changing Planning Guide Operating Build Guide Operate Supporting Operations Guide Optimizing MSA v2.0 Deliverables

18. Product Groups Partners Customers MSA Market Research Internal IT Reference Architecture Kit Program Documents Business Service Blueprints Technology Architecture Blueprints User Enterprise Model Implementation Kit Planning Guide Build Guide Operations Guide Creating the Deliverables

19. Using MSA • Customizable Baseline • MSA is a jumpstart to help meet unique customer requirements • Customization is expected and should be done as part of a Systems Integration engagement E.g. • Scaling the tiers : # Web servers # Database servers • Firewall rules based on services and protocols • Integration into existing environments • Standardization • Blueprint for change • Contribution to Standard Operating Environment • SOE, COE etc. – A “contract” between business and infrastructure

20. MSA Guidance Customer Implementation Program Documents High-Level Goals Architecture Blueprints Service Blueprints Planning Guide Build Guide Operations Guide Using the Deliverables Business Customer Requirements Technology User Envisioning Planning Plans & Initial Design Final Design & Test Lab Developing Stabilizing Tested Solution Deploying In Production Operating Ongoing Operations

21. Security Zones

22. Network Zones

23. Storage

24. Core Services

25. Network Services

26. Application Services

27. Management Services

28. Client Access

29. Public Services

30. Review • Targeting the Enterprise with scenarios and services for Technology Architecture • Reference Architecture with design choices • Implementation Guidance based on a specific instantiation • A basis for standardization, consolidation and migration • Jumpstart for infrastructure implementation projects • It’s free, public material that can help

31. Call to action • Check MSA web: www.microsoft.com/solutions/msa/ • Be familiar with ideas and documents • Evaluate, compare with your plans • Get Ready for Microsoft Systems Architecture 2.0 • www.microsoft.com/solutions/msa/evaluation/GetReady.asp • Evaluate the guidance • Provide feedback and suggestions • Find more details on TechNet web site: www.microsoft.com/technet/itsolutions/msa/

32. © 2003 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.