Become a Columnist Microsoft Exchange Site Microsoft Support SiteMSDN Exchange Site

   

Subscribe to OutlookExchange
Anderson Patricio
Ann Mc Donough
Bob Spurzem
Brian Veal
Catherine Creary
Cherry Beado
Colin Janssen
Collins Timothy Mutesaria
Drew Nicholson
Fred Volking
Glen Scales
Goran Husman
Guy Thomas
Henrik Walther
Jason Sherry
Jayme Bowers
John Young
Joyce Tang
Justin Braun
Konstantin Zheludev
Kristina Waters
Kuang Zhang
Mahmoud Magdy
Martin Tuip
Michael Dong
Michele Deo
Mitch Tulloch
Nicolas Blank
Pavel Nagaev
Ragnar Harper
Ricardo Silva
Richard Wakeman
Russ Iuliano
Santhosh Hanumanthappa
Steve Bryant
Steve Craig
Todd Walker
Tracey J. Rosenblath
 
 

Exchange 2000 Webstore Strategies

Page 1 | Page 2 | Page 3 | Page 4 | Page 5
SLA Breakdown

Three factors determine how an application is configured on the server and whether a new server is required: security, risk and availability. The worksheet in Figure 2 provides a good start in identifying each variable.

Figure 2: Application worksheet

Connectivity Requirements (This determines if a MAPI store is required)

  • Does the proposed application require:
  • Outlook 97 or Outlook 98 Access?
  • Offline Access?

WAN Impact (This will determine if replication traffic and remote traffic be analyzed)

  • Are the users (mostly) centralized to a single data center? Specify.
  • Are the users (somewhat) equally divided among the data centers (Global Access)
  • What is the projected daily traffic for the application? (Better phrasing required)
  • What is the expected population for the first six months?
    • Less than 500 users
    • 500-1000 users
    • 1,000-10,000 users
    • More than 10,000 users

Application Requirements

  • Does this application require:
    • Custom Sinks or agents?
    • Integration with Chat?
    • Integration with Conferencing? (Exchange conferencing server)
    • Integration with other applications (Databases or systems)
    • Additional security above and beyond the Secure ID and Kerberos
      • Extreme Physical Security
        • Cannot be located in Data Center
        • Cannot be on same machine as other databases
        • Administered by department
        • Cannot be accessed by Internal system
      • Specialized Departmental Management tools or access
      • Additional encryption requirements
      • Access to extranet or other business networks
    • FrontPage 2000 extensions
    • Indexing
    • Persistent Searches

Schema Requirements

  • Does this application require:
    • Active Directory Schema update or expansion?
    • Web store Schema sharing?
    • Extreme protection from schema inheritance?

Recoverability

  • What is the required uptime for the application (affects the price of the app)
A. 99.999
B. High Availability with a 4 Hour recovery window
C. High Availability with a 8 Hour recovery window
D. High Availability with no guarantees

Management and Monitoring (NetIQ and Provisioning server may offer some relief)

  • Does this application have any specific monitoring requirements?

Exchange 2000 Webstore Strategies

Page 1 | Page 2 | Page 3 | Page 4 | Page 5

Disclaimer: Your use of the information contained in these pages is at your sole risk. All information on these pages is provided "as is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Stephen Bryant or Pro Exchange. OutlookExchange.Com, Stephen Bryant and Pro Exchange shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.

Copyright Stephen Bryant 2008