promote Windows Server 2022 Core to DC missing sysvol

Question

I have made 3 attempts to install a second DC using windows server 2022 core and each time I end up with dcdiag errors similar to what you see below, where the new server 2022 core deployment would be the named server.

server DCX-XXX.XXX.com could not be queried, error 0x6ba "The RPC server is unavailable."

so I began troubleshooting and started with disabling the firewall AND changing the registry key listed below.

• Browse to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
• Set SysVolReady from 0 to 1 after that I get this error in dcdiag /a

Event String: The processing of Group Policy failed. Windows attempted to read the file \\XXX.com\sysvol\XXX.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful.

So I have come to the conclusion that using the latest windows server 2022 core build and promoting it to a domain controller is not seemless and requires remediation. I am reaching out to the community to determine if this is a known issue and if anyone has any suggestions. At this point I am going to deploy the firewall after opening all of the AD required ports. I dont think I should have to use the registry to enable sysvol and manually open the firewall ports when installing a clean from scratch DC.

I installed the DC by using the command listed below.

Also found that the policies folder was missing from the newly deployed Core installation.

Install-ADDSDomainController -DomainName 'xxx' -Credential (Get-Credential "AD\your-domain-admin") -InstallDns:$true

Answer 1

DCCO1-blah should have own static ip address (10.1.0.103) listed for DNS as well.

The "DFS Replication service has detected that no connections are configured for replication" is problematic and may be the result of the IPv6 stuff (if not configured correctly) There may be a rouge IPv6 DHCP server on the network (possibly a router) that could be disabled. Then on both do ipconfig /flushdns, ipconfig /registerdns, restart the netlogon service, or maybe reboot them.

If problems persist then put up a new set of files to look at.

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

Answer 2

No known issues. Likely is some other preexisting problem. Please run;

Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log (run on PDC emulator)
repadmin /showrepl >C:\repl.txt (run on any domain controller)
ipconfig /all > C:\%computername%.txt (run on EVERY domain controller)
ipconfig /all > C:\problemwserver.txt (run on problem one)

Also check the domain controller System and Replication (DFS or FRS) event logs for errors since last boot. Post the Event Source and Event IDs of any found. (no evtx files)

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

Answer 3

I accepted your answer because you took the time to engage and assist me. I would just like it to be known that after a fresh core install of windows 2022 and promoting to a DC I had to

• Browse to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
• Set SysVolReady from 0 to 1 after that I get this error in dcdiag /a
• disable the firewall
• do an non authoratative restore

I will go back in and re instate the firewall and unblock the necessary ports. I shoudlnt have to do any of that and others may experience this issue as well.