• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 303
  • Last Modified:

Best method to replace Physical Exchange Server 2003 with Hyper-V Virtual Machine of same on Server 2008

I am looking for advice on the best way to accomplish a project, as follows:

Our organization runs on a single domain, the DC is Server 2003. We have Exchange 2003 running by itself on a Server 2003 machine which is pretty much out of physical hard drive space, and very old. We have a couple of huge Server 2008 R2 machines that we are now running Hyper-V Virtual machines on, all Server 2008 R2, for file server, SQL, Web Server, Etc.

I want to set up a VM for Exchange Server 2003 so that I can move everything from the old Exchange server to it, replacing the old machine which would be retired at that time.

My questions are:

1. Should I set up a Server 2003, or a Server 2008 VM to run Exchange 2003 on? I know we are licensed already for Server 2003, but will it run as a VM with no problem?

2. Is ths as simple as creating a Server 2003 or 2008 VM, then installing Exchange 2003 on it with a dfferent name than the existing Exchange server, then moving mailboxes, exporting / inmporting settings, pointing our email from the outside to the new Exchange Server, and finally pointing everyone's Outlook at the new Exchange Server?

Any and all advice is appreciated - thanks!
0
ksoszka
Asked:
ksoszka
  • 7
  • 7
1 Solution
 
endital1097Commented:
1. you can only run exch 2003 on win 2003 and it will run on a VM
2. follow the article http://support.microsoft.com/kb/822931
0
 
endital1097Commented:
you may also want to consider using this time to migrate to exchange 2010
there are huge performance gains between these two versions as well as features
0
 
ksoszkaAuthor Commented:
endital1097, actualy we are licensed for Exchange 2010 too, but I am in a time crunch and want to keep this simple in order to get it done quickly. I will be moving from 2003 to 2010 though eventually. I am thinking I will need to get my DC up to 2008 for sure though, and the exporting of 2003 to 2010 must be a bit complicated, correct?
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
endital1097Commented:
your dc just needs to be 2003 sp1
there is more to the 2010 config so it would be quicker going to 2003
0
 
endital1097Commented:
in other words move to the new 2003 and get familiar and tweak 2010
0
 
ksoszkaAuthor Commented:
Ok, that MS help article looks pretty good. I will read it. What else is there for me to consider regarding getting the mail from the old server to the new one?
0
 
endital1097Commented:
if this is the only server in the exchange organization it is really simple and that article should cover it all
move mailboxes
replicate public folders
update the recipient update service
update offline address book settings
update smtp connectors
0
 
ksoszkaAuthor Commented:
EE has suggested I comment to keep this post active, I have not had a chance to do anything yet and now the holiday weekend is here, See y'all next week!
0
 
endital1097Commented:
enjoy :)
0
 
ksoszkaAuthor Commented:
Ok, that article tells me how to prepare to remove my old server, including moving stuff off it and reassigning roles. As far as installing the new server before I do all that, is there anything special that I should look out for or do, since it will be the 2nd Exchange Server at the time that I install it? Thanks!
0
 
endital1097Commented:
no, just make sure you install it in the same admin group and routing group
0
 
ksoszkaAuthor Commented:
Ok, I have only one of each of those, so no worries there. I'll begin now. Not going to accept solution yet, until I get at least some done. Thanks!
0
 
ksoszkaAuthor Commented:
Hi endital1097, so, I have a fresh Windows Server 03 install VM running and updated. I have not joined it to the domain yet. I am going to do so next. Then I will be installing Exchange Server 2003 on that server.

I found this article on Installing New Exchange 2003 Servers:
http://technet.microsoft.com/en-us/library/bb123643(EXCHG.65).aspx
which refers to this article "How to Move Exchange Server 2003 to New Hardware and Keep the Same Server Name":
http://technet.microsoft.com/en-us/library/aa997176(EXCHG.65).aspx

So, my question is what would be the advantage, or necessity, of keeping the same server name?
0
 
ksoszkaAuthor Commented:
Hi, I would like to accept one of the solutions.
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 7
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now