Reconnecting a DC after a Year !!!
Home › Forums › Microsoft Networking and Management Services › Active Directory › Reconnecting a DC after a Year !!!
- This topic has 2 replies, 3 voices, and was last updated 9 years, 8 months ago by
Anonymous.
-
AuthorPosts
-
nrshvnMemberMay 02, 2011 at 8:10 am #154458Hi Friends,
I was running my Domain with 3 Domain controllers One WinServer 2008 R2 and Two WinServer 2003 systems.One of the domain controller with server 2003 was configured as a “ISA” server and tested a year ago and the system was down till date , Now exactly a year after I started the machine without network as I want to configure ISA server and make it as a backup firewall incase my existing firewall fails.
Now I want to know is it safe to connect this server in to network again or I’ve to remove it from domain ??
The below event was taken from the running Domain controller[Server 2008 R2] and you can see that date also.
Log Name: Directory Service
Source: Microsoft-Windows-ActiveDirectory_DomainService
Date: 13-Jul-10 7:51:10 PM
Event ID: 1864
Task Category: Replication
Level: Error
Keywords: Classic
User: ANONYMOUS LOGON
Computer: BMMS.bmmil.com
Description:
This is the replication status for the following directory partition on this directory server.Directory partition:
CN=Schema,CN=Configuration,DC=bmmil,DC=comThis directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals.
More than 24 hours:
1
More than a week:
1
More than one month:
1
More than two months:
1
More than a tombstone lifetime:
0
Tombstone lifetime (days):
180Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled.
To identify the directory servers by name, use the dcdiag.exe tool.
You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is “repadmin /showvector /latency“. Please give your suggestions on what I’ve to do :confused:
-
AuthorPosts
You must be logged in to reply to this topic.