Additionally, you cannot have the RD Connection Broker Role Service installed on your Essentials server since it is a AD domain controller. These two sessions are used for administration purposes. Or one remote user and one at the console. For example, you could have two Active users connected remotely via rdp, but no one logged on to the physical console, Windows Server 2012 Essentials only supports a maximum of two Active sessions, including someone logged on to the physical console. If you have your servers as VMs it is quick and easy to purchase a new server andĮxport/import the VMs to it-no need to reinstall applications. For example, say you need a more powerful server in the future. Setting up your servers as VMs is generally (not always) the preferred way and has many benefits. That way one of the VMs could be a DC, and the second VM could have RDS with your In this scenario there is no need for hyper-v to be installed.Ī single Server 2012 Standard license would allow you to install it on the physical server, install Hyper-V, and then create two VMs, both running Server 2012 Standard. You will need to use a combination of local group policy, wmi, registry edits, etc., to configure settings. You could install Server 2012 Standard and install the RD Session Host and RD Licensing Role Services without joining it to a domain, but you will not be able to use the Server Manager RDS gui to manage it, or publish RemoteApps, or have collections,Īs well as some other features will not work. This implies a minimum of two servers, one for a DC, and one for RDS, which both can be VMs. In order to use Server 2012 RDS the way it was intended, you need to have a 2012 server joined to a domain (not a DC). Essentials only supports 2 Active sessions, regardless of how many RDS CALs you own.
0 kommentar(er)
