This is in regards to RDS, and working around the changes in the 2019 editions, so it may be more appropo in another topic, but most of the ones I have found are closed.
Not realizing RDS will no longer work on Server Essentials version (2019), we built a single VM to host RDS (we have a 10-pack license) and got all software installed.
We have purchased a 2019 Standard key and can't seem to convert
What we have tried to activate:
- Activate Microsoft's standard VL key with "Dism /online /Set-Edition:ServerStandard /AcceptEula /ProductKey:<removed>"
- then: "slmgr /ipk"
This seemed to work the first time, but we were too hasty and got our product keys mixed up... we put the Essentials key in again with the slmgr command... it was successful, but after several reboots, and retries, we cannot even do the dism command anymore... with the kms key or our purchased key - we get "error 0xc004f069"
we have also tried "cscript c:\windows\system32\slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
.... so if we can't get the conversion to take, we are wondering if this will work:
- Leave the 2019 Essentials VM alone as the Domain Controller VM
- Install an additional VM running Server 2019 Standard (as a member server on the same domain)
- Setup the 2019 Standard VM as the RD Connection Broker, RD Web Access Server, and RD Session Host (for our 10 RDS licenses)
- Have (up to) those 10 users RDS into the 2019 Essentials VM?
(or is it a requirement that the server you are 'RDS-ing' into, have the RD Session Host role installed - which apparently isn't possible with Essentials?)
Also in this case, since the Essentials is currently the DC, will the domain architecture require the new 2019 Standard to be the DC? If so, will a 2019 Standard DC have the option to run the required RDS roles, or must those be on yet another 2019 Standard VM that is NOT the DC?
Thanks in advance!