dongcamp100
asked on
windows phone 7 will not sync with exchange 2010
I recently migrated/upgraded my exchange 2007 server to exchange 2010. The exchange 2007 server has been removed and everything is ok, but... All of our mobile phones are syncing except the two Windows Phone 7 devices in the company. I bought and installed a new certificate for the new server from Verisign. We have SSL turned on and the Andriods & iPhones work fine, but the Windows Phone 7s give an 80072f06 certificate error. I have found several articles and most refer to domian admins which neither of the users are. I would appreciate any ideas on this.
Don
Don
Please reboot the Windows 7 phones and try again.
login to webmail, save the certificate by clicking the padlock ssl secure symbol to local HDD, then email (may be via gmail) those certificates to your phone. Open the email and click on cetificates attachment, it will install the certificates on phone and you will be able to configure your exchange a/c then, tried and tested it works
ASKER
#AmitKhilnaney I do not see how to save the certificate? I can look at all the details, but I don't see a way to save it. (IE9) The copy to file option is greyed out under details.
ASKER
Update- I ran the remote connectivity analyzer and got this output:
ExRCA is testing Exchange ActiveSync.
The Exchange ActiveSync test failed.
Test Steps
Attempting to resolve the host name mail.lassiter-ware.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 64.45.230.100
Testing TCP port 443 on host mail.lassiter-ware.com to ensure it's listening and open.
The port was opened successfully.
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Test Steps
ExRCA is attempting to obtain the SSL certificate from remote server mail.lassiter-ware.com on port 443.
ExRCA successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=mail.lassiter-ware.com, OU=Terms of use at www.verisign.com/rpa (c)05, OU=IT, O=LASSITER-WARE INC, L=LEESBURG, S=FLORIDA, C=US, Issuer: CN=VeriSign Class 3 Secure Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name mail.lassiter-ware.com was found in the Certificate Subject Common name.
Validating certificate trust for Windows Mobile devices.
Certificate trust validation failed.
Test Steps
ExRCA is attempting to build certificate chains for certificate CN=mail.lassiter-ware.com, OU=Terms of use at www.verisign.com/rpa (c)05, OU=IT, O=LASSITER-WARE INC, L=LEESBURG, S=FLORIDA, C=US.
One or more certificate chains were constructed successfully.
Additional Details
A total of 1 chains were built. The highest quality chain ends in root certificate CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US.
Analyzing the certificate chains for compatability problems with Windows Phone devices.
Potential compatibility problems were identified with some versions of Windows Phone.
Tell me more about this issue and how to resolve it
Additional Details
The certificate is not trusted on any version of Windows Phone device. Root = CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
I tried manually installing the certificate on the phone, but I get the same error. This is a brand new certificate from Verisign. How can it not be trusted on Windows Phones? Even after I maually installed the cert on the phone, it didn't work? Where do I go from here?
Thanks!
Don
ExRCA is testing Exchange ActiveSync.
The Exchange ActiveSync test failed.
Test Steps
Attempting to resolve the host name mail.lassiter-ware.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 64.45.230.100
Testing TCP port 443 on host mail.lassiter-ware.com to ensure it's listening and open.
The port was opened successfully.
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Test Steps
ExRCA is attempting to obtain the SSL certificate from remote server mail.lassiter-ware.com on port 443.
ExRCA successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=mail.lassiter-ware.com,
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name mail.lassiter-ware.com was found in the Certificate Subject Common name.
Validating certificate trust for Windows Mobile devices.
Certificate trust validation failed.
Test Steps
ExRCA is attempting to build certificate chains for certificate CN=mail.lassiter-ware.com,
One or more certificate chains were constructed successfully.
Additional Details
A total of 1 chains were built. The highest quality chain ends in root certificate CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US.
Analyzing the certificate chains for compatability problems with Windows Phone devices.
Potential compatibility problems were identified with some versions of Windows Phone.
Tell me more about this issue and how to resolve it
Additional Details
The certificate is not trusted on any version of Windows Phone device. Root = CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
I tried manually installing the certificate on the phone, but I get the same error. This is a brand new certificate from Verisign. How can it not be trusted on Windows Phones? Even after I maually installed the cert on the phone, it didn't work? Where do I go from here?
Thanks!
Don
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Fixed it by working with Verisign