Transition from Exchange 2003 to 2010

I am preparing to transition from an Exchange 2003 to a 2010 server. We only have 1 Exchange 2003 server and the new 2010 server is going to host all roles (except Edge) and run on a Win Server 2008 R2 server. I am updating our Domain Controller to be on a 2008 R2 server also. I've read some upgrade documents suggested on this site and reviewed the MS Deployment Assistant, but I have some questions.

1. My current Primary DNS suffix is xxx.local, but all the mail comes in addressed to mycompany.net. Does that mean I have a 'Disjointed Namespace'?

2. In the Deployment Assistant under 'Configure Disjointed Namespace', it references a document 'Domain Rename Procedure'. It's not telling me to rename the domain is it?

3. I was thinking about getting my certificate before starting the upgrade, but I was concerned that it would 'break' the old one and not allow OWA, ActiveSync, and Outlook Anywhere traffic thru. If I preorder the cert with the same domain name mail.mycompany.net, with other domains on it, will that break the old one? If it does break, could I install the new cert on the old Exchange server if the computer name is not on the new cert?

4. I'm planning on installing on a VMware 4.1 virtual machine. Are there any concerns doing this?

Any other advice?

Thanks,
imccoyAsked:
Who is Participating?
 
Jian An LimConnect With a Mentor Solutions ArchitectCommented:
if you're going to swap the server (i.e. exchange 2010) in, you will at least got some warning your user will lost some access.

It is always recommend to perform after hours.


okay, for new cert, since exchange 2010 use SAN (include autodiscover.domain.com, and all local domain cert), you need to request a new cert.

Depends on security, I usually find a wildcard certificate helps in this case as you can pre-order them (and it take a bit longer to order as it will goes to domain owner to verify and etc) then you can configure your exchange 2010 to use wildcard certificate (read wildcard certificate and exchange 2010. there are few article explain how it works)


the microsoft way is to move your Client access server first beefore your mailbox.
Given you only have 1 server, i really suggest to do this over a weekend and declare out of service during the weekend.

0
 
Jian An LimSolutions ArchitectCommented:
1. Disjointed Namespace only happen when you upgrade from windows nt4. if you start with windows 2000, you wont have Disjointed Namespace.

2. same as above

3. if you are using mail.mycompany.net, if you pre-order the same one with the provider, then you will break your first one. or else you wont. Also make sure you have a SAN certificate (to include all possible name), or a wildcard certificate

4. I believe is vsphere 4.1. make sure you read the pre-requiresite for Hardware Virtualization  under http://technet.microsoft.com/en-us/library/aa996719.aspx
0
 
imccoyAuthor Commented:
I'm still a little confused on how to handle the certificate. I want to use the same mail.mycompany.net so I won't have to change all of our remote users settings. So how should I proceed:

1. Get a new cert and run it on both servers? Is that possible?

2. Wait until I get Echange 2010 installed and try to get it done in one day? Will all of my ActiveSync & Outlook Anywhere users loose access until I can migrate all of the mailboxes?

Thanks.
0
 
imccoyAuthor Commented:
Thanks for the help
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.