Well, I think at last I’ve finally found the time, AND managed to find the specifics of what was holding this up so that I’m currently in the process of syncing the Phone with Exchange remotely via an AG+AAC connection back to the Exchange Server across the SSL VPN.
What transpired is that out Exchange Server has an Equifax Cert, but not a regular Equifax cert, that would be too easy - this is the CA-1 variety that has an expiry of 2020. So as this wasn’t built in to the WM5 device you have to go and install it before ActiveSync will forgive you the errors and actually carry on and do it’s stuff.
Needless to say it’s not that easy - first you have to Application unlock the phone (or run a HTC cert-ed version of Regedit to modify the registry - oops, only had the phone just over a week and I’ve voided the warranty already - a record even for me ;-))) Then you can proceed to download an exported version of the root certificate and run that with explorer to import it.
The real catch here would **appear** to be that you need the Regedit AND the cert to be copied to the Phone and NOT the Storage Card or it will refuse to sort itself out, nor give any error messages. Now just out of curiosity this appears to be remarkably like the behaviour of some software when faced with UNC’s (like MSI’s for example??) they just refuse to play nicely, and only if you’re very lucky will you get the 1037 error or whatever it is that alerts you that it might possibly be because you’re trying to run an MSI from a UNC location……
Go figure, but at least you now know about it? right?
Well my Phone has now synchronized correctly with the Exchange Server while connected via USB to the Laptop and to the Server via SSL-VPN, now I just need to see if it can connect without the bits in the middle……??
Any bets? ;-))
Update: ActiveSync across the wire - still "Waiting for network" (right!!) But on the bright side it will now work with any PC when connected through the USB - nearly there…….



