Exchange 2010 Roadmap Series: Transition and Migration Sponsored by Dell, Inc. and Intel

Speakers: Patrick Devine and Lee Benjamin

Patrick Devine: Hello, and welcome to a searchexchange.com presentation, ‘Exchange 2010-Roadmap Series - Transition and Migration’. My name is Pat Devine, and I am the moderator for today’s presentation. Joining me today is Lee Benjamin, messaging architect at ExchangeGuy Consulting. Lee is a recognized Exchange expert, acknowledged by Microsoft for his technical knowledge and community involvement as an Exchange MVP. Before we begin the presentation, I would like to review a few housekeeping items with you. The slides for this presentation will be pushed to your screen automatically. If you have any questions throughout the presentation, you can type them into the ‘Ask A Question’ area, which is located on the right side of the viewing console and they will be addressed at the end of the presentation. If you have any difficulty reading or viewing slides, there is an ‘Enlarge Slide’ button that you can click on which is located just below the slides. And if you experience any technical difficulties with this presentation, there is a ‘Help’ link that you can click on which is located on the lower right hand corner of your screen. With that said, I am now going to turn over things over to Lee to begin today’s presentation. Lee, take it away. Lee Benjamin: Thank you very much, Patrick and very welcome everybody. We are going to talk a little bit about Exchange 2010 today. I am sitting in Las Vegas where one of the two cities that Exchange has just been launched in and we are going through a part of series that we are running with Citrixchange.com, talking about Exchange 2010 Roadmap if you will to get them up and running on a number of different areas.

Exchange 2010 Roadmap Series� Roadmap Series Titles

� Transition and Migration

� Availability and Recovery

� Performance

� Virtualization

� Roadmap Agenda

� Roadmap For Topic

� Exchange 2010 Architecture

� New and Changed Features

� Explore Scenarios

We are going to cover transition and migration today and we will also in the series talk about availability and recovery about performance and about virtualization for Exchange 2010. Our basic agenda for each of the roadmap sessions will be talking about very quick roadmap for the topic. Talking about 20-channel architecture as it applies to the future, the future is that for the topic we will talk about specific new Exchange features that really relate to the topic and then we will explore some scenarios depending on the topic itself. Patrick cut some band here if necessary. I am here and we are looking at feedbacks though I don’t know if you are, if necessary let me know and we will start over. Let’s move along. Our agenda for today is pretty much as described. We will look at Exchange 2010 architecture as it applies to the transition and migration, how do you get from Exchange 2007 or Exchange 2003 or potentially other versions or earlier versions of Exchange may be lotus notes, dominoes or other messaging platforms and then we will go through some of those specific scenarios.

Agenda

� Roadmap to Exchange 2010

� Exchange 2010 Architecture

� New and Changed Features For Transition and Migration

� Transition and Migration Scenarios

So first thing we need to do is clearly understand a little bit of technologies. There is no upgrade in place for Exchange 2010. There are different reasons for this. For those of you who are coming from Exchange 2003, that was a 32-bit operating system windows server 2003 and there is no way to upgrade a 32 bit OS to 64 bit OS. Now for all the database changes over the last number of versions, again as the Exchange database that you are now familiar with, has moved up to a 64-bit database, so that is hard to do as well and leaving all server alone minimalizes any chances for security weaknesses that may have gone over the years. So we have two words that we are going to use in order to talk about moving from one version of Exchange to another massive transition and migration.

Roadmap to Exchange 2010

• Can’t Upgrade From 32bit OS to 64bit OS

• Database Changes Version to Version

• Potentially Leaves Security Weaknesses

No Upgrade In-Place

• From Existing Supported Exchange Version

• Keeping Same Organization Name, Same AD

• Utilize Move Mailbox, Stay ConnectedTransition

• From Unsupported Exchange Versions

• From Notes/Domino and Other Systems

• Pull Old Data Out, Insert Into Exchange 2010Migration

Transition is reusing an existing supported Exchange version, we are going to keep the same organization name, active directory is the same and we can then utilize mailbox capability of those of you have upgraded from Exchange versions before, you are familiar with this, what is new is moving from 2007 to 2010 as there now some functionality called the online mailbox move or online move mailbox and that allows user to actually to be connected and stay connected in the middle of the day moving even a very large mailbox where the mailbox will actually get moved while the user is online and only at the very end of the move mailbox process will they be disconnected for a short period of time just probably a minute or so I mean automatically reconnected when those last bits that they were working on will actually get moved to the new mailbox, anyway that is a neat piece of functionality.

