Slide1 l.jpg
This presentation is the property of its rightful owner.
Sponsored Links
1 / 74

Transforming Communications PowerPoint PPT Presentation


  • 109 Views
  • Uploaded on
  • Presentation posted in: General

Transforming Communications . [email protected] Unified Communications Specialist Microsoft Canada. Software Approach Enables Unification. Enterprise Telephony. E-Mail & Instant Messaging. Efficient Controls. Streamlined Experience. Audio Conference. E-Mail &

Download Presentation

Transforming Communications

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Transforming communications l.jpg

Transforming Communications

[email protected] Communications SpecialistMicrosoft Canada


Software approach enables unification l.jpg

Software Approach Enables Unification

Enterprise

Telephony

E-Mail &

Instant Messaging

Efficient Controls

Streamlined Experience

Audio

Conference

E-Mail &

Unified Messaging

Instant

Messaging

Enterprise

Telephony

Conferencing

Video

Conference

Web

Conference

Separate management & experience

Voice Mail

Common Platform


Microsoft unified communications l.jpg

Microsoft Unified Communications

  • Messaging

  • E-mail

  • Calendaring

  • Unified Messaging

  • Communications

    • Instant Messaging

    • Conferencing

    • Enterprise Voice

Identity & presence


Slide5 l.jpg

Microsoft Unified Communications Products and Services

Scenarios

Security and Compliance

E-mail Security, Compliance, and Continuity

E-Mail and Calendaring

Conferencing

VoIP

Conferencing

Unified Messaging

Mobility

IM and Presence

Products

On Premise

Hosted by Microsoft

Delivery

Hosted by Microsoft or by Partners

Hosted by Partners


Slide6 l.jpg

  • Demo


Embed communications in processes l.jpg

Embed Communications In Processes


Improve productivity of developers l.jpg

Improve Productivity of Developers


Three steps to rolling out office communications server l.jpg

Three Steps to Rolling Out Office Communications Server

Reduce interruptions and help your employees find the right people, right away

Lower your costs and reduce travel while increasing collaboration

Provide a more customized telephony infrastructure for mobile workers, tele-workers, and new employees

Provide a more flexible voice experience while reducing your telephony costs once conferencing is in place

Broadly deploy audio, web, and video conferencing while removing your reservation-less audio costs next

Light up your Microsoft Office investments by broadly deploying instant messaging and presence right away


Deploying and migrating microsoft office communications server r2 l.jpg

Deploying and Migrating MicrosoftOffice Communications Server R2


Objectives and takeaways l.jpg

Objectives and Takeaways

  • Objectives

    • OCS 2007 R2 Topology

    • OCS 2007 R2 Hardware and Software requirements

    • Deployment of OCS 2007 R2

    • Migration from OCS 2007 and LCS 2005 SP1

  • Takeaways

    • What are the available R2 Topology options?

    • What has changed from OCS 2007 topology and why?

    • How do I deploy R2?

    • What are migration options from existing OCS 2007 deployments to R2?


Ocs 2007 r2 architecture l.jpg

OCS 2007 R2 Architecture

UC endpoints

Public IM Clouds

ArchivingServer

DMZ

WindowsLive

AOL

OCS 2007 R2 Pool

Data

Audio/Video

Yahoo

  • Workloads:

  • IM/Presence

  • Conferencing

  • Voice

  • UCAS Applications

  • Apps sharing

  • Web Components

SIP

Active Directory

Remote

Users

Backend

SQL server

Front-End

Server(s)

Edge

Servers

CommunicatorWeb Access

Advanced

Media GW

Group Chat

Exchange

2007 Server UM

Federated

Businesses

(Mediation

Server)

Voicemail

Monitoring Server

PSTN


Standard edition deployment l.jpg

  • Ideal for

Standard Edition Deployment

Proof of Concept/Pilot

Branch Office

  • Functionality

  • IM, Presence, Peer-to-peer Voice, Conferencing

  • No External Access, Not Highly Available

  • PSTN requires Mediation Server

AD

  • Server Roles

  • Co-located on one server

    • Presence, IIS Share, Conferencing, A/V

Standard Edition

  • Scalability

  • 1 Server

  • Up to 5,000 users


Enterprise edition consolidated configuration l.jpg

  • Example Deployment

Enterprise EditionConsolidated Configuration

Medium Size Business

Regional Deployment

  • Functionality

