VMware
 

Knowledge Base

Search the Knowledge Base:
Products:
Search In:
 

VDM Client Fails to Connect to Virtual Desktop After Upgrading to VDM 2.1 or 2.1.1

Details

The VDM Client fails to connect to virtual desktops after upgrading the VDM agent to version 2.1. or 2.1.1.
 
The presence of the following two lines in the agent log indicates that certain components on the agent cannot communicate with each other, which prevents Java Message Service (JMS) messages from being sent:

09:57:51,579 WARN <Main Thread> [] Authentication function AcquireCredentialsHandle failed, return value 0x80090305, text=The requested security package does not exist


09:57:51,579 INFO <Main Thread> [] Unable to connect to <localHost> as user NT AUTHORITY\SYSTEM, authentication failed

The vitrual machines being deployed in a pool are stuck in the customizing state and are not becoming ready in the VDM administrator.

Solution

Set the following binary registry entries and restart the guest.

[HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM\Authenticate]

"AuthPackagesOutgoing"=hex(7):4e,00,4f,00,4e,00,45,00,00,00,00,00
"AuthPackages"=hex(7):4e,00,4f,00,4e,00,45,00,00,00,53,00,53,00,50,00,49,00,00,\
 00,00,00

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   
Actions
  • KB Article: 1007341
  • Updated: Aug 14, 2009
  • Products:
    VMware Virtual Desktop Manager
  • Product Versions:
    VMware Virtual Desktop Manager 2.x