Exchange Server RolesExchange 2003/2000� 1. Front-End Server

� Optional

� SMTP, POP3/IMAP4

� HTTPS

� Outlook Web Access

� Exchange ActiveSync

� Hygiene (AV/AS)

� 2. Back-End Server� Mailbox Databases

� Routing

� MAPI/Outlook

� Includes Front-End

Exchange 2007 and 2010

� 1. CAS – Client Access Server

� 2. HUB – Hub Transport Role

� 3. MBX – Mailbox Role

� 4. UM – Unified Messaging� Voicemail, Voice Access

� These Four Roles ‘Can’ Be Combined

� 5. EDGE- Edge Transport Role � Routing and Hygiene

� Lives Alone

Migration, on the other hand and we will go through the specific version as we move along, would be from an older version of Exchange, so Exchange 2005 if anybody still have their earlier version, I would not be a little surprised but only ones and twos are higher up there. There also lots of people with Exchange 2000 and there are some tricks actually to make that into, turn that into a supported transition approach and we will go through this. Coming from notes, Domino or other mail systems that would be a migration as well and what migration is about is really pulling all the old data out, putting it into perhaps some internal files or using that utility and stuffing that data into the Exchange 2010 database, so it is a fair amount of work, there are tools previous Microsoft had tool to help people with that and there is third party tools as well and as the third party tools are being updated for Exchange 2010.

Exchange 2010 Architecture

ExternalSMTPservers

MailboxStorage of

mailbox items

Edge TransportRouting & AV/AS

Unified MessagingVoice mail & voice access

Phone system (PBX or VOIP)

Client AccessClient connectivity

Web services

Hub TransportRouting & Policy

Web browser

Outlook Anywhere

(remote user)

Mobile phone

Outlook (local user)

Line of business application

So what is that, when we talk a little bit about Exchange server roles, I know that I have a mixed audience here today, so we are going to talk about those who are running Exchange 2003 and 2000 and then we will talk about the roles of Exchange for 2007 and 2010. So talking about 2003 and 2000 time frame, they were basically two roles for Exchange server. There was the front-end server role that was an actually optional role, you can split off the front end server, that would run intermittent standard protocol, so SMTP, POP3, IMAP4 and those protocols could come in through the front-end server, also HTTPS, so a lot of the traffic coming in for Outlook web access or perhaps the Exchange ActiveSync and those would come in through Port 443 Secure Web into the front-end server. Front-end server as well as sometimes use for hygiene anti-virus and anti-spasm for protecting your SMTP world as that came in, the other role was the back-end server and the back-end server would host the mailbox database on the mailbox database and the public folder database and other databases, it will also handle routing and MAPI and Outlook actually connected directly to the back-end server and that put a fair load on the back-end server with mailboxes and by the way of back end server includes all functionality of a front-end server. So those were the two roles that existed now, if you are like me and have managed meeting an enlarged Exchange organizations, we will come up with our other roles if you will, but really those were just specific of designation. I have a front-end server here it is going to handle all of my SMTP traffic; I am going to have another front-end server that only handles quite of WA traffic. I may have a mailbox server which is acting a HUB transport, sort of an official HUB didn’t exist, just a word of HUB for routing between different Exchange routing group sites for different locations. Now with Exchange 2007, a very large change was brought in to erase or to apply those roles as well as and juggle them around a little bit, and there was CAS client access server and that is the role where

all again internet protocols come into, HUB transport which is really about routing messages or moving routing out of the mailbox server and out of the back-end server into the HUB transport or a mailbox server role which could function and only specialize in handling all mailbox connections and providing the database information to end users and to the other processes.

Client Access Server Role (CAS)

Mid

dle

Tie

r

Exchange

Biz Logic

Ma

ilb

ox MAPI RPC

Store

Exchange Components

OWA

SyncUM

Transport

Agents

Mailbox

Agents

WS

Entourage

Outlook /

MAPI clients

DAV

Mid

dle

Tie

r

MAPI,

RFR &

NSPI RPC

Exchange Core Biz Logic

Exchange

