This configuration is stored in the following registry values: Use the RDMS GUI that's started on the active broker. You can use any of the following methods to implement this configuration.
#MICROSOFT REMOTE DESKTOP LICENSES LICENSE#
LicensingMode values Set the method for how the license server and the licensing mode will be applied on the RDSH server To do so, run the following PowerShell command: $obj = gwmi -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting Verify the license servers and current licensing mode that's configured on the Remote Desktop Session Host (RDSH) server Instead, you must implement a license server together with a license pack.
However, we don't recommended this approach. Reset grace period: The grace period can be reset to 0. Or by running the following PowerShell command: $obj = gwmi -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting The current grace period on a computer can be read by running the following command: wmic /namespace:\\root\CIMV2\TerminalServices PATH Win32_TerminalServiceSetting WHERE (_CLASS !="") CALL GetGracePeriodDays Troubleshooting specific RDP error messages to a Windows VM in Azure.License your RDS deployment with client access licenses (CALs).For more information, see the following articles:
The 120-day licensing grace period value is decremented to 0 (zero) as soon as a license server is configured. The listed resources in this article can help you resolve Remote Desktop Services (RDS) licensing issues. Try our Virtual Agent - It can help you quickly identify and fix common Active Directory replication issues
0 kommentar(er)
