1. Common Solutions Group May 13, 2009

2.  Faculty/Staff appropriate grade of service  Full Exchange environment ◦ Outlook (email, contacts, calendar, tasks) ◦ Outlook Web Access  Campus Active Directory integration ◦ Very difficult or impractical in Exchange 2007 ◦ Expected to be practical in Exchange 2010  Email anti-virus  2 nd tier support tools

3. ◦ Backup service with mailbox recovery capability ◦ Quota management  Starting at 2 GB  Ability to increase on a per-user basis is required ◦ The service will handle attachments of at least 20 MB ◦ A process to define and maintain the expectations for the high-availability service  Continuity of operations  Disaster recovery timelines & planning  Starting assumption: ½ business day is sufficient

4.  Mobile Device Support ◦ Blackberry Enterprise Server ◦ ActiveSync  IMAP  Anti-Spam  2 nd tier support  Voicemail  OCS  Telephone integration

5.  Deleted item retention policy settings  Retention and archiving rules that are customized per-group  Support for compliance add-on products  Provisions for local and hosted email routing and mailing list support  Physical and logical storage redundancy ◦ At least off-site backups if not remote real-time replication  How would support work and which level is where? ◦ Tier 1 vs. Tier 2 vs. Tier 3

6.  Telephone integration would be quite hard or impossible in the cloud now  Exchange 2010 will likely make AD integration possible/practical  SharePoint is out of scope (at least for now)  Who purchases the licenses? ◦ Best guess is that the user’s school would have their own Campus Agreement in place  There are baseline security requirements that will need to be decided for the service as a whole.

7.  Some custom tool development may be needed to implement this service.  We’ll need a process for preservation holds for e-discovery  POP is specifically excluded; support issues  A reasonable starting point may be Disaster Recovery and Business Continuity

8.  Questions  Discussion  … … …