#Windows server 2012 r2 remote desktop services install#
#Windows server 2012 r2 remote desktop services software#
#Windows server 2012 r2 remote desktop services license#

#Windows server 2012 r2 remote desktop services software#

Even if there is maybe different software out there that allows this. To go and buy Server 2012 Standard if there is another way of doing this. We are obviously also looking to save costs wherever possible.

The actual end result we are looking for is simply to have 5 people connected concurrently, doesn't matter what OS they log onto, but it still needs to be onto the same machine.

#Windows server 2012 r2 remote desktop services install#

My second question is, To have Server 2012 (Not essentials) with Hyper V installed, would I still need to have two VM's running just to het 5 people connected? Or can I have just that, and install my program directly on there so users can log in and use You say that I cannot have the RD Connection broker installed because it is an AD domain controller? What if it is not the domain controller, wouldn't that work? Or is it just as simple as to say that the Essential 2012 version doesn't support more thatР вЂќРЎС› RDP connections even when you have licenses for it? Virtual instances plus physical for hyper-v only.

#Windows server 2012 r2 remote desktop services license#

A single Server 2012 Standard license would allow the above since it allows two For example, you could have ServerР вЂќРЎС›012 Standard with Hyper-V installed on the physical box, with two VMs: one VM running Essentials and a second VM running Server 2012 Standard with RDS Role Services. This does not need to be a separate physical machine. If you need to have 5 users logged on to the server via Remote Desktop then you will need to have a separate Server 2012 (not Essentials) for this purpose. You may use the Remote Web Access feature to access PCs on your internal network (including the server) via Remote Desktop from outside of the office. 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.