Biz Logic

Ma

ilbo

x

MAPI RPC

Store

Exchange Components

OWA

SyncUM

Transport

Agents

Mailbox

Agents

WS

Outlook /

MAPI clients

Entourage

There is the unified messaging role which is an optional role, but way to include the voice mail interpretation and voice access between PBX and internal IP based PBX or through a gateway but allows you to have your voicemail inside of your inbox now. Now those were roles quickly combined, we combined them into your depending on your needs and the size of your organization. They can also run separately on different servers, different computers. Now, there is one additional role which is an optional role as well and that was the EDGE transport role. The EDGE transport role runs on its own machine, was really designed using the perimeter and it will handle routing and message hygiene.

Client Access Server

� CAS Now Handles All Client Communication

� Not Just Internet Protocols

� New RPC Client Access Service

� Moving MAPI/Outlook To CAS Is Significant

� Large Processing Load Off Mailbox Role

� Also Web Services For Entourage and Biz Apps

� Need To Plan For Additional Cores and Memory

We will talk a little bit littler later, this will stand alone; some organizations were on the HUB transport as their connection to the internet was solely supported in configuration as well. OK, here’s the architecture slide and we sort of want to review this because this brings everybody up to speed what 2010 architecture looks like from a high level perspective, so starting up at the upper left hand corner where we are looking at external SMTP servers. External SMTP servers come in through firewall, typically in organizations what have dual firewall and some level of perimeter protection for their message system, of the EDGE transport as we described providing routing and antivirus, anti-spam, also providing understanding how the users inside the organizations that mail should be accepted for. The edge talks to HUB transports with inside the organization of transports handle routing and also policy that is HUB transports can look at messages and act on messages with transport rules and other functionality. The HUB transports would talk to other HUB transports, also to the mailbox servers and for storage for mailbox and public folders databases if you are still using public folders. The unified messaging role off to the right, voice mail and voice access, all connected up to online PBX or voiceover IP PBX or voice over IP system, might be an existing system you have, may be that supports IP, voice over IP, may be it is we have a gateway in there that talks to an older PBX and now also there would be Microsoft office communication server which provides lots of additional unified communication as capabilities including voice over IP and enterprise voice.

Message Routing

� All Traffic Routes Through HUB Transports

� Routing Topology Is Active Directory Sites

� No Longer Exchange Routing Groups

� Larger AD Topologies May Require Work

� EDGE Designed for Perimeter

� Hardened SMTP, Protects AD with EdgeSync

� Anti-Virus and Anti-Spam on Periphery

� However, HUB Can Be Configured Direct To Internet

� CPU and Memory Are Key, Minimal Disk

� Add Redundancy With Additional Servers

The role of the client access server down below, the client access server handles traffic coming in from the internet, mobile phones, web browsers but also Outlook anywhere previously called RPC or HTTPS but basically packaging up packets from Outlook so that they are secure with SSL coming in over the internet. And those were coming in and talk through a firewall and perhaps a proxy firewall in order to put some additional protection there but we would talk directly to the client access server, internal also talk to the client access role and people are building across business applications and we will just touch on those briefly. So about the high level, we will review the Exchange. Let us talk about some of the key new and changed features for transition and migration. The biggest one and this is Exchange for the Exchange 2007 as well as the Exchange 2003 folks. So 2003 would be coming from the backend and front-end environment but 2007 as well where the Exchange components, the internet based Exchange components would come in and talking through the client access server that is the Exchange business logic with the middle tier that we are looking at on the left hand side of the screen. But outlook and MAPI clients are also large clients, Outlook and MAPI clients, Outlook or MAPI clients. We talked in and they are likely to restore that is to the mailbox roles and mailbox server and MAPI and RPC was hosted on that server. So those plans were actually popped to the back-end server in the 2003 environment or the mailbox server role in the 2007 environments. After entourage from the Macintosh talked web DAF and web DAF was also directly on the mailbox server roles, stored as EXE. With Exchange 2010, there is a big shift here and it is a good one, but it does have performance implications that everybody needs to deal with, designing their systems. So we have the existing CAS clients components but we also have work services, WS. And so the new rational entourage, the newest version of entourage for the Macintosh does not talk web DAF anymore it talks work services, so connects to an client access server.

