board logo
Posted by: Lemonde - 03 March 2020 18:04:39
We are seeing the following after recommencing a network that has been VM'd: Log Name: Directory Service Source: Microsoft-Windows-ActiveDirectory_DomainService Date: 03/03/2020 17:53:43 Event ID: 1587 Task Category: Replication Level: Information Keywords: Classic User: domain\%computername%$ Computer: domainDC02.domain.local Description: This directory service has been restored or has been configured to host an application directory partition. As a result, its replication identity has changed. A partner has requested replication changes using our old identity. The starting sequence number has been adjusted. The destination directory service corresponding to the following object GUID has requested changes starting at a USN that precedes the USN at which the local directory service was restored from backup media. Object GUID: a4092d6e-a526-47a7-acdb-326a94911221 (%computername%.domain.local) USN at the time of restore: 140046653 As a result, the up-to-dateness vector of the destination directory service has been configured with the following settings. Previous database GUID: 61a8cd11-e5a0-4b88-8fb8-7711db3b58f0 Previous object USN: 140218987 Previous property USN: 140218987 New database GUID: 5d68b218-77f8-4985-9949-863cd4877b13 New object USN: 140046653 New property USN: 140046653 Event Xml: 1587 0 4 5 0 0x8080000000000000 17640 Directory Service domainDC02.domain.local a4092d6e-a526-47a7-acdb-326a94911221 (%computername%.domain.local) 140046653 61a8cd11-e5a0-4b88-8fb8-7711db3b58f0 140218987 140218987 5d68b218-77f8-4985-9949-863cd4877b13 140046653 140046653 We cannot currently access the domain, will it sort itself out, or do we need to find a way to tell the DCs that the other DC is in charge?