Share via

Seconf DC doesnt working ...

Stanislav Timofeev 40 Reputation points
2023-09-17T16:11:16.3066667+00:00

Good evening !

Given: One AD DC on Windows Server 2008R2.

Task: to get an additional domain controller on Windows Server 2022.

Actions:I'm doing everything as usual as described here:

https://winitpro.ru/index.php/2023/03/02/dobavyt-dopolnitelnyj-kontroller-domena-active-directory/

All tests, as it is written there, pass without errors, BUT ... when the first and main (FSMO - did not transfer) DC to WS2008R2, it is not possible to enter local user computers: "... there are no domain controllers that could process a request to log in to the network ...".

Tell me, what could be wrong, where to dig?

Windows for business | Windows Client for IT Pros | Directory services | Active Directory
0 comments

Answer accepted by question author

Anonymous
2023-09-17T16:46:20.2533333+00:00

The two prerequisites to introducing the first 2019 or 2022 domain controller are that domain functional level needs to be 2008 or higher and older sysvol FRS replication needs to have been migrated to DFSR

I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2019 or 2022, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.

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

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.