How to transition Exchange 2010 to Exchange 2013 Part 1

By admin on April 2nd, 2013

With Exchange 2013 Cumulative Update 1 coexistence between Exchange 2010 (Service Pack 3) and Exchange 2013is finally supported. It’s been a long journey but let’s now focus on how to install Exchange 2013 and coexist with the latest and greatest Exchange version, 2013.

In this part I will cover how to install Exchange 2013 CU1.

In my lab I set up the following:

I use split DNS so the domain is called mailmasterlab.se both internal and external. Since it’s been common to have a TMG in front of Exchange I have included one and we will go through what configuration we will have to do there as well. See table below for all fact of the servers.

Function Version Server name Roles IP
Domain Controller 2012 Ex15-DC DC/GC/DNS 192.168.100.180
Exchange 2010 Ex15-Ex2010 MBX/CAS/HUB 192.168.100.101
TMG 2010 Ex15-TMG   192.168.200.190
192.168.100.254
Client (internal) Win8 Ex15-ClientInt Outlook  
Client (external) Win8 Ex15-ClientExt Outlook

Load Balancer

 

 

 

192.168.100.105

Of course there is no good reason for using a load balancer for only one server but in this blog series we will also build a DAG later on so I added a KEMP for that purpose and we will also look at how to configure it.

And the next server we will set up will be the Exchange 2013 server, note that to be able to install Exchange 2013 all Exchange 2010 servers in the organization will need Exchange 2010 Service Pack 3 before we can install. If any Exchange 2010 servers in your organization (including Edge servers) does not yet have SP3, start by upgrading them or the Exchange 2013 setup will fail because of a “hard block”.

Our Exchange 2013 server will have the following characteristics:

Function

Version Server name Roles IP
Exchange 2013 Ex15-Ex1 MBX/CAS 192.168.100.102

The next thing to do is to install an Windows 2012 server. Even though I won’t set up a DAG in this part 1 of this blog (will come in later posts) I recommend you who will to base your Exchange 2013 server on Windows Server 2012 Standard as Failover Cluster is included. in standard and much more affordable.

I won’t cover the Windows setup in details but when you have Windows 2012 in place follow the steps below.

Open Windows PowerShell

Run:

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, Telnet-Client

Note: Telnet-client is not required but very nice to have when testing and troubleshooting SMTP.

Restart your server.

Download and install Unified Communications Managed API 4.0 Runtime

Download Exchange Server 2013 RTM Cumulative Update 1 (CU1). Note that you can install from CU1 and don’t have to upgrade from RTM.

Extract the the content to a directory of you choice, in my case C:Ex1013

Start an elevated cmd and run setup if you like to run the GUI based setup or run the command you prefer to do a unattended setup. In this blog I will do it through the GUI.

You will be asked to check for updates, it’s unlikely that any updates will be found.

After you click next files will be copied and setup will initialize.

A few next and a accepted license agreement later you will be asked to install with recommended or custom settings, I go for custom in this case.

As I will install one Exchange 2013 server I go for both Client Access role and Mailbox role. Since I didn’t do anything specific to Windows roles and features I check “Automatically install Windows Server roles and features that are required to install Exchange Server”.

Pick your destination where you want Exchange to be installed. I go for default .

Next I select to keep Malware Protection enabled.

Setup will check that all components are in place and that the server is ready to be installed. A restart will probably be needed after all Windows components are installed. so lets restart and try again.

After rerunning setup you will see something like above, don’t worry about the warnings about Filter Pack.

Hit install and beside getting Exchange 2013 installed on the server your organization will now get some new stuff in AD,  yes as usual there are schema updates so be prepared that this might take a while (and require permissions).

Some 35 minutes later you have a brand new Exchange 2013 CU1 server! Congrats!

In part 2 of this blog series we will take a look at what we should configure on this brand new server, stay tuned!

Find all remaining legacy users and move them

By admin on May 19th, 2011

As you might have read I do a lot of mailbox moves right now and today I needed to find all remaining users in Exchange 2007 and create my last batch of moverequest.

To find all users in Exchange 2007 that had no moverequest associated to them and create a new moverequest I used:

Get-Mailbox -ResultSize Unlimited | where {$_.MailboxMoveStatus -eq "None" -And $_.Database -like "Exchange2007server*"} | New-MoveRequest –BatchName LastBatch -BadItemLimit 5 –SuspendWhenReadyToComplete

