Solved

Some PCs unable to login to a 2003 domain. One server may have tombstoned?

Posted on 2013-11-13
4
217 Views
Last Modified: 2013-11-18
Hi,

I have three domain controlers all running 2003

Some PCs are able to login without an issue but some cannot.

One DC was offline for over 60 days so I think it has now tombstoned. This DC has no roles and is not hosting any critial applications. I have NTDS replication in the event viewer (one is event ID 2042)

I'm tempted to demote the problematic DC in the short term to get the users back online as soon as possible. Would this sort this issue?

Is it as easy as DCPROMO and follow the wizard or is there anything else I can try? And can I demote a dc via remote desktop?. The DC in question is a virtual server on ESXI.
0
Comment
Question by:APC_40
  • 2
  • 2
4 Comments
 
LVL 24

Accepted Solution

by:
Sandeshdubey earned 500 total points
ID: 39646953
Event ID 2042 indicates server has has not replicated with its partner for longer than a tombstone lifetime.Demote/promote should fix the issue.

You cannot demote the faulty DC gracefully you need to do forcefull removal.You need to ran dcpromo/force removal and then run matadata cleanup on other DC(healthy) to remove the instance of faulty DC from AD database and DNS.If faulty DC is fsmo role holder server the you need to seize the FSMO role on other DC.

Once done you can promote the Server back as ADC.Also configure authorative time server role on PDC role holder server.

Reference link
Forcefull removal of DC: http://support.microsoft.com/kb/332199
Metadata cleanup: http://www.petri.co.il/delete_failed_dcs_from_ad.htm
Seize FSMO role: http://www.petri.co.il/seizing_fsmo_roles.htm
Authorative time server: http://support.microsoft.com/kb/816042
0
 

Author Comment

by:APC_40
ID: 39647231
I went straght to metadatacleanupp and did not use the force removal - will this cause issues? The DC appears to be gone though.

I have two DCs  - do I have to run metadatacleanup twice from each DC to cleanup the bad DC?
0
 
LVL 24

Expert Comment

by:Sandeshdubey
ID: 39647282
You have to run metadata cleanup only once to remove the instances of faulty server the other DC will replicate and remove the instances of faulty server no need to run on all DC.

On the faulty server excute dcpromo/force  to remove the AD.
0
 

Author Closing Comment

by:APC_40
ID: 39656058
Excellent answer - thanks
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

My purpose is to describe the basic concepts of virtual memory as implemented in a modern Windows-based operating system. I will also describe the problems inherent in older systems and how virtual memory solves them. The dark ages - before virtu…
Introduction: I have always been a big fan of Windows but my liking towards it is slowly being eroded by the variety of other Applications that I encounter, when I browse the Web. Most of the software available is free and maybe Open Source too. …
This video Micro Tutorial explains how to clone a hard drive using a commercial software product for Windows systems called Casper from Future Systems Solutions (FSS). Cloning makes an exact, complete copy of one hard disk drive (HDD) onto another d…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

757 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

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now