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

Windows 10 1809 desktops experience performance issues and may become "Agent Unreachable" state if the High Precision Event Timer (HPET) is disabled. (67175)

Last Updated: 11/29/2023Categories: How toTotal Views: 32695Language:
English

17 like this article

Subscribe to get an email
newsletter with new updates

17 people found this helpful Please provide article feedback:

Symptoms

This is a Legacy KB. 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.  Horizon 7.13.x has reached their End of General Support (Apr 30, 2023) and has entered into its Technical Guidance Support phase (ends Apr 30, 2025).

On Horizon 7 version 7.5.1, Connection Server set hpet0.present=false for desktop virtual
machines created by the automatic pool in regardless of Primary VM's vmx setting.
(The Microsoft High Precision Event Timer (HPET) is disabled by default on desktop virtual machines.)

However, it may cause Windows 10 1809 desktop virtual machines to get into "Agent Unreachable" state.
(The desktop can be "Available" state after starting up, but soon it may become "Agent Unreachable".)

The problem is not reported on Windows 10 1803 or earlier Windows 10 builds.

Resolution

This issue is resolved in Horizon 7 version 7.5.2 and later available at VMware Downloads.

Workaround

There are two options to avoid this problem, either (1) or (2).

It can be avoided by changing hpet0.present parameter to true for each desktop virtual machines vmx files.

We can set this parameter to all desktop virtual machines in a specific pool by using pae-VirtualCenterExtraConfig.

To do this, please follow the steps below.

Start the ADSI Edit Utility on your View Connection Server computer.

Click Action > Connect to...

Click Select or type a Distinguished Name or Naming Context. In the text box, type DC=vdi, DC=vmware, DC=int.

Click Select or type a domain or server. In the text box, type localhost.

Click OK.

Expand the ADSI Edit tree, navigate to OU=Server Groups, and select the Pool entry.

Select Action > Properties and edit the pae-VirtualCenterExtraConfig attribute, adding the new value: hpet0.present=true.

Note: If you edit the pool setting(e.g. navigate to Desktop Pools, select a pool and edit on View Administrator), the above pae-VirtualCenterExtraConfig change is discarded.

To recompose a pool, do not use "Edit" menu but click a pool and choose "Recompose" from "View Composer" menu.

It can be avoided by using cs-allowhpet=true parameter for global setting.

By this setting, all virtual desktop machines in automated desktop pools can have hpet0.present=true in each vmx file.
To to this, please follow the steps below.

Start the ADSI Edit Utility on your View Connection Server computer.

Click Action > Connect to...

Click Select or type a Distinguished Name or Naming Context. In the text box, type DC=vdi, DC=vmware, DC=int.

Click Select or type a domain or server. In the text box, type localhost.

Click OK.

Expand the ADSI Edit tree, navigate to OU=Properties, OU=Global and select CN=Common.

Select Action > Properties and edit the pae-NameValuePair attribute, adding the new value: cs-allowhpet=true.

Note: To set hpet0.present=false for a specific desktop pool for some reasons, then use option 1) for that pool.

Related Information

For Performance related issues you can follow below listed articles:

Creating an Optimized Windows Image for a VMware Horizon Virtual Desktop

Performance issues with Windows 10 version 1809 VMs running on snapshots on VMFS6 (67426)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
在 Horizon View 中将远程桌面连接与 NLA 一起使用的限制 (67832)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon

Related Versions:

VMware Horizon 7 version 7.5.x

VMware Horizon 7

Take Our Survey

Support Assistant