You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the "Take Action" headline in the above article:
Under Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options, double-click Domain controller: Allow computer account re-use during domain join.
Select Define this policy setting and <Edit Security…>.
Use the object picker to add users or groups of trusted computer account creators and owners to the Allow permission. (As a best practice, we highly recommend that you use groups for permissions.) Do not add the user account that performs the domain join.
When building environments through pipelines and DSC (from DC and up to servers/clients), this is much needed to allow reinstallation of individual servers/clients.
The text was updated successfully, but these errors were encountered:
Hi,
It would be great if the SecurityOption resource supported .
This was added/enforced in late 2023 to harden domain join.
https://support.microsoft.com/en-au/topic/kb5020276-netjoin-domain-join-hardening-changes-2b65a0f3-1f4c-42ef-ac0f-1caaf421baf8
From the "Take Action" headline in the above article:
Under Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options, double-click Domain controller: Allow computer account re-use during domain join.
Select Define this policy setting and <Edit Security…>.
Use the object picker to add users or groups of trusted computer account creators and owners to the Allow permission. (As a best practice, we highly recommend that you use groups for permissions.) Do not add the user account that performs the domain join.
When building environments through pipelines and DSC (from DC and up to servers/clients), this is much needed to allow reinstallation of individual servers/clients.
The text was updated successfully, but these errors were encountered: