You might need to be able to securely, remotely manage a set of Windows Servers that are not domain joined. One problem that you may hit while remotely managing this is that the server does not believe that it has a valid FQDN.
- Set the name of a computer to “Server1”
- Create a DNS entry that said that “Server1.mydomain.local” resolved to that computer
- You can then correctly ping the computer at that address
But when you trie to use tools like PowerShell Remoting or Remote Desktop – they would complain that “Server1.mydomain.local” did not believe it was “Server1.mydomain.local”.
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.local" Set-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\" -Name "NV Domain" -Value "mydomain.local"
After this your workgroup server will correctly identify itself with a valid FQDN.