Okay. IIS is listed on the Self Signed Certificate and NOT the Go-Daddy certificate. I know to enable IIS on the Go-Daddy certificate, I should....
Enable-exchangecertificate -thumbprint 8675309GoDaddyCertExample -Services IIS Can you tell me what the powershell command is to remove IIS from the Self Signed Certificate? -----Original Message----- From: Wright, Seth - wrightst [mailto:[email protected]] Sent: Tuesday, November 01, 2011 10:51 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and OWA [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 [email protected] with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe exchangelist
