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

Failed Server 2003 to SBS 2011 Migration

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
CRush1682
Asked:
CRush1682
  • 5
  • 5
1 Solution
 
Patrick BogersDatacenter platform engineer LindowsCommented:
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
 
CRush1682Author Commented:
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
 
Patrick BogersDatacenter platform engineer LindowsCommented:
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
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
CRush1682Author Commented:
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
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Hmm not so much. Did you check DNS is still running and RPC service has started?
0
 
CRush1682Author Commented:
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
 
Patrick BogersDatacenter platform engineer LindowsCommented:
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
 
CRush1682Author Commented:
Was very responsive in helping get issue resolved.
0
 
CRush1682Author Commented:
I was able to install successfully in migration mode.  Exchange 2010 install failed, but I'm on the right path.
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Great!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

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