Voic Enabled by Unified Messaging

Voicemail Enabled by Unified Messaging
3/31/ :57 PM Voic Enabled by Unified Messaging © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Exchange Unified Messaging
Replace your voic system IT User Organization Decrease Cost Reduce IT Management Optimize User Productivity Consolidate voic onto a single messaging platform Native Message Waiting Indicator announces the arrival of a new voic Manage voic and systems from a single platform Manage UM using scriptable commands and workflows Secure confidential and private voic Read voic with Voic Preview Create customized greetings and call transfer options Improved caller ID Situation Communication technology is changing rapidly after years of rest. A quickly growing number of organizations are struggling to provide agile and mobile workforces with new and smarter ways of managing voic . IT Administrators are increasingly being tasked with providing access to unified messaging in a secure and familiar manner to optimize productivity and decrease management overhead. Slide objective Exchange UM can replace your legacy voic system Exchange UM will have benefits for users, administration, and the organization as a whole Talking points To address this demand while reducing cost, Microsoft® Exchange Server 2010 offers unprecedented flexibility over traditional voic systems that improve daily productivity by consolidating and voic onto one inbox. Unified Messaging in Exchange natively lets users access voic , , contact, and calendar information that is located in their Exchange mailbox via telephone, computer, or mobile device. Exchange Server 2010 adds to the powerful Unified Messaging features brought in Exchange Server 2007 to provide the following benefits: Parse voic messages as they arrive by reading the corresponding Voic Preview to act upon voic messages quickly and efficiently without a telephone or speaker Manage the voic and systems from a single platform. Administrators don’t need to understand and maintain multiple systems, so they have more time for proactive work. End users can now create customized greetings and call transfer options to have more flexibility on where and when incoming calls get routed. Manage Unified Messaging using scriptable commands. Administrators can easily create customizable workflows and optimize their work to save time. Build highly available and reliable Unified Messaging infrastructures to match an organization’s needs. More users can now listen and interact with their and voic in their native language or dialect. The Message Waiting Indicator on the phone can be lit up to announce the arrival of a new voic message. Help identify unfamiliar callers and their voic messages. Exchange Server 2010 UM has been created with trustworthy computing goals and offers Protected Voic to secure confidential and private voice messages. As a result of these improvements, users can efficiently manage their day using a consistent and familiar experience. IT Administrators have more time to focus on proactive projects to add value to an IT strategy, instead of reactive fires which consume time and resources. At the top level, organizations save capital and operational expenditure by leveraging an Exchange Server platform for voic usage.

Voicemail in Your Inbox
Extend the Exchange Server vision by bringing voic to the inbox Simplify tasks and reduce administrative costs by consolidating infrastructure and training Expand the reach of Exchange to the telephone to allow “anywhere access” to your inbox, calendar, and contacts Situation: Unified Messaging in Exchange 2007 took a major step towards providing a universal inbox by helping users manage their voic and in the same place. Triaging voic remained a task separate from that of as users had to have speakers available and find themselves a private location to listen to potentially confidential or private voic messages. Providing a simple text based transcription of voic provides users a quick and easy way to identify the importance of a voic and how to prioritize a response without having to necessarily play the audio over a phone or PC. This becomes particularly valuable when checking in with and voic while on a mobile device or while in a setting, such as a meeting, where listening to a voic is not possible. Slide Objective: The audience should walk away understanding that we are taking our past investments in Unified Messaging even further in the next release of Exchange. With further enhancement of UM to include text- based transcription of voic , we provide users more choice when consuming voic message and further integrate voic into the universal inbox. Talking Points: Unprecedented flexibility over traditional voic systems that improve daily productivity by consolidating and voic onto one inbox.

Beyond Traditional Voicemail
3/31/ :57 PM Beyond Traditional Voic Triage voice messages quickly Voic Preview Save time and money by triaging voic in your inbox by reading the text preview Available in U.S. English, Canadian English, French, Portuguese, Italian, Polish, Spanish Inline Audio Playback Situation Voic has changed as is no longer simply accessible through an aged telephone interface Slide objective Save time and money by triaging voic in your inbox by reading the text preview It will be available in 6 languages Text is contextual and clickable to browse to a section in the recording Talking points Choice of MP3, WAV, or WMA file attachments Windows Phone improvements for inline player Exchange Server 2010 makes it easy to navigate through voice messages. Now your users can read the contents of voic as easily as they would read . If the text voic previews are opened using Microsoft Outlook® 2010, they become “actionable”. Recognized names, contacts, and phone numbers will all be identified with icons which users can add as contacts, call using Office Communicator, or communicate with via . Navigating the audio is as simple as clicking in the text, which will cause the voic to jump to that word and continue playing. Text Preview of Voic Contextual Actions © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Define a Personalized Voicemail Menu
Call Answering Rules Professional and powerful tools Call Answering Rules As simple as Inbox Rules Provide different menu choices based on the Caller ID Situation Call Answering is the most-used Unified Messaging scenario. Users want more control over how calls are answered. Slide objective Manage your voic in the same way you manage your inbox – with rules Talking points Exchange 2010 offers flexible Call Answering Rules that are as simple as inbox rules. Condition: if it evaluates to true, then run… Greeting and Menu: collect caller's choice of… Action: transfer, "Find me" or leave message Unified Messaging gives your users more control over how their calls are answered. For a sales professional, this could mean the difference between sending an important sales lead to voic instead of to an attended line. Call Answering Rules can present callers with custom greetings, Find-Me, and call transfer options in addition to voic prompts. These rules can be preceded by conditions (such as caller IDs, time of day, and Exchange free/busy status), giving your users greater control over how they can be reached over the phone. Define a Personalized Voic Menu Manage Rules

Protected Voicemail Prevent forwarding of voicemail
Protect All messages or only messages marked Private by sender Situation Exchange Server 2010 enables more control over who can access voic content and the operations that they may perform on it. Objective Information Rights Management can be applied to voic messages to prevent unwanted forwarding of messages Talking points Using Active Directory Rights Management Services, Do Not Forward permissions can be applied to voice messages that are designated either by the sender (by marking the message as private) or by administrative policy. This prevents the forwarding of protected voic s in a playable form to unauthorized persons, regardless of the mail client used. Un-checking Multi-media Playback option prevents voic from being transferred to desktop “Do Not Forward” template Integration with AD RMS and Exchange Unified Messaging Permissions designated by sender (by marking the message as private) or by administrative policy

Message Waiting Indicator
3/31/ :57 PM Message Waiting Indicator Be notified when you have a new voic Phone Gateway & PBX UM servers Mailbox servers Exchange 2010 UM supports MWI natively Configure through UM Mailbox Policy No new roles Highly scalable Also can send SMS to mobile phone with first 160 characters of Voic Preview Situation Users wanted to be notified when a voic Slide objective New highly, scalable message waiting indicator functionality is built-in to Exchange 2010 Talking points Users are notified of the presence and number of new or unread voic messages on their supported desk phone. Users can configure their text messaging notification account to receive the beginning content of the voic preview via SMS. Users additionally receive a stuttered dial tone when a phone is taken off-hook © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Rich Fax Partner Support
Integrated Experience Fax messages appear to the user in a familiar fashion Administration is done in EMC for provisioning and de- provisioning Partner Interoperability Program Fax specification is published and available to all partners who wish to have a first-class integration TekVizion is the certification partner Situation Fax support is an important part of some organizations’ messaging needs. Exchange is very well tested with a partner ecosystem for support of inbound fax. Slide objective A rich partner ecosystem exists for fax needs Talking points UM will listen for fax tone and pass the call off to a partner solution (whether on or off-premises). This enables single DID support Administration experience is managed natively from Exchange (Management Console or Management Shell) Flexibility and Security Partner connections are authenticated by Exchange Choice of hosted or on-premises partners

