Transcript Architecting Shared Server Hosting With

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
Topics






Hosting scenarios and models
Active Directory™ design
Messaging configuration
Scalability and reliability
Clients
Management
Hosting Scenarios And Models

Centralized (shared server hosting)




De-centralized




All software components, hardware live
at ASP data center
ISP-like configuration
Vast scale services (messaging, conf, wireless)
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
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
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
Active Directory Design
WTS Exchange 2000
Managed PC
Other ISV Apps
Wireless
Unified Messaging
Conferencing
Instant Messaging
Messaging
Office Online
Other TS Apps
Active Directory Design
Active Directory –
Shared Hosting Architecture
Benefits of a single platform (Windows 2000)
and integration of products
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
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
Messaging Configuration

Global address List and Offline Address list




Security



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>
AllUsers@customer1 ,
 Allow = read, execute, read permissions, list
content, read properties, open address list
AdminOu@customer1
 Full administrative privilege
For MAPI users
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
Messaging Configuration

External DNS

Primary zones per customer




For redundancy and replication
EX.

Customer1.com
@ MX 10
MAIL
www

pointing to the Virtual IP address
for the OWA
for the SMTP address
Integrated to the AD


IN A
WWW
MX
mail.Customer1.com.
A
208.217.184.2
A
208.217.184.3
;SMTP
;OWA
AD and FE server will resolve the mailbox location
and alias for the user
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
Scalability And Reliability


Scalability and reliability through
partitioning and redundancy
Partition separate servers for:




Protocols
Storage
Directory
Add redundancy with:


Clustering
Load Balancing
Scalability And Reliability

Scaling Vertical
Version
Processor
RAM
Windows 2000 Server
4 Way SMP
4 GB RAM
Windows 2000 Advance
Server
Windows 2000 Data center
8 way SMP
8 GB RAM
32 way SMP
64 GB RAM

Scaling Horizontal
Version
Net Load Bal
Cluster serv
Windows 2000 Server
N/A
N/A
Windows 2000 Advance
Server
Windows 2000 Data center
Up to 32 nodes
2 node
Up to 32 nodes
4 Node Cluster
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
Scalability And Reliability
FE/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
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


A resource group is an atomic unit of fail over/
fail back


Resource.dll: Exchange wrote its own // EXCHRES.DLL
Exchange Virtual Server
Let the back end do the heavy lifting



Processing
Accessing storage
Security
Failover/User Experience
EVS2
EVS1
X
EVS1
HTTP,POP,
IMAP,MAPI
Scalability And Reliability
Partition separate servers
Router /DNS
service
resolver
Protocol
Protocol
Protocol
Protocol
Protocol
Windows
2000
Directory
Store
Store
Cluster A
Store
Store
Cluster B
Scalability And Reliability
Storage
Machine
A
Machine
B
Shared Storage
Local Attach Storage
Supported
Scalability And Reliability
Storage

2 Node Cluster

1 Server Running



2 Servers Running





Nodes = 6 storage
18 Storage
3 Servers Running





Nodes = 15
storages
60 storage
2 Servers Running

Nodes = 10 storage
30 storage
1 Server Running

4 Server Cluster
Nodes = 10 Storage
20 Storage
3 Node Cluster


Nodes = 10
storages
40 storages
1 Server Running


Nodes = 5 Storage
20 storages
Always plan for 20 Storages at most per single server
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
Client Scenarios
PC - Desktop
PC - Laptop
Windows Terminal
Win CE - Palm PC
Win CE – HH Pro
Smart Phones
Cellular Phones
Digital tablets
Client
OWA
Authentication Protocol
Basic
Basic + SSL
NTLM
Digest
http
https
Advantages




Basic& Digest
browser independent
HTML 3.2+
No client updates
With SSL entire
session is encrypted
O2K
NT
Basic
MAPI
POP3
IMAP4
Rich functionality
large installed base
OE
Basic
Basic over
SSL
NT
POP3
IMAP4
LDAP
large installed base
little overhead, good
performance
POP3I
MAP4
Basic
POP3
IMAP4
Light and good to just
connect
Disadvantages
No offline
capabilities
 Secure
connection
requires SSL
 SSL slows down
performance
MAPI clients only
connect to the
backend
VPN required for
MAPI
Network Traffic load
SSL slows down
performance
NT requires VPN

Lack of features
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
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

[email protected]