While working on this, we encounter a problem with help desk logging in remotely to a machine. It changes the user SSO information to helpdesk.
I read an article from 2009, but I am not sure if there is an updated solution to this problem.
This is regarding the issue that arises when Helpdesk remotes into a client’s encrypted laptop using remote assistance,
or “help assistant”, and the user’s SSO details get changed. Specifically, the username gets changed to “helpassistant”
I'll branch this off as a new thread, as it's unrelated to the original question.
but, the answer is one of the XML files in the client directory has a list of user names who should never be considered for SSO. It includes the VMWare one by default, and you can add this one in if it's causing you problems.
Thanks. It is good to know what other applications do not like to play along with EEPC SSO.
I assume you meant "HelpAssistant".
I made an exclusion and it does not seem to be working. Do you have any idea on what it may be. The SSO details were set tup HelpAssistant.
You have made exclusion improperly. Correct syntax is:
<User name="__vmware_user__" />
<User name="ASPNET" />
<User name="HelpAssistant" />
There is also no space on the original defaul, vmware_user__"/>, between the double quotes and the forward slash, does it matter ? __" />