Exchange 2013/2016 Migration Step 8 Migrating Certificates from 2010 to 2016
Only consider doing this if you have a purchased (i.e. NOT using a self signed) certificate on your Exchange 2010 server. Bear in mind if you have the internalFQDN of your Exchange 2010 server as a SAN (Subject Alternative Name), then you cannot renew the certificate if it lasts longer than November 2013, so you might want to purchase a new one anyway.
Also make sure the public name of the server resolves to the public IP of the new server (or you change the port forwarding for HTTPS traffic to point to the new server).
1. On the Exchange 2010 Server > Launch the Exchange Management Console > Server Configuration > Select the certificate > Export Exchange Certificate.
2. Select a location to save the exported cert > supply a password > Next.
3. Finish.
4. On the Exchange 2013/2016 Server > Launch the Exchange Admin Center > Servers > Certificates > Select the ‘more options’ icon > Import Exchange Certificate.
5. Put in the path to where you saved the exported cert, and the password you used > Next.
6. Add in the Exchange 2016 Server > Finish.
7. Select the new certificate > Edit > Services > Select the service for which you want to use the certificate. Note: I don’t have Unified Messaging so I’m selecting all the other options > Save.
8. Answer ‘Yes’ to replace the self signed certificate that Exchange 2016 installs by default.
9. You can then open Outlook Web Access and give it a test (Remember to change the DNS records so that the Common Name on the certificate points to the new Exchange 2016 server).
Before doing this: Have a quick common sense check!
Do you need to migrate any Transport rules? (For Exchange Disclaimers etc).
Do you need to change any Journaling settings for your third party Email Archive solutions etc.
Do you need to replicate ant receive connectors from the old email server to the new one? (For Scanners, Photocopiers, SharePoint, SQL Mail, SAP, etc).
1. Before we can retire the old server we need to remove its databases, even though we have moved all the user mailboxes, If you try and delete the database it will complain that’s its not empty. This is because it will have either Archive or Arbitration mailboxes in it. To see, execute the following commands;
[box]
Get-Mailbox -Archive
Get-Mailbox -Arbitration
OR, If you have multiple source databases use the following syntax,
As you can see (in the diagram below) I have Arbitration mailboxes left in the old Exchange 2010 database, to move them use the following command, Note: Execute this command from the Exchange 2013 Server!
2. Wait a while and then check that they have moved. Note: You can check status with ‘Get-MoveRequest’.
3. In the Exchange Management Console > Organization Configuration > Mailbox > Database Management > Select the mailbox database > right click > Dismount Database.
4. Now Remove the database > Yes.
5. OK.
6. Offline Address Book Tab > Default Offline Address Book > Remove > Yes.
Note: If this OAB is still in use you will NOT be able to remove it, Go to the Address Book Policies tab > Change the default OAB from the 2010 one to the 2013 one.
7. If you try and remove the public folder database it will complain that it contains replicas, which you cant remove. The easiest way I’ve found to remove it is as follows. Dismount the public folder database.
8. Then delete (or move if you are paranoid) the database file (.edb file) and the logs for this database.
9. Then mount the database > Yes to all > It will mount a blank empty database.
10. You can now delete the database without error.
11. OK.
12. Close Exchange System Manager > Start > In the search/run box >appwiz.cpl {Enter} > Locate Microsoft Exchange Server 2010 > Uninstall.
13. Next.
14. Untick all the installed roles > Untick Management tools > Next.
15. Uninstall.
16. Finish.
Exchange 2013/2016 Migration Step 9 ‘Finish Up’
Remember if you are keeping this server, you might want to delete all the database files which get left behind. You will also want to change your backup software so that it is pointing to the new mailboxes/databases.
Related Articles, References, Credits, or External Links
Thanks to Shawn Welker for the Arbitration/Archive feedback
Thanks to leandro.chiesa for the OAB feedback
I recently posted an article on Exchange 2003 to 2010 Transition, Only to be asked, “Can you do the same for Exchange 2007 to 2010?”, so here it is 🙂
Before we start, I’m aware “Migration”, “Swing Migration”, and “Transition” have three very different meanings, Depending on which KB, blog or piece of Microsoft documentation you are reading. Be under no illusions the terminology, used in the title and the tags on this page is to catch the web traffic of those, who have an Exchange 2007 Server and want to move all their Exchange, to Exchange 2010 server.
Solution
In this Example I’ve got an Exchange 2007 Server running on Server 2003 R2 x64. My new server will run Server 2008 with Exchange 2010.
Just for a “worst case scenario” I’ve put in some public folders and I’ve got some Outlook 2003 clients.
Step 1 – “Pre-Site Visit”
1. Make sure before you start, you have the Exchange 2010 media and unlock code, you don’t want to download the media on a site with a slow internet connection, (at time of writing the disk image is 1GB in size).
2. If your existing domain controllers are all x32, and you are also upgrading domain controllers, during the process, Then you will be extending the domain schema (i.e. it’s not 2003 R2 or 2008) then make sure you have x32 bit Windows media with you (Note: 2003 and 2008 R1 only, as 2008 R2 is all x64 bit).
3. You domain and forest functional levels need to be (at least) Windows Server 2003, before you start the migration.
4. Make sure any third party anti virus and/or mail scanning software is supported and will work on Exchange 2010, and you have the media and licences handy.
5. You will need to install on a x64 bit server, make sure you have a server capable, and Windows x64 bit media with licences.
6. Before you even think about going further make sure you have a good backup! If you are lucky enough to have VMware ESX, Hyper-V or another virtualisation platform, consider doing a P2V conversion on your Exchange 2007 server then simply turning the 2007 Server off, then if it all goes to hell in a hand cart simply turn the original server back on again.
6. While your thinking about backups – does your backup software support Exchange 2010? you might need a new Exchange agent, check with your software reseller.
Step 2 – “Pre Install”
1. Before you do anything, it’s time for a common sense check, make sure your existing Exchange 2007 Organisation is happy and running cleanly, and has good communication with the domain and DNS. Get in the event logs and make sure it’s a happy server.
Time spent on reconnaissance is seldom wasted!
2. Now you THINK Exchange is happy, it’s time to MAKE SURE, launch the Exchange 2007 Management Console and select Tools >Best Practice Analyser
Run a “Health check”, and an “Exchange 2007 Readiness check”. (At time of writing there is no 2010 option).
3. Make sure your Exchange 2007 server(s) is/are up to “Exchange 2007 Service Pack 2” (In fact get the latest Exchange update roll up after that as well to be on the safe side).
Build Numbers
Exchange 2007 RTM Version 8.0.685.24 OR 8.0.685.25 Exchange 2007 SP1 Version 8.1.(Build 240.6) Exchange 2007 SP2 Version 8.2 (Build 176.2) Exchange 2007 SP3 Version 8.3 (Build 83.6)
To find your Exchange 2007 service pack level compare your build number with the build numbers above. Note you may need to install Windows Installer 4.5 before you can install SP2, (this requires a reboot).
4. The brief says your Global Catalog server should be at at least Server 2003 SP2, however I’d be updating all the domain 2003 controllers to Service Pack 2. (Note: you need 381Mb free space on the system drive, plus 170MB additional free space to install SP2).
Locate the Global Catalog Server
Find the Service Pack Level
Step 3 – “Deploy Exchange 2010“
1. Build you new x64 bit Windows server and apply all the relevant updates and service packs etc. The new server needs the Office 2010 Filter Pack Installing.
2. You need to add certain roles to the new server before attempting to install Exchange 2010 you can script that though I prefer to do things myself. Start > Server Manger > Roles > Add Roles > Next > Select Web Server (IIS) > Next > Next.
3. On Role Services, under security > tick Basic Authentication > tick Windows Authentication > Tick Digest Authentication > Under Performance tick Dynamic Content Compression.
4. Under Management Tools > Select IIS6 Management Comparability > Next > Install > Close (when finished).
5. Now you need to add “Server Features”, primarily .Net Framework 3.5 that is in Server Manager > Features > Add Features > Expand .NET Framework 3.5.1 Features > Expand WCF Activation > tick HTTP Activation > Select to add Required Role Services.
6. Scroll down and below “Remote Server Administration Tools” > Role Administration Tools > Select “AD DS and AD LDS Tools” > Next > Next > Next > Install > Close (when finished) > You may be asked to reboot.
Note: If you are installing on a domain controller (Which is NOT recommended), the “AD DS and LDS tools” will already be installed.
7. Post reboot the process will finish.
8. You need to set the startup type of the “Net Tcp Port Sharing” service to automatic > Click start > Run > Services.msc {enter} > Locate the Net Tcp Port Sharing Service and set its startup type to automatic.
Note: If you don’t see this service then you probably didn’t complete the reboot in the previous step.
The following steps are not actually required (they should be done by the actual install), BUT, on more than one occasion I’ve seen the setup fail and I’ve had to run these commands manually, so not I do them as a matter of routine.
9. Open a command windows and either navigate to the folder containing the Exchange 2010 setup files (Or the DVD) and issue the following command:
[box] Setup.com /PrepareSchema [/box]
10. While still at command issue the following command:
[box] Setup.com /PrepareAD [/box]
11. While still at command issue the following command:
[box] Setup.com /PrepareDomain [/box]
10. Put in the Exchange 2010 DVD, or navigate the folder containing the setup files. Run setup.exe, If you are using the multi language version you should be at “Step 3: Choose Exchange Language option” > Select it. > Select Install Languages from DVD.
11. Select “Step 4: Install Microsoft Exchange” > Files will extract and setup will Start.
12. At the Introduction screen > Next.
13. Accept the EULA > Next.
14. No, we don’t want to do error reporting > Next > Select “Typical” > (If you installing with SP1 see the note below) > Next.
*****Update 18/03/11*****
If you are deploying Exchange 2010 with SP1 included, at this point select “Automatically install Windows Server roles and features required for Exchange Server”
15. If this is the only one, or it going to be your main “Bridgehead Server” then it will be internet facing > tick the box > enter your full domain name > Next
16. No we don’t want to join the CEIP > Next > Exchange will perform a series of readiness checks > when finished click Install.
17. When done, click Finish > And the Exchange Management Console will Launch > To enter the Product Key, select “Server Configuration > Select the server > Select Enter Product Key. Then either restart the Exchange information store service or reboot.
At this point don’t expect each server to show up in the others Exchange Management Console
Step 4 – “Configure and Migrate”
1. First I’m going to create a public folder database, and replicate the public folders form Exchange 2007 into it, Go to the Exchange Management console on the 2010 server. > Expand “Organisation Configuration > Mailbox > Database Management tab > “New Public Folder Database. > Give the database a a name and choose the NEW server to host it > Next > New > Finish.
Then you need to make the new public folder database, the default one for the mailbox database > right click the mailbox database > Properties > Client Settings > Browse > Select the new one > OK > Apply.
2. The next step is to set up a replica of your public folders in the new database, to do this use the Toolbox > Public Folder Management console.
3. Now Exchange 2010 has its own public folder database it connects to that by default, Right click “Public Folders” > Select “Connect to Server” > Browse to the OLD server.
4. Select > Default Public Folders > The public folders should show in the middle screen > Right click the first one and select properties > replication tab > Add > Add in the NEW server > OK > You can un-tick the “Use public folder data store replication schedule” and change the drop down to “Always run” if you wish > Apply > OK.
5. If you have any Outlook 2003 clients you need to replicate the “SCHEDULE+ FREE BUSY” public folder > This is under “System Public Folders” > Select it and you will see the folder in the centre view, create a replica on the NEW server as in the above step.
Replication is a LOT faster than it used to be, within a few hours it should be complete, occasionally it stalls, if that that happens right click “Public Folders” and select “Update-Hierarchy” or In the Exchange Management shell issue the following command.
6. At this point you need to change the SMTP feed from the old Exchange 2007 box to the new Exchange 2010 Server, how you do this depends on your network setup, some examples of how you might do this are,
i. Change the SMTP (TCP Port 25) Port redirect on your router/firewall address ii. Swap IP addresses from the old to the new server. iii. Change the translation from public to private IP address to point to the new IP.
Note: If you have any mail scanning servers, anti spam hardware devices etc, then they will also need changing to point to the new server.
7. You will need to add the NEW server to the exchange organisations send connector, from within the Exchange Management Console > Organisation Configuration > Hub Transport > Send Connectors > Right click your send connector (yours may have a different name) > Properties > Source Server > Add > Add in the NEW server > Apply.
Then test mail flow works once again, this time through the new server.
8. Now you can start moving mailboxes from the old server to the new one, what I tend to do is move one mailbox, test mail flow outbound/inbound, then test mail flow internally from the mailbox I’ve just moved, to a mailbox that’s still on the old server. Once I’ve proved this works I will move the rest of the mailbox’s.
To move a mailbox, open the exchange 2010 management console, expand “Recipient Configuration” > Select Mailbox > You should see all the mailbox’s listed > Right click the mailbox you want to move > Select “New Local Move Request”.
At the introduction screen, hit the browse button and select your new servers data store > Next > Next > New > Finish.
Once you have moved one and tested, it you can move the rest of the mailbox’s.
Note: Outlook 2003 cannot connect to Exchange 2010, you need to turn on encryption before it will work. In Outlook Tools >Email Accounts > View or Change > Select the Exchange account > Change > More Settings > Security > Tick “Encrypt data between Microsoft Office Outlook and Microsoft Exchange Server > Apply > Restart Outlook.
To disable Encryption for ALL Exchange 2010 connections
Issue the following PowerShell command in the Exchange 2010 Management Shell.
9. Next task is to change the server responsible for generating the offline address book. On the Exchange 2010 server Exchange Management Console, Expand “Organization Configuration” > Mailbox > Select the “Offline Address Book” tab > Right click the Default Offline address book and select “Move” > Browse > Select the new server > OK > Move > Finish.
10. Now you will need to change your backups to include the new data stores. Your backup software will probably require you install the Microsoft Exchange Server MAPI Client and Collaboration Data Objects before it can back up the data stores correctly, before you install the backup agents (ARCserve and Symantec Backup Exec for example). Download the CDO Objects.
11. Be aware: some AV software (McAfee for example) likes to block TCP port 25 (SMTP), this is not good on an Exchange server! don’t forget to disable this feature or you may have mail flow issues.
12. Still on the subject of AV, Make sure the folders that contain the Exchange Databases and Logs are EXCLUDED from the AV scans. (If not. your Exchange Server can break if your AV decides to quarantine a log file for example). You should have Exchange aware Backup solutions anyway, e.g. McAfee GroupShield, Trend ScanMail, etc.
Step 5 – “Do Nothing“
1. Now I would wait, If you have any Outlook 2003 clients they will need to log on and get redirected to the new exchange server for their mail – this happens seamlessly in the background as long as the old server is still on, (though I have seen it fail and need to be manually changed on a handful of client machines).
Note: By
Step 6 – “Decommission and remove Exchange 2007”
1. First check your Public folders are in sync. Connect to each server and compare the size and item count, don’t forget to also check the SHEDULE+ FREE/BUSY folder if you set that to replicate.
Remove the replicas from the original server.
2. Now I would delete the mailbox database(s) from the old server.
or in EXTREME situations (sometimes it refuses to delete no matter what you do) run ADSIedit and remove it from CN=Configuration,CN=Services, CN=Microsoft Exchange, CN={organisation name i.e First Organisation}, CN=Administrative Groups, CN={Administrative Group name}, CN=Servers, CN={servername}, CN=Information Store, CN={Storage Group Name}, CN={Public Folder Database Name} THEN REBOOT
3. You now need to remove the old server from the source server list on the organisation send connector.
4. In control panel go to add remove programs and select Exchange Server 2007 > Next > Untick all the roles > Untick Management Tools > Next.
The server will run thorough its readiness checks > Uninstall > Finish.
Hello and Welcome to All who are reading this page. Many administrators out there are looking for guides to migrate their current CCR (Exchange 2007) environment to High Availability in Exchange 2010 SP1. In this article of mine, I will be covering the complete migration steps from Exchange 2007 Environment to Exchange 2010 environment with Existing Hardware. At the end, I will be showing how to configure the Exchange 2010 CAS Array with the help of the free Load Balancer (HAPROXY). Even though a good article is present on their website, I thought that if you will find everything in one place will be a bit stress release.
First of all, a brilliant article series is written by Mr. Henrik Walther about how to implement the CCR Cluster which can be found here, please go through this article series and you will be able to implement and understand the CCR operation. The HAProxy free OVF for the VMware Environment can be found here, download this and extract the zip file, it will give you two files, one will be with the name (Exchange 2010 HAProxy Virtual Load Balancer.ovf) and the second file will be with the name of (Exchange 2010 HAProxy Virtual Load Balancer.vmdk). Once extracted you have to import these files into your VMware Infrastructure I will show you how.
My whole Lab Environment is based on VMware ESXi 5.0, so if you would like to have your environment with VMware as well, you can download the Free version of ESXi 5.0 available on the VMware download site. You will have to register once (free registration) and download the .iso file. A license key will be emailed to your provided email address.
First of all let me show you my Environment
This is my current environment, with 2 ESXi hosts and 4 VM’s. Let me tell you the Roles installed on each machine.
FSDC – Active Directory Server (Windows 2008 SP2)
FSHCN1 – HUB Transport and Client Access Server. (Windows 2008 SP2)
FSMBXN1 and FSMBXN2 – The Mailbox Servers. (CCR CLUSTER). (Windows 2008 SP2)
I will be upgrading the existing environment to Exchange 2010, but now you will think that I don’t have a second Exchange 2010 HUBCAS Server, so how will I maintain the HUBCAS uptime. We need to add a new virtual machine in our environment with Windows 2008 R2 SP1, join it to the domain, and we will install the HUBCAS Role of Exchange 2010 SP1 on this VM.
Before installing the role of Exchange 2010 HUBCAS we have to prepare the active directory by issuing following commands.
[box]Setup /preparead[/box]
To run this command you mount the DVD of Exchange 2010 on the Domain controller or our newly created EX2010HCN1 VM. I ran it on the EX2010HCN1 machine and the output is as follows:
As you can see, that the status is failed, it failed because, this machine is not a domain controller and to update the schema it needs the ldifide.exe which can only be achieved by adding the feature RSAT-ADDS as shown in the powershell below.
After you have installed the required role and restarted the machine, run the command again and this time it should complete. Once this is done, now is the time to run the setup for Exchange 2010 HUBCAS Server installation on our Windows 2008 R2 machine. But before you can start the Exchange 2010 Installation you have to (MUST) upgrade all the Exchange 2007 Servers to SP2 at least, in my case I will be upgrading all the Servers to SP3. So lets have a look at the process of upgrading the Exchange 2007 Servers to SP3. But I will be writing about some errors also which I faced during the Upgrade. These errors are very common and many times my Colleagues also face them so I thought of listing them down.
Exchange 2007 HUBCAS Upgrade to SP3
So now we have to install SP3 on our Exchange 2007 HUBCAS Server. This can take up to 1 hour, depending on the machine you are working on. In my case it took about an hour.
NOTE: Once the installation is completed, you might get an error on the Finalization part; the error could be on MSExchange Transport Service not coming to running state. (This happens mostly when you did not disable IPv6 at the beginning of the Exchange 2007 Installation). Good technique would be to follow the guide from Microsoft to Disable IPv6 or this, behavior is normal, you just have to restart the machine and the service will come to the running state. It just needs some time to discover the exchange environment. (As it is said, many problems from Microsoft are resolved after a reboot).
Exchange 2007 Mailbox Upgrade to SP3
Before we start upgrading our Mailbox Servers, we have to make sure that the Clustered Mailbox is on the active node (FSMBXN1) in the cluster, as we will start working with Passive Node (FSMBXN2) Upgrade. This is to be done, because you don’t want your management to call you and start complaining about the Email services unavailability. Any normal IT Admin like me would just double click the setup.exe file and think that the upgrade can be done like that, (I am not sure about if it could be done through GUI), but the only way that I found out is through the command prompt.
Open the command prompt and type the drive letter name where the SP3 is extracted, in my case (d:) and press enter. The prompt will change and now you should be in your drive. Once there you should run the following command:
[box]Setup.com /Mode: Upgrade[/box]
The end result will be like this: (FSMBXN2-Passive Upgraded to SP3)
Now is the time to shut down the Cluster. This can be achieved by going on the Passive Node (FSMBXN2) which was just upgraded and issuing the following command from the exchange PowerShell:
You can get the name of your CMS name by typing the following command:
[box]Get-clusteredmailboxserverstatus[/box]
Once you run the Stop Command you will get a message to confirm to perform the action, just enter Y and press Enter.
After Stopping the CMS on the node, we have to move it to the Upgraded Node (FSMBXN2) (in offline mode Don’t bring it online, it should come online automatically). To move the CMS from one Node to the other Node we have to run the following command:
Now, our CMS is on the Upgraded Node (FSMBXN2) and we have to upgrade our CMS we can achieve this by issuing the following Command:
[box]Setup /UpgradeCMS[/box]
In my environment it took around 15 minutes and after this the Cluster was online on FSMBXN2. Now we have to upgrade the Second node (FSMBXN1) which was active. Again I issued the same command (Setup /mode:upgrade). It upgraded my node and then after the upgrade I had an error.
Note: During the upgrade of the second node in CCR your upgrade might fail and you will get error like this:
Don’t worry, just close the exchange management console if you have that opened and the exchange management shell as well and then re-run the upgrade. If after closing the exchange management console and the Shell, you still get the error you have two options here:
Either move the Quorum Owner by command to the Upgraded Node.
Or restart the machine that you are about to upgrade, this restart will automatically move the Quorum owner to the upgraded Node. (Easy and effective).
Installing Exchange 2010 SP1 HUBCAS after Upgrading Exchange 2007 to SP3
Insert the Exchange 2010 DVD into DVD drive. When the DVD Auto Plays , click Run Setup.exe under Install or run program. If Auto Play is disabled, navigate to the root of the DVD and run Setup.exe. Alternatively, browse to the location of your Exchange 2010 installation files and run Setup.exe. On the Introduction page, click next.
On the License Agreement page, review the license terms. select I accept the terms in the license agreement, next.
On the Error Reporting page, select Yes / No (as required) to enable the Exchange Error Reporting feature, next.
On the Installation Type page, select Custom Exchange Server Installation. (Note: For Exchange 2010 SP1, you can select to automatically install all required Windows roles and features for this server). You can also change the installation path for Exchange 2010, click Browse, locate the target folder, and then click OK. Click Next.
On the Server Role Selection page, select Client Access Role, and Hub Transport Role click Next. The Management Tools , which installs the Exchange Management Console and Exchange Management Shell, will also be selected and installed.
Now, as our Exchange 2007 Environment is with SP3, and we have installed our Exchange 2010 HUBCAS Server in the environment, is the time to Uninstall the Exchange 2007 SP3 from the Passive Node and Evict this node from the Cluster and install a fresh Windows 2008 R2 on this Machine.
Uninstalling Exchange 2007 from the Passive node in the Cluster
For the purpose of this Uninstallation I have moved the Cluster on FSMBXN1 and our Passive node is FSMBXN2.
Uninstallation Steps are pretty much easy. You have to go to Control Panel > Program and Features > Click Exchange 2007 and Click Uninstall. Uncheck all the items installed and after some time the Un-Installation will be complete.
On the maintenance page click Next.
On the Server Role Selection page, uncheck the Passive Clustered Mailbox Role and Management Tools, and Click Next and then click Uninstall. The uninstallation will take some time and at the end this is what you will get
Now we have to stop the cluster service and remove the Node from the Cluster (We have to do this from the Failover Cluster Manager). And then we can format the machine and install windows 2008 R2 on that.
Right-Click the node and first stop the cluster service and Right-Click again on the same node and click Evict. Than you can format the Machine and install Windows 2008 R2. Prepare the Newly formatted machine with all the Updates required for the installation of Exchange 2010 SP1. The updates required are as follows:
Installing Exchange 2010 SP1 Mailbox Server
We uninstalled Exchange 2007 from FSMBXN2 and formatted that Server with Windows 2008 R2. Now is the time to install Exchange 2010 Sp1 Mailbox Server. The steps are pretty simple:
Put the Exchange 2010 SP1 DVD in the Server.
Run the Setup
Accept the License Agreement.
Select the only the Mailbox Role to be installed.
It will take around 20 to 30 minutes for the Installation (depending on the Machine you are working on).
Once done just click finish and Restart the Server.
Migrating from Exchange 2007 to Exchange 2010
To start the migration, we have to move the mailboxes from Exchange 2007 to Exchange 2010. This can be achieved from the following steps:
Go to Recipient Configuration
Click Mailbox, on the right hand side you will see the list of users.
Right Click the users one by one or Select all the users with Ctrl-A and then Right Click and select local move request.
When you will click local move request, you will be given option for the mailboxes where to move. Select the Mailbox which resides on Exchange 2010 Sp1. And go through the rest of the options.
If you feel that there might be some corrupted messages in the mailbox, you can set the count for the corrupted messages.
Once the mailbox move has been completed we have to do move the Offline Address Book Generation to this New Exchange 2010 Server. To do this:
Go to Organization Configuration.
Click Mailbox and on the right hand side you will see the tab for Offline Address Book.
You will see, Offline Address book listed there. Right Click on the address book and select Move.
Once you click Move, you will be given the options for Servers that you want to move the generation on. Select the Exchange 2010 Server.
After moving click Update.
Once the generation has been shifted to Exchange 2010 Server, now is the time to Replicate you Public Folders if any to Exchange 2010 Servers. To do this:
Click Tool book in Exchange 2010 Management Console.
Double Click Public Folder Management Console and follow the pictures below.
After clicking the connect server type the Name of the Exchange 2007 CCR Cluster (FSMBX1) and click connect.
Once connected you will be on a page like below:
As I am not having public folders, my only concern is the Schedule + Free Busy information to be replicated to Exchange 2010. To do this Right click on the Folder being shown in the right hand console and click Properties, you will be brought to the page below:
Click on the Replication Tab and click ADD and then select the Exchange 2010 Mailbox Server Name:
It’s better if you follow the rest of the Article from here.
Now I am assuming that our Exchange Mailboxes have been migrated from 2007 to 2010 and are working fine. Now is the time to uninstall Exchange 2007 from our environment. So let’s do that. To uninstall Exchange 2007 from our Environment we have to go to our node FSMBXN1 and open the command prompt and issue the following command:
[box]Setup /mode:uninstall [/box]
or be specific as shown in the command prompt below
This will take some time and you will be getting the result as follows:
Now, our uninstallation is complete and we can carry on to un-join the Server from the domain and format it. Once your new machine with Windows 2008 R2 is up and running we have to rename the machine as you like, join it to the domain and install all the necessary updates for the installation of Exchange 2010 SP1 and at the end install Exchange 2010 SP1 Mailbox role.
Now let me give you a brief of my Exchange 2010 Environment.
I have the following servers having Exchange 2010 Installed:
EX2010FSHCN1 (IP = 192.168.0.7)
EX2010FSHCN2 (Will be added later)
EX2010FSMBXN1 (Public=192.168.0.8 and Private=11.11.11.1)
EX2010FSMBXN2 (Public=192.168.0.9 and Private=11.11.11.2)
HAPROXY (Management IP=192.168.0.12 and Load Balanced IP=192.168.0.13)
Implementing DAG (Database Availability Group)
As we have finished installing Exchange 2010 SP1 Mailbox Role on the Second node as well, now is the time to create DAG (Database Availability Group). A good article from Mr. Henrik Walther is present at this Site. Follow this article and you will have complete and better understand how DAG can be Implemented and Managed.
I will just be covering the steps of creating the DAG:
Under Organization configuration go to Mailbox.
When you have selected mailbox, on your right hand side, you will see, Database Availability Group Tab. Select this TAB.
Then you will see the option of New DAG on extreme right hand side. Click this.
When you will click the option, you have to type the Name of the DAG. Not necessary to type the Witness server and witness directory, as the setup will automatically locate a HUBCAS Server and create the Directory in that. You can make sure of this, by going to the properties of your newly created DAG.
Now, we need to assign a Static IP Address for the DAG. This can be done by going to the properties of DAG and click the IP Address Tab and click ADD and type the IP address that you want to use for DAG.
Once that is done, you have to close the EMC or go back to Database TAB and refresh. Once refreshed, you have to add a Database Copy to the Second Member for the High Availability.
To add a database copy to the second server in the DAG, you have to right click the Database for which you want a second copy, and click Add Database Copy. The wizard will ask you for the Target Server, click browse and then select the server where you want the copy to be created.
The wizard will take some time to create the copy and once that is done, you are up with your Exchange Mailbox Servers and your mailboxes are on Full availability.
Installing HAProxy in VMware Environment
In the beginning of the article I have mentioned the links from where you can download the OVF file for VMware. If you have downloaded that, now is the time to add that OVF file into VMware Environment and finish our job. Usually Client Access Servers High Availability is obtained by NLB (Network Load Balancing), But if we deploy HAProxy in our Environment, we don’t have to create the CAS Array based on NLB. We just have to deploy the CAS Servers in our Environment and Add the IP Addresses of all the CAS Servers in the HAProxy Management and HAProxy will automatically load balance the CAS Servers.
After downloading the HAProxy OVF file, open the VSpehre Client and connect to the ESXI Server where you want to import the VM. I have a VMware High Availability Cluster in my environment so I will be deploying the OVF in the cluster. Of Corse in the cluster also you have to choose on which ESXi Server I should be hosting the Machine.
Click File -> Deploy OVF Template:
When you will click OVF Template
You have to browse to the location on your local machine where you have extracted the Zip file.
Once you are at the location click Next, Accept the license agreement and click Next.
Type the name of the Virtual Machine and click the Server where you want the Machine to be placed.
Then in one step it will ask you where to keep the VM files, you have select the Datastore where you want the VM to be. It will be better if you place it in a Volume accessible by all the hosts in a Cluster.
Select the Disk Format of the Storage, i selected thin format.
Click next and you are done.
Once the machine is imported you can power it on.
Once you start the machine you have to login with Username (root) and Password (setup). Login and configure the Management IP address, give the password for the user (admin). Give a load balanced IP Address and give the IP Address for the First CAS Server in the Site. Later when you will add more CAS Server you can add the IP Addresses of those CAS Servers as well.
Related Articles, References, Credits, or External Links
I’ve already covered migration from 2003 here, I got an email today {Thanks Ashley :)} to say that when they tried to migrate the address policies from 2003 to 2010 using this command:
[box]Get-EmailAddressPolicy | where {$_.RecipientFilterType –eq “Legacy”} | Set-EmailAddressPolicy –IncludedRecipients AllRecipients[/box]
They got the following error;
Error on Exchange 2010
Set-EmailAddressPolicy : The recipient policy “Default Policy” with mailbox manager settings cannot be managed by the current version of Exchange Management Console. Please use a management console with the same version as the object.
Error on Exchange 2007
The recipient policy “Default Policy” with mailbox manager settings cannot be managed by the current version of Exchange Management Console. Please use a management console with the same version as the object.
Solution
This happens because In your Exchange 2003 environment, there is a Mailbox Manager Policy that’s been tied to the recipient update policy.
Option 1 (If you have access to the 2003 Exchange Management Console)
1. On your Exchange 2003 Server Launch the Exchange Management Console > Recipients > Recipients Polices > You may have more than one if so repeat this process with each one > right click > Change Property Pages > Make sure “Mailbox Manager Settings” is NOT TICKED. (If it is, Untick it and re-run the command above).
Option 2 (If you DO NOT have access to the 2003 Exchange Management Console)
1. From within ADSIEdit (Install the support tools if you can’t find it) > Configuration > CN=Configuration… > CN=Services… > CN=Microsoft Exchange… > CN={Your Exchange Org} > CN=Recipient Policies > Right click CN=Default Policy > Properties.
2. Locate the msExchPolicyOptionList attribute > Edit > Remove the entry that’s called ” 0xec 0x13 0x68 0x3b 0x89 0xce 0xba 0x42 0x94… (Mailbox Manager Settings)” > OK > Apply > OK.
Related Articles, References, Credits, or External Links
At the time of writing (14/02/13), the answer is NO, for full coexistence with Exchange 2013 you need to have Exchange 2013 CU1 (Cumulative Update), which at this time is unreleased (Expected Q1 of 2013 – so we are not far away).
Note: CU2 is now released.
Solution
So What do I get with Exchange 2010 SP3?
1. You can install Exchange 2010 on Windows Server 2012, (though you can’t in-place upgrade the OS of an existing Windows 2008 R2 server to 2012).
2. Full support for Internet Explorer 10.
3. All fixes from previous update roll-ups, (including MS13-012).
You will need to perform an AD schema update to install SP3.
Related Articles, References, Credits, or External Links
I’ve already written at length about migrating from Exchange 2003 to 2010, I was doing a migration this week and migrating the public folders was proving to be a pain.
If you have multiple public folders within public folders then setting up replication can be a nightmare, as the replication settings don’t get passed down to the child object.
Normally you could use PFDAdmin and this would do it for you, or use the Exchange ExFolder tool, or even the powershell scripts included with Exchange 2010 (like AddReplicatoPFRecursive.ps1). But sadly all these failed for me today.
In the end, with the aid of third line support at Microsoft, it was fixed using a feature of Exchange 2003 that I NEVER KNEW was there 🙂
Solution
1. The bad news is you still have to add the new Exchange 2010 server as a replica on the top level folder. (Right click > Properties > Replication Tab > Add > Add in the new server > Set the interval to always run > priority to urgent (unless you have a LOT! then choose Normal) > Apply.
Update: Eagle eyed visitor Brian Morphey, mailed me to point out that in my diagram all the folders are under the Exchange 2010 Administrative group, How did they get there? You need to use Exchange system Manager to create a public folder group in the new administrative group then simply DRAG the public folder group from the old admin group to the new one.
2. Right click the folder again > All Tasks > Manage Settings.
3. Select “Modify lists of replica servers” > Next.
4. Add servers > Next.
5. Add in BOTH the 2003 server AND the 2010 server > Next.
6. Finish.
7. It will now run through all the sub folders and apply the same replication settings on all of them, this can take a while depending on the number of folders.
8. Go to the Exchange 2010 Server and open the Public Folder Management console, right click Public Folder {your server name} > Update Hierarchy.
9. Repeat the above, but this time select “Refresh”.
10. Finally to speed things along, you can right click each folder and select “Update Content”.
11. Now wait! It can take a while till replication is complete.
Removing Public Folder Replicas
Once All the data has replicated across you can remove the 2003 replica by doing the reverse.
1. Right click the public folder > All Tasks > Manage Settings > Next > Modify List of replica servers > Next.
2. Remove servers> Next > Tick the server you want to REMOVE the replica from > Next.
3. Finish > Depending on the amount of data it may take a while.
Migrating Public Folders with Exchange 2010 Scripts
Step 1 Set up Public Folder Replication to Exchange 2010
On the Exchange 2010 Server open the Exchange Management Shell and execute the following three commands;
[box]
CD “C:Program FilesMicrosoftExchange ServerV14Scripts”
.AddReplicaToPFRecursive.ps1 -TopPublicFolder “” -ServerToAdd “EX-2010.petenetlive.com”
Before we start, I’m aware “Migration”, “Swing Migration”, and “Transition” have three very different meanings, depending on which KB, blog or piece of Microsoft documentation you are reading. Be under no illusions the terminology used in the title and the tags on this page, are to catch the web searches of those who have an Exchange 2003 Server and want to move all their Exchange, to Exchange 2010 server.
There are a lot of people who held out on the upgrade to Exchange 2007, and those people will now be looking to jump straight to Exchange 2010. Unfortunately you can’t just “Pop in the DVD” and let it upgrade. In fact there is no direct upgrade, you need to perform what Microsoft calls a “Transition” to Exchange 2010.
This means you prepare your existing Windows domain and Exchange Organisation, to let Exchange 2010 exist, then you build an Exchange 2010 server, migrate your data into it, and finally remove your original Exchange 2003 server.
Solution
Assumptions:
In this example I’ve got an existing Exchange 2003 environment running on Windows 2003. I’m putting in Exchange 2010 onto a new server running Server 2008 R2. Post install the NEW server will hold client access, mailbox, and hub transport roles.
Exchange 2003 to 2010 Licensing Requirements
Unless you have Microsoft “Software Assurance” you cannot simply upgrade to 2010 for free. You will need to buy the Exchange 2010 Base product (Server Licenses come in two flavours, Enterprise or Standard) and you will need aCAL for each client that will access Exchange. Exchange CAL’s also come in two flavours, Standard and Enterprise (For most people standard is fine, enterprise lets you use archiving and unified messaging. Enterprise CAL’s are an “Add On” you need a standard CAL AS WELL, though you can mix and match, i.e. Have 100 Standard and 50 enterprise CAL’s, (so you have 100 people connecting, but only 50 of then need the enterprise features).
You may wish to look at an “Open Value Agreement”, which lets you pay the cost over a three year term.
Note: An Enterprise CAL is NOT just for Exchange Enterprise 2010 and a Standard CAL is NOT just for Exchange Standard, this is a common mistake.
Note2: To use the archiving feature of the enterprise CAL, you need to have a licensed copy of Outlook 2010 on the client.
Warning: Exchange 2003 let you run a licensed copy of Microsoft Outlook for each client, this was dropped (with Exchange 2007). If you are upgrading Exchange from 2003 to 2010, and have your Outlook licensed like this you will NEED TO PURCHASE licenses for each clients copy of Outlook.
Step 1 – “Pre-Site Visit”
1. Make sure, before you start, that you have the Exchange 2010 media and unlock code, you don’t want to download the media on a site with a slow internet connection, (at time of writing the disk image is 1GB in size).
2. If your existing servers are all x32, and you are also upgrading domain controllers, during the process you will be extending the domain schema (i.e. it’s not 2003 R2) then make sure you have x32 bit Windows media with you.
3. Make sure any third party anti virus and/or mail scanning software is supported and will work on Exchange 2010, and you have the media and licenses handy.
4. You will need to install on a x64 bit server, make sure you have a server capable, and Windows x64 bit media with licenses.
5. You will need your Exchange 2003 CD, it’s fond of asking for it during the uninstall process.
6. Before you even think about going further make sure you have a good backup! If you are lucky enough to have VMware ESX, Hyper-V or another virtualisation platform, consider doing a P2V conversion on your Exchange 2003 server then simply turning the 2003 Server off, then if it all goes to hell in a hand cart simply turn the original server back on again.
7. While your thinking about backups – does your backup software support Exchange 2010? you might need a new Exchange agent, check with your software re seller.
Step 2 – “Pre Install”
1. Before you do anything, it’s time for a common sense check, make sure your existing Exchange 2003 Organisation is happy and running cleanly, and has good communication with the domain and DNS. Get in the event logs and make sure its a happy server.
Time spent on reconnaissance is seldom wasted!
2. Make sure your Exchange 2003 server(s) is/are up to “Exchange 2003 Service Pack 2” (In fact get the latest Exchange update roll up after that as well to be on the safe side).
Note: Update 07/01/15: Ensure if you use ActiveSync, that you install this hotfix on the 2003 server. (Yes it says for Exchange 2007 co-existence, but it’s relevant to Exchange 2010 upgrades as well).
Exchange 2003 Build Numbers
Microsoft Exchange Server 2003 6.5.6944 October 2003 Microsoft Exchange Server 2003 SP1 6.5.7226 May 2004 Microsoft Exchange Server 2003 SP2 6.5.7638 October 2005
If it looks like this, your onto a winner;
3. The brief says your Global Catalog server should be at at least Server 2003 SP2, however I’d be updating all the domain controllers to Service Pack 2. (Note: you need 381Mb free space on the system drive, plus 170MB additional free space to install SP2).
Locate the Global Catalog Server
Find the Service Pack Level
4. The domain functional level needs to be at “Windows Server 2003”. When done, leave enough time for it to replicate to all domain controllers in the domain.
5. Now the forest functional level needs raising to “Windows Server 2003”. When done leave enough time to replicate across the entire forest.
6. Now you need to put your existing Exchange organisation into “Native Mode”.
Multiple Exchange 2003 Servers Note:
7. If you have multiple Exchange 2003 Servers with routing groups you need to suppress link states, on EVERY Exchange 2003 server, Start > Run > regedit {enter} > Navigate to Locate HKEY_LOCAL_MACHINESystemCurrentControlSetServicesRESvcParameters > Right Click > New DWORD > Call it SuppressStateChanges. > Set its value to 1 >Then either reboot or restart the Simple Mail Transfer Protocol (SMTP) service, the Microsoft Exchange Routing Engine service, and the Microsoft Exchange MTA Stacks services.
8. At this point I would apply the “cup of coffee” rule, then check the domain controllers event logs and the event log on the Exchange 2003 box make sure everything is running smoothly.
9. Now you THINK Exchange is happy, it’s time to MAKE SURE download and then run the Microsoft Exchange Pre-Deployment Analyser (ExPDA).
9. Continue to run and fix any problems it reports. Note: If you use a smart host, you may see the following warning,
SMTP is configured to route all messages to a smart host.
You may have some mail routing issues if you leave your smart host configured (it’s set on the Virtual SMTP server on the Exchange 2003 Server (or on your SMTP connector if you have one in routing groups)). Remove it for now, and add it back to the 2010 Send connector later.
Step 3 – “Deploy Exchange 2010“
1. Build your new server and apply all the latest service packs and updates. Join it to the domain, and log in with a user account that is a member of the Schema Admin’s group, before proceeding you need to install the Office 2010 filter pack on the new server CLICK HERE.
Warning: Never disable IPv6 on an Exchange 2010 Server! Make sure it’s installed before proceeding.
2. You need to add certain roles to the new server before attempting to install Exchange 2010 you can script that though I prefer to do things myself. Start > Server Manger > Roles > Add Roles > Next > Select Web Server (IIS) > Next > Next.
3. On Role Services, under security > tick Basic Authentication > tick Windows Authentication > Tick Digest Authentication > Under Performance tick Dynamic Content compression.
4. Under Management Tools > Select IIS6 Management Comparability > Next > Install > Close (when finished).
5. Now you need to add “Server Features”, primarily .Net Framework 3.5 that is in Server Manager > Features > Add Features > Expand .NET Framework 3.5.1 Features > Expand WCF Activation > tick HTTP Activation > Select to add Required Role Services.
6. Scroll down and below “Remote Server Administration Tools” > Role Administration Tools > Select “AD DS and AD LDS Tools” > Next > Next > Next > Install > Close (when finished) > You may be asked to reboot.
The next step cannot be carried out unless you have rebooted.
7. You need to set the startup type of the “Net Tcp Port Sharing” service to automatic > Click start > Run > Services.msc {enter} > Locate the Net Tcp Port Sharing Service and set its startup type to automatic.
8. Put in the Exchange 2010 DVD, run setup.exe. If you are using the multi language version you should be at “Step 3: Choose Exchange Language option” > Select it. > Select Install Languages from DVD.
9. Select “Step 4: Install Microsoft Exchange” > Files will extract and setup will Start.
12. No, we don’t want to do error reporting > Next > Select “Typical” > (If you’re installing with SP1 see the note below) > Next.
*****Update 18/03/11*****
If you are deploying Exchange 2010 with SP1 included, at this point select “Automatically install Windows Server roles and features required for Exchange Server”
13. If this is the only one, or it going to be your main “Bridgehead Server” then it will be internet facing > tick the box > enter your domain name > Next
14. At this point you select your existing Exchange 2003 Server > Browse to it > Select it > Next > No we don’t want to join the CEIP > Next.
15. Exchange will perform its readiness checks, it will probably give you a couple of warnings, the first one is telling you (once ran) you can’t have an Exchange 2007 server in the domain, and the other it telling you to replicate free/busy data if you have Outlook 2003 clients. (We will sort that out later). > Click Install.
16. When done click Finish.
17. The Exchange management console will open, to enter the Product Key, select “Server Configuration > Select the server > Select Enter Product Key. Then either restart the exchange information store service or reboot.
Note: You will notice that, if you look in the Exchange 2003 Management Console you now have an extra administrative group (Called FYDIBOHF23SPDLT – that’s geek humor, roll each letter and number back one).
Step 4 – “Configure and Migrate”
1. Your new server will have one mailbox database and one Public folder database, you can change their paths, if you want to move them onto faster drives, or other volumes. Select “Organisation Configuration” > Mailbox > You can right click each data store and move it if required. Note: You can also set up local continuous replication here as well.
2. Now Its time to make sure nothing is broken, go to the existing Exchange 2003 Server and check mail flow inbound and outbound.
3. Do you have any clients running Outlook 2003 or earlier? If you do remember the warning we saw earlier?
Warning: If Microsoft Outlook/Office 2003 is in use, you should replicate the free/busy folder on this server to every other free/busy server in the organization. This step should be performed once setup completes.
Well now, lets assume we do have Outlook 2003, this means calendar scheduling is done from a public folder (called the SCHEDULE+ FREE BUSY folder) this public folder needs to be replicated to our new server, or calendaring and scheduling will break. Note: If your clients are Outlook 2007 or above then skip this step – those clients use the auto discover service instead.
On the Exchange 2003 Server Open Exchange Management > Locate the Public folders > Change the view to “System Folders”.
Then expand the “SCHEDULE+ FREE BUSY” folder and locate the folder that has the same name as your OLD administrative group (i.e. NOT the one with FYDIBOHF23SPDLT in it). right click it and select properties.
Then on the replication tab, add in the NEW Exchange servers “Public Folder Database”.
Once you have it added, set the replication.
4. Do you use Public Folders? If not skip to the next step, if you do you will need to replicate them to the new server. If you have just completed the step above the procedure is the same. On the Exchange 2003 Server, open Exchange System Manager> Locate the Public folders > If you cannot see your public folders, change the view to “View Public Folders”.
Select each one of your public folders, go to its properties and add in the New Exchange 2010 Server as a replication partner.
Note: If you have a lot of “Nested Public folders” then this can take ages, click here
Note: If mail cannot flow from 2003 to 2010 then the public folders will NEVER replicate make sure that works before expecting the folders to replicate OK. If it does skip to number 5.
Mail will not flow between Exchange 2003 and Exchange 2010
This happens a lot! The quickest and simplest way to fix it, is to delete and re-create the routing group connector between the Exchange 2003 and Exchange 2010 server. Execute the following four commands in the Exchange Management Shell. (Just insert your server names).
Note: If replication fails and you recieve an Event ID 1020
The store driver couldn’t deliver the public folder replication message “Backfill Request (SMTP Address)” because the following error occurred: Property: [0x3ff00102] , PropertyErrorCode: UnknownError, PropertyErrorDescription: 0x80040107.
Then go to Microsoft KB2855083
5. At this point you need to change the SMTP feed from the old Exchange 2003 box to the new Exchange 2010 Server, how you do this depends on your network setup, some examples of how you might do this are,
i. Change the SMTP (TCP Port 25) Port redirect on your router/firewall address ii. Swap IP addresses from the old to the new server. iii. Change the translation from public to private IP address to point to the new IP.
Note: If you have any mail scanning servers, anti spam hardware devices etc, then they will also need changing to point to the new server.
6. Once the SMTP Feed has swapped across, inbound mail may fail and return the following error,
EX2010.domaina.com #530 5.7.1 Client was not authenticated ##
To fix that you will need to allow anonymous access on the servers default receive connector.
You may also find outbound mail will fail and sit on the outbound queue with the following error,
A matching connector cannot be found to route the external recipient
To fix that you will need to create a “Send Connector”. Launch the Exchange 2010 Management Console > Organization Configuration > Hub Transport > Send Connectors > New Send Connector.
Give the new connector a name > Under “Select intended use for this send connector”, select “Internet” > Add >Set the address space to a single asterisk > Select “Include all sub domains” > OK > Next > Enter a smart host (if you use one, or you removed it earlier) > Next > Next > New > Finish.
Then test mail flow works once again, this time through the new server.
7. Now you can start moving mailboxes from the old server to the new one. What I tend to do is move one mailbox, test mail flow outbound/inbound, then test mail flow internally from the mailbox I’ve just moved, to a mailboxes that’s still on the old server. Once I’ve proved this works I will move the rest of the mailbox’s.
To move a mailbox, open the exchange 2010 management console, expand “Recipient Configuration” > Select Mailbox > You should see all the mailbox’s listed > Right click the mailbox you want to move > Select “New Local Move Request”.
At the introduction screen, hit the browse button and select your new servers data store > Next > Next > New > Finish.
Once you have moved one and tested it you can move the rest of the mailboxes.
8. Next task is to change the server responsible for generating the offline address book. On the Exchange 2010 server Exchange Management Console, Expand “Organization Configuration” > Mailbox > Select the “Offline Address Book” tab > Right click the Default Offline address book and select “Move” > Browse > Select the new server > OK > Move > Finish.
9. The old Exchange server relies on the recipient update service, the new server does not. If you try and edit your address policy with the Exchange 2010 console you will see this error,
“The specified e-mail address policy couldn’t be edited. E-mail address policies created with legacy versions of Exchange must be upgraded using the ‘Set-EmailAddressPolicy’ task, with the Exchange 2010 Recipient Filter specified.”
Unfortunately this can not be fixed in the management console, you need to issue some powershell commands to fix it. Click Start > All Programs > Microsoft Exchange Server 2010 > Exchange Management Shell.
Issue the following command,
[box]
Get-EmailAddressPolicy | where {$_.RecipientFilterType –eq “Legacy”} | Set-EmailAddressPolicy –IncludedRecipients AllRecipients
[/box]
Once executed you need to press “Y” to accept.
Note: You may have multiple recipient policies in operation, they will all need upgrading.
Note2: If you get an error along the lines of “Mailbox manager settings cannot be managed by the current version of Exchange Management Console” Click here.
10. While we still have the “Management Shell” window open we need to update our “Address Lists” as well to do that issue the following 5 commands one by one.
11. At this point locate the directories that hold your new Exchange databases and logs, and MAKE SURE that these folders have been excluded from your normal AV scanning. AV has a habit of quarantining Exchange log files and breaking the database – this is easy to fix when the stores won’t mount but it’s not good!
Step 5 – “Do Nothing“
Seriously, now you need to wait, before you can proceed all the public folders need to have replicated to the new server, in some cases this can take days, as a general rule of thumb, at this point I would wait 1 week before proceeding to decommission the Exchange 2003 server, this allows for both public folder replication, and any head slapping “Doh! we forgot to {insert random forgotten thing here}”.
Also in this time, any clients running Outlook (Pre 2007) can log in, and will get their Outlook profile automatically updated to point to the migrated mailbox on the new Exchange 2010 server.
Step 6 – “Decommission and remove Exchange 2003”
1. Lets check our public folders, this one is in sync.
And then switch to system folders (See here if you forgot how to swap the view). If you see the status as “Local Modified” or “Remote Modified” then check the item count on the folders to make sure they have the same item count (Select the status column).
2. Once you are happy you can remove the replica that is on the Exchange 2003, > Properties > Replication > Select the 2003 Server > Remove > Apply.
4. Remember when you installed Exchange 2010 it created a new administrative group in your Exchange 2003 organisation? (The FYDIBOHF23SPDLT one). It did this to connect to the existing organisation, and it created some routing group connectors, you now need to remove them.
5. Even though Exchange 2010 does not use the recipient update service, you need to tell Exchange 2003 that it does, because you can’t remove Exchange 2003 from a server that thinks it is providing Recipient Update Services. Launch the “Exchange System Manager” > Expand recipients > Select Recipient Update Services > Right click each one and change the server name to the new Exchange 2010 server. Do this for EVERY policy.
Note: With Exchange 2010 (post SP1) This May Not Work!
So that you can gracefully remove Exchange 2003, The Recipient Update Services needs to be removed first. If you cannot gracefully remove it (as above). Then you will need to Manually Remove it from Active Directory. To do this run ADSIEdit.msc (On Server 2003 you will need the support tools installing first). Then navigate to;
Then delete the entries in the right hand window.
6. Have a quick common sense check! Are you sure everything is OUT of your Exchange 2003 Databases? If so, delete your stores from Exchange 2003 > you will need to dismount them first > Repeat for all private databases.
7. Finally you can now go to “Add or Remove Programs” and remove Exchange 2003. (Change the action type to “Remove”). Note: You may be asked to insert the Exchange 2003 install media.
When done reboot the server.
Step 7 – “Finish up“
1. Now you may need to change your backups to include the new data stores. Your backup software may require you install the Microsoft Exchange Server MAPI Client and Collaboration Data Objects, before you install the backup agents (ARCserve and Symantec Backup Exec for example).
2. If you have any links to “Outlook Web Access” (i.e. on your public website or in Share point, they will need the URL’s changing from https://server/exchange to https://server/owa if you would like to redirect http to https see the following article,
3. Be aware: some AV software (McAfee for example) likes to block TCP port 25 (SMTP), this is not good on an Exchange server! Don’t forget to disable this feature or you may have mail flow issues.
4. You may get some support calls like “internal user A cannot send an email to internal user B” if that happens check that they are NOT using the automatically remembered email facility in Outlook. This stores previously typed email addresses in a local file called an NK2 file (or nicknames file), but it stores internal addresses like this…
Those paths no longer exist, get then to pick the name from the “Global Address List” instead, or if they are really persist ant you can add a line to the login script that deletes the .nk2 file.
5. ActiveSync problem on migrated users. You may find there is a problem with some migrated users unable to use ActiveSync, if that is the case see the following link.
Thanks to Rick Faria, who both pulled me up on my shoddy technical terminology, and asked,
The only thing I don’t see in your article and actually the thing that seems to be the most involved is dealing with trying to move over your Exchange 2003 SSL cert for OWA or if your renewal is close taking care of that with a new one. You don’t really mention that process.
Related Articles, References, Credits, or External Links
Thanks to Mark V for the hotfix to 2003 update. Thanks to Rasmus Haslund for the feedback. Thanks to Dave Pape for the feedback Thanks to Jay Malone for the “Removing RUS information” Thanks to Shane Brath for the feedback and suggestions. Original Article written: 11/10/12
Whilst doing an Exchange 2003 to Exchange 2010 migration last week, I moved a test mailbox to the new Exchange 2010 server. But when I attempted to open the mailbox in OWA I got this;
“Your request couldn’t be completed because no server with the correct security settings was found to handle the request. If the problem continues, contact your helpdesk.”
Solution
At first I assume this was some IE error and was probably because I was on the Exchange 2010 server and trying to open the test mailbox there, instead of a client where the security on IE would be a little more lax.
But that was not the case, it turns out you see this error when the mailbox is still on the 2003 server and has not yet moved to the new server. When I actually checked the mailbox move was ‘stuck’ in a queued state.
Related Articles, References, Credits, or External Links