Ask Learn
Preview
Please sign in to use this experience.
Sign inThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Recently I needed to be able to securely, remotely manage a set of Windows Servers that were not domain joined. One problem that I hit while setting this up was that each of the servers did not believe that they had a valid FQDN.
For example – I could:
But when I tried to use tools like PowerShell Remoting or Remote Desktop – they would complain that “HyperVSV1.mydomain.com” did not believe it was “HyperVSV1.mydomain.com”.
Thankfully, this is relatively easy to fix.
If you open PowerShell and run the following two commands:
Set-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\" -Name Domain -Value "mydomain.com" Set-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\" -Name "NV Domain" -Value "mydomain.com"
After this your workgroup server will correctly identify itself with a valid FQDN.
Cheers,
Ben
Please sign in to use this experience.
Sign in