RDS CALs - licensing servers

Question

We currently have a number of terminal servers and remoteapp servers, all running Server 2016 and all depending on a licensing server (a dedicated Server 2016 VM) for issing the RDS CALs.

Some of the RDS CALs are covered by SA and eleigible for upgrade to Server 2019, and some are not so will need to be replaced with new ones.

As we look to start the move to 2019, I will need to set up a new licensing server. Installing the new CALs won't be an issue, but how is it going to work with the ones on the 2016 server covered with SA? Can they be migrated (and become valid for 2019), or is it a case of deactivating from this server and reactivating on the new one?

Also, will a server 2019 licensing server with 2019 RDS CALs be able to issue licenses to 2016 terminal servers? The change-over will be gradual over a number of months so 2016 and 2019 terminal servers will co-exist for a while.

Thanks

Answer 1

Hi,

Some of the RDS CALs are covered by SA - May I know if you have RDS deployment on Azure and the licensing server is also setup on Azure? And does SA mean "Services Provider License Agreement"?

As we look to start the move to 2019, I will need to set up a new licensing server. - Will this new licensing server be setup on Azure VM?

You can refer to below article for RDS CALs migration. But we are not sure if 2016 SA CAL will be valid for 2019.

Migrate your Remote Desktop Services Client Access Licenses (RDS CALs)
https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/migrate-rds-cals

Will a server 2019 licensing server with 2019 RDS CALs be able to issue licenses to 2016 terminal servers? - Yes, 2019 licensing server with 2019 RDS CALS is able to issue licenses for 2016 terminal servers.

RDS and TS CAL Interoperability Matrix
https://social.technet.microsoft.com/wiki/contents/articles/14988.rds-and-ts-cal-interoperability-matrix.aspx
RDS CAL version compatibility
https://learn.microsoft.com/en-nz/windows-server/remote/remote-desktop-services/rds-client-access-license#rds-cal-version-compatibility

Thanks,
Eleven

Answer 2

Hi,

1) Please be informed that if your remote desktop session host server is 2019, only 2019 CAL could support remote connections. So you will need to buy new 2019 CAL for 2019 server, 2016 CAL could not be used.

RDS and TS CAL Interoperability Matrix
https://social.technet.microsoft.com/wiki/contents/articles/14988.rds-and-ts-cal-interoperability-matrix.aspx
RDS CAL version compatibility
https://learn.microsoft.com/en-nz/windows-server/remote/remote-desktop-services/rds-client-access-license#rds-cal-version-compatibility

2) For RD licensing server, we can migrate it from 2016 to 2019. After migration, the new 2019 licensing server could issue license to 2016 session host serve. And you will need to install new 2019 CAL so that it could also issue license to 2019 session host server.

Migrate your Remote Desktop Services Client Access Licenses (RDS CALs)
https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/migrate-rds-cals

3) Of course, you can also in-place upgrade licensing server from 2016 to 2019. Before upgrading, you will need to stop the remote desktop licensing service and restart it after upgrade completion.

Hope the information could resolve your questions.

Thanks,
Eleven

Answer 3

Thanks.

The RDS CALs I want to transfer were 2016 CALs when installed (that was the current version at the time), but are now also valid for 2019 as they ahd software assurance at the time when 2019 was released. When I transfer them to the new server, I need them to be seen as 2019 CALs so that they can be issued to both 2016 and 2019 terminal servers. If I migrate them will it see them as 2019 CALs? If not, will it see them as 2019 if I deactivate them on the old server then reactivate them on the new one?

I've always been very wary of doing in-place OS upgrades of servers. Admittedly I've not done it with 2016 to 2019, but with earlier versions it's tended to give trouble.

Thanks

Answer 4

Hi,

RDS CALs only have downgrade rights but no upgrade rights. 2016 CAL will not be seen as 2019 CAL whether after migration or deactivation and reactivation.

If you have further concern, you could contact RDS CAL vendor or Microsoft Licensing Activation Centers for double confirm.

Microsoft Licensing Activation Centers worldwide telephone numbers
https://www.microsoft.com/en-us/licensing/existing-customer/activation-centers

Thanks,
Eleven

Answer 5

Just to return to this one, I'm not sure that you've understood the point. The CALs were bought as 2016, but with software assurance they are valid for 2019 - the software assurance effectively confers upgrade rights on them.

I simply need to know wheter if migrated to a 2019 server it will treat them as 2019, or whether I will need to deactivate them on the old server and reactivate on the new.

Thanks