Win Mobile

There are scenarios where Windows Mobile phones have security locked down to require installation/setup programs to have a valid certificate from a trusted source.

Installation fails if the package:

#1. Does not have a certificate.
#2. The certificate included is self-signed/from an internal certificate authority (CA) and the phone does not have the CA in the Trusted Root Authority.

Solution, in order of preference:

#1. If the package has a self-signed/internal CA certificate, import the CA into the Trusted Root Authority on the phone.
#2. Remove the certificate requirement: Set HKLM\Security\Policies\Policies\0000101a to 1 using a Windows Mobile registry editor. Setting the value to 0 will re-enable the requirement.

Read more about the issue here and why, most of the time, having this security setting turned on is a good thing.

It is only a matter of time until there is an Office Communicator client for the XBox and the Wii. Next step to a total Big Brother-esque system is to have location triggers that will set your status to say "Near the coffee machine in the Office" and report your GPS/aGPS location. Unfortunately, I know of some organizations that really would like that type of micromanagement of their employees.

Read more about the OCS client for Blackberry at Matt's site here. To go directly to the download page for the client, go here.

The strange part about the client, to me at least, is that it requires a Communicator Web Access installation that the Blackberry Server talks to directly using NTLM/Windows Authentication.