Office Communications Server 2007 R2, or OCS "Wave 14". Regards,
Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Cameron [mailto:[email protected]] Sent: Wednesday, August 04, 2010 4:57 PM To: NT System Admin Issues Subject: Re: Exchange 2010 Certificate Issue ummmmm....lol....You must mean Office Communicator?...if so, yes it's been installed but not configured yet On Wed, Aug 4, 2010 at 4:55 PM, Michael B. Smith <[email protected]<mailto:[email protected]>> wrote: Obviously, you have not yet installed OCS. If you think Exchange UC certificates are tough; you ain't seen nothin' yet... Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com<http://theessentialexchange.com/> From: James Kerr [mailto:[email protected]<mailto:[email protected]>] Sent: Wednesday, August 04, 2010 4:48 PM To: NT System Admin Issues Subject: Re: Exchange 2010 Certificate Issue I really hate cert management in exchange 2007. I don't know if its the same with 2010 but I use a cert (UCE cert?) that lets me list multiple domains. I use it for external and internal. So for example I have mail.domain.com<http://mail.domain.com/> and autodiscover.domain.local and a couple of others but I don't remember off the top of my head. ----- Original Message ----- From: Cameron<mailto:[email protected]> To: NT System Admin Issues<mailto:[email protected]> Sent: Wednesday, August 04, 2010 4:03 PM Subject: Exchange 2010 Certificate Issue Greetings all, We currently have a new Exchange 2010 Server running on W2K8r2. Clients running mix of IE 7/8 When they try and run OWA, they get an error that "The security certificat presented by this website was issued for a different websites address". If you click "Continue to this website (not recommended) everything works as it should. It seems that the self signed certificate is not in the trusted root CA. We do have a GoDaddy cert for external and it seems to be working fine. I've looked at instructions that show how to export the cert, create the file and then explain how to import it into the Trusted Root CA, but it fails and tells me that it can't create a PKCS #12 file. I'm pretty sure that there has to be an easy answer to this as the users are *complaining" about the error. As always, TIA! Cameron ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
