Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

RDS application session disconnects every hour on Windows Server 2019 (79535)

Last Updated: 1/31/2023Categories: InformationalTotal Views: 15672Language:
Chinese (Simplified)JapaneseEnglish

14 like this article

Subscribe to get an email
newsletter with new updates

14 people found this helpful Please provide article feedback:

Details

Issue might not be seen when user connects for the first time to an application. Once user disconnects and reconnects to the session, post every 60 minutes, the session gets disconnected

Issue is seen only with RDS host running on Windows Server 2019 on any Horizon Agent version (applicable till Horizon 7.12)

Issue is seen with Blast, PCoIP and HTML access but not with RDP protocol

Issue is NOT seen when RDS host is not configured for RDS licensing (grace time period)

This issue is by design as the RDS hosts are not being managed by RDConnection Broker

With temporary license (grace period) the issue is not seen because during the grace period the RDSessionHost server does not connect with the RDLicensing Server until its expiry

Why is this issue not seen with RDS-2012 or RDS-2016 servers and only with RDS-2019 servers ?

RDS 2019 does have upgraded CALS (Client Access Licenses). It uses the same CALS as 2016 but the certificate provided in the CALS has a more modern signature hash present. Due to which certificate signing (CALS assignment) does run into issues when deployed without RDConnection Broker.

Solution

Important: We recommend you migrate from Horizon 7 to Horizon 8 as soon as possible. Horizon 8 offers numerous improvements in performance, scale, and experience for both Administrators and end users. Please see Ensuring a successful migration from Horizon 7 to Horizon 8 (89840)  for additional advice.

Upgrade to Horizon Agent 7.13 or Horizon Agent 2006. - note upgrade of Horizon Servers is also required.

Horizon 7.12  has reached the end of general support -  Please see VMware Horizon 7 version 7.13 Support Plan (81189)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
VMware ESXi で デバイスドライバをダウングレードする方法 (2079279)

KB
•
将 VMware ESXi 中的设备驱动程序降级 (2079279)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
View Client から Connection Server に接続すると、次のエラーで失敗する：ホスト名を解決できませんでした (Couldn't resolve host name) (2106968)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon Cloud on Microsoft Azure

VMware Horizon

Related Versions:

VMware Horizon 7.x

VMware Horizon 7

Take Our Survey

Support Assistant