We’re listening! Deploying Windows Mobile 5.0 on Windows SBS

Jason writes:

"Will there be an edit to the WM5 on SBS documentation in the *very* near future? It's just dead wrong in the Copy certificate to the device section (p 18). The certificate needs to be exported from the server, imported to the device (use a .cer file), instead. your proposed method works in very few cases, whereas an export import should always work."

Thanks Jason! We appreciate your feedback and are investigating the issue. We are planning an update to this doc soon and will incorporate any changes that result from our findings.

How about the rest of you SBS'ers out there? Have you used the doc Deploying Windows Mobile 5.0 with Windows Small Business Server 2003? Did you run into the same problem that Jason did? Let us know.  We value your experience, and others will benefit from your feedback.

This posting is provided "AS IS" with no warranties, and confers no rights.

Comments (4)

  1. I have been struggling with this for quite some time, I have found a solution and I wonder what you think…

  2. chris rue says:

    been showing this for awhile…

    i documented this exact method over at the funcave as part of the direct push demo setup using device emulator & wm5 series:


    i also presented this method live in the 3rd installment of the ‘crown jewels’ webcast series offered by ts2 in April:


    and finally, have shown this method live to a couple of user groups (Orlando IT Pro & AlabamaSMB) in the last several months.


  3. briwlls says:

    Yes, I to have the same issue.

    I’ve been open Outlook Web Access, clicking on the security lock within Internet Explorer and exporting that certificate to the a location on the network.

    I then tranfer that .cer file typically domain.cer to the phone via Explorer within Activesync. I then navigate to that file on the phone and install the certificate.

    This procedure is for the self signed certificate.

  4. TechSoEasy says:

    Hey guys… I think one blog needs to talk to the other blog.


    Jeffrey B. Kane


Skip to main content