As you can see I create suspended moverequests that will be resumed later on but that is of course optional.

Happy moving!

Get all your moverequest batch names

By admin on May 19th, 2011

I’m in the process of moving a lot of mailboxes and I do that in batches. I have a Excel spreadsheet where all batches are documented and that works pretty good, at least until more people get’s involved or I forget to document a batch.

So I needed to get a list of all unique batch names. Here’s what I did:

Get-MoveRequest –ResultSize Unlimited | Sort-Object –Property batchname | Select batchname | Get-Unique –AsString

Last chance to Master Exchange 200x to Exchange 2010 Transition

By admin on November 19th, 2010

Last chance to attend my training on Exchange 2003/7 to Exchange 2010 Transition is soon here. It’s a three day lab with all my expertise from transition projects mixed with a full hands-on lab where you will do a full transition from Exchange 2007 to Exchange 2010.

During the three days you will get:

  • Theoretical training about Exchange 2010 in general
  • How to plan your transition
  • How to solve problems with different clients during your transition
  • Hands-on lab where you will do all the steps in a transition
  • How to set up Exchange 2010 for High Availability
  • Hands-on lab on HA (DAG/CAS Arrays/Load Balancing)

The training will be at Labcenter in Stockholm. Check out their site for details and sign up!

Do you want to master Exchange 2010 Transition?

By admin on August 3rd, 2010

Well over a year ago I started writing a lab/workshop on how to transition from previous versions of Exchange to Exchange 2010. I have given this lab for over a 100 Exchange admin by now and added all my experience from my own transitions into it.

Do you want to master Exchange 2010 transition? Great! Have a look at Labcenter for a more detailed description (in Swedish) of the lab.

The lab covers both transition from Exchange 2003 and Exchange 2007 to Exchange 2010.

Why install a Exchange 2007 before going to Exchange 2010 and things to think about!

By admin on July 4th, 2010

I have been in the process of writing this blog for a long time and now it’s finally here. The reason for this blog is that after you install Exchange 2010 you can no longer install a previous version of Exchange into the same organization (in a supported way). You might think that that is not a problem and you are probably right but there are two scenarios when you might run into problems.

  1. If you ever need to migrate from Lotus Domino to Exchange
  2. If you need WebDAV

Migration

Let’s talk a bit about the first scenario and why this might be a problem.

When you perform you Schema updates for Exchange 2010 (or run the setup witch will update the schema for you) you will be prompted with a warning:

Setup is going to prepare the organization for Exchange 2010 by using ‘Setup /PrepareAD’.  No Exchange 2007 server roles have been detected in this topology.  After this operation, you will not be able to install any Exchange 2007 server roles.

So when you want to migrate mailboxes from Lotus Domino you could do that with Microsoft Transporter Suite. As stated in the overview it’s only supported for Exchange 2007

Transporter Suite contains a set of tools for migrations from both Lotus Domino Servers, and generic IMAP/POP sources. For Lotus Domino the suite contains a set of tools for Directory and Free/Busy interoperability between Lotus Domino 6, 7 and 8 and Exchange Server 2007 and Windows Server 2003/2008 Active Directory. In addition for Lotus Domino the suite contains migration tools to migrate users, groups, personal address lists, mailboxes, personal mail archives, and applications from Lotus Domino 5, 6, 7 or 8 to Active Directory, Exchange Server 2007, and Windows SharePoint Services 3.0. For generic POP/IMAP servers the suite contains a set of tools to bulk migrate mailboxes from any generic email servers that support the POP3 or IMAP4 protocol to mailboxes in Exchange Server 2007

There is no Transporter Suite for Exchange 2010 so this means that you would have to use a Exchange 2007 server to migrate your Lotus Domino data to Exchange.

So if you are about to install Exchange 2010 and might need to migrate from Domino, think about installing a Exchange 2007 first. Please also read the last part of this blog for more info about things to think about

If you already installed Exchange 2010 and now find you self in a situation where you need to migrate Domino to Exchange 2010 there are some third party tools you can use, BinaryTree and Quest.

 

 

WebDAV

The second reason for installing a Exchange 2007 server before you install Exchange 2010 could be WebDAV. WebDAV is not a part of Exchange 2010 so if you have systems that use WebDAV you will need to have a Exchange 2007 server for that purpose.

 

Things to think about