International Support
Prompts, text-to-speech, speech recognition Total of 26 Languages Catalan English German Russian Chinese (Hong Kong) Australia Italian Spanish Canada Japanese Spain Chinese (PRC) GB Norwegian Mexico India Chinese (Taiwan) Swedish Polish United States Danish Korean Finnish Dutch Portuguese French Brazil Portugal France Situation Language support is important for access to voic Prompts and Outlook Voice Access Slide objective Exchange Unified Messaging will support 16 languages at launch Soon after, another 10 languages will be supported Talking points Prerecorded prompts to provide callers with a familiar interface Text-to-speech reading of so that the system can read your voice messages in foreign languages Speech recognition so you can say things like “Calendar for tomorrow”

Architecture Enterprise-class reliability UM protocols:
3/31/ :57 PM Architecture Enterprise-class reliability Situation Leverage the existing messaging architecture or scale out onto separate servers Slide objective Place UM Servers nearby the mailbox servers Will communicate to a number of servers Talking points Scale out and scale up architecture will support very small and very large enterprises Will want to place UM servers by the mailbox server as the UM server needs to pull configuration data from the mailbox UM protocols: SIP/RTP to gateway/PBX LDAP to the directory MAPI/RPC to mailboxes Can place UM servers distant from PBXs Support scale out and server consolidation © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Regulatory Controls Flexibility to meet business needs
Greater control of voic Voic in your Inbox Single administration point Powerful retention policies can be applied Reduces the cost of accessing, querying, and producing voic Option for standalone voic New-ManagedContentSettings -MessageClass IPM.NOTE.Microsoft.Voic * -Name "Voice Mail Retention Period" -AgeLimitForRetention "30" -foldername "Inbox" -RetentionAction "PermanentlyDelete" -RetentionEnabled $true Situation Companies face complex regulatory requirements around information retention and discovery. They need tools that help them easily manage voic in compliance with these requirements. Slide objective The audience should understand how Exchange 2010 makes voic easier to manage and control from a compliance standpoint. Talking points Exchange Unified Messaging does not change a company's obligation to retain voic . However, by using Exchange UM, organizations will find it easier to control voic . It will also be easier to implement a retention policy that applies to and voic messages. Should it become necessary to prepare for litigation, Exchange Unified Messaging reduces the cost of accessing, querying, and producing voic . Additional resources

Summary Voicemail: the next generation
3/31/ :57 PM Summary Voic the next generation A great replacement for legacy voic Deep investments in UM features that will add real benefit to common scenarios Voic Preview Call Answering Rules Built-in Message Waiting Indicator Protected Voic Access to both Contacts and Groups 26 languages supported Provide the controls and protection you need for your compliance needs Situation Recap of the features and benefits Slide objective Review features shown previously Voic Preview Call Answering Rules Built-in Message Waiting Indicator Protected Voic Access to both Contacts and Groups Talking points Close on a review of all features and parts shown. There is an Appendix for reference © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

3/31/ :57 PM Licensing Server A license must be assigned for each instance of the server software that is being run. The Exchange Server license is sold in two server editions: Standard Edition: designed for the mailbox needs of small to medium organizations. Also appropriate for non-mailbox roles in a larger Exchange deployment. Enterprise Edition: designed for larger organizations that may require a greater number of mailbox databases. Situation Recap of the features and benefits Slide objective Review features shown previously Voic Preview Call Answering Rules Built-in Message Waiting Indicator Protected Voic Access to both Contacts and Groups Talking points Close on a review of all features and parts shown. There is an Appendix for reference © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

3/31/ :57 PM Licensing Client Exchange requires a CAL for each user or device that accesses the server software. There are two types of CALs for Exchange: Standard CAL: designed to help users be more productive from virtually any platform, browser, or mobile device Enterprise CAL: new integrated archiving functionality and information protection capabilities, while also helping you cut costs by replacing legacy voice mail. The Enterprise CAL is sold as an add-on to the Standard CAL. To enable Enterprise CAL features, the user must be licensed with one Standard CAL plus one Enterprise CAL. Situation Recap of the features and benefits Slide objective Review features shown previously Voic Preview Call Answering Rules Built-in Message Waiting Indicator Protected Voic Access to both Contacts and Groups Talking points Close on a review of all features and parts shown. There is an Appendix for reference © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Some Negatives Considerations for putting VM on Exchange
3/31/ :57 PM Some Negatives Considerations for putting VM on Exchange Voice mail is now and discoverable Servers, servers, and more servers, and licenses! IT management competition Redundancy of the IT infrastructure – “Exchange is down again” / robustness Reliance on Active Directory to work. Lack of TUI support – only “Aria like” Auto Attendant capabilities still lacking Lack of migration tools Interoperability No Message Networking Situation Recap of the features and benefits Slide objective Review features shown previously Voic Preview Call Answering Rules Built-in Message Waiting Indicator Protected Voic Access to both Contacts and Groups Talking points Close on a review of all features and parts shown. There is an Appendix for reference © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Microsoft® Exchange Server 2010 Mailbox High Availability and DR

Email Trends Email is business critical: Email volume is growing
Time loss after a failure is measured in seconds Data loss after a failure needs to be close to zero “Business users report that they currently spend 19 percent of their work days, or close to two hours per day, on .” – Messaging & Collaboration – Business User Survey 2007, Radicati volume is growing Situation is business critical. Organizations face the challenge of managing an increasingly large volume of data. Slide objective Describe the current trends which are affecting High Availability: growth in data and increased reliance on . Talking points Researchers found that the average corporate user will send and receive 33% more messages over the next four years Many users have personal/online accounts with multi-GB storage limits & want to know why corporate mailboxes are so limited Administrators have to store and manage this growing volume of , including backing it up and restoring it when problems occur Customers say, “If stops, my business stops” They need to accomplish continuity efficiently and cost-effectively “The average corporate user, today, can expect to send and receive about 156 messages a day, and this number is expected to grow to about 233 messages a day by An increase of 33 percent over the four-year period.” – Messaging & Collaboration – Business User Survey 2008, Radicati Users expect larger corporate mailboxes

Large Mailbox Benefits
Improve user productivity Access to all from all clients Less time spent managing mailbox quota Eliminate lost or corrupted .PST files Reduce IT operations costs Simplify discovery and retention management Eliminate proliferation of .PST files stored outside of IT control Utilize high-capacity disk drives efficiently Situation volume continues to grow, driven by the nearly ubiquitous use of as the core communications tool for businesses. At many organizations, mailboxes are too small to accommodate this growth, forcing employees to spend time deleting messages or moving them to .PST files to stay under quota. Your employees may wonder why their personal accounts have multi-gigabyte storage limits while their work accounts are a fraction of the size. Small mailbox quotas are not just an inconvenience for your users. Undersized mailboxes can lead to the proliferation of .PST files. Because .PST files exist outside the Exchange server, they are difficult for you to manage, difficult to search for legal discovery purposes, insecure, and rarely backed up. Slide objective Communicate the benefits of large mailboxes. Talking points We think of large mailboxes as allowing you to store at least a year’s worth of messages in the one mailbox Time Items Mailbox Size (MB) 1 Day 1 Month 4000 ~300 1 Year 52,000 ~3800 4 Years 208,000 ~15000 User profile: 160 Receive + 40 Send /Day Profile, 75KB, no deletions, 5 day work week

Exchange 2010 Mailbox Resiliency
Enables deployment of large, low-cost mailboxes Single solution for High Availability, Disaster Recovery, and Backup Simplified administration reduces complexity Built-in features for mailbox recovery Improved availability Storage flexibility Talking Points: We have made some significant improvements in a number of areas that we know were challenging for administrators when deploying large mailboxes. All these Exchange 2010 improvements enable you to deploy low-cost, large mailboxes. We now have a single solution for high-availability, disaster recovery and backup. This allows you to do very fast recovery, regardless of the size of the data, and reduces the user down-time, so users stay connected to Exchange for longer— even in the event of a failure. We’ve also simplified the administration model, and simplified the deployment, which reduces both the cost and complexity of deploying and managing a resilient mailbox solution. With Exchange Server 2010, the use of replicated database copies, combined with the high availability architecture to protect against failures, enables your organization to meet fast recovery times without the need for traditional backups, saving time and money. But beyond management of failures and backups, we’ve also improved the end-to- end availability. If an administrator needs to move a mailbox, traditionally, the user loses access to their mailbox for the time that the move takes—and the larger the mailbox gets, the longer that time period. We’ve introduced an Online Move Mailbox feature, which reduces user down-time by allowing users to stay connected to their mailbox even while it’s being moved. And to further reduce the cost of your infrastructure, we’ve introduced a range of storage choices, so you now have more flexibility in the storage that you can use for Exchange. We’ve significantly improved the performance, and we provide support for larger, slower, cheaper disks, which reduces the storage costs for Exchange 2010.

