?
Solved

Migration from SBS2008 to SBS2011 Failed

Posted on 2013-05-28
6
Medium Priority
?
1,115 Views
Last Modified: 2013-12-02
I have been struggling with this issue for weeks if not months. I have a client with a SBS2008 server and a SQL2008 on HyperV. Both are Domain Controlers, each hold different FSMO Roles. The primary server for DHCP and DNS is SBS2008. The SBS2008 use to house Exchange 2007 but that has been moved to Mircosoft Hosted Exchange. FYI the Exchange 2007 that is on SBS2008 server has all of the services stopped also note I can not upgrade from base product to SP3. The hardware is in a degrade state and repairing is NOT an option.

We have purchased a new server with SBS2011.

From the SBS2008 server I get the following migration errors:
1. Log on as batch job" user right assignment is not correct
2. Microsoft Exchange Server 2007 SP3 is not installed
3. Some FSMO roles are missing on the source Windows SBS server
4. The server is in a journal wrap condition
5. User accounts are not trusted for delegation

Error Corrections are:
1. We followed the instructions from this technet link: http://technet.microsoft.com/en-us/library/gg563788.aspx
2. Cannot Correct
3. The following FSMO roles: RID, PDC, Domain Naming, Infrastructure are handled by SBS2008
Schema Master is handled by SQL2008
4. Not sure how to correct
5. Not sure how to correct

From the SQL2008 server I get the following migration errors:
1. "Log on as batch job" user right assignment is not correct
2. Error is found in the DNS Zone JUstMFG.local
3. Found an Offline domain controller present in AD. Server SBS2008
4. Some FSMO roles are missing on the source Windows SBS server
5. The server is in a journal wrap condition
6. User accounts are not trusted for delegation

Error Corrections are:
1. We followed the instructions from this technet link: http://technet.microsoft.com/en-us/library/gg563788.aspx
2. In DNS zone company.local, your local server is not in the name server records.
SQL2008 has a Host (A) and a Name Server (NS) record. It does not have a cname record, but I can add one either.
3. On SQL2008 server under AD Users and Computers SBS2008 does have a status of Unavailable. However on SBS2008 status is Online. So not sure how to fix this error.
4. Not sure how to correct
5. Not sure how to correct

So now you know my problem. Looking for your advice.
1. On the new server should I install SBS2008 without Exchange add all of the required service packs are fixes - then upgrade to SBS2011?
2. Shut down the current SBS2008 (treating it as if there was a full hardware failure) and do a fresh install of SBS2011?
If I do 2. is there a way to copy over DNS, DHCP and AD from SBS2008 or do I have to build everything from scratch?

In advance thank you for your help.
0
Comment
Question by:Trish Glees
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
6 Comments
 
LVL 96

Expert Comment

by:Lee W, MVP
ID: 39202396
If the existing servers are VMs why not move them off the current hardware onto new hardware?

If the existing servers are VMs why not COPY them onto a temporary server so you can try to recover them without affecting the business?

My recommendation would be to start by copying the VMs to a new/temporary system and fixing them - transfer the FSMO roles back to SBS (that's a license violation and SBS 2008 SHOULD be shutting down if it doesn't have all the roles).  Then activate all the Exchange services and install Exchange SP3 so it's up to date.  Then shut down the services again if you're not using exchange locally.

ALL WORK SHOULD BE DONE ON THE COPIES UNTIL YOU PROVE EVERYTHING IS FIXABLE.

Alternately, why start with a CLEAN environment and setup SBS 2011 on the new server with a new server name and a new AD.  DNS rebuilds itself.  DHCP is MINOR for most orgs, and AD, that's going to be your headache - but even that, if you do things the way SBS intends you to do them, it shouldn't be THAT labor intensive unless the company has 50 or so employees.
0
 

Author Comment

by:Trish Glees
ID: 39202437
The HyperV hardware that SBS2008 and SQL2008 are installed on is in a breakdown status. SBS2008 has been bandaided so badly that the move to another HyperV failed with bad consquences.

I think it is time to bite the bullet and start from Scratch. When you say DNS rebuilds it self what do you mean?  
Also since SQL2008 needs to stay running should I DCPROMO it first?
0
 
LVL 96

Expert Comment

by:Lee W, MVP
ID: 39202509
> The HyperV hardware that SBS2008 and SQL2008 are installed on is in a breakdown status.
> SBS2008 has been bandaided so badly that the move to another HyperV failed with bad
> consquences.

I don't understand this. Really doesn't make sense to me.  The MOST vital part is CLEARLY working - the VHDs.  If they were corrupt the OSs wouldn't work.  Export the VMs to an attached external hard drive.  Shutdown the VMs and simply COPY the VHDs and then redefine the hardware profiles.  Either way, the way I'm reading your comment on the condition of the hardware and the network really doesn't make any sense to me.

DNS is DYNAMIC.  When computers join the domain and are assigned an IP they register with DNS.  When the DCs start up they register with DNS (service records).  Unless you have some specific DNS entries you want to preserve (which probably shouldn't have been done in the first place, DNS rebuilds itself).

DHCP doesn't need to be transferred - be safe, power off ALL other systems that get DHCP addresses (including your wireless router if you have one), and then re-setup DHCP on the new server, disabling the service on the old server.  The new DHCP should start answering.  If you have a lot of reservations, that could be a pain, but in general, you shouldn't/don't need reservations for much ... maybe a few printers... so the time it takes to setup DHCP cleanly is probably just about as fast as any transfer method for a small environment.  Maybe faster.

As for SQL - that's going to be your biggest potential problem.  It's probably used with a line of business app - you need to contact that vendor and learn how to restore it.  It's POSSIBLE you could demote the SQL server without any negative consequences, but you would almost certainly be better off recreating the server and reinstalling SQL.  

(By the way, unless you consider yourself an active directory expert, DO NOT add a second DC to the domain - one is fine.  You really need to understand how AD works and especially how to do restores before having two DCs.  Two are great and I used to recommend them all the time, but these days, I've learned that not everyone has my skill level and if you don't know what you're doing you could EASILY trash the AD itself if you do things wrong).
0
Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 
LVL 59

Expert Comment

by:Cliff Galiher
ID: 39202515
First, a relatively simple question, as the answer will have an impact on my suggestions:

You say exchange is hosted now. SBS 2011 (standard) comes with exchange 2010 integrated. Is it your intent to keep exchange hosted, or pull it back on-premises?
0
 

Accepted Solution

by:
Trish Glees earned 0 total points
ID: 39213291
We have decided to start from scratch. This will correct all of the bandage issues and will allow us to bring Exchange 2010 on premise again. Thank you to everyone who has supplied solutions to this problem.
0
 

Author Closing Comment

by:Trish Glees
ID: 39224983
We have decided to build a new forest, so no solutions is needed.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

Know what services you can and cannot, should and should not combine on your server.
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses

762 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