September 9, 2009

My poor iPod fell down the shaft
While on vacation in Charleston South Carolina I had a traumatic experience. I was taking the elevator down from the third floor where our room was in the Marriott Courtyard hotel in North Charleston, when the doors opened I walked out, not looking up but checking my email on my iPod Touch. When I did look up I saw I was only on the second floor. Looking back down at my ipod I turned back to the elevator, took one step and was bumped by the closing door. The bump knocked the ipod from my hand and sent it tumbling 2 stories down the elevator shaft. I didn’t realize what had happened at first, then while scanning the floor I noticed the familiar glow of the screen shinning up at me. I was relived to see it was still on. The extremely helpful staff at the hotel was able to retrieve it for me in short order. I never invested in a case, cover or any kind of protection for the ipod, and as it turns out I didn’t need to. Other than a few nicks, a couple of scratched and a bit of a dent the thing is fine and in perfect working order. I think I will reward it with a iPhone 3.1 software upgrade.
1 Comment |
Blackberry, dwight g adams, gaming, iphone, smartphones | Tagged: durable mobile device, hotel, hotels, iphone, ipod, marriott |
Permalink
Posted by Dwight
June 23, 2009
We host email for several small business customers. After a recent Blackberry Enterprise Server (BES) update, I’ve had a lot of trouble with the enterprise activation of new phones. The user enters the correct information on the blackberry, and it comes back with an error to contact the system administrator.
In 3 separate cases last week, with both a storm and a pearl, I had this problem. We are running the LATEST BES OS (v4.7) which was realased in the last few days, and even after I wiped the phones, it would NOT do the enterprise activation. Again it gave me a “contact system administrator” error on the blackberry.
Finally I installed the blackberry messenger software on the clients computer. Just by installing the software and connecting the phone, the enterprise activation worked.
For verizon customers you can get the software here:
http://vzw.smithmicro.com/blackberry/download.aspx?ct=corporate
For Sprint customers: (Pearl selected in this case)
http://www.nextel.com/en/software_downloads/pda_smartphone/blackberry_8130.shtml
download the “BlackBerry Desktop Manager Version 4.7”
http://www.nextel.com/en/software_downloads/pda_smartphone/blackberry_8130.shtml
download the “BlackBerry Desktop Manager Version 4.7”
Leave a Comment » |
BES, Blackberry, Tech post | Tagged: BES, Blackberry, Enterprise Activation |
Permalink
Posted by Russ
March 5, 2009
At Corneredge we support all PDA’s to ensure full sync with all customer email services. Blackberry’s are great for this, and typically very easy to setup.
I recently had to set up a Blackberry on a BES server on a new network we were supporting. Despite repeated efforts, the Blackberry consistently made contact with the BES Server, and then failed on the IT Policy.
The issue was this: even if your bringing a blackberry from a domain (domain.com) in Site A into a same-named domain (domain.com) in Site B, you must break the connection that the Blackberry’s PIN has over the Blackberry network. Until then, the Enterprise Activation will not work. This type of situation would come up when you change your MX record, for example.
You basically have two options here:
1. Contact the old BES host in the old site and ask them to remove the PIN; or
2. Go to the Blackberry Device / Options /Advanced / Service Book, and blow away the value “”Desktop [CMIME]”.
Once that happens, the Blackberry brings you through the mail setup routine as if it were brand new out of the box, and will sync fine with your BES server in the new environment.
1 Comment |
BES, Blackberry, CES Systems, David DeRitter, Tech post | Tagged: BES, Blackberry, Blackberry Activation, blackberry migration, Blackberry Setup, Blackberry Sync, Corner Edge Solutions, Enterprise Activation, Error, Exchange Server, Microsoft Exchange |
Permalink
Posted by David