Impossible to add AD DS services in Windows Server 2022

Question

HI, I Have a problem with my new DELL PowerEdge Server with Windows Server 2022 Standard ROK. I can't install/add the services AD DS roles. The install begin correctly and finish with the message :
"Feature Install: Request to add or remove features on the specified server failed. Unable to perform the operation because the server you specified requires a restart"
Exactely in french :
"Installation de fonctionnalité : échec de la demande d'ajout ou de suppression de fonctionnalités sur le serveur spécifié. Impossible d'effectuer l'opération, car le serveur que vous avez spécifié nécessite un redémarrage"

I Had also tried with succeed to install Features AD DS and AD tools

The environnment is :
The first/old server name is LPF81-S-01 in LPF81.local Domain (always in activity) with Windows Server 2012 R2 Essentials (IP config : IPV4 :192.168.0.1, sub : 255.255.255.0, bridge : 192.168.0.50, DNS1 : 192.168.0.1, DNS2 : nope, No IPV6). It contain AD DS, DNS Server and DHCP Server. It is now the only server.

I would like install the second/new server (the DELL with Windows server 2022 Winver 20348.1194) for promote him in the future, only one AD DS, DNS and DHCP Server.
The second/new server name is NewLPF81-1-01. It can join LPF81.Local domain. And I can open LPF81\Administrateur Windows Session. His config is : Windows Server 2022 Standard ROK with IP Config : IPV4 : 192.168.0.2, sub : 255.255.255.0, bridge : 192.168.0.50, DNS1 : 192.168.0.1, DNS2 : 8.8.8.8, no IPV6.

sfc/scannow is OK
DISM /Online /Cleanup-image /checkhealth is OK
DISM /Online /Cleanup-image /Restorehealth is OK

Can somebody help me ?

Thank you very much !

Answer 1

Sounds badly broken and the simplest / quickest solution is to clean install it, patch fully and try again. Also note a domain controller and all members should only use domain DNS, no router or public DNS server addresses on connection properties.

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
https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405

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--

Answer 2

Thank you for your answer.

When you said "quickest solution is to clean install it, patch fully and try again", it is significate, that i should reinstall to factory settings my news server ???

I've tried to delete DNS 2 : 8.8.8.8. The only DNS on the new server is 192.168.0.1 (the first AD DS Controler). Trying to reinstall after this : same failure

For the first prerequisites : i have checked on the old server in User and Computer Active Directory, right click on LPF81.local and select "Raise domain functional level" was already domain functional level : "Windows Server 2012 R2" ("maximum domain fonctional level")

For the second prerequisites; on the old server :

• cmd\dcdiag.exe : all testes are OK. Except one : SystemLog : a warning event has occurred:
  The 192.168.0.0 IP address range is 92% full with only 3 IP addresses remaining. Systemlog test passed.
  => It is a problem or not ?

-cmd\dcdiag /test:dns : all is alright

-cmd\repadmin /showrepl :
- Default-First-Site-Name\LPF81-S-01
- Option DSA : IS_GC
- Site Options : <none>

-cmd\repadmin /replsummary :
-DSA Source : max difference number of failure %% error
-DSA destination max difference number of failure %% error
=> don't understand the signification

Answer 3

Oh I have forget it : my Windows server 2022 is already licensed (it is licensed by DELL himself in factory)

Answer 4

You'll need to get past the issue of the broken operating system. The simplest / quickest solution is a clean installation as mentioned above. Starting off with something broken is not a good start.

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

Answer 5

OK. I thought OS was Ok because verification with sfc/scannow and DISM was OK. I will reinstall OS on the new server and i will return on this thread to say if it is OK or not. Very thank you for your spending time !