I hope I'm not the only one experiencing this issue:
SME 10.1 domain join of Win 10 pro workstation fails.
Multiple Win 10 workstations that were joined to our domain prior to March 2023 remain joined and work as expected. Attempts to join the additional workstation fail with the server responding that the account already exists (it did not). I tried joining the workstation using a different computer name to no avail. To provide the user of this machine some access to the SME shared files, I simply created a local user account and configured his machine as a member of a workgroup, named identically to our SME domain. Works, but not ideal.
Prior to join attempts, I had applied the registry patch below, per
https://forums.koozali.org/index.php/topic,54948.msg289206.html.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"NetJoinLegacyAccountReuse"=dword:00000001
It is my understanding that Microsoft intends to disable the NetJoinLegacyAccountReuse key function. Their guidance regarding the March 14th updates reads:
If you deployed the NetJoinLegacyAccountReuse key on your clients and set it to value 1, you must now remove that key (or set it to 0) to benefit from the latest changes.Additional changes that will impact netlogon and more are imminent, per
https://techcommunity.microsoft.com/t5/windows-it-pro-blog/latest-windows-hardening-guidance-and-key-dates/ba-p/3807832.
I'm not seeking a solution, per se, but I am curious as to what SME features might Microsoft break next. Are there workarounds to allow Win 10 (and 11) domain join on SME 10.1 in the near term? Looking forward to your replies.
Thanks, Curt