...Alternatively, go to https://your_owa_url/ and view the certificate using the browser. That should show you exactly which cert IIS is sending.
--- Seth On Nov 1, 2011, at 10:50 AM, Seth Wright wrote: > [PS] > Get-ExchangeCertificate | ? { $_.Services -match 'IIS' } > > That should tell you which one of your certificates is being used for OWA. > (Hopefully it hasn't changed since 2007, since I tested it on 2010.) > > --- > Seth > > > > > On Nov 1, 2011, at 10:30 AM, McCready, Rob wrote: > >> A few months ago, we installed an additional certificate on our Exchange >> 2007 Hub Transport server (from Go-Daddy) so that users could access OWA >> from an IPAD. Everything worked fine until yesterday when we had to renew >> the Self Signed Certificate that Exchange initially installed during setup. >> I would have thought that the Self Signed Certificate would not play a roll, >> since Exchange would be using the Go-Daddy certificate for OWA purposes. >> But I do find it odd that the Self Signed certificate was updated last >> night, and now OWA is not working this morning. I’m wondering if clients >> are trying to use the Self Signed certificate by default instead of the >> Go-Daddy certificate? Is there any way to determine which certificate a >> client is trying to use for OWA? > > --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist