How to reinstall the failed Additional Domain Controller on Windows 2012

April 1, 2013 at 9:15 am 2 comments

Hi Folks

Recently I faced an issue with a customer where we have installed a Windows 2012 Additional Domain Controller as a Virtual Machine on Hyper-v Server , he was getting the below error.

So I was trying with all the CHKDSK , Last Known Good Configuration , Directory Restore mode BUT everything failed, Including the below suggestion on Technet forums

http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/22e97f03-7308-43bd-9fa7-3d3560bf67bf/

Since I had to meet the SLA on solving the ticket , I decided to re-install the Additional Domain Controller on the same name ,which will avoid me of Cleaning the metadata and other complex task.

So I performed the follow steps.

Re-installed the Windows 2012 Guest on Hyper-V
Change the name to my previous Additional Domain Controller name.
Open the Powershell

Add-WindowsFeature AD-Domain-Services –> This will install the Active Directory Domain Services.
Import-Module ADDSDeployment
Install-ADDSDomainController -AllowDomainControllerReinstall -Credential (Get-Credential) -DomainName “test.local”This will prompt you to enter the credential , make sure you enter the credential either in DOMAINNAME\Administrator OR Administrator@DOMAINNAME
Secondly it will prompt you to enter the Directory Restore Password
That’s all it will promote the new server as a domain controller , you do not need to do anything on DNS or other related services.
Finally you will need to install the ADDS Management Tools to Manage the Active Directory components you could do it via PowershellImport-Module ServerManager
Add-WindowsFeature RSAT-AD-PowerShell,RSAT-AD-Tools and hit enter

OR via the GUI

Voila… My problem was solved . Good luck Guys….

Entry filed under: Windows 2012.

How to install only Security Updates on CentOS Error code: 0x800F0906 while installing Microsoft .NET Framework 3.5

2 Comments Add your own

1. OxfordSBSguy.com | April 14, 2013 at 6:14 pm

I had a similar problem with a hyper-v vm I had restored into a test environment. The way I resolved it was to take a system state backup of the original machine, copy it to the test environment, boot the troublesome hyper-v vm into Directory Services Restore Mode, and then restore the system state.

I’m now making sure that as well as a 3rd Party VM backup I’ve also got a Windows Server Backup System state available to me in my production environment.

Carl
http://Oxfordsbsguy.com
Reply
- 2. Muralee | April 15, 2013 at 7:30 am
  
  Hi Carl
  
  Thanks for the Comment.
  
  Unfortunately for me I tried all the Restore Mode available in the Safe Mode which failed and also this particular customer of mine does not have any backup solution which worsen my situation.
  
  Regards
  Muralee
  Reply

Hope you like it..