Immediately after a domain join, we have observed the following message
from the Windows 7 client (which appears to be benign as discussed below):
"Changing the Primary Domain DNS name of this computer to "" failed.
The name will remain "TESTDOMAIN". The error was:
The specified domain either d
Sorry - I think
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Netlogon\Parameters
RequireStrongKey=0
is currently required (at least with Samba 3.3.4). The client will
successfully join the domain without this key, but attempting to log in
with a domain account (after a reboot) will give
Correction to this post as the second DWORD should have been
DNSNameResolutionRequired.
However, I'm interested to know why the error message we receive occurs
- it seems to me that setting DNSNameResolutionRequired to 0 should also
prevent Windows 7 attempting to set its DNS name after the domain
Hi Volker,
We can confirm that only the first two keys (i.e.
DomainCompatibilityMode & DomainCompatibilityMode) are required in order
for Samba 3.3.4 & Windows 7 RC to domain join and interoperate.
Immediately after a domain join, we have observed the following message
from the Windows 7 client (