The big change here bigger than that because this is most of your internal users, Outlook and MAPI clients now talk to the middle tier layer or talk to the CAS, so all of the MAPI functionality all over resides directly on the store but actually the endpoint, the NSPI in a network server provides random phase, what Outlook looks for to connect to is now client access server and this is really good because it says you can scale up connections separately scaling up the mailbox environment. So the CAS in talking to the store is more efficient in its connection and what it can do but handling lots and lots of MAPI connections for organizations that have many, many Outlook clients can actually skill using basically adding additional CAS servers and can do that and scale that separately from the mailbox store. Now within the CAS, so have talked about this large CAS handles all the client communications, the not so standard internet protocols, the new big piece in here is what is called the RPC client access servers. So the thing that you need to really think about is are mailbox servers getting very, very busy and in order to move some of that load, that load has now moved over to the client access servers. Those of you who were coming from 2003 environment, you need to just be aware of that as you are architecting and that is the client access plate instead of talking directing to the mailbox server. For those of you who have already deployed Exchange 2007, recognized it in moving it to Exchange 2010 the load on the client access server will be greater than it was before, so that if you are looking at hardware, those servers they require that they moved up, you are going to look at additional cores and additional memory but also the way of scaling those is getting the end user and these are some boxes, they don’t have need for much storage and therefore they are sort of you know to you kind of boxes 1 and 2 U kinds of sometimes called pizza boxes, add additional ones and we are going to load balancing of one sort or another, in order to scale those. Message routing all happens through the HUB transport servers. HUB transports are really about moving the mail from one server to another but also moving down within a single server and there were lots of good compliance reasons and channeling reasons and archive reasons in order to make that happen. So when you install an Exchange mailbox server by the very nature you must have at least a single CAS and a single HUB in order to go along with that message that mailbox server. Routing topology has shifted. The routing is now active directory sites, no longer using Exchange routing groups, some of the larger AD topologies may require some work in order to make the message slow but the way that they have sites setup for little bit of work, its not that complicated but it needs to be designed and thought out. EDGE is really a new server role introduced in 2007, really designed for the perimeter, if you will forgive the analogy; it is not your father’s Exchange server, your grandfather’s Exchange server anymore. It is a hardened SMTP version of Exchange with lots of functionality that does not need to be there and it is not there and it really is designed to handle just routing in and out for the organization as well as putting anti-virus and anti-spam on the periphery there. Again people can configure a HUB to talk directly to the interval prior to talking to another messaging hygiene clients or servers that organizations mail and already be using.

Windows And Active Directory

� Exchange Server 2010 Is Only A 64bit Server Application

� Exchange Server 2010 Runs On Windows Server 2008 SP2 64bit or Windows Server 2008 R2 64bit

� Windows Server 2003 SP2 Or Greater Global Catalog In Each Site

� At Least Windows Server 2003 Forest Level Functionality

� Exchange 2010 Does Not Support RODC/ROCG� Though They Can Exist In The Network

� Schema Will Be Updated

CPU and memory again are key for message routing, not a lot of disk but again you add additional redundancy by adding additional servers into the load balancing. Windows and active directory for just a moment. Windows 2010 is only a 64-bit server application; those two are coming from 2003, now that you need to make the rules to windows server 64-bit operating system, either 2008 SP2 64-bit, or 2008 R2 64-bit. Those who are coming from windows server 2000 Exchange server, 2000 already know that Exchange is a 64bit application. Now there was a 32bit version of Exchange 2007 that was intended only for training scenarios and was not meant for production environment. It does not even exist in the Exchange 2010 world. You also need to make sure that you have at least windows server 2003 SP2 or greater Global Catalog servers in each of your active directory sites. You also need to decide what sites you are going to have Exchange, you also need to rise as far as functional level to at least windows server 2003, Exchange server 2000 does not support read only demand controllers, read only global catalogs, though they can exist in the network itself for lots of good reasons Exchange needs to do not only reading but writing to active directory and global catalog, so it will not make use of them, if they are in the network already, that is fine but Exchange will not look at them and the schema will get updated for Exchange 2010 as well. OK the mailbox role server. Exchange 2010 we had a 64 update to the Exchange database and Exchange 2007 that is away from some severe memory limitations and it could really grow and obviously the 64bit database which runs on a 64bit application which runs on a 64bit or less and you are aware where that is all coming from. The speed performance is pretty phenomenal. The Exchange team every time gets harder about how the data is being accessed and where Exchange traffic is very rusty talking to the database prior, it is actually now much

