Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Replacing my SBS2003 box with Hyper V 2012R2 VM's


  • Please log in to reply
1 reply to this topic

#1 Killswitch67

Killswitch67

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:06:20 AM

Posted 11 February 2014 - 05:46 PM

Hi Folks,
 
Apologies if I have posted on the wrong Forum
 
I will keep this brief .
 
My customer currently has an old SBS 2003 standard physical server. They utilize the integrated Exchange 2003 system. It now needs to be changed/upgraded due to lack of hard disk space and incompatibility between Outlook 2013 and exchange 2003 amonst other thing.
 
SBS is no longer available but as the company has grown substantially in the last few years SBS would have been unsuitable anyway. The company has about 80 user accounts across 60 Computer systems.
 
I have decided after much research to replace the old SBS2003 system with one new Physical server running Windows 2012R2 Hyper V as the Host O/S.. I have also setup 2 Gen 1 VM's running Server 2012 standard, (NOT 2012 R2). I have then promoted one of the VM's to be a domain controller simply by adding Active Directory Domain services role. The othe VM will be used as an exchange 2010 server .. I have the Exchange 2010 SP3 installation lying in wait on the second VM but I havent installed yet as it requires access to domain accounts.
 
The new Server has about 1 terabyte of Hard drive space and 32 gig Ram. The DC has been allocated 8 gig of Ram and 500 gig of Hard drive space. The exchange 2010 VM has been allocated 12 gig Ram with 150 gig Hard drive space.
 
 
 
What I need now is a guide on how to get this new server installed on my existing network and removing the existing SBS2003 box. 
 
I know i have to attach the new domain Controller VM to the existing domain and allow active directory account information etc to replicate onto the new DC VM. Apparently this can take a few days. I am unsure however at which point I connect the exchange server to the old sbs2003 box in order to move the mailboxes.. actually I am not even sure if I ever connect the new exchange VM to the old sbs 2003 box. Would it be better to get the DC replaced first. i.e attach the DC to the existing domain.. let the active directory info to replicate.. transfer the roles, demote the sbs2003 box?? I am concerned that the old mailboxes on the sbs2003 box will then be irretrievable..
 
Perhaps someone can clarify the steps in sequence that I need to follow to end up with my DC VM and Exchange 2010 VM with migrated mailboxes installed as replacement for the current sbs 2003 box.
 
Some other notes:  Although i have used 2012 R2 for the hyper V host I have decided that 2012 made better sense for the VM operating systems due to the better compatibility with exchange 2010 in one VM and simply because of online advice on the DC VM. 
 
Thanks in advance


BC AdBot (Login to Remove)

 


#2 stillgrey

stillgrey

  • Members
  • 42 posts
  • OFFLINE
  •  
  • Local time:02:20 AM

Posted 17 February 2014 - 08:15 PM

VM's are the easy part :)

 

If it was me and I have done a few SBS migrations, I would still talk to the folks at SBSMigration.com  In a nutshell they provide you with all the documentation you need and hold your hand from start to finish for ~ 300 bucks.  I can promise you it will save you the 3 hours of billable time to go this route, but you charge your client for the kit and you both will come out better.  When you hit snags, they know the answer.  Migrating Exchange is very tricky/picky. But the way their process works, your original server is untouched,  So if something goes wrong in the migration, there it sits, same as it was, still good to go.

 

But this is not the best place for ideas on this either.  I would run by experts exchange and post your quizzer there also.

 

Best,

 

Grey






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users