AD

  • IM, Presence, Peer-to-peer Voice, Conferencing

  • Highly Available, Medium Scale

  • No External Access

  • PSTN requires Mediation Server

  • Server Roles

SQL

Enterprise Edition Front-End Servers: Consolidated

  • Scalability

  • 5 Servers

  • Up to 100,000 users

IIS Share

Audio/Video

Presence

Conferencing


Enterprise edition expanded configuration l.jpg

  • Example Deployment

Enterprise EditionExpanded Configuration

Large Enterprise

Central Datacenter

  • Functionality

AD

  • IM, Presence, Voice, Conferencing

  • No external access, No PSTN

  • Server Roles

Enterprise Edition Front-End Servers: Expanded

Active

Passive

  • Scaled-out across servers

  • High Availability, High scale

  • Scalability

A/V Conferencing Servers

Web Conferencing Servers

  • 14 Servers

  • Up to 125,000 users

IIS Servers

Enterprise Pool: Expanded


R2 topology l.jpg

R2 Topology


R2 topology18 l.jpg

R2 Topology


Recommended r2 topology l.jpg

Recommended R2 Topology

  • Enterprise Consolidated topology

    • Primary supported topology

    • Consolidated Edge Server

    • New Monitoring Server (CDR and QoE)

    • Dedicated Archiving Server

  • Motivation for Consolidated topology

    • Simplify OCS deployment

    • Fewer, more powerful systems (64 bit)

    • Co-locate server roles

    • Requirements for CDR, Archiving, and QoE

    • Maintain flexibility


Secondary topologies l.jpg

Secondary Topologies

  • Standard Edition (single server)

    • Distributed with SQL Express 2005 SP2 (SP3)

  • Expanded Enterprise Edition

    • Supported - Command line only setup


Software requirements l.jpg

Software Requirements

  • OS - x64 only

    • Windows Server 2003 x64 SP2

    • Windows Server 2008 x64

  • SQL 2005 SP2 (SP3) and SQL 2008

  • AD Forest/Domain level: Windows Server 2003 and 2008

  • Exchange UM: Exchange 2007 SP1 or the next version of Exchange

  • Virtualization support – limited support (post RTM)

    • Hyper-V on Windows Server 2008


Office communicator 2007 r2 l.jpg

Office Communicator 2007 R2

Rich Unified Communications client providing an intuitive, easy to use interface that brings together the communications experience

  • Rich presence, Contacts, Instant Messaging

  • Powerful phone features

  • Escalation of modalities -- IM, voice, video, conferencing

  • Integration with Office Applications

  • Rich device support

  • VPN less remote access

New in R2!

  • Usability Improvements

  • Voice mail integration

  • Team Ring & Delegation

  • Audio Conferencing

  • Desktop Sharing

  • HD VGA support

  • Part of premium Office 2007 editions

    • Office Professional Plus

    • Office Enterprise

  • MSI driven setup

  • Roll out Communicator 2007

    • SMS package

    • Desktop deployment wizard

  • Client settings are auto configured


Live meeting client l.jpg

Live Meeting client


Hardware recommendations for enterprise edition l.jpg

Hardware Recommendationsfor enterprise edition

  • Front-end server

    • x64 Dual Quad-Core CPU, or 4 way Dual-Core CPU

    • 8 GB Memory

    • 10K rpm disk drives

  • Back-end SQL server

    • x64 Dual Quad-Core CPU, or 4 way Dual-Core CPU

    • 16 GB Memory

    • 10K or 15K RPM disk drives (multiple spindles)

  • Other servers

    • use Front-end or Back-end spec as appropriate


Impact of r2 changes l.jpg

Impact of R2 Changes

  • x64 capable hardware required

  • x64 OS required

  • Migration options

    • Side-by-Side migration

    • Export data – new install option

  • Existing Expanded topology deployments may want to migrate to consolidated topology

  • Exchange UM: Exchange 2007 SP1 required

  • Deployments on Windows 2000 AD forest/domain to move to Windows 2003 minimum level


Choosing r2 topology l.jpg

Choosing R2 Topology

* Final scale numbers to be published at R2 release


Deployment planning l.jpg

