Recently in Sprint Category

One of my clients has 11 sites connected to an MPLS network provided by Sprint and part of that service is proactive monitoring for outages. For the past 3 months Sprint have been unable to contact me when an outage occurs as they cannot update their contact information correctly and when they do contact me (or I call into their support center) they fail to meet their SLA's of 1 hour on ANY of the many outages we've had.
The call I received today is the worst I've had. Two days ago one of the lines was disconnected (and Sprint notified). 48 hours later I receive my first phone call from Sprint telling me that there is an outage. 48 hours for a proactive monitor?????? The weird thing is that the ticket stats show they have advised me of the outage but yet again they called the wrong number. I have no idea why they are monitoring a disconnected line but 48 hours to let me know is a VERY slow response time.

After receiving a Samsung IP830W to allow international access to exchange, I had a big headache getting the device to sync with the exchange server.
The initial problem was caused by the SSL certificate having expired on the exchange server. Normal browsers can just hit the ok button to continue, but Windows Mobile5 will refuse to sync unless this is fixed.
Rather than purchase a new SSL certificate and wait the couple of weeks for Verisign or Network Solutions to provide me a certificate (this was needed *now*) I did some research and came up with the website SSL Enabling OWA 2003 using a free 3rd party certificate. Following the instructions was very simple and after a few minutes I had the certificate installed on the server. However the Windows Mobile Device would not accept the certificate! More research later the solution seemed to be to copy the cert file to the device and double click it but this still didn't work.
In the end I copied the ca.cer file to my pc and then used the infrared connection to copy it to the device. This got around the previous problem I had with the certificate programs not recognising the previous certificate I had BUT I then got the issue "Security permission was insufficient to update your device".
Whilst I was doing this I was on the phone with Sprint (on hold) for twenty minutes and at this point they answered the phone and were useless. They admitted they hadn't had any training on this, that no certificates were allowed to be installed on the device and to contact Microsoft. I hung up on the guy as he obviously had no clue and downloaded the RegeditSTG file from Bernt Lervik. Using the instructions at Bernt's site I edited the registry to allow the certificate to be installed. I did have to extract the zip file first and copy the exe file across as opposed to the zip file. Note that in order to expand the branches I had to use the center key within the rocker switch as the stylus/enter key wouldn't work.
Start regeditSTG and navigate to the hive key HKLM\Security\Policies\Policies
Change the following three registry keys (hint: hit Values first)
a. 00001001 to 1 (was 2)
b. 00001005 to 40 (was 16)
c. 00001017 to 144 (was 128)
After that I was able to double click the ca.cer file to install it, and then start the activesync process with exchange.

Hope this (convuluted) solution will help any other users and me the next time I have to do this certification dance.