remote desktop licensing issue

Sistemisti 1 Reputation point

Hello everyone,
ask for help regarding a remote desktop licensing issue:
I have 2 servers, windows server 2008 r2 and windows server 2019.
Server 2008 holds the Remote Desktop License Server role (both 2012 and 2019 versions).
Since I have an error in installing the license role on the new server (2019) why, despite having the new server point to the old license server, does the 120 days count start? Is there no compatibility between the new server and the license server role that is still on the old server?
Thanks for the reply

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,239 questions
0 comments No comments
{count} votes

12 answers

Sort by: Most helpful
  1. cthivierge 4,056 Reputation points


    A RDS CAL can be installed on a Server that has the same version or a newer version.
    Ex: a 2019 RDS CAL can be installed on a RDS License Server 2019 or 2022.

    A RDS CAL is backward compatibility.
    Ex: A 2019 RDS CAL can issue CAL for a client that connect to a RD Session Host 2019 or lower version

    Here is a compatibility between the Windows Server version and the RDS CAL that can be installed. Also, you may have your answer about the 120 dats grace period.

    0 comments No comments

  2. Sistemisti 1 Reputation point

    Thanks for the reply,
    so the only way i have to get the users to connect correctly in terminal on server 2019 is to install the license server role on server 2019 and migrate the licenses?
    If the answer is yes, could I post the error that is returned to me when I install the role on server 2019?
    thank you

    0 comments No comments

  3. cthivierge 4,056 Reputation points

    When you say "migrate", you want to move the current RDS CAL (Windows 2008) on your new Windows 2019 Server or you also want to upgrade the version of the RDS CAL from 2008 to 2019 ?

    For the error you have, you can post it and we may be able to help you.


    0 comments No comments

  4. Sistemisti 1 Reputation point

    Yes, I would like to move the license server from 2008 to 2019 (I also have 2019 version terminal licenses installed on the 2008 server).
    The error is unable to find the referenced assembly error 0x80073701
    this is a part of the cbs log

    2022-01-24 16:17:56, Error CSI 00000009 (F) STATUS_SXS_ASSEMBLY_MISSING #51592# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
    2022-01-24 16:17:56, Error CSI 0000000a (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #51434# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = e6b94a31a909baec6b08ad5b4b149e96, version 10.0.17763.1075, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Package_4164_for_KB4580390~31bf3856ad364e35~amd64~~', rah = (null), manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]

    0 comments No comments

  5. cthivierge 4,056 Reputation points

    This seems to be related to an update issue (KB4580390) and maybe others.

    The problem with this type of error is that you may spend a lot of time to troubleshoot and to fix the error.

    If it's a new server you have just installed, i would suggest to reinstall a new server and you will probably not receive this error message.

    0 comments No comments