DeploymentPlanning

  • Features required

    • IM/Presence, Peer-to-peer audio/video, HD Video

    • Group chat

    • Enterprise Voice (Standalone or Co-existence), Response Group Service, Delegation, Attendant Console

    • Conferencing, Dial-out PSTN Conferencing, Reach Application Sharing

    • External Access (Edge)

    • Compliance requirements for IM and Conferencing

    • Voice/Media quality monitoring


Deployment planning28 l.jpg

DeploymentPlanning

  • Site Analysis

    • How many sites?

    • How many users in each site?

    • What features are needed per site?

    • What is the usage model for features at a site?

    • Do you require High Availability?

    • Compliance requirements for IM and Conferencing

    • What is the bandwidth available at each site?

  • Deployment Path

    • Migration or new deployment? Which version LCS 2005 SP1 or OCS 2007?


Voice and video interoperability for microsoft office communications server 2007 r2 l.jpg

Voice and Video Interoperability for Microsoft Office Communications Server 2007 R2


Slide30 l.jpg

  • Software-powered VoIP Architecture

  • Deployment Scenarios

Build Foundation

  • Build Foundation

  • Single identity with Active Directory

  • IM and presence with OCS

OCS 2007 Co-Existence

OCS 2007 Co-Existence

Add software-powered VoIP with OCS 2007

Keep legacy phone

  • OCS 2007 Stand-Alone

  • Add software-powered VoIP with OCS 2007

  • Unified Messaging with Exchange Server 2007

  • Replace legacy phone

OCS 2007 Stand-Alone


Slide31 l.jpg

Software-powered VoIP Architecture

Deployment Scenario – OCS 2007 Co-Existence

  • Simultaneous ringing on Office Communicator and legacy phone

  • Provide interoperability with PBX systems

  • Users have both, Office Communicator and legacy phone

  • Make use of PBX legacy capabilities

  • Receptionist and boss-admin needs

  • Emergency call requirements

  • Analog lines (e.g. fax machines)

  • Voicemail

OCS 2007 Co-Existence

Existing

PBX

Mediation

Server

OCS 2007

Inbound Routing

Outbound Routing

Voice Mail Routing

SIP/PSTN

Gateway

IM, Presence,

Audio, Video, Conferencing, IVR

SIP


Slide32 l.jpg

Software-powered VoIP Architecture

Deployment Scenario – OCS 2007 Stand-Alone

  • Migrate teams or departments to software-powered VoIP

  • Typically information or mobile workers

  • None VoIP users haveIM and presence

  • Supports standardPBX migrationprocedures

  • Common PBX network interfaces

  • PBX numbering plans

  • No PBX upgrade required

OCS 2007 Stand-Alone

Existing

PBX

Mediation

Server

OCS 2007

Inbound Routing

Outbound Routing

Voice Mail Routing

SIP/PSTN

Gateway

IM, Presence,

Audio, Video, Conferencing, IVR

SIP


Slide33 l.jpg

Centrex architectureLogical view: Hosted Centrex Solution

Centrex

PBX

Enterprise

Carrier

PRIs

Ext. 14

PSTN

Ext. 12

  • Centrex Switch is hosted on Prem and being fully managed by Telco

  • A new PRI could be provisioned by Telco and programmed to CF DN from Centrex services into a new PRI


Slide34 l.jpg

Centrex architecturePhysical view: Architecture

PSTN

PRI Link

+403 xxxxxxxx

Enterprise

Carrier

Centrex

PBX

Ext. 14

M

U

X

M

U

X

PSTN

Ext. 12

  • From a physical perspective, I assume, a PRI link is being used and on each side is a Multiplexer installed that splits up the PRI into connections for the extensions

  • The NET GW could be plugged in in front of MUX and it will do AD look up to identify DN as a Centrex or OCS.


Slide35 l.jpg

Centrex architecturePhysical view: Architecture

PSTN

Copper twisted pair over Fiber

+403 xxxxxxxx

Enterprise

Carrier

Centrex

PBX

Ext. 14

M

X

M

U

X

PSTN

Ext. 12

  • From a physical perspective, there is no Multiplexer installed that splits up the PRI into connections for the extensions

  • Requires to order new PRI and order re-direct services from Bell


Choice of endpoints l.jpg

Choice of Endpoints

Video

Interoperability

PC & USB

Devices

Phones

Software-powered VoIP


Microsoft s real time c odecs rtaudio and rtvideo l.jpg