Mailbox Resiliency New unified solution for High Availability, Disaster Recovery, and Backup
San Jose New York Mailbox Server Mailbox Server Mailbox Server DB1 Replicate databases to remote datacenter DB1 DB1 Recover quickly from disk and database failures DB2 DB2 DB2 DB3 DB3 DB3 DB4 DB4 DB4 DB5 DB5 DB5 Situation: As the importance of communications in today’s workplace continues to grow, companies count on their IT staff to prevent outages and data loss. Traditionally, customers have been required to deploy expensive shared-storage clustering and purchase 3rd party data replication products to provide full redundancy of Exchange Server services and data. Exchange Server 2007 introduced a built-in data replication technology called Continuous Replication, which significantly reduced the cost of deploying a highly available Exchange infrastructure. Running a highly available Exchange infrastructure still requires a great deal of time and expertise, because integration between Exchange Server and Windows Clustering is not seamless. Companies want an easier way to replicate their data to a remote location, in order protect their Exchange environment against site-level disasters. Slide Objective: Position the new Mailbox Resiliency model as the evolution of previous HA methods, which has been extended to include HA, DR and Backup, with significantly less cost and complexity. Talking Points: Exchange Server 2010 has evolved from the same Continuous Replication technology found in Exchange 2007, combining on-site data replication (CCR) and off-site data replication (SCR) into a single solution. Mailbox servers can be defined as part of a Database Availability Group which uses continuous replication to update database copies and can provide automatic recovery from a variety of failures whether they are at the disk level, server level, or the datacenter level. Exchange Server Database Availability Groups handle all aspects of clustering internally. There is no need to manage failover clustering separately in Windows Server. Granular fail-over and recovery is now at the mailbox database level , rather than the Server level. This results in faster failover times (less than 30 seconds). Administrators can add replicated database copies incrementally (up to 16 total), and Exchange switches between these copies automatically as needed to maintain availability. Mailbox servers involved in clustering can host other Exchange roles (Client Access, Hub Transport, etc), so full redundancy of Exchange services and data can be achieved with just two servers. The new high availability architecture provides simplified recovery from a variety of failures (disk-level, server-level, and datacenter-level), and can be deployed on a variety of storage types. Evolution of Continuous Replication technology Provides full redundancy of Exchange roles on as few as two servers Reduce backup frequency through up to 16 replicas of each database Can be deployed on a range of storage options

Mailbox Resiliency Overview
AD site: Dallas DB1 DB3 DB5 Clients connect via CAS servers Client Access Server Client Mailbox Server 6 AD site: San Jose Client Access Server Database Availability Group Easy to stretch across sites Failover managed within Exchange Mailbox Server 1 Mailbox Server 2 Mailbox Server 3 Mailbox Server 4 Mailbox Server 5 Slide objective Describe how the new High Availability solution works, including stretching the solution across sites. Talking points Here is Contoso’s new Exchange 2010 environment. Tomas is the lead Exchange and Active Directory administrator for Contoso. He has overall responsibility for providing messaging and communications services to all of Contoso’s employees. Tomas’ primary challenge is to maintain high levels of availability with a flat or shrinking budget year-over-year. There are 5 servers in the main datacenter in San Jose that host mailboxes. These mailbox servers are grouped to provide automatic failover. The group of servers is known as a Database Availability Group. Each mailbox database has 3 instances, which we’ll refer to as copies, <click> placed on separate servers to provide redundancy. At any given time, only 1 of the 3 database copies is active <click> and accessible to clients. <Click> This gives us database centric failover and <click> all the failover is managed within Exchange which makes it very easy to manage. The Client Access Server <click> manages all communications between clients and databases. Outlook clients no longer connect directly to mailbox servers, as they did in previous versions of Exchange. When a client such as Outlook connects to Exchange, it first contacts the CAS Server. The CAS Server determines <click> where the user’s active database is located ( in our case the user is on DB1 which is currently active on Mailbox Server 1), and forwards the request <click> to the appropriate server. When the client sends an <click>, the active database is updated. Then, through log shipping <click>, the other 2 passive copies of the database are updated. <click> Let’s say that a disk fails <click>, affecting one of the databases on Mailbox Server 1. In previous versions of Exchange, the administrator would need to failover all the databases on Mailbox Server 1 to recover from this failure, or else restore the Database 1 from a tape backup. However, Exchange’s new architecture supports database-level failover, so Database 1 has automatically fails over to Mailbox Server 2 <click> without affecting the other databases. The Outlook client, having lost its connection to the database, automatically contacts the CAS Server to reconnect. The CAS Server determines which mailbox server has the active copy of the users’ database. It connects <click> the client to Mailbox Server 2. When new mail is sent <click>, the active database on Mailbox Server 2 is updated. The second copy of the database <click> is also updated through log shipping. The end user is unaware that anything has happened, and Tomas can replace the failed disk drive at his leisure. Administrators can set up to 16 copies per database to meet the Service Level Agreements for their users. For a special category of users, Tomas keeps a 4th database copy on a mail server in a geographically remote location <click>. This server is located in a different Active Directory site, but is kept up- to-date over the Wide Area Network using the same replication technology as the other servers. (No stretching of subnets) If a hurricane, earthquake, or other catastrophe should shut down the main datacenter, this remote server can be activated and readied for client access in a short period of time. DB1 DB1 DB4 DB2 DB5 DB3 Database -centric failover DB2 DB5 DB3 DB1 DB4 DB1 DB1 DB3 DB4 DB2 DB5

Mailbox Resiliency Components
Database Availability Group (DAG) Mailbox Servers Mailbox Database Copies Active Manager RPC Client Access Service Active Manager Client RPC Client Access Service AM Client Database Availability Group Active Manager Active Manager Active Manager Situation Exchange 2010 High Availability Solution is made up of a number of components which work together to provide a simplified, unified solution for both high availability, disaster recovery and backup. Slide objective Introduce the components of mailbox resiliency in Exchange 2010. Talking points Database Availability Group – often referred to as a ‘DAG’ - Set of up to 16 Mailbox servers that communicate to manage failures that affect individual databases. Any server in a DAG can host a copy of a mailbox database from any other server in the DAG. Mailbox Servers - When a server is added to a database availability group (DAG), it works with the other servers in the DAG to provide automatic, database-level recovery from database, server, or network failures. Mailbox Database Copies - Databases are ‘disconnected’ from servers and Exchange 2010 adds support for up to 16 copies of a single database. Only Mailbox databases, not Public Folder databases, can be replicated. Storage groups removed, so log shipping replication now operates at the database level. transaction logs are replicated to one or more other Mailbox servers, and replayed into a copy of a mailbox database that is stored on those servers. Note that you can't replicate outside the DAG (key difference from SCR). Active Manager - DAGs use a new component in Exchange 2010 called Active Manager, which is a process which runs on each Mailbox Server that is a member of the DAG. There are two Active Manager roles: primary active manager (PAM) and standby active manager (SAM). PAM is the Active Manager in a DAG that decides which copies will be active and passive. PAM is responsible for getting topology change notifications and reacting to server failures. The DAG member that holds the PAM role is always the member that currently owns the cluster quorum resource (default cluster group). If the server that owns the cluster quorum resource fails, the PAM role automatically moves to a surviving server that takes ownership of the cluster quorum resource. The SAM provides information on which server hosts the active copy of a mailbox database to other components of Exchange (e.g., RPC Client Access service or Hub Transport). The SAM detects failures of local databases and the local Information Store. It reacts to failures by asking the PAM to initiate a failover (if the database is replicated). RPC Client Access Service – New connection point on the CAS Server for Outlook. Connecting to the CAS Server rather than the mailbox server makes the database failover process almost seamless for Clients. Active Manager Client – The CAS Server uses the Active Manager Client process to query Active manager on the mailbox servers to determine which server hosts the active copy of a mailbox database. DB1 DB1 DB1 DB2 DB2 DB2 DB3 DB3 DB3

