Outlook 2007 and Mandatory Profiles, could not load SSL libraries
Hello Everyone!
I am working on building a Citrix TS environment and am having some issues with Outlook 2007 and our mandatory profile. Our environment is running Server 2003 R2 Std and Citrix XenApp 5 Platinum.
When a user that is using my mandatory profile launches Outlook 2007 they receive a message that states "The application experienced an internal error loading the SSL libraries. This site should not be trusted." This message will pop up three times and Outlook will work fine after that, it is merely an annoyance.
We normally have one SSL error popup for users without Mandatory profiles (Our certificate doesn't match our server name) however the message that pops up for non mandatory profile users asks them if they want to continue and they have to select either yes or no, then it goes away.
Does anyone know why this is acting differently for a mandatory profile? Is there anyway to get this to stop doing this? I know that we can correct it by fixing the certificate, however my boss is unwilling to do that. Thanks for any assistance you can provide.
I am working on building a Citrix TS environment and am having some issues with Outlook 2007 and our mandatory profile. Our environment is running Server 2003 R2 Std and Citrix XenApp 5 Platinum.
When a user that is using my mandatory profile launches Outlook 2007 they receive a message that states "The application experienced an internal error loading the SSL libraries. This site should not be trusted." This message will pop up three times and Outlook will work fine after that, it is merely an annoyance.
We normally have one SSL error popup for users without Mandatory profiles (Our certificate doesn't match our server name) however the message that pops up for non mandatory profile users asks them if they want to continue and they have to select either yes or no, then it goes away.
Does anyone know why this is acting differently for a mandatory profile? Is there anyway to get this to stop doing this? I know that we can correct it by fixing the certificate, however my boss is unwilling to do that. Thanks for any assistance you can provide.
peakpeak
What about creating your own certificate and adding it to the trust list?
ASKER
Peak,
Thanks for the response. I will have to check with my boss on this one. He is a bit more involved in how things work than we would like a manager to be :-) I will post back once I get a response from him.
Thanks for the response. I will have to check with my boss on this one. He is a bit more involved in how things work than we would like a manager to be :-) I will post back once I get a response from him.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
dborger,
Thanks for the response and I am sorry for my delayed response. I am currently using the Citrix Profile Management feature and it works great, however this problem was with the mandatory profile that I was using. Giving full control did not correct the issue.
For some reason, something in this profile was broken when it came to HTTPS, even Internet Explorer could not load HTTPS sites. I was unable to register the DLL's used by Windows for HTTPS/SSL transactions. I have created a new mandatory profile and HTTPS/SSL connections are working correctly. Thanks again!
Thanks for the response and I am sorry for my delayed response. I am currently using the Citrix Profile Management feature and it works great, however this problem was with the mandatory profile that I was using. Giving full control did not correct the issue.
For some reason, something in this profile was broken when it came to HTTPS, even Internet Explorer could not load HTTPS sites. I was unable to register the DLL's used by Windows for HTTPS/SSL transactions. I have created a new mandatory profile and HTTPS/SSL connections are working correctly. Thanks again!
ASKER
Please see my final comment for the full solution. dborger's comment put me down the correct path to correct this issue.