Armitage318
asked on
DNS errors after adding DC Windows Server 2019
Hi, I have 3 DC controller (Windows 2008 R2, Windows 2008,Windows 2012 R2).
The one with Windows 2008 R2 is no longer available (hardware issue), so I simply removed all stuff (with NTDSUtil, DNS, and so on) and installed a NEW DC with Windows Server 2019.
I needed to migrate from SYSVOL to DFS to do this (task completed fine).
Right now it seems that AD replica is fine, since I created a test user on DC windows 2019 and I found this user on other 2 DC (Windows 2008 and Windows 2012 R2).
Anyway, on Windows Server 2019 dashboard, I see this:
In Event Viewer I see lots of error related to DNS:
(sorry, it is in italian).
How can I investigate this error?
NOTE: before promoting this server Windows 2019 to DC, I mistakenly added an unnecessary role: Active Directory Lightweight Services instead of Active Directory Domain Services.
Can this cause my error? Can I safely remove that role?
The one with Windows 2008 R2 is no longer available (hardware issue), so I simply removed all stuff (with NTDSUtil, DNS, and so on) and installed a NEW DC with Windows Server 2019.
I needed to migrate from SYSVOL to DFS to do this (task completed fine).
Right now it seems that AD replica is fine, since I created a test user on DC windows 2019 and I found this user on other 2 DC (Windows 2008 and Windows 2012 R2).
Anyway, on Windows Server 2019 dashboard, I see this:
In Event Viewer I see lots of error related to DNS:
(sorry, it is in italian).
How can I investigate this error?
NOTE: before promoting this server Windows 2019 to DC, I mistakenly added an unnecessary role: Active Directory Lightweight Services instead of Active Directory Domain Services.
Can this cause my error? Can I safely remove that role?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I have recommended this question be closed as follows:
Accept: 'Armitage318' (https:#a43225844)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
I have recommended this question be closed as follows:
Accept: 'Armitage318' (https:#a43225844)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
ASKER