From ae07fbd96bf60cb97c5198cd056c08d5bd7010b0 Mon Sep 17 00:00:00 2001 From: Herbert Mauerer <41573578+HerbertMauerer@users.noreply.github.com> Date: Wed, 30 Oct 2024 13:16:25 +0100 Subject: [PATCH] Update Uninstall-ADServiceAccount.md add Name uniqueness warning remove rodc reference, you can run this one on RODC --- .../activedirectory/Uninstall-ADServiceAccount.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docset/winserver2022-ps/activedirectory/Uninstall-ADServiceAccount.md b/docset/winserver2022-ps/activedirectory/Uninstall-ADServiceAccount.md index 31242af52d..eb45b76b53 100644 --- a/docset/winserver2022-ps/activedirectory/Uninstall-ADServiceAccount.md +++ b/docset/winserver2022-ps/activedirectory/Uninstall-ADServiceAccount.md @@ -31,6 +31,8 @@ You can identify an MSA by its distinguished name (DN), GUID, security identifie You can also set the parameter to an MSA object variable, such as `$` or pass an MSA object through the pipeline to the *Identity* parameter. For example, you can use the **Get-ADServiceAccount** cmdlet to get an MSA object and then pass that object through the pipeline to the **Uninstall-ADServiceAccount** cmdlet. +You will receive an error if the account name is not unique in the forest, meaning an account with the same samAccountName may be in multiple domains in the forest. + ## EXAMPLES ### Example 1: Uninstall a specified MSA @@ -164,7 +166,6 @@ A parameter with name **ForceRemoveLocal** is provided to un-install standalone ## NOTES * This cmdlet does not work with AD LDS. * This cmdlet does not work with an Active Directory snapshot. -* This cmdlet does not work with a read-only domain controller. ## RELATED LINKS