Microsoft’s Real-Time CodecsRTAudio and RTVideo

  • Supports Wideband and Narrowband modes

    • Wideband greatly improves intelligibility and naturalness of speech

  • Constant and Variable bit rate modes

    • Dynamically responds to changes in audio complexity

  • Highly efficient use of Bandwidth

    • More quality at equivalent bandwidth

    • Same quality at lower bandwidth

  • Multi-rate codec

    • Enables real-time adaptation


Slide38 l.jpg

Evidence of Better Quality of Experience

3rd party study shows superiority across network conditions

Mean Opinion Score (MOS)

5.0

4.0

3.0

2.0

Perfect quality network

Typical enterprise network

~2.5

Overloaded enterprise network

~2.2

~1.6

Multisite connectivity

RTAudio

(wideband)

~1.4

RTAudio

(narrowband)

Internet conditions

IP Telephony

(G.711)

Source: benchmarking study performed by Psytechnics Ltd in December 2006

http://www.psytechnics.com/downloads/VoIP_benchmarking_report.pdf

IP Telephony

(G.729)

Typical MOS interpretation: 1=bad, 2=poor, 3=fair, 4=good, 5=excellent


Polycom components in an office communications server 2007 topology l.jpg

Polycom Components in anOffice Communications Server 2007 Topology

RMX 2000™ ConferencingServer

OfficeCommunications Server 2007

H.323

CX700

CX200

H.323

Gateway

PSTN

PSTN

Gateway

CX100

Voice Gateway

ExchangeServer 2007

ActiveDirectory

Traditional PBX

HDX 4000™

HDX 8000™

TraditionalPhones


Polycom phones for office communications server 2007 l.jpg

Polycom Phones for Office Communications Server 2007

The Polycom CX line of Office Communications Server 2007 enabled products

CX100 Speakerphone

CX200 Desktop Phone

CX700 IP Phone

A total end to end VoIP solution sale:

Microsoft servers and applications

Polycom endpoints

Polycom Quality

Brand integrity

Superior high definition voice technology

Polycom Worldwide Sales Channel

Large enterprise account presence

Industry leading distributor partners

VoIP sales expertise

Superior service, training and support

CX700

CX200

CX100


Cx700 polycom ip phone for microsoft l.jpg

CX700: Polycom IP Phone for Microsoft

Standalone IP telephone

Connects to Office Communications Server 2007

Microsoft® Windows CE device

Office Communicator 2007 embedded

High definition voice

Full duplex speakerphone with Handset and headset modes

Advanced user interface

5.7” color touch screen

Presence status LED

Contact directory integration – click to call


Polycom usb phones for microsoft l.jpg

Polycom USB Phones for Microsoft

CX100 Speakerphone, CX200 Desktop Phone

Integrated with Office Communicator 2007

Buttons and indicators extend client interface to familiar phone device

USB 2.0 Peripheral devices

True plug-and-play; no additional software or drivers to install

Powered via USB port

High definition voice

Full duplex speakerphones

Rich voice experience


Polycom solutions l.jpg

Polycom Solutions

Video Endpoints

Partner Integrations

Media Servers & Conference Platforms

Management &Scheduling

Video Recording, Streaming & Content Management

Security & NAT/FW Traversal

43


Polycom interop implementation l.jpg

Polycom Interop Implementation


Anywhere access l.jpg

Anywhere Access


Anywhere access similar experience from desktop to mobile devices l.jpg

Anywhere AccessSimilar experience from desktop to mobile devices

Microsoft® Office Outlook® 2007

Microsoft® Office Communicator 2007

Microsoft® Office Outlook® Mobile

Microsoft® Office Communicator Mobile

Exchange Server 2007

Office Communications Server 2007

Microsoft® Office Outlook® Web Access

Microsoft® Office Communicator Web Access

Microsoft® Office Outlook® Voice Access

Microsoft® Office Communicator Phone Edition


Microsoft mobility vision l.jpg

Microsoft Mobility Vision

LOB Applications

E-Mail

Access Control

Intranet Web Applications

Managed PC

Team

Workspaces

Unmanaged PC

(Home PC, Kiosk, etc)

Documents

& Files

Instant

Messaging

Firewall

Mobile & Traditional Devices

Web & Video Conferencing

Calendaring


Microsoft s unified communications innovative mobile experience l.jpg

Microsoft’s Unified CommunicationsInnovative Mobile Experience

Office Communicator for Windows Mobile

Presence and Location

Corporate address book

Secure IM


