my Server 2016 Essentials machine is hosed

Question

I recently performed a clean install of WSE 2016 and it has never worked.
The hardware is a new HP Envy TE-01-1 with i7-10700F CPU at 2.90 GHz, 8 cores, 16 threads, and 32GB Ram.
It came with Windows 10 Home, so it is not a true server, and many device drivers don't exist because the hardware is newer than the software. But, it seems to me that there is enough active hardware for Server 2016 to operate. I am not trying to run any virtual machines.

When I run System Information, the System Name displays as Win-9LUPAQIOPFM, a name that I am unfamiliar with. I expected it to match the name I assigned to the server, "WSC-DC1". Is that normal? It seems like System Information is totally unaware that this machine is supposed to be serving the role of domain controller.

Control Panel\System and Security\System shows the full computer name correctly: WSC-DC1.WSC.local
Windows is activated.
AD does not seem to have installed correctly, therefore DNS is inop.

I don't know where to start troubleshooting. Can somebody offer some help?

Here is the first part of what I get when I run DCDiag:
Directory Server Diagnosis

Performing initial setup:
Trying to find home server...
Home Server = WSC-DC1
[WSC-DC1] Directory Binding Error -2146893022:
The target principal name is incorrect.
This may limit some of the tests that can be performed.
* Identified AD Forest.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\WSC-DC1
Starting test: Connectivity
[WSC-DC1] DsBindWithSpnEx() failed with error -2146893022,
The target principal name is incorrect..
Got error while checking LDAP and RPC connectivity. Please check your firewall settings.
......................... WSC-DC1 failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\WSC-DC1
Skipping all tests, because server WSC-DC1 is not responding to directory service requests.

Answer 1

That sounds like a default name windows setup assigned. I'd check the computer name shown here. Control Panel\System and Security\System, Advanced\Computer Name

Also please run;

Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log
repadmin /showrepl >C:\repl.txt
ipconfig /all > C:\dc1.txt

then put unzipped text files up on OneDrive and share a link.

Answer 2

HI TheWileyOne-9784,

1.When I run System Information, the System Name displays as Win-9LUPAQIOPFM, a name that I am unfamiliar with. I expected it to match the name I assigned to the server, "WSC-DC1". Is that normal?
No, it isn't normal.

WSE2016 need to use windows server essentials wizard to create AD forest and configure itself as DC. So did you assign the "WSC-DC1" to the server like below picture?

2."AD does not seem to have installed correctly, therefore DNS is inop."
If it is possible, could you please follow below video to install wse2016 again? I check this video is correct to install wse2016, meanwhile if we don't need to install DHCP, we can ignore it.

Setup Windows server 2016 essentials (EN)
https://channel9.msdn.com/Blogs/MVP-Azure/Setup-Windows-server-2016-essentials-EN

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Just checking if there's any progress or updates?

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 4

Domain controller must have it's own static ip address (10.1.10.10) listed for DNS so the router address should be removed / replaced. Also there appears to be a rouge IPv6 DHCP server on network (router?), either turn that function off or uncheck IPv6 in connection properties. Then do ipconfig /flushdns, ipconfig /registerdns, restart the netlogon service. I did not bother looking at other files since this one is a show stopper.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 5

I had it set up the way you describe, but there was no Internet access

Regardless this is a fatal error, the server will never be functional like that.

I also added IPv6

Not sure what is meant by if it isn't configured correctly then this causes great confusion for active directory DNS

--please don't forget to upvote and Accept as answer if the reply is helpful--