Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

Windows 10 Enterprise Multi-session desktops and applications get disconnected after 60 minutes of usage (78242)

Last Updated: 3/17/2020Categories: TroubleshootingTotal Views: 6962Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Users that logon, then disconnect and then re-connect to a session on a desktop or application farm that is based on a Windows

Enterprise 10 Multi-session image will be automatically disconnected after 1 hour of their last re-connection.

There is no data loss, and reconnecting to the farm or app session will bring it back in the same state it was during the disconnection.

The issue will only happen when an existing session is disconnected and then re-connected.

The issue only affects ‘Windows 10 Multi-session’ based farms and happens when using both Horizon native and HTML clients.

The issue only occurs when using Blast or PCoIP protocols. RDP protocol will not cause the problem.

Purpose

The purpose of the article is to  understand and mitigate the issue until a long-term solution is implemented.

Cause

The cause of the issue has been linked to the  changes to Windows 10

Enterprise Multi-session terminal services licensing mechanism caused an incompatibility with Blast and PCoIP session re-connection.

Resolution

For desktop farms, configure the farm by choosing RDP as the default protocol, instead of Blast or PCoIP.

Notice that only the Windows versions of Horizon Client support RDP protocol therefore clients using the Mac OS and HTML versions of the Horizon Client will default to Blast protocol and still see the problem.

Application farms only support Blast and PCoIP therefore it’s not currently possible to avoid the problem for this kind of farms. The recommendation is to reconnect to the application and continue to use it normally.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
ESXi 6.7 以降では、仮想スイッチが不正な形式のパケットを仮想マシンに転送しない (78283)

KB
•
无法下载以句点开头的虚拟机文件 (78286)

KB
•
SRM サイトのインベントリ マッピングで変更が行われた後、既存の保護グループ（保護された仮想マシン）のインベントリ マッピングを更新できない (78232)

KB
•
REST API による、新しく作成された「HostAndCluster」フォルダへの ESXi ホストの追加 (78267)

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 DaaS Bundle

VMware Horizon DaaS

VMware Horizon

Related Versions:

Take Our Survey

Support Assistant