more smooth out, so that it is good, four-gate level limitation as I said has gone away. Typical mailbox server role, you are going to see organizations with 8 to 16 gigabytes of memory. You could go higher than that but probably not necessary for standard configurations. There are ways to actually calculate and look at your particular load for an Exchange server and you really need to do that because it is not about small, medium or large and it is not about number of users though that is convenient if we talk about it, it is really within your organization for your users and the kind of load that they put on heavy, low, medium heavy and insane number of messages per day. You could play up to 24 cores within a server that is handling multiple loads, technically you are going to see commonly 8 to 16 cores to a mailbox only server, probably the sweet spot for most organizations is probably those eight core dual Quad. A lot of mailbox servers could go larger than that.

Mailbox Role� 64bit Update to Exchange Database in 2007

� 70% Faster Than Prior Version

� No More 4GB Limitation

� 8-16GB Typical For Large Mailbox Server

� 4, 8, up to 16 Cores for Mailbox Only Servers

� Up To 24 Cores for Multiple Roles

� Designed For Direct Attached Storage

� Database Availability Groups (DAG)Provide Easy High Availability

� DAG with 3-4 Servers Or More Will Be Common

The mailbox role is really designed for directed hatch storage and we can have separate conversation about that in some of the other sessions in this roadmap series but the performance is really designed for direct attached storage, the kinds of IO that Exchange is doing, will really be less expensive for you. Does that mean that if you already have got a storage area network you are going to try without, I doubt it, you made a large investment there. You need to take a look is the best use of storage area network or perhaps you are looking at other parts in the organization need an upgrade or need more space on the storage area network and that may be an opportunity to say you know I don’t need to have Exchange because there are other ways that we build in or don’t see within Exchange 2010. One of those is the most really probably I think we need this feature, it is the database availability groups or DAGs. Let us take high availability requirements, a capability that used to be done in Exchange 2010 and prior versions with clustering in Exchange 2007 we moved from only a single copy cluster to a CCR cluster,

continuous replication where two nodes of a cluster were actually separate copies of the data and the replication of CCR, also LCR and SCR local continuous replication, standby continuous replication, but that replication technology is on top of windows clustering. And you needed to understand if these were configured windows clustering to make high availability on the mailbox server look in 2007 and prior in 2010, the DAG heights of the clustering functionality that is meted, you don’t need to know how the clustering administrator or how the clustering consult is not a requirement for Exchange and you can actually change on the sly and Exchange enterprise server to be a member of DAG and the DAG will go out pull in the pieces of clustering that it requires that it needs and will configure that in the background in order to set up replication between multiple servers in a database availability group. So this is really pretty normal functionality and you are going to see you know DAGs with 3 or 4 servers or even more will be very common. So there has been redundancy with that Exchange data, by having a secondary and perhaps a third copy of my Exchange data, now the notes you put in there, the better functionality or better protection you thought that also you are splitting the load between lots of different servers. You can have just if you want to ultimate here, you can have DAGs with 2 to 16 servers and then many those could handle 100 databases, that is probably about reality for most organizations but organizations with 8 to 10 databases, 3 more servers in a DAG. I think you are going to find very common that people don’t want to be able to have high availability, also some resiliency, some protection in case something does go wrong. All right. Let us go and move to our last section here. Transition and migration scenarios.

Transition From Exchange 2007

� Service Pack 2 For Exchange Server 2007 Is Required

� Every Exchange 2007 Server In Site Where Exchange 2010 Will Be Deployed

� Every Exchange 2007 CAS In The Organization

� Order For Transition is CHUM…� CAS, HUB, Unified Messaging (If It Exists), Then Mailbox

� Deploy 2010 Roles In Parallel With Existing 2007 Roles

� HUB and CAS Talk To Same Version Mailbox Role

� HUB and CAS Talk To Other Version HUB and CAS

� Setup Legacy Subdomain And Certificate

� Redirect OWA/EAS/OA Traffic In The Background

So let us start with Exchange 2007 and these are sort of high level steps as things that you need to do by having a length at the end of the presentation that will take you into some

