Skip to content

Commit 96d8ab0

Browse files
authored
AB#3039 Update manually-remove-lingering-objects.md
1 parent 039ab05 commit 96d8ab0

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

support/windows-server/active-directory/manually-remove-lingering-objects.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ ms.custom: sap:Active Directory\Active Directory replication and topology, csstr
1212

1313
This article helps manually remove [lingering objects](information-lingering-objects.md#summary) after you bring an outdated domain controller (DC) or global catalog server back online. In many cases, you can clean up lingering objects using the `repadmin /removelingeringobjects` command or tools like [Lingering Object Liquidator](lingering-object-liquidator-tool.md). However, these facilities don't work if you have [abandoned objects](https://support.microsoft.com/topic/attributes-that-contain-stale-or-bad-data-cause-exchange-offline-address-book-oab-generation-failures-and-event-ids-9126-9330-and-9339-together-with-stop-error-code-8004010e-occur-d505154b-f51f-6604-436b-e30fe4e486d9).
1414

15+
_Original KB number:_   314282
16+
1517
When you bring a domain controller or global catalog server back online after it has been offline for a long time, any of the following issues might occur:
1618

1719
- Email messages aren't delivered to a user whose user object was moved between domains. After you bring the outdated domain controller or global catalog server back online, both instances of the user object appear in the global catalog content. Both objects have the same email address, so email messages can't be delivered.

0 commit comments

Comments
 (0)