I understand that Windows Server Essentials 2012 R2 must be deployed as a the only domain controller in an environment. It cannot simply be used as domain-joined Windows Server running SQL or something. However, I cannot find information to confirm that the inverse is true. It's my understanding that any Windows Server Standard/Datacenter instance can be domain-joined to a domain hosted by Windows Server Essentials. Basically, so long as the Essentials server is the only domain controller, there shouldn't be a licensing problem (CALs aside) with additional Windows Servers, right?
Windows – Can other Windows Servers be in the same AD domain with a Windows Essentials server
essentials-2012-r2licensingwindows
Related Solutions
My question was answered on technet in this forum thread: https://social.technet.microsoft.com/Forums/en-US/bab16fb2-2aad-4463-a9e9-4bbcc5be7588/cannot-open-dashboard-from-connected-client-to-restore-a-single-file?forum=winserveressentials&prof=required
I'm not sure why this should be necessary, but the fix was:
Regedit on the Essentials Server HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\TSAppAllowList “fDisabledAllowList” My guess is that the value you have is "0". If it is, just change to "1". No reboot necessary.
Once this value was changed in the registry the dashboard application can be launched from the client even without the Remote Desktop Services role installed on the server used for backups. So no RDS CALs are needed.
I did a test as I had similar question and needed to find out for myself (for a client) if I could upgrade Windows 2003 to Windows 2016 Essentials. It is not officially documented anywhere, but did a test using a bare bones Windows 2003 Std server (not even any updates) and a trial Windows 2016 Essentials version. Actually both were in trial mode.
IF DOING THIS ON A PRODUCTION SERVER, USE AT YOUR OWN RISK. MAKE BACKUPS, etc.
This is just a quick rundown and by no means a complete step by step. On VM’s or test PC, whatever floats your boat. I also assume you will have experience with migrating domains.
- Made the Windows 2003 Std server AD, DNS, etc, and added some users and login scripts. Basic stuff. Gave it a Static IP.
- Raised its Domain AND Forest Functional Level to Windows 2003.
- When installing the Windows 2016 Essentials server on my test PC, I made sure NOT to use the Essentials Wizard at all. Went into the Add Remove wizard and removed the Essentials Experience (you could I suppose re-install this later after all is said and done, but for my purposes, will not need it.) It will require a reboot. NOTE: To get rid of the Essentials Wizard from constantly nagging you on reboot, open the Registry on the 2016 server and go HKLM\software\Microsoft\windows\currentversion\run and delete the Essentials Wizard exe, or back it up and then delete, etc.
- Rename the server in the Server Manager\Local Machine.
- Give it a static IP and let the DNS point to the 2003 DC.
- Add the 2016 Essentials server to the 2003 domain as a member server. It will need a reboot.
- Once it’s all rebooted and you logged into the 2003 AD domain, proceed with creating the 2016 Essentials server as a domain server by following the usual Microsoft best practices. (This is a pretty good step by step: https://www.virtualizationhowto.com/2016/10/prepare-active-directory-windows-server-2016-dc-adprep/)
- Once the 2016 Essentials server is now the DC and DNS, etc, you need to ensure the Operations Masters Roles are NOT using the old 2003 Std server, and you also need to make sure the old 2003 Std server is NOT a Global catalog server.
- Once step 8 is done, run a dcpromo /adv on the 2003 Std server and let it demote itself to a member server.
- Ensure the DNS on the 2016 Essentials Network adapter now only has itself as the DNS server. It will likely show both itself and the old 2003 STD server as DNS servers.
- Once that’s completed, check your DNS on the 2016 Essentials server to ensure the Sites and any A records do not point anymore to the old 2003 Std server. Also, check your Active Directory Sites and Services, Default First Site Name and Servers, and then delete the old 2003 Std there.
That did it for me. No issues so far, although this is a test scenario. But it can be done in my opinion. If anyone has found otherwise, please let us know.
Best Answer
You can have a second DC with Essentials (as you could with SBS--there were entire TechNet articles about deploying your second server in an SBS environment). Essentials has to hold all the FSMO roles in your domain, but you can indeed have more than one DC with SBS or Essentials.
(This is a common and pervasive myth.)
So yes, you can have member servers, too.