of the Microsoft articles within the tech net environment, we will talk them in more detail about all of this. Some of the things you need to know Exchange service pack 2 for Exchange 2007 is required to get Exchange 2007 to talk to Exchange 2010 and actually this scheme updates already as well and that needs to be in every site whether Exchange 2010 will be completed, also need to be updated on every Exchange 2007 cast in the organization and a little bit of order for you to just keep in the back of your mind thinking is CHUM, CAS first, then HUB, then unified messaging if you got it, and then finally the unified mailbox server role. You can actually be deploying 2010 role in parallel with your existing 2007 roles. You need to be aware of the fact that the different versions can only talk to like versions. Let me describe that a little better. The HUB and the CAS talk to the same version mailbox role, so the HUB Exchange 2007 and the CAS for 2007 talk to the Exchange 2007 mailbox role. HUB and CAS from Exchange 2010 do not talk directly to an Exchange 2007 mailbox. They talk to their counterpart HUB and CAS from the 2010 role to the 2007, so HUB talk to 2007 to 2010 which then talks to the individual mailbox role. Another set of things that you are going to need to do or ought to do is to set up a legacy sub domain, perhaps legacy.yourcompany.com what hat legacy domain is going to do along with setting up a certificate for that legacy domain is to redirect outlook access and Exchange active Sync and help look anywhere traffic in the background, so that if there is somebody can access to let us say an older user, user that had a mailbox 2007 is upgraded to enter your organization such that the traffic comes in from internet to an Exchange 2010 CAS that Exchange 2010 CAS is going to look up and figure out and say your mailbox is really 2007 and it is going to use that legacy sub domain in order to invariably to the end user, allow the traffic over to the 2007 CAS in order to provide outlook with access log in or other functionality from the 2007.

From Exchange 2007 Continued� Now Ready For Online Mailbox Moves

� Move Process Runs While User Is Still Connected

� Only Brief Loss Of Connection At End Of Move

� If You Are Still Using Public Folders� OWA 2010 Can Only See PF’s on 2010 MBX

� Replicate Them To Exchange 2010

� If You Have Entourage Clients (Mac)� Entourage Has Used WebDAV To Connect To

Exchange 2007 CAS

� Exchange 2010 Does Not Support WebDAV

� Newest Entourage Uses Exchange Web Services (EWS)

� Might Keep An Exchange 2007 CAS For WebDAV

OK, we got little things for 2007. Once we have got all of the infrastructure, we have got parallel infrastructure in place. We have looked over to internet facing connections and we have got our legacies sub domain and certificate setup and we can get on to mailbox moves and from 2007 to 2010, the process for mailbox moves has changed a bit in that you can direct Exchange to use a process which keeps the user online. So you don’t have to do this update, you don’t have to kick the users off of Outlook and what is going to happen is the online process where actually stop moving the user while they are still connected well invariably actually block their mailbox and create a new little database of the changes that are happening during the move and at the very end of the move, the end users will experience a brief loss of communication approximated for a minute and how busy they have actually been and at that point it will move that last little bit that special little temporary database of changes that were made during the large part of the move and that redirect the client so that they are now talking to the Exchange 2010 server. That is a really neat capability so even though large mailbox moves can happen with only a brief loss of connectivity for the end user and you can do this during the middle of the day. If you are still using public folders, one of the things you want to think about, Outlook web access or outlook client, a whole lot of outlook clients can see public folders on either 2007 or 2010, Outlook web access 2010 though can only see the public folder database on the 2010 mailbox server. So as you have got public folders, you are still using public folders, you have a lot of created public folder database on 2010 and that will replicate your public folders to 2010, so that with web access 2010 you can see those.

Transition From Exchange 2003

� Switch To Exchange 2003 Native Mode

� No Previous Versions Remaining

� Must Be At Exchange 2003 Service Pack 2

� Active Directory At Windows Server 2003 Forest Functional Level

� Global Catalogs Running Windows Server 2003 SP2

� At Least One GC Per Site

� Implement New Server Roles on New 64bit Hardware

� Move Mailboxes (Not Online)

If you have entourage clients from the Macintosh, we talked about web DAF before and that is how entourage used to connect, there is a brand new version of the entourage client. It uses Exchange web services because Exchange 2010 does not support DAV, so

