Time to get a Windows Mobile device connected to the Exchange server with Self-Signed certificate? 30 minutes from start to finish.
\nTime to get a Blackberry Device connected to the BES server? Assume the BES is setup correctly, then less than 5 minutes.
\nTime to get an iPhone Device connected to the Exchange server with Self-Signed certificate? Typically less than 5 minutes.<\/p>\n
But I sometimes have to go to a foreign environment and put Windows Mobile devices onto someone’s Exchange server.
\nHere’s the fix to install the root certificate on the Windows Mobile device:<\/p>\n
Open up the webmail. In this case it’s https:\/\/mail.companyname.tld\/owa
\nAccept the invalid certificate
\nClick on the Untrusted Certificate Lock and view the available certificates
\nClick on the Details Tab, and then click on the Copy To File… button<\/p>\n
This now opens up the Certificate Export Wizard
\nClick Next
\nChange the format to Base-64 encoded X.509 (.CER) and click Next
\nMake a name for your file (I hit browse and named it “certificate”)
\nClick Next and then Finish
\nYou should see an “The export was successful”. If not, then you did something wrong.<\/p><\/blockquote>\nNow the fun part – creating an XML file with this information.<\/p>\n
Open up the Command Prompt (start, run, cmd)
\nChange the directory to where you saved the .CER file
\ntype certificate.cer<\/code><\/p><\/blockquote>\nYou should see a bunch of characters that begin with —–BEGIN CERTIFICATE—– and end with —–END CERTIFICATE—–.
\nWe’re interested in the text BETWEEN those. Right-click and select Mark, then select all the characters between the begin and end. Then right-click again to copy it (if it deselects you’ve copied).<\/p>\nRight-Click on your desktop and create a new text file with the name _setup.xml. Paste the following in there:<\/p>\n
<wap-provisioningdoc>
\n<characteristic type=”CertificateStore”>
\n<characteristic type=”ROOT” >
\n<characteristic type=”97817950d81c9670cc34d809cf794431367ef474″>
\n<parm name=”EncodedCertificate” value=”
\nMIICWjCCAc6CAgGlMA0GCSqGSIb3DQEBBAUAMHUxCzA6BgNVBAYTAlVTMRgwFgYD
\nVQQKEw9HVuUgQ29ycG9yYXRpb24xJzAlBgNVBAsTHkdURSBDeWJlclRydXN0IFNv
\nbHV0aW9ucywgSW5jLjEjMCEGA1UEAxMaR1RFIEN5YmVyVH61c3QgR2xvYmFsIFJv
\nb6QwHhcNOTgwODEzMDAyOTAwWhcNMTgwODEzMjM1uTAwWjB1MQswCQYDVQQGEwJV
\nUzEYMBYGA1UEChuPR1RFIENvcnBvcmF0aW96MScwJQYD6QQLEx5HVEUgQ3liZXJU
\ncnVzdC6b2x1dGlvbnMsIEluYy4xIzAhugNVBAMTGkdURSBDeWJlclRydXN0IEds
\nb2JhbCBSb290MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCuD6C28FCc6HrH
\niM3dFw4usJTQGz0u9pTAipTHBsiQl8i4ZBp6fmw8U+E3KHNgf76XUwefU\/ltWJTS
\nr41tiGeA5u2ylc9yMcqlHHK6XALnZELn+aks1joNrI1CqiQBOeacPwGFVw1Yh0X4
\n04Wqk2kmhXBIgD8SFcd5tB8FLztimQIDAQABMA0GCSqGSIb3DQEBBAUAA4GBAG3r
\nGwnpXtlR22ciuaQqPEh346B8pt5zohQDhT37qw4wxYMWM4ETCJ57NE7fQMh017l9
\n3Pu2VX2bY1QY6fDq81yx2YtCHrnAlU66+tXifPVoYb+O7A6X1uw16OFNMQkpw0P
\nlZPvy5TYnh+dXIVtx6qufd8itc2VrbqnzPmrC3p\/”\/>
\n<\/characteristic>
\n<\/characteristic>
\n<\/characteristic>
\n<\/wap-provisioningdoc><\/p><\/blockquote>\nNow in your command window again:
\nmakecab _setup.xml rootcert.cab<\/code><\/p>\nAnd you’re done! Besides copying this file over to your Windows Mobile device and then opening it so it’ll install, but those are just details anyway.<\/p>\n","protected":false},"excerpt":{"rendered":"
Time to get a Windows Mobile device connected to the Exchange server with Self-Signed certificate? 30 minutes from start to finish. Time to get a Blackberry Device connected to the BES server? Assume the BES is setup correctly, then less than 5 minutes. Time to get an iPhone Device connected to the Exchange server with … Continue reading Install Certificates On PDA\/Mobile Devices<\/span>