Mailbox Resiliency Fundamentals
Database Availability Group (DAG) A group of up to 16 mailbox servers that host a set of replicated databases Wraps a Windows® Failover Cluster Defines the boundary of replication and failover Slide objective Describe in detail what a Database Availability Group is and how Mailbox servers work within them. Talking points Database Availability Group DAG is created initially as empty object in Active Directory Mailbox servers added to a DAG Windows failover cluster is formed Server joined to cluster for the DAG The quorum model is automatically adjusted Create mailbox database copies Seeding is performed automatically Monitor health and status of database copies When an administrator creates a DAG, it is initially empty, and an object is created in Active Directory that represents the DAG. The directory object is used to store relevant information about the DAG, such as server membership information. When an administrator adds the first server to a DAG, a failover cluster is automatically created for the DAG. DAGs use a subset of Windows Failover Clustering technologies, namely, the cluster heartbeat, cluster networks, and the cluster database (for storing data that changes or can change quickly such as database mount status, replication status, and last mounted location). A Witness Server is configured for the cluster, but must be server outside the DAG. As subsequent Mailbox servers are added to a DAG Although a Windows Failover Cluster is created, no cluster resources are created and all DAG administration is managed from Exchange. Failover management is also managed entirely within Exchange. Because DAGs rely on Windows Failover Clustering, they can only be created on Mailbox servers that are running Windows Server 2008 Enterprise or Windows Server 2008 Datacenter. Exchange Standard Server will support DAGs, however Exchange Std Server is limited to 5 databases, while Exchange Ent. Server will support upto 100 databases per server. Replication of database copies, and failover of those database copies, can only be with servers which are members of the same DAG. Mailbox Servers In Exchange 2007 database server either hosted only active or passive copies of a database. In Exchange 2010, a server within a DAG can hold both Active and passive copies of databases, so the mailbox server needs to service both of these types of databases. Executes Store services on active mailbox database copies. Executes Replication services on passive mailbox database copies. Active definition of health – Is Information Store capable of providing service against it? Passive definition of health – Is Replication Service able to copy logs and play them into the passive copy? Each server can host up to 100 database copies. Mailbox servers Host the active and passive copies of multiple mailbox databases Support up to 100 databases per server

Continuous Replication in SP1
X Replication Log Buffer ESE Log Buffer Send me the latest log files … I have log 2 Database behind on logs (e.g Server Reboot) Database available for log replication Log fragment detected and converted to complete log Log is built and inspected Database copy up to date Log File 6 Log File 6 Log File 7 Slide objective Describe how Continuous Replication works in Exchange 2010 SP1 – including the failure situation Talking points Continuous Replication was updated to Reduce data loss and to remove log drive as a single point of failure When the mailbox database is behind in logs, then Exchange uses Continuous Replication – File Mode to ship missing, completed logs from the active to the passive copy. Note that while the passive database is “catching-up” logs continue to be created on the active database. Once the passive copy is up-to-date with logs, then Exchange automatically switches between File Mode and Block Mode As blocks are written to the active log buffer, they are also shipped to the passive database copy Once the log buffer is full, the log is built and inspected on both the active copy and the passive database copy What happens on a failover during block mode? When a failure occurs, the System detects presence of log fragment. If all logs are not successfully copied log fragment converted to complete log and the Activated database sees all available committed data Incremental reseed understands how to remove any divergence between complete log on original source and “activated passive’s partial log” Log File 3 Log File 3 Log File 4 Log File 4 Log File 5 Log File 5 Log File 1 Log File 2 Log File 1 Log File 2 Continuous Replication – File Mode Continuous Replication – Block Mode

Simplified Administration Reduces cost and complexity
High Availability administration all within Exchange 2010 Exchange Management Console for common tasks Exchange Management Shell (PowerShell) Mailbox Databases managed at Organizational Level Same automated database failover process used for a range for failures—disk, server, network Simplified activation of Exchange 2010 services in a standby datacenter Situation Running a highly available Exchange 2003/2007 infrastructure requires a great deal of time and expertise, because integration between Exchange Server and Windows Clustering is not seamless. Slide objective Show how administration has been simplified in Exchange 2010. Talking points In the past administration was spilt between Windows Failover Cluster Manager and Exchange. All the HA configuration and management is now done through the Exchange Management tools. The most common tools are all available in the EMC GUI interface, and all tasks can be scripted or run through via Powershell commands. Whether there is a disk failure, server failure or perhaps a network failure, the same failover mechanism is used. In the case of a full datacenter failure, additional actions will be required to bring the full site online, but since the mailbox servers are all part of the same DAG the failover process for the for the mailbox servers and data the process is the same as a failover within the same site. Tools provided to simplify management Active Mailbox database redistribution. Problem: Keeping databases evenly balanced across servers in the DAG; Solution: Periodically run “RedistributeActiveDatabases” Moves databases to most preferred copy Start/StopDagServerMaintenance. Problem: Offloading server to perform maintenance or take it down Active databases and PAM; StartDagServerMaintenance moves Active database copies to other copies & PAM, if present. Then it Blocks Server from becoming the PAM & Activation of local copies. StopDagServerMaintenance unblocks (resumes) Server from becoming the PAM & Activation of local copies Single Copy Alert Failover Metrics Reporting - CollectOverMetrics.ps1 SP1 Improvements include: Performance improved by 50%; Additional data collected - Block mode replication data; More detail on replay and store timings; Summary data added to report; Additional detail on exceptions to 30 second *overs

Incremental Deployment Reduces cost and complexity
Datacenter 1 Datacenter 2 Mailbox servers in a DAG can host other Exchange 2010 roles Database Availability Group Mailbox Server 1 Mailbox Server 2 Mailbox Server 3 DB1 DB1 DB1 DB2 DB2 DB2 Situation In previous versions of Exchange, enabling clustering on an existing mailbox server would have required the administrator to move all mailboxes off the server, tear it down, and then reinstall Exchange. Slide objective Administrators can add high availability to their Exchange environment after their initial deployment, without reinstalling servers. Talking points Well, Tomas’ early days as an Exchange administrator, he had a simple environment with one mailbox server. This mailbox server was not part of a cluster. When Tomas decided to implement clustering, he feared that this might involve a great deal of work. In previous versions of Exchange, enabling clustering on an existing mailbox server would have required him to move all mailboxes off the server, tear it down, and then reinstall Exchange. But because of Exchange’s new architecture, Tomas simply had to add a second mailbox server to his environment <click> and place it in a database availability group <click> with Mailbox Server 1. Then he set up replication <click> for the existing databases on Mailbox Server 1. The process was quick, intuitive, and required no reinstallation. To extend this to become a site reliant solution – Tomas can simply add a third mailbox to a separate site in his environment <click> and add it to the DAG. Then he sets up replication <click> for the existing databases. <click> Multiple server roles can also co-exist on servers that provide high availability. This enables small organizations to deploy a two-server configuration provides full redundancy of mailbox data, while also providing redundant Client Access and Hub Transport services. It is easy to extend an existing Exchange 2010 to include high availability and this reduce both the cost and complexity of the HA deployment. No subnet or special DNS requirements! DB3 DB3 DB3 Easy to add high availability to existing deployment High availability configuration is post-setup

