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

Random Slow Logons with Dynamic Environment Manager with Non-Persistent Desktops (78014)

Last Updated: 7/11/2023Categories: How toTotal Views: 10786Language:
English

7 like this article

Subscribe to get an email
newsletter with new updates

7 people found this helpful Please provide article feedback:

Symptoms

To find more articles on DEM slow login see Troubleshooting Slow Logins with Dynamic Environment Manager (DEM) .

In a non-persistent VDI environment, the Dynamic Environment Manager(DEM) agent takes a long time to perform its processing at logon, and the log file shows noticeable delays between actions that only involve items on the DEM configuration share.

Simple actions like reading a tiny config file from the configuration share take a long time, chances are that SMB oplocks are causing these delays. For more detailed information and defer to vendor documentation for SMB share see Microsoft document Opportunistic Locks.

Example: In this example, reading and processing B.ini and D.ini took 35 seconds each.

Note: The underlying issue does not always result in exactly this delay as this is just an example.

2021-02-26 14:36:02.385 [INFO ] Config file '...\A.ini' added to DirectFlex cache
2021-02-26 14:36:37.392 [INFO ] Config file '...\B.ini' added to DirectFlex cache
2021-02-26 14:36:38.997 [INFO ] Config file '...\C.ini' added to DirectFlex cache
2021-02-26 14:37:14.005 [INFO ] Config file '...\D.ini' added to DirectFlex cache

Delayed or slow DEM logoff.

Cause

At logoff, the DEM agent processes files from the configuration share to save the user’s settings.

On a non-persistent desktop, the VM is deleted after the user logs off.

Resolution

Please follow the workaround below.

Workaround

If the DEM log file shows delays when reading files from the configuration share and are using non-persistent VDI, deploy the following workaround:

Configure a shutdown script through local group Policy > Scripts (Startup/Shutdown)  The typical path in local policy would be is Computer Configuration\Windows Settings\Scripts (Startup/Shutdown).

Refer to windows documentation for a particular operating system(O/S) variant.

C:\Windows\System32\net.exe stop /y workstation

Note: Do not configure as a logoff script.

The "Script Name" field is not for a label or description, it's for the fully-qualified name of the script (or of the executable, in this example.)

Please set Script Name to C:\Windows\System32\net.exe and Script Parameters to just the parameters, i.e., stop /y workstation

This will act as a measure to help ensure that the SMB client correctly signs out of the SMB server.

Related Information

More detail on the above causes:

At logoff, the DEM agent processes files from the configuration share to save the user’s settings. The underlying SMB implementation maintains some state between the SMB server and the SMB client, keeping track of recently accessed files. If the same file is accessed from another VM (for instance because a DEM logon is taking place), the SMB client is notified to drop that file from its cache.

On a non-persistent desktop, the VM is deleted after the user logs off. It can happen that the SMB client is unable to correctly sign out of the SMB server before the VM is deleted, leading to timeouts in the SMB server when it tries to contact the SMB client. During this time, SMB clients on other machines can be put on hold, leading to the delays seen in the log file.

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
•
NUMA での仮想マシンの NVDIMM 構成オプション (78094)

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 Dynamic Environment Manager

Related Versions:

VMware Dynamic Environment Manager 9.10.x

Take Our Survey

Support Assistant