Windows Server 2019. vSpace sessions disconnect every 60 minutes.

Windows Server 2019. vSpace sessions disconnect every 60 minutes.

We have received reports from customers that after they set up their vSpace Pro Enterprise Edition environment on Windows Server 2019, the sessions disconnect every 60 minutes. 
 
This is related to a known restriction regarding Remote Desktop (RDS) “Per User” CALs licensing on Windows Server 2019.  According to Microsoft’s guideline, “RDS “Per User” CALs license on Windows Server 2019 requires Active Directory/Domain Control.
If no Active Directory/Domain Control is used (i.e., based on local user provisioning), the user’s session will be disconnected every 60 minutes. This behavior affects both native RDP sessions and vSpace Pro Enterprise Edition sessions. Please refer to this article for details.
 
Please find the following recommendations as current best practices for setting up your 2019 Microsoft Licensing Server with NComputing products:  
  
  1. There are two types of CALs license – RDS “Per User” CALs and RDS “Per Device” CALs. We recommend to set the RDS CALs license to “Per User” mode for their vSpace Pro deployment as described on this article.  This remains the same on Windows Server 2019.
  2. In addition, AD/Domain Control must be used to deploy vSpace Pro Enterprise Edition in a Windows Server 2019 environment.  Otherwise, the user session will be disconnected every 60 minutes as described in the article above.

In summary: 

  For vSpace Pro Enterprise Edition deployments using Windows Server 2019, the customer must have:
• AD/Domain Control for their deployment, and
• RDS CALs must be set to “Per User” mode

If the customer does not use AD/Domain Control (i.e., based on local user provisioning), 
• We recommend using Windows Server 2016 instead of Windows Server 2019 due to the 60-minute session disconnect restriction as described 
If the customer requires Windows Server 2019 for the vSpace Pro Enterprise Edition deployment the user sessions will disconnect every 60 minutes. There are work-arounds but these do not provide the best user experience:   
Educate the user to manually reconnect the vSpace session after the 60-minute session disconnect, or
- Provision the NComputing thin client to allow for “user auto-login” option with pre-entered user account credentials. In the case of disconnect the NComputing thin client will automatically attempt to reconnect.

Windows Server 2019

vSpace session
CAL license type
(Per User)
CAL license type
(Per Device)
No AD/DC 
disconnect after 60 min (no warning)
disconnect after 60 min (no warning)
with AD/DC
No restrictionNo restriction






RDP session
CAL license type
(Per User)
CAL license type
(Per Device)
No AD/DC 
Gets 60 minute warning & disconnect
No restriction
with AD/DC
No restrictionNo restriction


REV. 2019