either get new version of the entourage client that uses EWS Exchange web services or you know use an Exchange 2000 CAS around for your existing Macintosh clients that are still using low DAF until you get a chance to update those on the desktop to new version connectivity with web services is a great improvement.

From Exchange 2000..?

� It Is Not Supported To Transition Exchange 2000

� This Could Mean A Migration Of The Data

� However… Exchange 2000 Was Last Exchange Version Where Upgrade-In-Place Was Supported

� So… Upgrade-In-Place To Exchange 2003 SP2

� Set Exchange 2003 Native Mode

� Then Transition Exchange 2003 SP2 to Exchange 2010

� New 64bit Servers Will Be Required For 2010

New version of MAC office and I think it wont be called entourage and it will actually be called outlook is due sometime in the 201 timeframe. All right transitioning from Exchange 2003 is a little bit different you obviously need to an actually just true to 2007, you need to make sure that you have switched to 2003 native mode that means no previous versions of Exchange so on, you need to be up to Exchange 2003, active directory like 2007 needs to be at least windows server 2003 at functional level, your Global Catalogs need to be windows server 2003 SP2 of at least one global catalog per site. Then you can go off and implement the new server roles on new 64 bit hardware, if you connect the 2003 role, most likely your server hardware is four to five to six years old at this point, it is probably not capable of supporting 64 bit, depending exactly when it was purchased and you are going to be looking at new hardware for your Exchange. A big difference but again that is how we have done things in the past and people have done well with at this time. Your moving mailboxes will not be that online connected now that I talked about but moving mailboxes can happen on a scheduled basis at night and that works very well. Some people working are kicked off from particular departments during the day but once you got the process down, you are going to actually automate and say I want all of these users of these groups to move mailboxes in the middle of the night and it can be scheduled and if there are problems, it can actually leave the mailbox where it is and you can deal with those on a one off basis the following day. And now mailbox Exchange

2000. This is an interesting one. Formally officially it is not supported to transition Exchange 2000 to the Exchange 2010 world. So if one thinks about it, this could easily mean that we did need to do a migration of the data, we need to rip out all the data out, use a third party utility place it into 2010 and a fair amount of work there. Probably there is a little bonus if you will, Exchange 2000 was the last version of Exchange where you could do an upgrade in place, ah, ha go ahead, get it all in place, Exchange 2000 to 2003 SP2 and obviously make sure you have good backups in case you have got problems.

From Older Exchange

� Exchange 2000

� See Previous Slide

� Exchange 5.5 Or Earlier

� Cannot Transition via Move Mailbox (Hard Block)

� This Is A Migration

� Export All Data Using 3rd Party Utility

� Import All Data Using 3rd Party Utility

� New 64bit Servers Will Be Required

On a general statement, if you have got any version 2000, 2003 which is not particularly stable and may be an issue that you have been sort of avoiding or putting off, you would like to get your systems to be stable, obviously you do any transition in order to have the best chances of success and keep your end users happy because ultimately that is how you will measure up to how well you did on the project. So OK once we have upgraded in place to Exchange 2003 SP2, then we can set Exchange 2003 native mode and then you can go ahead and do a transition from Exchange 2003 SP2 to Exchange 2010 like we talked about as well, again you definitely got to have older servers here and you will need new 64 bit servers and the different roles of configuration that we described. Other Exchange versions, so we talked about 2000, if you are having 5 or earlier this will really need to be a migration that is there is no real mailbox capability, Microsoft used to have migration tools, does not have those to be able to pulled out from older systems, and so there are third parties who have been doing that and clearly 64 bit server is now in my surveys, users host their many organizations that are on Exchange 2003, small percentage of organizations are still running 2000 and all the talking that I do is a little hot here in this virtual environment we are working in today but we want to have people raise their hands, it is now pretty rare to find people running exchange and it has been a while since I have heard of people running 5.0 or 4.0, but I am sure that there is a few out there.

Coming from other messaging environments like notes and Domino, there has been a notes transporter suite from Microsoft that worked with the Exchange 2007 version and prior of Exchange but they are updated for 2010.

From Domino/Notes

� Domino/Notes Transporter Suite From Microsoft

� Works With Exchange 2007, Not Updated for 2010

� Migrate Notes To 2007, Then Transition

� A Pure Exchange 2010 Organization Cannot Go Back To Add An Exchange 2007 Server

