Skip to content

Commit cf35b3a

Browse files
authored
update
1 parent 202b63b commit cf35b3a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

support/windows-server/active-directory/cannot-edit-delete-ad-object-error-sam.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Can't Edit or Delete an AD Object and Receive Errors
33
description: Helps resolve an issue where you can't edit or delete an AD object and receive the error Attribute is owned by SAM or The specified account does not exist.
4-
ms.date: 03/10/2025
4+
ms.date: 03/11/2025
55
manager: dcscontentpm
66
audience: itpro
77
ms.topic: troubleshooting
@@ -102,7 +102,7 @@ The object was deleted and undeleted. Deleted objects don't have the `sAMAccount
102102
To resolve this issue, use the new facility included in Windows Server 2025 to repair broken objects as specified in [[MS-ADTS]: fixupObjectState](/openspecs/windows_protocols/ms-adts/37294765-9e7d-41a1-aded-2d6f744eee8c).
103103

104104
> [!NOTE]
105-
> There's also functionality to repair the `LastLogonTimeStamp` attribute. For more information, see [Will update link to the new article for this attribute].
105+
> There's also functionality to repair the `LastLogonTimeStamp` attribute. For more information, see [User or computer accounts have the lastLogonTimestamp value set to a future time](accounts-lastlogontimestamp-future-time.md).
106106
107107
### Step 1: Identify the object name and globally unique identifier (GUID)
108108

0 commit comments

Comments
 (0)