[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 110
  • Last Modified:

Failed 2008r2

Hi

I have two windows 2008r2 servers.  

One, that just crashed with no chance of recovery but I can get into the System Drive .  "Dc01". It held all the FSMO roles.  

The second, Alive and well. It's a D.C. with no FSMO roles.   "DC02".

I'd like to ...

DC02 seize all FSMO roles
Keep all gpos in tack.  
Rename DC02 to DC01

Thank you
0
mizgroup
Asked:
mizgroup
1 Solution
 
Niten KumarPrincipal Systems AdministratorCommented:
You can use ntdsutil to seize fsmo roles on DC02.  ntdsutil is a command line utility. Group policies wont be affected. After seizing fsmo roles you will have to remove all metadata for DC01 again using ntdsutil.  And finally you can use netdom to rename DC02 to DC01.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
DC02 seize all FSMO roles
Ok, Seize them using NTDSUtil

Keep all gpos in tack.  
Has nothing to do with anything.  GPOs are not affected unless you're going to rebuild the entire domain.

Rename DC02 to DC01
WHY?  Just rebuild the failed once you remove it from AD.
2
 
mizgroupAuthor Commented:
Sorry just to clarify.  If I seize the roles instead of transferring them, will I still have all the gpos of the domain.

What meta data would I need to sufffienctly remove before doing the netdom?

Thanks
0
Technology Partners: 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!

 
Lee W, MVPTechnology and Business Process AdvisorCommented:
I'll repeat:
GPOs are not affected unless you're going to rebuild the entire domain.
1
 
sAMAccountNameSr. Systems EngineerCommented:
Hi mizgroup

You can use powershell to sieze all the FSMO roles (Seize FSMO roles with Powershell)

Lee W is absolutely correct, this activity has no bearing on GPO.  They are replicated through a different mechanism and will remain intact.  I also agree, you do not need to rename the failed DC.

Here is an article which goes over what metadata is left behind and how to clean it up:
Clean up metadata (Technet)

Once the metadata is cleaned up, you can rebuild the failed DC, allowing it to retain the original name and IP address - this will allow anything that was pointing directly to it to resume normal operation.

(Edit)
Also, you mentioned you can still get to the system drive on the failed DC.  Do not try to recover the data on that drive or do a repair.  Just wipe it and rebuild it.
0
 
Niten KumarPrincipal Systems AdministratorCommented:
Since DC01 has failed you can't transfer roles so you only have the option to seize roles.  GPOs won't be affected when you seize roles.  How???  If you clients are getting the GPOs then they are getting it from the working DC.  And seizing roles only affects roles and does nothing to the GPO. It seems you are very unsure of what will happen.  Believe me I felt the same when i did this for the first time.

Watch the following video on YouTube and you will get a fair idea on what you have to do.  It is step by step clear explanation.

https://www.youtube.com/watch?v=DzJTCYtp7XI
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

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