Backup Using Exchange 2010 Reason for Backup Recovery Feature Exchange 2010 Feature Benefit Fast Recovery HW/SW Failures Mailbox Resiliency Fast recovery Data redundancy Datacenter Failures Data Retention Accidentally Deleted Items Single Item Recovery Guaranteed item retention Situation In addition to high availability and disaster recovery, most organizations deploy backup systems to ensure that Exchange data can be recovered in a timely manner. As mailbox sizes grow, the time required to recover data from backups can become unacceptably long. Slide objective With Exchange Server 2010, the use of replicated database copies, combined with the high availability architecture to protect against failures, enables your organization to meet fast recovery times without the need for traditional backups, saving time and money. Talking points Organizations have many reasons for taking backups Exchange provides a number of built-in features which provide recovery from these types of failures without the need to use traditional backups. If all the recovery requirements can be met by Exchange features, then organizations can consider not taking backups at all, resulting in dramatic cost savings, or can reduce the frequency of their backups. Traditional backups can still be done ( there is a slide in the appendix which covers this ) VSS backup and restore supported at database level Backup from active and passive copies VSS Restore to Active only Administrator Error Lagged Copy Past point-in-time database recovery Mailbox Corruption Long Term Data Retention Personal Archive + Retention Policies Secondary mailbox for older data

Traditional Backup Support
Traditional point-in-time backups useful for: Point-in-time mailbox snapshots Disaster Recovery with a single datacenter Public folder backups VSS backup and restore supported at database level Backup from active and passive copies VSS Restore to Active only Exchange 2010 plug-in for Windows Server® Backup Volume level backup Application (Exchange) level restore Slide objective Customers may still have some very valid reasons for keeping backups, so with the new database centric failover model, the backup strategy needs to be considered. Talking points Traditional backups are still supported in Exchange 2010 Exchange 2010 enables backups to be taken from wither the passive or active database copies. A VSS backup solution is required since the Streaming Backup APIs have been removed. Backups can be taken from any copy of the database the active or any of the passive copies So this gives customers several options including: Always choosing perhaps a passive copy of the database which needs to be backed up. If a server holds copies of all databases, then there is an option to backup an entire server Or, a dedicate backup server can be designated for a given database. With these options, you can restore from any of these backups. The recovery storage group has been replaced by the recovery database in Exchange 2010. A basic built-in backup solution is available for Exchange 2010 – same functionality as the Exchange SP2 plug-in. Not designed as a full backup solution – suited to very small deployments or as an emergency/test backup DPM is available as a Microsoft backup solution.

Higher Availability During Failures Keeping users connected
Client Client Access Server failure….. Client reconnects through another Client Access Server Load Balanced Client Access Servers Mailbox Database or Server failure….. Client disconnected for <30 seconds Situation With E2003/E2007, a database or server failure required users to be disconnected while the cluster failed over the alternate node. Slide objective Show how, in Exchange 2010 with all clients connecting through the CAS Server, the client experience is improved during any failures. Talking points The new client access architecture provides 2 levels of protection against server and/or database failure which keeps users connected for longer and increases an Oragnization’s uptime. Multiple CAS Servers can be configured in an load balanced array, so that a failure of a CAS Server will not affect the client. The client is simply redirected to an alternate CAS Server. If there’s a failure of a mailbox database, or a mailbox server, the client is only disconnected for as long as it takes for that mailbox database copy to be activated on the other server. Because we’re not doing a whole server fail-over, that’s a very fast process; the client is only disconnected for up to 30 seconds or less DB1 DB1 DB1 DB1 DB2 DB2 DB3 DB3 Mailbox Servers Database Availability Group

Higher Availability During Moves Keeping users connected
Client Mailbox Server 1 Mailbox Server 2 Client Access Server Users remain online while their mailboxes are moved between servers Sending messages Receiving messages Accessing entire mailbox Administrators can perform migration and maintenance during regular hours Situation Administrators commonly move mailboxes between servers and databases as part of maintenance activities or when migrating between Exchange versions. Currently, when an administrator moves a mailbox, this takes the user offline for the duration of the move, leaving them no access to . As mailbox sizes have grown, mailboxes take longer to move, so administrators have been forced to perform mailbox moves at night and on weekends to minimize disruptions for end users. Slide objective Describe how give administrators can use the new online move mailbox process to perform Exchange maintenance and migrations without sacrificing their evenings and weekends. Talking points In Exchange 2010, mailbox moves can be done in online mode: users remain can send, receive, and read mail while the contents of their mailboxes are moved to a new location. Maintenance activities can now be performed during the day, rather than a nighttime or weekend maintenance window. Migration to Exchange 2010 (whether Exchange 2010 is deployed on-premise or online) can be accomplished faster and with less end-user disruption. Achieving four nine SLA (i.e availability) means roughly 50min of downtime per year. In the past, moving a 1GB mailbox takes around 90minutes, so even if all your services were up 100% of the time, if you moved the mailbox once, you will not be able to achieve the four nine SLA. è hence, we want online mailbox moves. Exchange 2007 SP2 allows online moves, while Exchange 2003 enables offline moves.

Improved Transport Resiliency Automatic protection against loss of queued due to hardware failure Edge Transport Hub Transport Edge Transport Mailbox Server Situation As organizations examine their infrastructures to eliminate potential points of failure, they look for ways to protect against data loss beyond just mailbox servers. During period of heavy traffic, queues of undelivered messages can build up on transport servers. If a transport server fails with messages in its queue, data may be lost. In the past, the only way to guard against the loss of message queues was to replicate the queue with expensive third-party replication products. Slide objective Explain how transport servers in Exchange 2010 provide protection against messages being lost in transit. Talking points Transport servers in Exchange 2010 (both Hub Transport and Edge Transport servers) have built-in redundancy to protect against the loss of messages in transit. With shadow redundancy, A “safe copy” of each message is retained until the transport server verifies that all of the next hops for that message have completed delivery. If any of the next hops fail before reporting back successful delivery, the message is resubmitted for delivery to that next hop. Let’s walk through an animation to illustrate how this works: A user composes an message to a business partner, and presses “send” <click> The message moves from their outbox on the mailbox server to a hub transport server Next, it is transferred to an edge transport server at the network perimeter. A “shadow copy” of the message remains on the hub transport server. If a disk drive on the Edge transport server fails before the message can be delivered… …the “shadow copy” is automatically resubmitted through another route The message reaches the business partner successfully, and the shadow copies are removed Previously this level of redundancy would have been expensive to deploy and complicated to manage, but now it is built-in and automatic As an added benefit, in this new redundancy model, transport servers essentially become “stateless,” which makes it easier to take them offline for service. Servers keep “shadow copies” of items until they are delivered to the next hop Simplifies Hub and Edge Transport Server upgrades and maintenance

Storage Improvements New options with performance enhancements
Choose from a range of storage technologies to reduce costs without sacrificing system availability JBOD (RAID-less) Storage Area Network (SAN) Direct Attached w/ SAS Disks SATA Disks Situation Employees wonder why they can’t get large (multi-gigabyte) storage limits for their work like they can for their personal accounts (Hotmail, Yahoo, Google, etc). Exchange Server 2007 enabled organizations to deploy new storage configurations (Direct Attached storage) and offer larger mailboxes to their employees. Storage costs still remain a major expense in most Exchange environments. Slide objective Emphasize that Exchange 2010 provides administrators unprecedented flexibility in choosing a storage architecture. Talking points Exchange includes improvements to performance, reliability, and high availability that enable a wide range of storage options. Including SAN, DAS, cheaper SATA disks and JBOD (RAID-less) configurations. Exchange 2010 delivers a 70% reduction in disk IO from Exchange 2007 levels, lowering the bar for minimum disk performance required to run Exchange. IO patterns are optimized so that disk writes are less bursty and more suitable for SATA (desktop class) disks. SATA optimizations is about using cheaper “good enough” disks. Exchange 2010 is more resilient to storage problems. When corruption is caused by minor disk faults, Exchange automatically repairs the affected database pages using one of the database copies configured for high availability. When Exchange 2010 is deployed with 3+ database copies, these low-level performance improvements enable the use of RAID-less / JBOD storage. Exchange 2010 storage enhancements 90% reduction in IOPS from Exchange Server 2003 Smoother IO patterns Resilience against corruption

