[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Adding Windows Server 2008 enterprise DC to existing Small business Server 2003 Domain

Posted on 2011-05-09
28
Medium Priority
?
352 Views
Last Modified: 2012-05-11
Currently our company has a Windows Server 2003 Domain Controller that also serves Exchange 2003, DNS, AD, file server, blackberry enterprise server.  I have just purchased a new system with VMWARE ESXi and would like to break up the services into separate virtual machines.

here are my main questions:
what would be the best way to split up the services into different vm's?
how/when should I add the new Domain controller to the domain?
how/when should dns duties be transferred?
what is the easiest way to transfer the mailboxes from exchange 2003 to exchange 2010?

i plan on taking the existing DC that is providing basically all of our services and throwing it out the window so to speak once I get the new one up and running.

0
Comment
Question by:tkdwarrior
  • 13
  • 8
  • 5
  • +2
28 Comments
 
LVL 97

Expert Comment

by:Lee W, MVP
ID: 35724639
Things to keep in mind:

*You need to replace all Client Access Licenses with CALs for Exchange 2010 and Server 2003 (Enterprise comes with 25 for Windows, NOT for Exchange)
*You will no longer have "Remote Web Workplace" functionality
*You will no longer have as many management wizards to make management easier
*You will pay more than if you purchase SBS 2011 and run that in a VM
*You will not have any fail-over in terms of secondary DCs - if the physical hardware fails, you will be DOWN.

0
 

Author Comment

by:tkdwarrior
ID: 35724720
ok, I already have paid the money and I have Windows Server 2008 R2, Enterprise Edition ready to be loaded.  It also allow me 4 virtual machines licenses running enterprise edition as well(takes care of the need to split up services)
0
 
LVL 124
ID: 35724729
1. Domain Controller Server - services AD, DNS and DHCP
2. Exchange Server 2010 - services Exchange 2010 and BES
3. A File Server - File and Print Services

4. Create a new Windows 2008 VM now, and add to domain. DCPROMO (use /adprep)
5. Migrate AD Roles to new Windows 2008 VM (AD, DNS and DHCP)

6. Install Exchange 2010 into existing Exchange 2003 organization, and transfer mailboxes.

These are all at a very high level. There's a lot of work to do here, in one question!
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 

Author Comment

by:tkdwarrior
ID: 35724761
any links or detailed description of what im actually going to have to do that will take 'a lot of work'?
0
 
LVL 31

Expert Comment

by:Justin Owens
ID: 35724826
I would not put BES and Exchange 2010 on the same virtual.  It will cause looping.  Better to have BES on a different machine.

DrUltima
0
 
LVL 28

Accepted Solution

by:
bgoering earned 2000 total points
ID: 35725404
0
 

Author Comment

by:tkdwarrior
ID: 35725418
@bgoering   VERY NICE.  this is the kind of step by step instructions i was looking for.  I am still in the process of backing up the source server and will begin the migration itself this weekend when people are out of the office.  If anyone else has any tips feel free to chime in.
0
 
LVL 28

Expert Comment

by:bgoering
ID: 35725529
Glad to be of help - good luck with your migration. Let us know how it goes
0
 

Author Comment

by:tkdwarrior
ID: 35751506
Ok as I am preparing to follow the migration strategy at http://www.servermigrationlabin.com/2011/01/migrate-sbs-2003-to-server-2008-r2-with.html, I am noticing that my situation will call for different steps.  My server is going to be broken down into 3  virtual machines and the migration strategy provided assumes all services will be migrated to 1 physical windows 2008 box.  Also, I would like to end up giving the ip address that the 2003 server currently holds to the new AD, DNS, DHCP VM running server 2008.  What would be the best route for doing this?
0
 

Author Comment

by:tkdwarrior
ID: 35751526
Also, with the suggested migration strategy, how long should I warn people that the Exchange server will be down so they know when they wont be receiving email anymore?
0
 
LVL 124
ID: 35752196
Give yourself a Windows with enough time, so your not under pressure to rush and get service backup.
0
 
LVL 124
ID: 35752200
If you understand what is required, I would give yourself an entire weekend.

Friday 5pm Shutdown - Service Outage.
Monday 8am Startip - Service Restored.
0
 
LVL 28

Expert Comment

by:bgoering
ID: 35753543
How will you be dividing the services amongst the three machines?
0
 

Author Comment

by:tkdwarrior
ID: 35754394
i plan on doing this migration this weekend starting tonight(friday) until whenever i get finished.  I just need to tell them how long email will be down.  is there someway i can 'catch' the emails during the time im down?  do i need to be offline the whole time i do the migration?  

heres how i will split up the services on VM's

1. Domain Controller Server - services AD, DNS and DHCP
2. Exchange Server 2010 - services Exchange 2010
3. A File Server - File and Print Services + Blackberry express server

thanks!
0
 

Author Comment

by:tkdwarrior
ID: 35754508
While I'm at it.  I currently have a complete system backup of the server 2003 box using Symantec System Recovery.  Should this be sufficient or do you know of any horror stories tied to this software?  I may go ahead and download the trial of Acronis True image and do a full backup using it as well.  I would HATE not to be able to restore the 2003 box if something goes wrong!
0
 
LVL 28

Expert Comment

by:bgoering
ID: 35754537
I would think that you could do a fair amount in advance - installing and patching up to date the destination servers for example. The amount of time to migrate depends mainly on how much data you have to migrate. If you plan to do it all over a weekend I wouldn't worry too much about losing email as typical mail servers will retry delivery for several days before giving up.

Follow the article posted above. Do all of the Active Directory, DNS, DHCP tasks to get the environment to the new AD server, then do all of the exchange tasks to get the mail and folders moved. The file and print would just involve adding the file server role to the destination server, creating shares, installing printer drivers, etc. - then copying the data over (look at robocopy).

The BES server I am not very familier with so far as migrating. Perhaps you would want to make a new question in the Blackberry group on how to migrate that piece.
0
 
LVL 124
ID: 35754554
Can you ISP Store and Forward your mail queue?
0
 

Author Comment

by:tkdwarrior
ID: 35754556
The blackberry express server isn't a worry at all.  I can configure that from scratch with no problems.  We only have 15 users total within the organization so the data migration SHOULDN'T take extremely long.
0
 
LVL 28

Expert Comment

by:bgoering
ID: 35754580
LOL - no, I have not heard any horror stories about Symantec (but I don't use it myself). I like the Acronis idea - I have used that once or twice for P2V migrations and it worked well for that. One can't have too many backups!
0
 

Author Comment

by:tkdwarrior
ID: 35754623
and to touch on my question above about the new server taking over the old server's IP address.  After I migrate everything over to the 2008 server, can I just flip flop the assigned ip address from the 2003 server to the new one?  Currently all outside email is sent to 172.x.x.30(the 2003 box).  
0
 
LVL 28

Expert Comment

by:bgoering
ID: 35754725
You indicated you would be retiring the 2003 server - at that point you will be assigning its old ip address to the new exchange server so that it can begin processing incoming email. So far as I know Exchange relies solely on DNS - so long as the DNS will resolve correctly before and after the change there shouldn't be any issues with changing the IP.
0
 

Author Comment

by:tkdwarrior
ID: 35756759
While on the topic of ip addresses.  Since I am breaking apart 1 server into 3, what will I néed to do in order to assign the 2 'new' servers a static ip?
0
 
LVL 28

Expert Comment

by:bgoering
ID: 35756772
Whoever allocates your IP addresses would need to issue new addresses for the other two servers - they can't all use the same one. You would then assign those in the network configuration.
0
 

Author Comment

by:tkdwarrior
ID: 35756838
Currently we only have local iP addresses I'n tcp/ip configuration. I just know that when I remOte I'n to the exchange server from outsiderhe network, there is outside Internet ip as well.
0
 
LVL 28

Expert Comment

by:bgoering
ID: 35757045
It should be no problem with getting internal ip addresses, it is the external ones that concern me. In your setup your Exchange server will need a number of ports open to the Internet to handle things like OWA, SMTP, POP3, POP3S, IMAPS, etc. (depending on what you are exposing from exchange to the Internet). BES I know needs port tcp/3101 outbound, but I am unclear if it needs that port inbound. Perhaps your firewall person could tell you what the inbound BES traffic looks like. If it doesn't need any inbound you should be in good shape just moving your existing IP to the new Exchange server, if BES needs inbound traffic you will need to be able to port forward its inbound traffic to the new IP that would require some coordination with whoever manages your firewall.

I wouldn't expect any issues with that seeing as all these services co-exist on the same server now without conflicts. Just be aware there may be some additional perimeter security configuration required to route the appropriate ports to the proper servers when you split the services.
0
 

Author Comment

by:tkdwarrior
ID: 35759031
ya so Dell didn't ship the server with vmware esxi preinstalled like i paid them to.  instead it came preinstalled with server 2008.... i am going to chew someone's '*ss tomorrow morning and try to get a new server shipped asap.  please keep this question open.  I may end up just installing esxi myself if they cant get me a new server soon.
0
 

Author Closing Comment

by:tkdwarrior
ID: 37527945
using this guide and splitting up the services to different VM's worked well.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Giving access to ESXi shell console is always an issue for IT departments to other Teams, or Projects. We need to find a way so that teams can use ESXTOP for their POCs, or tests without giving them the access to ESXi host shell console with a root …
For anyone that has accidentally used newSID with Server 2008 R2 (like I did) and hasn't been able to get the server running again because you were unlucky (as I was) and had no backups - I was able to get things working by doing a Registry Hive rec…
This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility. Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Suggested Courses

865 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question