1 / 29

What Is An ASP

Architecting a Multi-host Environment With Exchange 2000 Andres Sanabria Network Specialist Microsoft Corporation. What Is An ASP. Defining Characteristics: Applications-centric Deploy, host, manage and rent Applications license ownership One-to-many Delivers on contract Centrally managed.

scott
Download Presentation

What Is An ASP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Architecting a Multi-host Environment With Exchange 2000Andres SanabriaNetwork SpecialistMicrosoft Corporation

  2. What Is An ASP • Defining Characteristics: • Applications-centric • Deploy, host, manage and rent • Applications license ownership • One-to-many • Delivers on contract • Centrally managed

  3. Topics • Hosting scenarios and models • Active Directory™ design • Messaging configuration • Scalability and reliability • Clients • Management

  4. Hosting Scenarios And Models • Centralized (shared server hosting) • All software components, hardware live at ASP data center • ISP-like configuration • Vast scale services (messaging, conf, wireless) • De-centralized • Co-located and/or off-site CPE • Remotely managed by MSP • Tied into ASP directory in some cases • Fully distributed (dedicated server hosting) • Complete data/config isolation • Management, monitoring and recovering • Highest SLA, costs

  5. Active Directory Design • Customer Requirements • Single point of management for any resource (applications, users, email,..etc) • Totally secure and isolated environment • Share the same infrastructure for multiple companies • Delegate Configuration to ASP personnel • Delegate user mgmt to customer • Automate most of my work • Scripts, schedule task, application • Increase the availability

  6. Active Directory Design Name Space Partition • Organization Unit - OU Model • Each OU will host a Company • Administrative containers • Unit of delegate administration • User Principal Name- UPN Model • (Same as pre-Windows 2000) = OU name //Usability • Set security ACL in groups created in the OU • AllUsers@customer1 , AdminOu@customer1 • Remove Authenticate Users • Single forest • Keep it simple, “Less Is Better” • Security – top design priority

  7. Active Directory Design

  8. Unified Messaging Instant Messaging Other ISV Apps Other TS Apps Conferencing Office Online Messaging Wireless Managed PC WTS Exchange 2000 Active Directory Design Active Directory – Shared Hosting Architecture Benefits of a single platform (Windows 2000) and integration of products

  9. Active Directory Design • Configure the AD to be GC to improve performance • At least one GC per geographical location • Replicated to two servers for Redundancy • Build in a “Round Robin” type of solution • Easy to integrated via ADSI, or LDAP call

  10. Messaging Configuration • Recipient Policies • Automatically create SMTP address base on rules • Users/LogonName ends with <OU Name> = @<SMTP Address> • Groups/DisplayName end with <OU Name> = @<SMTP Address> • Multiple SMTP Address per user

  11. Messaging Configuration • Global address List and Offline Address list • Support Multiple GAL and ADL • Have a common place for all the user to look up other users • Users/e-mail ends with <OU Name> • Security • AllUsers@customer1 , • Allow = read, execute, read permissions, list content, read properties, open address list • AdminOu@customer1 • Full administrative privilege • For MAPI users

  12. Messaging Configuration • Outlook Web Access • Limiting MAPI/RPC lookup via AD • msExchQueryBaseDN • Using ADSIEdit.exe • ou=<ou name>, dc=<domain_name>, dc=<root_domain> • Ex • ou=Customer1, dc=myAsp, dc= com • Per user • Scriptable via ADSI

  13. Messaging Configuration • External DNS • Primary zones per customer • IN A pointing to the Virtual IP address • WWW for the OWA • MX for the SMTP address • Integrated to the AD • For redundancy and replication • EX. • Customer1.com @ MX 10 mail.Customer1.com. MAIL A 208.217.184.2 ;SMTP www A 208.217.184.3 ;OWA • AD and FE server will resolve the mailbox location and alias for the user

  14. Scalability And Reliability • Exchange 5.5 • Designed for enterprises and SMORGs • Thousand users • MCIS • Designed for hosted configurations • Million Users • High-performance POP/IMAP/NNTP services • Chat Server • Provisioning built-in • Scales to the masses

  15. Scalability And Reliability • Scalability and reliability through partitioning and redundancy • Partition separate servers for: • Protocols • Storage • Directory • Add redundancy with: • Clustering • Load Balancing

  16. Scalability And Reliability • Scaling Vertical • Scaling Horizontal

  17. Scalability And Reliability • Network Load Balancing • TCP/IP Load Balancing • 32 nodes could be view as a single server • Great for front-end servers • Used by TCP/UDP Protocols, app. • HTTP, IMAP, POP3, smtp • dynamically adjusts, distributing requests

  18. Scalability And ReliabilityFE/BE Configurations • Front-end servers are important for hosting configurations • Provides unified namespace across the farm • Offloads SSL processing from back-ends • Provides an additional security layer • Allows for seamless server consolidation • Allows seamless distribution of user data across multiple servers without having to re-authenticate • IMAP/POP/HTTP/WebDAV

  19. Scalability And Reliability • Cluster Server • Application . state full, back-end servers • Fail Over in the case that the application fail • Fail Back when the server is back on line • Active || Passive application • Exchange is a Cluster aware application • Resource.dll: Exchange wrote its own // EXCHRES.DLL • A resource group is an atomic unit of fail over/fail back • Exchange Virtual Server • Let the back end do the heavy lifting • Processing • Accessing storage • Security

  20. EVS1 X EVS1 Failover/User Experience EVS2 HTTP,POP, IMAP,MAPI

  21. Scalability And Reliability Partition separate servers Router /DNS service resolver Protocol Protocol Protocol Protocol Protocol Windows 2000 Directory Store Store Store Store Cluster A Cluster B

  22. Scalability And ReliabilityStorage Machine A Machine B Shared Storage Local Attach Storage Supported

  23. 4 Server Cluster 3 Servers Running Nodes = 15 storages 60 storage 2 Servers Running Nodes = 10 storages 40 storages 1 Server Running Nodes = 5 Storage 20 storages 2 Node Cluster 1 Server Running Nodes = 10 Storage 20 Storage 3 Node Cluster 2 Servers Running Nodes = 10 storage 30 storage 1 Server Running Nodes = 6 storage 18 Storage Scalability And ReliabilityStorage Always plan for 20 Storages at most per single server

  24. Scalability And Reliability • Scalability is priority one for most hosting scenarios • Current scenarios: • 1 million user test • FE/BE scalability • SAN testing • Large scalability labs in Bldg 43 + MPSC

  25. PC - Desktop PC - Laptop Windows Terminal Win CE - Palm PC Win CE – HH Pro Smart Phones Cellular Phones Digital tablets Client Scenarios

  26. Management • Remote Management • Windows Terminal Server • MMC • Lights Out Operation • Automatic tasks • CDO / CDO EXM • ADSI • OLE DB • Objects : • Interfaces, methods, properties • Dual interfaced • C++, Visual Basic, VB Scripting Edition, Jscript

  27. Call To Action • Follow the next session • Check the Architecture White Paper • Use the “Deployment guide” • Saturday we will build the ASP environment • Send feedback and comments to • ASPTech@Microsoft.com

More Related