Exchange 2010 OWA, Activesync

Yesterday I created a self-signed certificate using my Exchange Server. I was able to install and then deleted the old expired cert and two certs with no services assigned. Outlook clients are no longer getting "expired cert" message but OWA and Activesync have quit working. Also, now I can't get to cert web enrollment site. Please help!
DL197Asked:
Who is Participating?
 
DL197Connect With a Mentor Author Commented:
I set certsrv folder to http access. I was then able to generate second cert which solved my problem. Evidently, first cert was corrupt as I generated second exactly the same.
0
 
raeldriConnect With a Mentor Commented:
have you enabled the certifcate?

Get-Exchangecerticate | FL
Enable-ExchangeCertificate -thumbprint (pastethumbprint) -services IIS

Open in new window

0
 
DL197Author Commented:
[PS] C:\Windows\system32>Enable-ExchangeCertificate -thumbprint (71917B6EB8DBDA82FB367C201DE523D5191030DC) -services IIS

Bad numeric constant: 71917.
At line:1 char:46
+ Enable-ExchangeCertificate -thumbprint (71917 <<<< B6EB8DBDA82FB367C201DE523D5191030DC) -services IIS
    + CategoryInfo          : ParserError: (71917:String) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : BadNumericConstant
0
Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

 
DL197Author Commented:
[PS] C:\Windows\system32>Get-ExchangeCertificate | FL


AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                     ule}
CertificateDomains : {belton.local, mail.belton.local, mail.beltontexas.g
                     autodiscover.belton.local, autodiscover.ci.belton.tx
                     .beltontexas.gov, beltonpd.local, beltontexas.gov, c
                     s.gov}
HasPrivateKey      : True
IsSelfSigned       : True
Issuer             : C=US, S=TX, L=Belton, O=City of Belton, OU=Belton, C
NotAfter           : 4/9/2013 5:11:18 PM
NotBefore          : 4/9/2012 4:51:18 PM
PublicKeySize      : 2048
RootCAType         : None
SerialNumber       : 4657376577E2329B437E7251904AD6D7
Services           : None
Status             : Valid
Subject            : C=US, S=TX, L=Belton, O=City of Belton, OU=Belton, C
Thumbprint         : 704B3ADA43B4FA89B254AD06F6280A0A6D12FB62

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                     ule, System.Security.AccessControl.CryptoKeyAccessRu
CertificateDomains : {belton-CITY-EX2-CA}
HasPrivateKey      : True
IsSelfSigned       : True
Issuer             : CN=belton-CITY-EX2-CA, DC=belton, DC=local
NotAfter           : 4/9/2017 3:46:37 PM
NotBefore          : 4/9/2012 3:36:38 PM
PublicKeySize      : 2048
RootCAType         : Registry
SerialNumber       : 2708CB79F0F7909648B3C2D3A7EDBB31
Services           : IMAP, IIS, SMTP
Status             : Valid
Subject            : CN=belton-CITY-EX2-CA, DC=belton, DC=local
Thumbprint         : 71917B6EB8DBDA82FB367C201DE523D5191030DC
0
 
raeldriCommented:
remove the brackets from the thumb print sorry
0
 
DL197Author Commented:
Command completed successfully. OWA site still doesn't come up. Neither HTTP or HTTPS...... Restarted IIS, no luck.
0
 
raeldriCommented:
What shows in the IIS access logs?
0
 
DL197Author Commented:
Where do I find those?
0
 
DL197Author Commented:
Found them @ c:\windows\system32\errorlogs\httperr. They are really long, not sure what I am looking for. See a lot of "Timer_ConnectionIdle" and "2012-04-10 13:51:20 ::1%0 49496 ::1%0 80 HTTP/1.1 POST /powershell?serializationLevel=Full;PSVersion=2.0 - 1 Connection_Dropped MSExchangePowerShellAppPool
2012-04-10 13:51:20 ::1%0 42795 ::1%0 80 HTTP/1.1 POST /PowerShell?serializationLevel=Full;clientApplication=EMC;PSVersion=2.0 - 1 Connection_Dropped MSExchangePowerShellAppPool
2012-04-10 13:51:20 ::1%0 42810 ::1%0 80 HTTP/1.1 POST /PowerShell?clientApplication=EMC;PSVersion=2.0 - 1 Connection_Dropped MSExchangePowerShellAppPool
2012-04-10 13:51:20 ::1%0 42805 ::1%0 80 HTTP/1.1 POST /PowerShell?serializationLevel=Full;clientApplication=EMC;PSVersion=2.0 - 1 Connection_Dropped MSExchangePowerShellAppPool
2012-04-10 13:51:20 ::1%0 42801 ::1%0 80 HTTP/1.1 POST /PowerShell?serializationLevel=Full;clientApplication=EMC;PSVersion=2.0 - 1 Connection_Dropped MSExchangePowerShellAppPool"
0
 
DL197Author Commented:
It was the method used to solve the problem.
0
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.