Oh. Well, after generating certificates for LCS2005 from the command line with an ini file and making sure it had a 'private' key that was all properly setup, so far the OCS certificates have been pretty darn easy.
Everything currently works but I think I do have a 'problem' somewhere, just haven't been able to schedule a time to deal with it. Complicating things was our Domain Admin decided to upgrade all our DCs to 2008r2 and broke the OCS stuff until we redid the forest prep. So I don't know if I have a problem or if it's resolved. :) On the bright side, I should be able to get time in about 2 weeks to see. Steven Peck http://www.blkmtn.org On Thu, Aug 5, 2010 at 5:21 AM, Michael B. Smith <[email protected]>wrote: > There are just so many of them and they have to be EXACTLY RIGHT and there > is not a neat & cool wizard like there is for Exchange. :-P > > > > Regards, > > > > Michael B. Smith > > Consultant and Exchange MVP > > http://TheEssentialExchange.com > > > > *From:* Steven Peck [mailto:[email protected]] > *Sent:* Wednesday, August 04, 2010 6:37 PM > > *To:* NT System Admin Issues > *Subject:* Re: Exchange 2010 Certificate Issue > > > > Wait. why are OCS2007r2 certs hard? (in the middle of migrating from > LCS2005 to OCS2007r2). > > > My next step is swinging the autodiscover in DNS over to point to the OCS > server so I can decom the LCS environment. > > Steven Peck > > On Wed, Aug 4, 2010 at 2:55 PM, S Powell <[email protected]> wrote: > > when they try to access OWA internally they have the Cert issue correct? > > are they trying to access owa.domain.com or internal.machine.name ? > > we had to make sure that our cert had both names. > > > > > Google.com Learn it. Live it. Love it. > > > > > On Wed, Aug 4, 2010 at 13:03, Cameron <[email protected]> wrote: > > 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/> ~ > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