Mobility overview exchange server 2007 security and mobility l.jpg

Mobility OverviewExchange Server 2007 Security and Mobility

External Web Server

Exchange

Users

  • Secured by default with SSL:

    • Outlook Anywhere, Exchange ActiveSync, and Outlook Web Access

    • Self-signed certificate installed out of the box

    • Deploy Windows Certificate Services

    • Use a third-party PKI product or CA

  • Remote device wipe

  • Device password policies

DMZ

Internal Network

Internet

Active Directory

HEAD QUARTERS

External traffic secured with SSL and authentication


Ocs 2007 r2 architecture50 l.jpg

OCS 2007 R2 Architecture

UC endpoints

Public IM Clouds

ArchivingServer

DMZ

WindowsLive

AOL

OCS 2007 R2 Pool

Data

Audio/Video

Yahoo

  • Workloads:

  • IM/Presence

  • Conferencing

  • Voice

  • UCAS Applications

  • Apps sharing

  • Web Components

SIP

Active Directory

Remote

Users

Backend

SQL server

Front-End

Server(s)

Edge

Servers

CommunicatorWeb Access

Advanced

Media GW

Group Chat

Exchange

2007 Server UM

Federated

Businesses

(Mediation

Server)

Voicemail

Monitoring Server

PSTN


Ocs edge server firewall policy l.jpg

OCS Edge Server Firewall Policy


Migrating to ocs 2007 r2 l.jpg

Migrating to OCS 2007 R2


Primary migration option l.jpg

Primary Migration Option

  • Side-by-Side migration

    • Deploy R2 Pool in parallel to existing OCS 2007 deployment

    • Move users gradually to R2 pool

    • Validate R2 deployment

    • Decommission OCS 2007 servers

  • Minimal Service outage

  • Additional hardware required

  • Recommended for Enterprise deployments


Alternate migration option l.jpg

Alternate Migration Option

  • Export data – new install option

    • Export user’s buddy list data with DBImpExp.exe utility

    • Deploy OCS 2007 R2

    • Import buddy list back in with DBImpExp.exe utility

  • Service outage

  • May not require additional hardware

  • Existing hardware to meet recommended minimum

  • Recommended if no additional hardware is available, or service outage is acceptable


Client migration overview l.jpg

Client MigrationOverview

  • Migrate OCS first

  • Client Migration overview

    • Older clients work with newer server (N-1 Client support)

    • All existing client features will work with upgraded server

    • New features (for example Attendant Console) require client and server to be upgraded

  • Client migration strategy

    • Migrate server components first

    • Move users to R2 pool

    • Migrate clients


Client migration additional considerations l.jpg

Client MigrationAdditional considerations

  • Internal and external users

    • User may have older clients on notebooks, or on home PCs

  • Multiple-Points of Presence (MPOP)

    • Migrate all clients and enforce client version on server

  • Special scenarios

    • Special cases and interoperability restriction may apply

    • Full client and MPOP matrix will be available

    • New features for external users require upgraded Edge and Director


Lcs 2005 sp1 migration l.jpg

LCS 2005 SP1 Migration

  • LCS 2005 SP1 can coexist with OCS 2007 R2

  • Outside-In migration

    • OCS 2007 R2 Edge compatible with LCS 2005 SP1 pool

  • Move-User to migrate users

    • Migrate clients (Multiple Points of Presence restrictions)


Active directory schema changes l.jpg

Active Directory Schema Changes

AD

OCS 2007 R2schema

OCS 2007 schema

LCS 2005 SP1

Pool

OCS 2007

Pool

OCS 2007 R2

Pool


Side by side migration full side by side l.jpg

Side-by-Side MigrationFull side-by-side

OCS 2007 Clients

Auto config

OCS 2007

Pool

OCS 2007

Director

OCS 2007

Edge

Existing public IP-DNS, public Cert

OCS 2007 R2

Pool

OCS 2007 R2 Clients

Manual config

OCS 2007 R2

Director

OCS 2007 R2

Edge

Additional public IP-DNS, public Cert


Side by side migration inside out migration l.jpg

Side-by-Side MigrationInside-out migration

OCS 2007

Pool

OCS 2007

Director

OCS 2007

Edge

OCS 2007 R2

Pool

OCS 2007 R2

Director

OCS 2007 R2

Edge

Move

Users


Side by side migration migrate edge l.jpg