RAID-less Storage Now an Option Reduces the number of disks required
Just a Bunch of Disks (JBOD) configuration One disk per database/log Database copies to provide resilience from disk failures Automatic page repair improves resiliency DB1-Active DB1-CopyA DB1-CopyB Situation Exchange 2010 makes RAID-less storage a practical option. Slide objective Show the possibilities enabled by RAID-less storage. Talking points We can now start to look at RAID-less storage as an option. Reduces the number of disks that you need for Exchange. By using a JBOD, or just-a-bunch-of-disks configuration, we use one database and log per disk. We then use database copies to provide resilience from disk failures, instead of relying on the RAID configuration. If there’s a failure in one of the disks in the system, the whole database is affected, and it moves to another copy which is on another server. If there’s just a small problem in one page on a database, Exchange automatically gets the page from a copy of the database and does an in-place repair or patch of the corrupted page: no user effect and nothing admins have to do. In JBOD environment being down to a single copy is a threat to data protection. RTM alerted this based on a SCOM roll-up, but it is critical this condition be detected and alerted, independent of environmental issues. CheckDatabaseRedundancy script is provided in Service Pack 1 – There must be two “non-stale” copies; Incorporates detection logic with suppression; Script checks all databases hosted on a server Log Log Log Page1 Page1 Page1 Page2 Page2 Page2 Page3 Page3 Page3 Database Database Database

Large Mailboxes at Low Cost
Exchange 2010 no longer needs expensive, high-performing disks Use storage efficiently and lower storage costs Larger, slower, lower-cost disks—SATA (Tier 2) Disks Maintain reliability and performance Built-in Exchange 2010 Mailbox Resiliency features Exchange 2010 supports a range of storage options Direct Attached Storage (DAS), Storage Area Network (SAN) RAID and RAID-less (JBOD) Slide objective Exchange 2010 enables organizations to give their users large mailboxes without breaking the budget Talking points Large Mailbox Vision Whitepaper Exchange Server 2010 enables organizations to give your users larger mailboxes at lower cost without sacrificing performance or reliability. Built-in high availability and disaster recovery, storage system improvements, and self-healing from disk faults let you use large, inexpensive disks in configurations that maximize data redundancy. By taking full value of the growing size of the disks, we can improve our storage utilization in the organization. An example of the low costs -- The Exchange 2010 high availability solution allows you to use fewer servers, but gain resilience and maintain performance levels – From 4x2-node CCR clusters to a 6 node DAG with 3 copies of each database.

Mailbox Resiliency Summary
Single solution for High Availability, Disaster Recovery, and Backup Simplified administration and fast recovery Simplified disaster recovery Built-in Exchange 2010 features for mailbox recovery Improved availability for users Online Move Mailbox Flexible storage options to reduce costs Enables deployment of large, low-cost mailboxes Slide objective Describe the Mailbox Resiliency improvements in Exchange 2010 Talking points Single solution for high-availability, disaster recovery and backup for fast recovery, regardless of the size of the data, and reduced user down-time even in the event of failure. Spending less time managing and deploying the solution, also improves uptime for users -- Exchange managing the failover process, allowing you to deploy the solution in an incremental fashion and making it as easy to stretch the solution across datacenter in different sites. These changes will help reduce the operational costs of deploying and managing the solution. Simplified the administration model and deployment reduce the cost and complexity of deploying and managing a resilient mailbox solution. Beyond the mailbox databases themselves the bigger issue of end-to-end availability has been enhanced by reducing the number of messages which can be lost while being sent between transport servers and enabling users to stay online when their mailbox is being moved through the Online Mailbox Move feature. Storage Flexibility By improving the performance of Exchange, we are able to provide more storage options which provides more flexibility to users. These IO performance reductions mean that users are able to take advantage of larger low-cost disks and when combining that with the high availability features can consider some new deployment scenarios around RAID-less disk configurations. The net result is a reduction in storage costs while being able to provide users with larger mailboxes. Exchange 2010 enables you to deploy low-cost, large mailboxes.

