Solved

Failed Server 2003 to SBS 2011 Migration

Posted on 2014-02-15
10
515 Views
Last Modified: 2016-11-23
Let me start by saying I wouldn't be here if I had a good backup, which I don't.  I am in the process of migrating from an old Server 2003 Standard box to a new SBS 2011 Dell server.  I prepped the server, ran the migration tool, created the answer file and installed SBS 2011 on the new Server in Migration mode.  Unfortunately the new server wasn't partitioned correctly, and like an idiot, I just wiped the RAID array to restart without doing anything first.  The source server had automatically transferred most domain roles to the new server (of course) and now is no longer the master for most domain roles.  I was able to force seize the PDC and Infrastructure Master roles in Active Directory Users and Computers, but I can't seize the RID role nor the Domain Naming Operations Master in AD Domains and Trusts.  I have tried using ntdsutil to connect to the source server, however when I go through roles -> connections -> connect to server myservername I get error "DsBindW error 0x6ba (The RPC server is unavailable).  I'd love to not have to rebuild the domain manually (13 users).  Is there anyway to force/seize the remaining roles, bring the source server back to "the way it was" and start over?
0
Comment
Question by:CRush1682
  • 5
  • 5
10 Comments
 
LVL 20

Expert Comment

by:Patrick Bogers
ID: 39861768
Oof though one.... Did you seize the schema role allready? (right way to seize roles are 1st Schema master, 2nd dns master and last RID, PDC and infrastructure.)

If not working open command prompt and type:   regsvr32 schmmgmt.dll
Then, run MMC and select to add Active Directory-schema. Rightclick Active Directory-schema and choose 'change Domeincontroller'

This would get you further along the way i pressume.
0
 

Author Comment

by:CRush1682
ID: 39861807
I went into Change Domain Controller in the AD Schema snap in and the source-server is listed as the DC.  If I then go to Operations Master and try to change the Schema Master (which is listed as the SBS2011 server) to the SourceServer I get "The requested FSMO operation failed, the current FSMO holder could not be contacted..."

I just installed the Server2003 support tools, should I go into ADSIEDIT and remove all traces of the SBS2011 server?

Also of note, under AD users/computers in the Domain Controllers OU both the source server and the sbs2011 server are listed.  I can not delete the SBS2011 server, and under "Type" both are listed as "Computer".
0
 
LVL 20

Expert Comment

by:Patrick Bogers
ID: 39861837
Hmm did you try NTDSUTIL firstly? I wouldnt recommend running ADSIEDIT and kill all traces but if it is your last resort.... there is not much left to get broken.
0
NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

 

Author Comment

by:CRush1682
ID: 39861859
My problem with using ntdsutil is that all instructions seem to start with "connect to server ServerName", which is where I get the RPC error.  What can I do in ntdsutil WITHOUT being able to use the "connect to server" command?
0
 
LVL 20

Expert Comment

by:Patrick Bogers
ID: 39861874
Hmm not so much. Did you check DNS is still running and RPC service has started?
0
 

Author Comment

by:CRush1682
ID: 39861911
Ok, so I was able to use "connect to domain" and then I was able to seize the the schema master!  I believe i have successfully seized all FSMO roles!  I confirmed by trying to run DCPromo on a temp-SBS2011 install I just did and it seemed to work.

However:  I am still getting the RPC server unavailable message when I try the connect to server command on the original server.

DNS Server & Remote Procedure Call services are running.  Maybe I should just ignore it and try the SBS2011 in Migration mode again?
0
 
LVL 20

Accepted Solution

by:
Patrick Bogers earned 500 total points
ID: 39861917
Looking good, if all the roles are present again you could try DCDIAG and try to become error free or just continue the migration.
0
 

Author Closing Comment

by:CRush1682
ID: 39862976
Was very responsive in helping get issue resolved.
0
 

Author Comment

by:CRush1682
ID: 39862978
I was able to install successfully in migration mode.  Exchange 2010 install failed, but I'm on the right path.
0
 
LVL 20

Expert Comment

by:Patrick Bogers
ID: 39863123
Great!
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

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

Suggested Solutions

Synchronize a new Active Directory domain with an existing Office 365 tenant
Is your Office 365 signature not working the way you want it to? Are signature updates taking up too much of your time? Let's run through the most common problems that an IT administrator can encounter when dealing with Office 365 email signatures.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

821 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