If you for any reason needs a Exchange 2007 server on your way to Exchange 2010 there are some things you should think about:

Routing Groups

When you install a Exchange 2007 Hub Transport server into a Exchange 2003 organization you will be asked to point out a Exchange 2003 server. The reason for this is to set up a routing group connector between Exchange 2003 and Exchange 2007.

Screenshot from Exchange 2007 setup

After you select a Exchange 2003 server setup will create a routing group connector between the server you install and the selected Exchange 2003 server. So what’s the problem with that? Well since the dialog in the screenshot above only will show up when you install your first Hub Transport server there is a possible risk of single point of failure and if you only have your Exchange 2007 server for “better safe then sorry” purpose then you might not care that much about it an possible even shut it down with the result of no mail flow between Exchange 2003 and 2007/2010.

To avoid that to happen you can use Exchange Management Shell to configure the RGC with multiple bridgehead servers.

[PS] C:>Set-RoutingGroupConnector <Name of RGC> -TargetTransportServers <Name of Exchange Server> -SourceTransportServers <Name of Exchange Server>

Note: By default there are two routing group connectors created, enter multiple Target and Source Transport servers on both.

When you install your Exchange 2010 Hub Transport Servers it’s a good idea to include them as well.

Virtual Directories

After you install your Exchange 2010 servers you probably don’t want clients to access the “temporary” Exchange 2007 box so the are a few things to configure to avoid that.

Here are the settings I change (in these examples loadbalancer.mailmaster.local represent the internal Exchange 2010 load balancer and webmail.mailmaster.se the external URL, in my case a TMG Server)

Set-ClientAccessServer Exchange2007server -AutoDiscoverServiceInternalUri:"https://loadbalancer.mailmaster.local/Autodiscover/Autodiscover.xml"

Set-OwaVirtualDirectory "Exchange2007serverowa (Default Web Site)" -InternalUrl: “https://loadbalancer.mailmaster.local/owa” -ExternalUrl:”https://webmail.mailmaster.se/owa”

Set-ActiveSyncVirtualDirectory "Exchange2007ServerMicrosoft-Server-ActiveSync (Default Web Site)" -InternalUrl: “https://loadbalancer.mailmaster.local/Microsoft-Server-ActiveSync” -ExternalUrl:”https://webmail.mailmaster.se/Microsoft-Server-ActiveSync”

Set-OabVirtualDirectory "Exchange2007ServerOAB (Default Web Site)" -InternalUrl: “https://loadbalancer.mailmaster.local/oab” -ExternalUrl:”https://webmail.mailmaster.se/oab”

Set-WebServicesVirtualDirectory "Exchange2007ServerEWS (Default Web Site)" -InternalUrl: “https://loadbalancer.mailmaster.local/EWS/Exchange.asmx” -ExternalUrl:”https://webmail.mailmaster.se/EWS/Exchange.asmx”

If you perform the above you can shut down your Exchange 2007 server and there will still be mail flow and client will still be able to connect to your Exchange 2010 servers.

Some other questions I can imagine can arise…

Q: Can I shut down the “temp Exchange 2007 server” and forget about it?

A: No! If you do the computer object will get tomb stoned in  Active Directory so the server should be online once in a while to prevent that. If you want to check how long you tombstone time is, check this out

Q: Can I uninstall the “temp Exchange 2007 server” and reinstall if needed?

A: No! To be honest I have tried that and I can actually get it to work but I have asked this question to members of the Exchange product group and got a no. It might be that it hasn’t been tested…

Q: How do I uninstall the “temp Exchange 2007 server” when I no longer need it (and I’m SURE I don’t need it)?

Nothing special here, you uninstall it like you would with any Exchange 2007 server, here’s a How to…

Q: Do you really install this “temp Exchange 2007 server” at every customer before you install Exchange 2010?

A: No! But I make sure the customer understands the pros and cons with that BEFORE I install Exchange 2010

Q: Will there be a change in SP1 regarding this?

A: To my knowledge no!

 

Additional information:

Cannot install Exchange 2007 roles after you prepare Active Directory for Exchange 2010

Installing Exchange 2003/2007 in an Exchange 2010 Environment

 

Did you miss TechDays 2010?

By admin on April 21st, 2010

Or would you just like to see some of the sessions again?

Check out the recorded sessions here! My session about Exchange 2010 transition is in there as well.