ExBPA 2.8.7926.0 issues warning like the following:
The principal for SSL certificate 'https://domain1.com' does not appear to
match the host address. Host address: domain1.com. Principal: C=US,
S=California, L=Town, O="Company Name", OU=Operations, CN=host1.domain2.com.

The info referenced above is entirely erroneous. In fact, the SSL Cert on
my Exchange server is altogether different and is working perfectly. I've
checked IIS over and over but it looks OK. I ran SSL Diagnostics tool and
it gave me the following, which is all correct.

[ W3SVC/1 ]
ServerComment = Default Web Site
ServerAutoStart = True
ServerState = Server started
#Impersonated server account
SSLCertHash = long number
SSLStoreName = MY
#CertName = mail.correctdomainname.com
#You have a private key that corresponds to this certificate
#ContainerName='long number'
#ProvName='Microsoft RSA SChannel Cryptographic Provider'
ProvType=PROV_RSA_SCHANNEL KeySpec=AT_KEYEXCHANGE
#Subject: C=US, S=CA, L=Town, O=Companyname, OU= Corp,
CN=mail.correctdomainname.com
#Issuer: C=US, S=Arizona, L=Scottsdale, O="GoDaddy.com, Inc.",
OU=http://certificates.godaddy.com/repository, CN=Go Daddy Secure
Certification Authority, SERIALNUMBER=#
#Validity: From x/x/200x 3:30:46 PM To x/x/200x 3:30:46 PM
CertVerifyCertificateChainPolicy succeeded
SecureBindings = x.x.x.x:443:

Where is ExBPA getting its informatiom? Has anyone else run into this
problem?

Server: W2k3, ent, Exchange 2003 Ent. OWA, OMA, HTTPS over RPC. All working
perfectly.

Archived from group: microsoft>public>exchange>tools