Concurrent license usage is incorrect when users connect via VPN.
book
Article ID: CTX326631
calendar_today
Updated On:
Description
If users connect via a VPN license usage does not increase after first user session launch despite unique users connecting from unique endpoints
Environment
Citrix is not responsible for and does not endorse or accept any responsibility for the contents or your use of these third party Web sites. Citrix is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement by Citrix of the linked Web site. It is your responsibility to take precautions to ensure that whatever Web site you use is free of viruses or other harmful items.
Resolution
A registry key was added to 2106 VDA which passes the complete device BIOS id which should handle a scenario where the hardware ID presented to the VDA is the VPN NIC hardware id. This feature is disabled by default on the VDA and can be enabled as per the following steps: Create the following registry value on the VDA (if MCS or PVS provisioned VMs please update master image/ vdisk in private mode and update catalog).
HKLM\System\CurrentControlSet\Control\Terminal Server\Wds\icawd\
Type: DWord
Name: fSerialNumberOverride
Value: 1
Problem Cause
When using certain VPN solutions the device hardwareid passed to the license server will be a common hardwareid assigned to the VPN
When accessing a site configured to consume concurrent licensing a licence will be issued based on the endpoint hardwareid during first session launch then returned to the license pool when all sessions launched via this hardware ID end.
Since all clients connecting via this VPN will have the same hardware ID a single license will be issued to the first device and any other device which connects via the same VPN will consume the same concurrent license.
i.e. if 200 clients connect to the same site via a VPN which uses a common hardware ID - 1 concurrent license will be consumed
The following article explains why this is seen - https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB40133/?kA1j00000000357This issue is addressed in the 2106 VDA - CVADHELP-14950
Was this article helpful?
thumb_up
Yes
thumb_down
No