This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 81%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
Hello,
We need to put a Windows Server 2019 Essentials in a DC AD of another Windows Server 2019 Essentials. The problem being that afterwards we have errors. The errors appeared 3 months after the integration in the AD.
Can it be integrated with this license? I specify that we have less than 25 users and only 1 DC.
If so, where can these errors come from?
The server we are trying to integrate had AD DC before, but not anymore because we removed it.
Best regards
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Ok, you should be able to have two essentials servers on same network but they couldn't both be part of the same domain.
--please don't forget to Accept as answer if the reply is helpful--
The server licensing rights have been expanded, allowing you to install an instance of Essentials on your physical server to run the Hyper-V role (with none of the other roles and features of the Essentials Experience installed), and a second instance of Essentials as a virtual machine (VM) on that same server with all the Essentials Experience roles and features.
--please don't forget to Accept as answer if the reply is helpful--
Hello,
Thank you for your response. I forgot to specify that we are on 2 physical servers, we have nothing virtual. We had to acquire this 2nd server because of a specific application. It was not planned at the beginning, a few years ago.
So we wanted to put one of the two servers on the AD of the other, but we had these problems.
Best regards
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 28.999999999999996%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVW%3C/text%3E%3C/svg%3E)
The Microsoft blog Windows Server 2019 Essentials update has this to say:
If configured as a Domain Controller, Windows Server 2019 Essentials must be the only Domain Controller, must run all Flexible Single Master Operations (FSMO) roles, and cannot have two-way trusts with other Active Directory domains.
In short, configuring it as domain controller will have drastic consequences for the network in which it is found.
I strongly advise to skip Windows Server 2019 Essentials and get instead Windows Server 2016 Essentials.
reference：https://superuser.com/questions/1481039/does-windows-server-2019-essentials-have-to-be-a-domain-controller-as-requiremen
Tip: This answer contains the content of a third-party website. Microsoft makes no representations about the content of these websites. We provide this content only for your convenience.
Hope this information can help you
Best wishes
Vicky