Exchange

For a complete guide on how to check these values and to also extend, prepare and verify Active Directory for Exchange, click here.

Exchange 2019

Exchange 2016

PREVIOUS: Migrating Exchange 2003 to 2010 – Part IV

We are in the home stretch! This has been a great series. I hope it has been beneficial to you.

In our final article, we will cut mail flow over to the 2010 server. We will also take a look at Offline Address Books. Finally, we will decommission our 2003 server.

PREVIOUS: Migrating Exchange 2003 to 2010 – Part III

In our previous article, we ran through the Exchange Setup Program. We then discussed and implemented our namespace. We configured a split-brain DNS. Then we wrapped up by applying a 3rd-party certificate.

In this article, we will move our databases and logs to their dedicated disks. We will configure Public Folder replication. Move test users and confirm mail flow to the new server. Discuss backing up Exchange 2010. Move production users.

PREVIOUS: Migrating Exchange 2003 to 2010 – Part II

In our previous article, we sized and built the base for our multi-role Exchange Server. Then we extended our Active Directory Schema.

In this article, we will run through the Exchange Setup Program. We will then design and implement our namespace as well as configure split-brain DNS. We will finish by applying a 3rd-party certificate.

PREVIOUS: Migrating Exchange 2003 to 2010 – Part I

In our previous article, we discussed how to check and raise the domain, forest, and Exchange functional levels. We also looked at the minimum service pack requirements for our domain controllers.

In this article, we will look at extending our Active Directory Schema and begin installing our multi-role Exchange server.

With Exchange 2003 going end of life in less than two weeks, I have had a significant influx of last-minute migrations and migration questions.

For those that don’t know, Exchange 2003 is reaching end-of-life on April 8th, 2014.

What this means is that there will be no further patches or service packs for this product, nor, will you be able to receive any form of paid assistance from Microsoft.

You may be able to find a consultant that can help with Exchange 2003 for years to come. Keep in mind, that finding someone with that knowledge and skillset will diminish over time.

Real World: A couple of years ago I helped a friend with a failed Exchange 5.5 box. Yes, that is not a typo. We were able to get it operational. The miracle is that I remembered a best-kept secret from 5.5 to get it going. These were things I hadn’t thought about in 12 years!! I truly shocked myself.

The larger concern, however, is the complete lack of updates. If an exploit were to be found in the product, after April 8th, you are on your own.

Now, is the time to upgrade!

There are many great articles that have already covered this process. One of my favorites is by Jaap Wesselius. And while Jaap writes a fantastic article I wanted to write my own article for a slightly different audience in mind.

That of the small business.

Specifically, seventy-five users and below.