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(201.6, 82%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPF%3C/text%3E%3C/svg%3E)
We are building a 2019 Domain with Exchange server that is 2019 that our current domain - a domain with a functional level of 2012 - will have a 2 way trust with.
We have an 2012 RDS setup that has a 2012 licensing server with 2250 2012 RDS CALs and a 2019 licensing server with 2250 2019 RDS CALs. When people connect to the the 2019 domain from the 2012 RDS system, do they need to have a 2019 CAL to do so or will the 2012 CAL do? Can we still use a mixture of both which is what we are currently doing?
![](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)
That sounds more like remote desktop for administration purpose. In this case you're allowed two concurrent connections for remote management and RDS Cals should not be needed.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Hi,
thanks, I understand that you can have 2 admin connections to a server but this is not for admin purposes.
We have several thousand people working from home that are remoting in to the 2012 system. These people will need access to the 2019 domain - they will use the 2012 system as a jumpbox into the 2019 system.
Rightly or wrongly, this is the way we will be doing it and I don't want to enter a discussion as to why it's setup this way, it just is; will we need to have 2019 CALs for everyone that does this?
Thank you
they will use the 2012 system as a jumpbox
Got that, what are they jumping on to is the question? what OS, purpose, etc.?
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
I just need confirmation that if I RDP to any device within that new 2019 network from the 2012 network, then I need a 2019 RDS CAL?
I'm not sure what you mean by "any device"? The 2012 RDS Cals can only be used to connect to a 2012 or lower RDS host. Same for the 2019 RDS Cals the 2019 RDS Cals can only be used to connect to a 2019 or lower RDS host.
--please don't forget to upvote and Accept as answer if the reply is helpful--
HI,
my apologies , when I say 'any device' I mean any PC or server in that domain from the other domain.
So, it goes:
User connects into a 2012 Web RDS and gateway in a 2012 domain then...
from a 2012 connection broker & session host within that RDS infrastructure within the 2012 domain , connect into...
the 2019 domain to a 2019 server or Win10 PC or running a Outlook remoteapp which connects to Exchange 2019.
Basically, what series of CALs/Licenses will I need to do that. Can I get away with only having 2012?
For me - it's a no - as we are using 2019 at various points. However, a project manager is insisting that I don't need 2019 CALs or licenses to do the above.
Hi, appreciate your answer.
I always knew that was the case but I just need confirmation that if I RDP to any device within that new 2019 network from the 2012 network, then I need a 2019 RDS CAL? Or do I just need a 2019 Windows CAL?
There is also the question of Exchange 2019 from within that 2019 network, what license do I need to access that ?
You can't use RDS CALs for earlier versions to access later versions of Windows Server, but you can use later versions of RDS CALs to access earlier versions of Windows Server.
https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-client-access-license#rds-cal-version-compatibility
--please don't forget to upvote and Accept as answer if the reply is helpful--
