The first line containing this word should be a line that will say something like “GetCertificate: Only using certs from issuers: ‘com, vmware-vdi, dc3-CA'”. If you start at the place in the log file where you had previously found the phrase “HttpSendRequest returned ERROR_INTERNET_CLIENT_AUTH_CERT_NEEDED”, search downward for the word “GetCertificate”. To find the reason why, you need to look at the debug log file again.
#Install smart card certificate outlook windows
If the certificate you want to use to login is in the Personal store, that means that the Windows View Client believes that it is invalid for authentication to the current View Connection Server. ActivClient) to “copy” certificates from a smart card to the Personal certificate store for use by applications such as Outlook, Internet Explorer, and the View Client. It is the job of the smart card middleware (e.g. If you go there and do not find the certificate that you want to use from your smart card, then you likely haven’t configured your middleware correctly. The Windows View Client doesn’t read them directly off of the smart card instead, it looks in Start > Control Panel > Internet Options > Content > Certificates > Personal. If you configured certificate authentication correctly in the View Connection Server, the next step is to determine whether the View Client can find the certificate you want to use for authentication. “userCertAuth = true” instead of “useCertAuth = true”). The most common error is not setting the attributes of the “locked.properties” file correctly or having a typo (e.g. Refer to the View Manager Administration Guide for more details about this. If you do not see this line anywhere, then you have not set up the View Connection Server correctly to support smart card authentication.
If you see this, that means that the View Connection Server is telling the View Client that it wants to certificate authentication, which is good. The first thing that you are looking for is a line that contains the phrase “HttpSendRequest returned ERROR_INTERNET_CLIENT_AUTH_CERT_NEEDED”. The easiest way is to scroll to the approximate time that you clicked the Connect button and saw the failure. Now starts the fun part: trying to understand the gibberish that is a log file. Open the most recently modified file in this directory starting with “debug”. On Windows Vista and later, the directory is C:\Users\\AppData\Local\VMware\VDM\logs. On Windows XP, the directory to find this in is C:\Documents and Settings\\Local Settings\Application Data\VMware\VDM\logs. Now you need to find the most recent debug log detailing this failure.
After you have set this, launch the View Client, reproduce your failure, and note the exact time that you hit Connect. In this registry key, create a new REG_SZ value with Name “TraceEnabled” and Data “true”. If you are on 64-bit Windows, navigate to HKEY_LOCAL_MACHINE\Software\Wow6432Node\VMware, Inc.\VMware VDM.
To enable TRACE logging, open “regedit” and navigate to HKEY_LOCAL_MACHINE\Software\VMware, Inc.\VMware VDM. The first step is to enable TRACE logging on the View Client and reproduce the authentication failure. Instead you are taken to the username/password dialog or see an error dialog saying “Smart card or certificate authentication is required.” This blog post will help you troubleshoot situations like these using the Windows View Client 4.0 or later. This will often manifest by connecting the View Client to the server and not being prompted for your PIN. I will occasionally get requests from people to help them troubleshoot smart card authentication to the View Connection Server in a setup that just doesn’t seem to work.