Hello,

We are running a multi-tenant SaaS platform using Apache Guacamole with the
RDP protocol (via FreeRDP) on the backend. Our customer’s RDP license
server is configured to use the *Per Device* licensing model. Recently,
we’ve observed a significant increase in Microsoft RDP license consumption,
which we suspect is due to how client device UUIDs are being generated and
presented by FreeRDP.
Our Problem:

It seems Microsoft treats each RDP session (even for different users from
the same tenant) as a *new device*, likely because the RDP client
(Guacamole + FreeRDP) doesn't persist a consistent UUID or machine identity
across sessions for the same tenant.
Our Questions:

   1.

   *How does FreeRDP currently generate or persist a client UUID or machine
   identity used for Per Device licensing?*
   2.

   *Is there a way (via ClientHostname, or another method) to inject a
   stable, per-tenant UUID into FreeRDP sessions through Guacamole?*
   3.

   *Has anyone implemented a patch or configuration in Guacamole to support
   deterministic UUIDs per tenant to control RDP licensing usage?*
   4.

   *Are there any known implications of using ClientHostname or similar
   fields for license tracking across RDP sessions?*
   5.

   *Would upstream FreeRDP or Guacamole be open to a feature request for
   better multi-tenant support in licensing scenarios?*

We’re looking to implement a patch or extension to inject per-tenant
deterministic UUIDs or device identities into the FreeRDP session initiated
by Guacamole, and would greatly appreciate any advice, guidance, or prior
experiences from the community.

Thanks in advance for your time and support!

Best regards,
Dilip

-- 


This communication (including any attachments) is intended for the sole 
use of the intended recipient and may contain confidential, non-public, 
and/or privileged material. Use, distribution, or reproduction of this 
communication by unintended recipients is not authorized. If you received 
this communication in error, please immediately notify the sender and then 
delete all copies of this communication from your system.

Reply via email to