Exchange Online Overview
[Note to presenter: If your audience wants information on the future of Exchange Online (including Exchange 2010 updates to the service), then use the “Exchange Online NDA roadmap” ( deck instead of this one. One of the great things about working in IT is that technology is continually advancing – so there are always opportunities to do your job more efficiently and help your users be more productive. Today I’d like to talk about one of those opportunities—cloud computing, or Software as a Service—and how it applies to your environment.

IT Challenges Customers tell us…
I need my IT costs to be lower and more predictable… I want to give users the features of the latest platform but we don’t have the resources to upgrade right now… Situation Organizations share many common IT challenges. Slide objective Get the audience thinking about the difficulties they face that could be solved by Software-plus-Services. Talking points Common challenges faced by IT organizations can be summarized in statements like these: We’re on a tight budget, so I need my IT costs to be lower, and more predictable. I want to give users the features of the latest platform, but we don’t have the resources to upgrade our systems right now. We’re chronically understaffed, and I need to free up our people to work on strategic projects instead of maintaining existing systems. With all the cost cutting going on, our IT budget isn’t big enough to get the advanced security and redundancy we need in our datacenters Cloud computing can be part of the solution for these problems. I need to free up my IT staff to work on strategic projects instead of maintaining existing systems… Our IT budget isn’t big enough to get the advanced security and redundancy we need…

The Benefits of Cloud Services
Cost Agility Simplicity Quality Makes costs regular and predictable Can reduce operating and capital expenses Pricing includes both software and hardware Helps IT adapt to mergers and acquisitions quickly Makes it easy to extend services to new parts of the workforce Accelerates deployments and upgrades Reduces maintenance requirements Enables IT staff to focus on strategic work Provides advanced reliability and security Gives users access to the newest features Situation Cloud computing is attracting a great deal of interest, because of how it helps organizations meet today’s IT challenges. Slide Objective Communicate the benefits of cloud-based services generally, and how these benefits apply to the messaging workload. Talking points The benefits of cloud computing include: Cost Subscription-based services turn ‘lumpy’ capital expenditures into more predictable monthly expenses. Cloud-based services can reduce total cost of ownership. Price is inclusive of software, hardware, maintenance, and support. Agility Cloud services can scale rapidly to accommodate growth. Example: Onboard users quickly after merger or acquisition without re- architecting. Workers who don’t have communications and collaborations tools today can get lightweight, web-based tools for the first time. Simplicity Cloud services can be deployed quickly and easily. Maintenance is taken care of—no need to manage servers, upgrade software, perform backups, etc. Offload routine maintenance to focus on strategic projects. Quality Large-scaled cloud services invest heavily in security, redundancy, disaster recovery, operational excellence. Very few organizations have time & resources to make these kind of investments in-house. Cloud services are “evergreen”—updated regularly without user intervention, providing latest technology to be more productive. How do these apply to ? is big—in terms of how many employees use it, storage, IT resources. Potential for big wins in financial, technology, and people benefits. is business critical, so IT departments need a way to move to the cloud without disrupting users or sacrificing capabilities. Exchange Online meets this need, giving you the benefits of cloud-based messaging with the features you love about Exchange on- premises. “Enterprise is a complex but essential utility…Offloading this burdensome operation allows IT organizations to focus on solutions that can offer business advantages.” – Larry Cannell, Burton Group

Microsoft Online Services Enterprise software delivered via subscription services and hosted by Microsoft Solutions are dynamic – shrink and grow. Business Productivity Online Suite Slide objective Communicate the breadth, utility, and credibility of Microsoft Online Services. Talking points Exchange Online is part of Microsoft Online Services The Business Productivity Online Suite includes Exchange Online, SharePoint Online, Office Communications Online, and Live Meeting Capabilities include: Financially-backed 99.9% uptime guarantee Datacenter-level, geo-dispersed redundancy Manage everything through easy-to-use Web interface 24/7 phone, & Web support Users today include Autodesk, Coca Cola Enterprises, Energizer, & Pitney Bowes Additional resources Source of quotes on slide:

Exchange Online Offerings
Today’s presentation Standard Dedicated Exchange Exchange Exchange Exchange Slide objective [This is an optional slide – use it if you need to clear up any confusion about which offering is being discussed.] Talking points Exchange Online is offered in two options, Standard and Dedicated. Both are hosted in Microsoft datacenters. The Standard offering provides the core capabilities of Exchange 2007 in a multi-tenant, hosted environment. Because of the standardized nature of this service, customers of all sizes can onboard to the service quickly, using a set of migration tools that we provide for free. This service was launched in Nov 2008. The Dedicated offering provides each customer with dedicated hardware located in a Microsoft datacenter. Dedicated is similar to an on-premises Exchange deployment in terms of its capabilities, and is especially appropriate for customers who have 20,000 seats or more. Both the Standard and Dedicated offerings will be upgraded to Exchange 2010, but the Standard offering is where you’ll see the most changes in the Exchange 2010 timeframe. That is the focus of this presentation. Additional resources You can learn more about the technical capabilities Exchange Online at Multiple customers, one architecture Rapid, standardized deployment All connectivity to hosted environment occurs over public Internet Single customer per architecture Many customization options VPN or dedicated circuit links customer site to Exchange environment

Exchange Online Highlights
Business-class Messaging Simplified Management Anywhere access from a variety of devices Large mailbox sizes with flexible policies Robust collaboration features Unified Web-based administration center Support via phone, Web, and Active Directory synchronization Security and Reliability Deployment Flexibility Slide objective Provide a high-level overview of Exchange Online features and benefits. Talking points Exchange Online provides benefits of cloud-based with the robust capabilities of an on-premises Exchange deployment. Core features of Exchange Server 2007: Anywhere access to mailbox data from PC, Web, and mobile devices. Large mailboxes they can connect to using familiar tools like Outlook. Enterprise-grade collaboration features such as shared calendars, delegates, conference rooms, and distribution lists. Benefits of an online service: Simplified management: Manage settings over the web from a easy-to-use administration portal. IT pro support available 24/7. Synchronize from your local Active Directory to your online environment, to keep it up-to-date automatically. Security and reliability: Exchange Online is hosted out of carrier-class datacenters and includes a premium disaster recovery service that is tested regularly. Built-in Forefront Online Protection for Exchange helps keep viruses and spam from reaching your users’ inboxes. Optional services such as archiving and encryption help meet compliance and privacy needs. Deployment flexibility: A Software-plus-Services approach to cloud computing means that you can choose on-premises software, Exchange Online services, or a mix of both, to suit your organization’s needs. You can set up coexistence between Exchange Online and your local Exchange Server, so you can move some users Online while keeping others on-premises. Migration tools help make the transition to Online smooth, by letting your users take all of their mailbox data with them to the cloud. You can use the deskless subscription to give to your employees with lightweight needs, in cost-effective way. Let’s take a closer look at each of these areas. Geo-redundant datacenter architecture Multi-layered antivirus and spam filtering Archive and encryption services available Coexistence between online and on-premises Comprehensive data migration tools Low cost offering for deskless workers

Business-Class Messaging Anywhere access
Rich client access via Outlook 2003 and later Premium Web experience via OWA Support for a broad range of mobile devices Calendaring Contacts Tasks Company Directory Mobility Offline Access Situation If employees have to learn new user interfaces and change their work practices as part of a move to the cloud, the result would be dissatisfaction and higher support costs. However, because Exchange Online allows users to continue to work as they do now, you have the freedom to “swap out” your back-end infrastructure with minimal disruption. Slide objective Show how Exchange Online enables users to work just as they would with on-premises Exchange. Talking points Anywhere access means that users can connect to their mailbox with a consistent experience across PC, web, and mobile. Exchange Online provides a full-featured Outlook experience without the need for a VPN connection, including features in cached mode such as the offline address book. Outlook Web Access provides a premium online access experience that matches the look and feel of the full Outlook client. Mobile access is available from a wide range of devices that connect directly to Exchange via the ActiveSync protocol. These include Windows Mobile, the iPhone, Nokia devices, and many more. Support for Blackberry devices is also available as an add-on. PCs Browsers Phones

Business-Class Messaging Large mailbox sizes
25GB default allocation per user Mailbox sizes can be customized per user Situation Limited mailbox sizes constrain users, force them to spend more time deleting messages, and can result in the proliferation of archive files. Slide objective Describe how Exchange Online gives customers the benefits of large mailboxes. Talking points Exchange Online provides large mailbox sizes, 25 GB per user by default. Larger mailboxes mean less time cleaning out inboxes, fewer archive files, and easier backup and recovery since there are not multiple files sitting on client hard drives.

Simplified Management Unified administration
Manage subscriptions Provision users Reset passwords Configure services Get help and support View service health Access tools and resources Situation Managing messaging infrastructure can be time-consuming and expensive. Slide objective Show how Exchange Online was designed with simplified administration in mind. Talking points The Web-based administration center, shown here, helps you manage and configure all the components of the Business Productivity Online Suite from one place. A Customer Portal allows you to manage subscriptions, billing, and trial accounts for all of your Online services. In the Online Administration center you can: Set up new users, and provision them with services. Reset user passwords, individually or in bulk, since all services share a unified login experience. Configure settings for each Online service. For example, the section for Exchange administration allow you to manage: Shared contacts, distribution groups, anti-spam settings, conference rooms, and mailbox quota. Open support requests. Follow up on the status of open issues. Check service health, and download tools.

Simplified Management Active Directory synchronization
Directory Sync tool installed on local server Synchronizes on-premises Active Directory with Microsoft Online Simplifies user provisioning Powers unified global address list Situation Active Directory is a crucial piece of the IT infrastructure of many organizations, and making use of the data stored there can make setup and administration of cloud services easier. Slide objective Show how on-premises Active Directory works with Exchange Online. Talking points Setting up synchronization from Active Directory to Online Services lets you leverage the information that’s in your on-premises directory so you don’t have to do administration in two places. The Active Directory Synchronization tool is a free download that you install on a server in your network. The tool syncs any changes made in Active Directory and pushes those changes to the Microsoft Online environment. This means that when you add a new employee, delete a terminated employee, or change contact information, these changes are automatically propagated to the cloud, so you don’t have to do it manually. These items become read-only in the cloud, and you continue to manage them with familiar tools in AD, the same way you do today. The directory sync tool synchronizes changes every 3 hours. To protect your security, it does not sync sensitive information, such as domain passwords. Directory sync also keeps distribution groups and the global address list up-to-date automatically Directory sync plays an important role when you run in coexistence mode between your local Exchange Server and Exchange Online.

Simplified Management Regular service updates
Datacenter staff handles security patches and updates You focus on critical projects instead of routine maintenance Your users have access to the latest capabilities Situation Updating and managing servers is time-consuming and costly, but users need the latest technology to be as productive as possible. Slide objective Show how Exchange Online reduces the burden of updating and provides new functionality automatically. Talking points Our datacenter staff deploys security patches and updates, and rolls out new features and capabilities regularly. Let experts in the datacenter manage your infrastructure, while your IT department focuses on supporting your business’s priorities. Give your users access to the latest technology so they can be more productive—with minimal effort on your part.

Security and Reliability Highly secure, private and reliable e-mail services
Hardware, network, and datacenter redundancy Geographic site resilience Multi-layered data security CyberTrust certified Secure access via SSL Situation Organizations don’t want to “lose control” of security and reliability as they move to the cloud. Slide Objective Demonstrate that security, reliability, and availability of Exchange Online is best-in-class, and often exceeds the what organizations can do on their own. Talking Points A minimum of “n+1” redundancy is used across disk drives, network connections, power sources, etc. Data are replicated to geo-redundant data centers. Software is deployed on the latest hardware and network equipment in carrier-class datacenters. Experts monitor systems around the clock and failover systems are tested regularly. A defense-in-depth security strategy is followed, with best-in-class operational processes. The service undergoes regular third-party testing & certification, including CyberTrust. Forefront Online Protection for Exchange is included to help block malware, spam, viruses & phishing. Exchange Hosted Archive is available for e-discovery and archiving requirements. Mail can be also be journaled to existing archiving solution. Exchange Hosted Encryption available for confidential business communications. Many organizations, when they reflect on questions like, “When’s the last time we tested our disaster recovery plan?” and “Are we confident we could do a mass restore of our data from backup?”, find that Exchange Online provides a higher level of availability and security than they have today.

Security and Reliability Built-in virus and spam protection
z Internet Situation Organizations need robust antivirus and anti-spam solutions in place, to keep their users from being burdened with malicious messages. Slide objective Describe the enterprise-class anti-spam and antivirus capabilities of Forefront that are built into the service and require minimal effort for the administrator to configure and maintatin. Talking points Forefront Online Protection for Exchange is included as part of the Exchange Online subscription, to help block malware from reaching your users’ inboxes. This is an enterprise-class antivirus and anti-spam service. The service uses proprietary anti-spam technology to achieve high accuracy rates. Forefront uses multiple and complementary anti-virus engines help catch -borne viruses and other malicious code. It covers both incoming, outgoing, and internal messages. This helps protect your organization from malicious content that originates from behind your firewall. All of this is built-in to your service. No configuration is necessary to start or maintain the filtering technology. High-accuracy spam filtering Multiple virus-scanning engines Covers inbound, outbound, and internal messages Included with Exchange Online subscription

Deployment Flexibility Coexistence capabilities
HQ Branch Office Slide objective Explain how Exchange Online provides advanced deployment flexibility, by coexisting with on-premises Exchange Server environments Talking points Coexistence capabilities mean you can use Exchange Online in combination with a local Exchange Server to allow some accounts to stay on-premises while others are hosted. All users share the same domain name, see the same global address list, and so on. Coexistence capabilities make it easy to test out the capabilities of online with low risk. These capabilities also make migration to the cloud smoother. You can split your workforce, giving the right messaging services to the right users, in the most efficient way Scenarios: Universities want students in the cloud but faculty on-premises. Airlines want pilots and flight attendants in the cloud but corporate staff on-premises. Banks want their unregulated retail workers in the cloud but the regulated workers on premises. If you have a merger or acquisition, you can onboard the new organization directly to Exchange Online much faster than building out a new on-premises environment. Exchange Online can coexist with Exchange Server on-premises All users share the same domain name and global address list Enables easy pilot deployments and smooth migrations Gives you the flexibility to segment your workforce

Deployment Flexibility How coexistence works
Inbound routes first to on-premises server and then to Exchange Online Directory Sync keeps address lists and groups up to date Wizard-based setup process simplifies deployment Slide objective Explain how coexistence between Exchange Server and Exchange Online works. Talking points Exchange Online includes a comprehensive guide that explains coexistence and how to set it up. Summary of the process: In a coexistence setup, when users are moved to the cloud, they send with the same reply address and domain name that they had on-premises. Your MX mail records in DNS continue to point to your on-premises environment. All inbound mail goes there first, and then mail for users located in the cloud is routed to their Exchange Online mailboxes. Transport Layer Security, or TLS, encrypts the tunnel between your on-premises server and Exchange Online, to help guard against anyone eavesdropping on your internal communications. The Active Directory Sync tool ensures that all users see the same address book, and distribution lists. Wizards simplify the process of setting up coexistence and migrating mailboxes.

Deployment Flexibility Mailbox migration
Free migration tool available Tool is installed on-premises Migrates all mailbox items ( , calendar, contacts, and tasks) Administrator can move users individually or in bulk Supports Exchange 2000+, POP3/IMAP Slide objective Describe the robust mailbox migration toolset for administrators that comes with Exchange Online. Talking points Mailbox migration tool highlights: Select multiple mailboxes in your current environment, and move their complete contents to Exchange Online including mail, appointments, meeting requests, personal contacts, and tasks. Tool updates forwarding addresses so that continues to flow properly during coexistence after a user is moved. Supports Exchange Server versions 2000 and up. A tool for migrating from POP and IMAP based systems is also available. Additional tools from our partners designed specifically for migrating from non-Exchange platforms.

Exchange Online Voice Mail Differences between online and premisise
The good news is Exchange Online UM is almost the same in functionality to the Exchange 2010 on premises UM offering. It offers the following capabilities: Call answering Outlook Voice Access Automated attendant Message Waiting Indicator for on premises phones Text transcription of all voic Play on phone Slide objective Describe the robust mailbox migration toolset for administrators that comes with Exchange Online. Talking points Mailbox migration tool highlights: Select multiple mailboxes in your current environment, and move their complete contents to Exchange Online including mail, appointments, meeting requests, personal contacts, and tasks. Tool updates forwarding addresses so that continues to flow properly during coexistence after a user is moved. Supports Exchange Server versions 2000 and up. A tool for migrating from POP and IMAP based systems is also available. Additional tools from our partners designed specifically for migrating from non-Exchange platforms.

Some of the key differences: Autoattendants with Exchange Online UM are DTMF only. Speech works with on prem Exchange UM only. Directory look-up with Outlook Voice Access is also DTMF only. Speech recognition works with on prem Exchange UM only. Not all UM powershell cmdlets not available such as UMserver cmdlets. Limited support of PBX integrations. Slide objective Describe the robust mailbox migration toolset for administrators that comes with Exchange Online. Talking points Mailbox migration tool highlights: Select multiple mailboxes in your current environment, and move their complete contents to Exchange Online including mail, appointments, meeting requests, personal contacts, and tasks. Tool updates forwarding addresses so that continues to flow properly during coexistence after a user is moved. Supports Exchange Server versions 2000 and up. A tool for migrating from POP and IMAP based systems is also available. Additional tools from our partners designed specifically for migrating from non-Exchange platforms.

Some of the key differences: Autoattendants with Exchange Online UM are DTMF only. Speech works with on prem Exchange UM only. Directory look-up with Outlook Voice Access is also DTMF only. Speech recognition works with on prem Exchange UM only. Not all UM powershell cmdlets not available such as UMserver cmdlets. Limited support of PBX integrations. Best served with Audiocodes/PRI integrations. Slide objective Describe the robust mailbox migration toolset for administrators that comes with Exchange Online. Talking points Mailbox migration tool highlights: Select multiple mailboxes in your current environment, and move their complete contents to Exchange Online including mail, appointments, meeting requests, personal contacts, and tasks. Tool updates forwarding addresses so that continues to flow properly during coexistence after a user is moved. Supports Exchange Server versions 2000 and up. A tool for migrating from POP and IMAP based systems is also available. Additional tools from our partners designed specifically for migrating from non-Exchange platforms.

PBX Integration Example using Audiocodes
Slide objective Describe the robust mailbox migration toolset for administrators that comes with Exchange Online. Talking points Mailbox migration tool highlights: Select multiple mailboxes in your current environment, and move their complete contents to Exchange Online including mail, appointments, meeting requests, personal contacts, and tasks. Tool updates forwarding addresses so that continues to flow properly during coexistence after a user is moved. Supports Exchange Server versions 2000 and up. A tool for migrating from POP and IMAP based systems is also available. Additional tools from our partners designed specifically for migrating from non-Exchange platforms.

3/31/ :57 PM © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

3/31/ :57 PM Enjoy Lunch! © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Voic Enabled by Unified Messaging

Similar presentations

Presentation on theme: "Voic Enabled by Unified Messaging"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Voic Enabled by Unified Messaging

Similar presentations

Presentation on theme: "Voic Enabled by Unified Messaging"— Presentation transcript:

Similar presentations

About project

Feedback