[SSO]升級到vCenter 5.5結果AD驗證失敗

[schumi]

http://kb.vmware.com/selfservice/micros ... Id=2060901

This is a known issue affecting vCenter Server 5.5.

To resolve this issue, replace the %WINDIR%\System32\idm.dll file on all systems running vCenter SSO 5.5 with the idm.dll file attached to this article.

Note: The attached idm.dll file is provided by VMware. It has been tested and verified by VMware engineering. If you experience issues after replacing the dll file, contact VMware Technical Support.

To replace theidm.dll file on the Windows Server 2012 running SSO 5.5:
Ensure that you are logged in as an administrator
Stop the VMware Identity Management Service on the vCenter SSO server. For more information on stopping services, see Stopping, starting, or restarting vCenter services (1003895). This step also stops the VMware Secure Token Service.
Back up the existing idm.dll by copying %WINDIR%\System32\idm.dll to %WINDIR%\System32\idm.dll.orig.
Download the idm_patch09252013.zip attachment that contains the replacement idm.dll file from this article.
Run md5 checksum on the downloaded idm_patch09252013.zip. The md5 checksum should match the MD5 checksum in the note below.
Decompress the zip file to a temporary location then copy the idm.dll to %WINDIR%\System32\.
Confirm that you have both new (idm.dll) and old (idm.dll.orig) in the %WINDIR%\System32\ Directory.
Start the VMware Secure Token Service on the vCenter SSO server. For more information on starting services, see Stopping, starting, or restarting vCenter services (1003895). This step also starts the VMware Identity Management Service.

After replacing the dll and restarting services, the initial AD login may take longer than normal to authenticate.

Note: The MD5 checksums are:
ZIP MD5SUM: 6834498d1f2fea13cdc059218134e239
DLL MD5SUM: 18199961d0bd134e1c0dfe74f71231b9