Certificate prblem with MOC 2007 R2

Dear All,

I installed OCS 2007 R2 Ent, after the installation, I'm trying to login by MOC 2007 R2 using one of network computer. The attached error appear when i try to login.
how to solve that?


Who is Participating?
BusbarConnect With a Mentor Solutions ArchitectCommented:
do you use automatic login or manually specified the servers.
you will need to make sure that the server FQDN is included in the certificate, if this is enterprise pool, the pool name must be included in the cert.
Arabsoft_SecurityAuthor Commented:
i use automatic login.

all FQDN are included in the certificate.

avisharConnect With a Mentor Commented:
This error occurs only one one PC or any PC ?

1).If you use a internal CA then copy the cert from the certificate authority and add it to the trusted certificates
2).Request another certificate from the Internal CA
3).If the above doesnot work then enable logging in communicator and post the uccp log

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

List the DNS records that you have for OCS including the SRV.
List the SAN entries of the certificate that you have associated on the Front End Server.
Jeff_SchertzConnect With a Mentor Commented:
Go into the General Options in Office Communicator and Turn on Windows Event Logging for Communicator.

After attempting a new login you should find events in the Windows Application log which describe in more detail the exact issue with the certificate.  Commonly it will report a name mismatch, but you might also have a certificate chain trust issue preventing sign-in as well.

Is this computer a member of the same domain as the OCS server?  do you have an internal Enterprise CA deployed which issued the certificate(s) to the Front-End server? Or are you using trusted public third-party certificates?
duffman76Connect With a Mentor Commented:
If you are trying to use autologon make sure the DNS SRV records are in place


Also if you are signing into a different domain then what your client is logged into make sure that the client trusts the certificate that is being issued.  If you are just testing you might have to install the certificate manually on the client.  

Run the validation wizard that is part of the ocs administrative tools and it will determine if your certificate is valid from the server standpoint.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.