� Create Exchange Organization By Building Single Exchange 2007 Server Before Introducing Any Exchange 2010

� 3rd Party Migration Tools Coming

So if you want to migrate notes and Dominos to Exchange 2007, you could again migrate those to the 2007 role and then transition, move those mailboxes up to Exchange 2010 now. If you are really thinking or planning on doing this and you want to be able to use the free but the Microsoft transporter suite from Exchange 2007 for domino recognized or mails that have pure Exchange 2010 organizations cannot go back and add in Exchange 2007, so 2007 server, if you install a brand new, sometimes called a Greenfield installation of Exchange 2010 and there has never been a prior version in your organization. If you do that, you cannot go back and add an Exchange 2007 server. So what you might want to do if you want to use or look at using the transporter suite is to install create your Exchange organization by building and putting in a single Exchange 2007 server and then introducing Exchange 2010 and that will allow you to do the migration suite, to pull over from note to 2007 mailboxes and then you could use both mailboxes from 2007 up to 2010. There are third party migration tools coming for directly from Domino and notes various versions too, directly to Exchange 2010 and sort of keeping your eyes and ears peeled for those versions. I will really sort of summarize what we have talked about we covered a lot of ground, again this was meant to be a roadmap for Exchange 2010 transition and migration, sort of how you get there from here which out in the New England area basically in the Boston area and we have an old joke which is you cannot get there from here, well actually you cannot get there from here, and that is what we talked about in a number of different ways to do that. The transition is really straightforward using mailboxes and those of us who have been doing Exchange through the versions you are very familiar with. On my mailbox moves are new and very

cool to allow people to stay connected, you are going to require parallel hardware for the CAS and HUB and for your mailbox environment. So you are going to move mailboxes to a new mailbox server and Exchange 2010. You also need to implement parallel CAS and HUBs environment for routing messages and routing client communications. Think about scalability, resiliency and availability and things we will talk about in some of the other sessions, you know the good news is that the performance exchange continues to be rather phenomenal in how much faster and how much smoother the performance curves are and the ability to use direct storage and even less costly disks in those drives but you need to think about you know how I am I going to build in the scalability in terms of the numbers of users supported whether that users you know the problem with too many users in a single server and in a small number of servers is they really not protected against disaster or protected against failures and see how to spread that load so scalability is not necessarily in terms of larger but in terms of additional servers so that you can manage failover and switchover capabilities, brining in resiliency as well you can have your HUB transports, you can build in failure modes within there as well, transport shadowing so that if you lose a transport server, you lose HUB transport or chain of HUB transport connectivity on that there is a secondary path and that messages are not lost, even they are in transit. Again, you are going to be looking for new 64-bit servers, if you are coming from 2003 or as we described earlier versions, depending on when you came, when you upgraded to exchange 2007, you may have hardware that you can redeploy or start of leap frog, but you are going to need supplemental servers in order to handle your transition, your move from 2007, but if you are smart about it, you could select and bring in some new servers in order to handle transition and then when you are done with the transition, and looking and saying how can we be smart about the use of hardware, you could reuse that hardware depending on additional high availability and resiliency into your Exchange 2010 environment. That sort of summarizes where we are today, what we talked about, moving transitioning.

Roadmap Summary

Exchange 2010: You Can Get There From Here

Transition Straight Forward Mailbox Moves

Requires Parallel Hardware For CAS/HUB, and MBX

Plan Resources for Scalability, Resiliency, and Availability

Acquire New 64bit Servers If Moving From 2003

Supplemental Servers If Moving From 2007, Re-use for HA

On the link here for the tech net tech center for Exchange, I encourage folks to go about there and there is additional documentation and then also some visits to saunter through all other different options that you can narrow down and what you need to do in your particular organization. With that I would like to thank you for attending today and join us again for additional seminar in this Exchange 2010 Roadmap Series. With that, I am going to hand back to Patrick. Patrick Devine: Great, thanks Lee. That concludes today’s presentation, ‘Exchange 2010, Roadmap Series, Transition and Migration’. If you would like to review today’s material at some later data, an archived version of this event will be made available on our searchexchange.com webcast library. I would like to thank Lee Benjamin for taking the time to be part of today’s presentation, and also I thank you for taking your time to join us today. This is Pat, wishing everybody a great day.