Within some environments and especially an RDS or Citrix based SBC environment, there can be a problem with the root SSL certificates when using Office Communicator 2007.
In my case:
The first user on serverA who starts the Office Communicator won’t have any problems, because it can use the imported root SSL certificate to secure the connection. The second user (on serverA) who starts the Office Communicator will have problems, because the Office Communicator in the first session probably tries to change something and the root certificate is removed.
why? good question, but even Microsoft doesn’t know why, but it happens.
Ok.. you can fix this by doing the following steps:
- Login to the same server as the users
- Start regedit
- Go to: HKLM\Software\Microsoft\SystemCertificates\ROOT\Certificates
- Note which certificate ID’s are present
- Start the Office Communicator (as a user) on the same server
- Determine what certificate ID disappears (if nothing disappears, let a second user login)
- Reinstall the root certificate (the same ID will now appear)
- Give the user write rights to the root certificate registry key (the ID)
- Let the user start Office Communicator
- The BLOB value of the root certificate will change and will not be removed.
- Export the modified certificate with regedit
- Remove the write rights from the user account to the registry key.
- Let the user start Office Communicator and let an other user login on the same server and start Office Communicator
- No certificate errors!
- Import the exported regedit file on every server.
- Good luck!
Was once an enthusiastic PepperByte employee but is now working elsewhere. His blogs are still valuable to us and we hope to you too.