Running an isolated test environment with restored domain controllers and exchange 2016 CU19 to test bringing in exchange 2019 for a migration. Exchange was installed earlier this week on 2019 server core.
Built a new windows 10 20H2 system on that same network and installed the prerequisites but still fails in the readiness checks stating it can't access the registry. Both the remote registry service and tcp/ip netbios helper services are running. File/printer sharing are enabled; ran setup elevated with my domain admin account. No surprise that sfc/dism scans returned no issues since it was just built today. Firewall profiles are disabled.
There is a 'more info' link which, of course, takes you to a page that says they haven't added content for that subject yet.
to take it a step further, the setup log states that it tried to run 'get-exchangeserver' with the identity option as my windows 10 machine and returns the error that it searched for my computer name as type 'server' and the domain controller said the object doesn't exist. The computer account is fine; i have removed and added back to the domain but didn't make a difference. also tried running as the domain administrator with the same result.
anyone get this to work or know why it throws that error?
