If Add2Exchange was working and now it's not, post here.
I know you mentioned that Add2Exchange will work with Exchange 2010. But we haven’t spoken about the mixed mode i.e. when we have to run both 2003 and 2010 at the same time. So some of our users will be on 2003 and some on 2010 or 2013 for the duration of the migration. How will Add2Exchange handle that? Thoughts, comments, recommendations? Thanks…
Add2Exchange Std and Enterprise will both work fine
After you install the new Exchange box, run this
Download and run THE LATEST version of Add2Exchange (STD or EE) using these procedures: http://support.diditbetter.com/kb/A2E_194.aspx. Be sure to note the website now uses cloud downloads so you have to download the helper application and then run that to get the setup. Tip: Save the webpage it redirects you to as a favorite.
It is important to get the newest version of either Add2Exchange Standard (STD) or Enterprise (EE) version upgrade you have installed to avoid a cross grade. Pick the right version because upgrading to Enterprise from Standard is easy, to undo that is quote a project.
If you have already migrated mailboxes and the relationships are in alert, see this post:
Even if you have not migrated and want to know your options, including free options, read the above post.
When you are ready to move the mailboxes or stores
Stop the Add2Exchange Service
Finish the Exchange PF or mailboxes moves for that step in the migration
Start the Add2Exchange Service and wait a full sync
Any of the relationships with parts you moved will go into alert
Then download and run THE LATEST version of Add2Exchange (STD or EE) Recovery and Migration manager – If you don't already have it licensed, then submit a license, and use the store or call in to paynow. The license soft subscription matches that of A2E and is only $125 if you are on Premier Support. Buy Now Please verify you are running the latest because previous versions had mishandled exceptions, like when you had deleted a user prior. Get the new RMM by uninstalling the older version and installing the new one. Buy Now
Then carefully run RMM it and fix and repoint the rels to the new box. Warning: Be sure to use the Plus (+) key when opening up child folders since a doubleclick is like entering, and picking the parent folder will be a disaster since it will repoint to the WRONG folder for EVERYONE who had that folder in a relationship. Go slow at first and match the red words to the Tree Structure.
That’s about it.
Next time you do the next step in the Migration, do the same process above except all the upgrading.
When you have a date when you are planning to start the process please email firstname.lastname@example.org for a firm time. We can handle it as a Level 3 incident or Level 5, Premium Support. It takes over an hour for the process and we will train you so you can do this when you need to since it may go in several phases. We use our remote support tool to accomodate, but can usually use any tool you have. http://support.diditbetter.com/remote-support.aspx.
After you have migrated, your Exchange 2003 server may still provide CAS services so the relationships may not go into alert immediately. Once the 2003 server is decommissioned or stores are downed, the relationships will surely go into alert. Add2Exchange Console will fail to open with a CDO fail to log on message. BTW, decommission the old box by using this procedure: http://support.diditbetter.com/kb/A2E_217.aspx
The fail to log on and repoint to new server is simple to fix, because the program will auto ask you to change the exchange Server name, so go ahead and put the netbios name or fqdn of the new Exchange machine or CAS in now. Leave the Service account name as it is.
If A2E is installed on the old 2003 Exchange Server, then it will probably work as it is, but you may want to migrate A2E off of there. My best advice is to build a VM for us to use so the program does not have to be moved again and we can tailor our environment for best performance. http://guides.diditbetter.com/a2e-guide/system_requirements.htm and for Exchange: http://guides.diditbetter.com/a2e-guide/exchange_2003_configuration.htm
To move A2E, you could just deleted all rels and remove dest copies and reinstall fresh and remake them but many people don't want to do that amount of effort and the users are without the information. Also, calendar entries in the past will not get recreated, but sometimes that is good. To do in place migration of A2E, many use the Server Move tool in the licensed side of the A2E Toolkit. Buy Now
The same licensing deal applies to this tool as the RMM tool. If you are going to leave A2E here, you would have to update CDO to talk to the new server. If A2E is staying on the old box, uninstalling Exchange is the only answer. Stop the Add2Exchange Service and put on Manual. Uninstall Exchange and reboot and then install ExchangeMapiCDO located in the \Preinstaller directory in the downloaded A2Eupgradezip file.
The next step is relicensing. When you change the name of the Exchange Server, the licensing goes out and it will have to be relicensed. If you are on Premier Support, we submit a request and relicense it at no charge, and if not, there is a $50 per module license transfer fee. Use this process: http://guides.diditbetter.com/a2e-guide/license_menu.htm
Then, when you get the keys, paste them in and it will thank you, as do we all. Close the A2E Console and be sure to start the Add2Exchange Service. Warning: on some 2008R2 boxes, closing the Console does not ask you to start the A2E Service automatically, so use the Services control manager function or the white Diditbetter.mmc icon on the desktop, a really handy tool to manager A2E, consolidating Services, Event Viewer, AD, 2003 Exchange and others into one MMC place.
TiP: When you are going to do an MS Critical update, migration or reboot the box, use our start and stop utilities as a tool to make sure it is done in an orderly fashion. These are smarter net start and net stop utilities and these are the only programs we install which any user of the machine can use. (This is not the truth with the Add2Exchange Console - only the Service account can use this - so no shortcuts to that please.)
The Add2Exchange Stop will stop the A2E Service then wait and then when done, will stop our A2ESQLServer instance. To start, it starts the A2ESQLServer first and then the A2E Service. Tip: Copy these and only these shortcuts to these programs to the desktop of all users:
Hope this helps clarify