Side-by-Side MigrationMigrate edge

OCS 2007 Clients

Auto config

OCS 2007

Edge

Existing public IP-DNS, public Cert

OCS 2007 R2

Edge

Existing public IP-DNS, public Cert

OCS 2007 Clients

Auto config

Migrate clients

OCS 2007 R2 Clients

Auto config


R2 migration of other components ocs components outside the pool l.jpg

R2 Migration of other componentsOCS Components outside the pool

  • Mediation Server

    • R2 Pool and Edge compatible with OCS 2007 Mediation Server

    • R2 Mediation Server compatible with OCS 2007 Pool and Edge

  • Communicator Web Access (CWA)

    • Side-by-side migration only (from CWA 2007, CWA 2005)

    • OCS 2007 users must use CWA 2007 browser URL. R2 users must use CWA R2 URL.

    • URL Redirection for 2007 or 2005 users hitting R2 URL

  • Archiving/CDR/QoE

    • R2 split roles into Archiving and Monitoring (CDR/QoE)

    • Changed schema does not allow data migration


Takeaways ocs 2007 r2 l.jpg

TakeawaysOCS 2007 R2

  • New server roles

  • Available Topologies

  • Hardware and Software requirements

  • Planning and Deployment

  • Migration strategies


Migrating to exchange 2007 l.jpg

Migrating to Exchange 2007


Deploy l.jpg

Deploy

Flexible deployment by Server Role

Setup wizard for installation and configuration

Automated server provisioning available through Windows PowerShell scripting


Deploy flexible server role topology l.jpg

Deploy – Flexible Server Role Topology


Built in protection continuous replication now in three flavors l.jpg

Built-In ProtectionContinuous Replication - Now In Three Flavors!

New

FileShare

DB/Logs

Standby

Local

DB/Logs

Replication to a standby server

Replication to a second disk set

Logs

DB

Logs

DB

  • Designed for site resilience

    • Replicated on per-storage group basis

    • Source and destination can be a single mailbox or cluster (LCR)

    • Manual failover

Cluster

DB

Logs

DB

Logs

Replication within a cluster


Built in protection scr adds site resilience to ccr deployments l.jpg

Built-In ProtectionSCR Adds Site Resilience to CCR Deployments

CCR offers high availability or site resilience:

Primary Datacenter

Standby Datacenter

Primary Datacenter

  • CCR Cluster

  • CCR Cluster

Regular CCR for high availability

Stretched CCR for site resilience

Adding SCR to a CCR deployment provides complete coverage:

Primary Datacenter

Standby Datacenter

CCR cluster in primary datacenter provides high availability

SCR copy in standby datacenter provides site resilience

  • CCR Cluster


Operational efficiency optimized for performance and scalability l.jpg

Operational EfficiencyOptimized for performance and scalability

  • Simplified server routing

  • Fast and accurate search

  • Native 64-bit architecture

    • Superior performance

    • Improved storage efficiency

64-bit by the numbers

32-bit = 232 or 4 gigabytes of addressable memory

64-bit = 264 or 16 exabytes of addressable memory


Edition comparison l.jpg

Edition Comparison

E2003 Server Editions

Standard Edition

2 databases

72 GB storage

Enterprise Edition

20 databases

Clustering

E2007 Server Editions

Standard Edition

5 databases

No storage limit

Upgrade to EE w/o reinstall

Enterprise Edition

50 databases

Clustering

Customer

  • Orgs with high scalability requirements

  • Large number of users

  • Large mailbox deployments

  • Clustered environments

  • Orgs with limited scalability requirements

  • Fewer users

  • Lower requirements for mailbox size


Legacy co existence l.jpg

Legacy Co-existence

Exchange 2007 Client Access servers can connect to Exchange Server 2000 and 2003

Exchange 2007 Hub Transport servers can route e-mail to Exchange 2000 and 2003

Exchange 2007 Public Folder database is required to share free\busy information with pre-Outlook 2007 clients


Mailbox migration l.jpg

Mailbox Migration

Single migration engine for all mailbox moves

Manage and migrate Exchange Server 2003 mailboxes from the Exchange 2007 Management Console

Script migrations with the Exchange Management Shell


Slide74 l.jpg

© 2008 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.Theinformation 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. The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious.  No association with any real company, organization, product, domain name, email address, logo, person, places, or events is intended or should be inferred. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.


  • Login