BlackBerry Device Preparation
 

Any of you go through and remove the languages, sample video, etc. on newer BlackBerry devices? I noticed that with some of our BlackBerry 8310 models (likely all Curve devices), of the 56MB of available memory (8MB goes to the platform/device ROM), 44MB is in use out of the box. We've obviously had an issue with people not being told they are limited with memory - even moreso because the device has 10 million languages you will never use - and they end up taking 40 photos and *bam* - "Where did all of my emails go?"

Just curious what other companies are doing prior to end-users receiving devices, if anything - uninstalling default software, training end-users, purchasing memory cards?

I don't do any of that since we ship most devices directly to the end users (and rarely install Desktop Manager). We haven't yet introduced camera phones into the list of standard devices, so I'm not too worried about pics. I do have a few pretty savvy users, though, who have purchased memory cards on their own and ripped their own DVD's. Those are the users I love since they know what they are doing and I don't have to worry about them.

I shudder at the thought of adding a camera device to our standards list.......

The only thing I have currently done is publish an article for our help desk. Its basically a mashup of the existing memory optimization documents out there.

I noticed the memory level of the 8310 out of the box too. We clean up the devices internally, but not external devices, just too many for that.

Would like to see this as an option (being able to select what parts of the OS is installed) when we are able to push the OS out from the BES when its fully available. Havent had the new device OS to test with yet.

...even if you had OS 4.5, the OTASL option will only be enabled by RIM's NOC at some undetermined future timeframe. This means that even if you had BES 4.1 SP5 and OS 4.5 available, no visual option would be present in the BES for configuration.

I bought 2Gb cards from NewEgg for like $8.50 each and am just passing out the newer BB's with these cards already installed and the camera already set to save to the card. Cheap insurance.

Didn't know that, haven't looked all that much at 4.1.5, only the obvious things like Software Config status, force calendar Sync etc. Just been waiting for 4.5 OS first.

When we were rolling out 7130 with 4.1 we had to nuke them then rebuild with just the English language pack as we were hitting the 512 cod file device limit (Not such a problem with 4.2 as they have a limit of 1024 codfiles). From then on we decided to rebuild every device with only the language packs and software we wanted on them.

We get a lot of this type of problem with our users. At the moment we've been reactive with it as the numbers aren't too high, but I'm keep a close eye on it as we may need to remove the sample stuff and some language files (although this is difficult as we have a lot of bi-lingual clients) from the devices before they go out if it gets worse. Not ideal that it's happened with the 8310 and it seems RIM dropped the ball on this one.

It really depends on the user in our environment. All devices go through me first; they don't get shipped to the end user. If they are a pretty savvy user, I'll leave most things intact. On the other hand, I strip out things that might be considered dangerous to a user who might lack the technological interaction required to properly interact with an advanced data device. (ie: act like a flying monkey)

No joke: Before I removed languages from devices and deployed them as-is, I had one user who asked me, "The device says it knows French. Does that mean I know it too or will it teach me?" ::blink::

I end up removing the languages, but leave most things intact. I make my end users buy their own media cards if their camera is enabled (which most are not by default). I forget to disable the language shortcut key all the time, so I end up with users telling me that their devices are now writing in arabic, and for some reason they can't dial their phone correctly.

I do other modifications before I hand the device over to the end users due to the fact that 90% of my end users think their devices are pagers.

as soon as i open the box, i app loader lite and remove all languages, the sample video (why is this here?! its utterly useless), the tty(l) and the password keeper. the main reason i actually started removing the languages is because people would occasionally do the shortcut key to change the language like brinaht said above. shortly thereafter i realized how much space it actually frees up since i started having users run out of space. this coupled with my ocd makes for me to immediately run app loader anytime i get my hands on a unit now.

i also do this on sprint and verizon devices though it doesnt make that big of a difference since these devices only come with like 3 preinstalled languages anyways

I wish that were the case here. We have people show up all the time with their personal devices wanting BES access.

Those devices ordered by the university do come through me, so I usually remove any extra languages (with exceptions based on role), set the Keep Messages to 15 days for most (though some prefer 30), the sample video, Brickbreaker, and Password Keeper. I used to hide the last two application, but found that nobody ever missed them and those who had them never used them.

We never remove anything before deploying, but we do hide some items and inform users that they are expected to use the device for business. If there are any issues after deployment, then we remove things selectively. We try not to nerf them, within reason.

For those of you who do remove it, do you do it yourself or do you have a group who receives and coordinates the activation of the devices? My responsibilities rarely touch down with the end-user procurement and activation processes, therein my problem with initial control. I've tossed around the idea that something needed to be done when we receive the devices, but my suggestion was tabled until more analysis could be completed. My issue is that with the lack of exposure that I do have, when tickets are escalated to me for the Low Memory Manager issues, then something early on in the process needs to change.

...in these cases, we aren't talking about a couple hundred devices... we're talking thousands of devices and the best method by which to control the pre-packaged software on them.

I agree with that. If it's getting escalated to you then the reactive approach you're currently taking is the wrong one.

It's a difficult one to actually save yourself time with because you're either going reactive and raising a ticket for it, or you go proactive and remove all the stuff off each device before you provision it for the user - either way your guys are spending the same amount of time fixing it. I suppose if you had a VIP user who didn't need or want the hassle then it's better to go with the proactive approach, but in terms of workload at your end you're either doing it at the start or at the end (damned if you do and damned if you don't)!!!

Jibi,
i think it would be almost impossible to control the prepackaged device software do to decentralized purchasing. Each section uses the provider they like or can get coverage from...and they each have different loads. Although when I do have hands on with the device I remove the languages/certificates the user doesn’t want/need.

However I recall that a RIM person I spoke to in WA, stated that there is a way to control apps wirelessly. By setting up an app config then sending the user a URL. once connected the url the device did a wireless config....and could update or adjust the loaded software? I think that this may need looking into

Jibi,
I'm primarily the only one who orders & activates the devices as well as monitoring the BES as best as I can. I try to do the proactive approach on the 83XX, 81XX and the 88XX models and the 8700s are left on their own. Occasionally when I have a telecom person at another site activate a device for me I try to explain how to delete the languages, but it seems to not ever be implemented correctly.

I agree with BBAdmin, whether you do it proactively or retroactively, you're still going to be dealing with the same amount of time. It is always nice to deal with things proactively rather than have to clean up issues as they come up!

As of now, on top of managing our environment (of over 9000 users) i also touch every new device that comes in, this means removing all of that junk. we are tossing around the idea of getting a new person or intern on our team to do these things which would give me the opportunity to set the precedent to do have them do these things. I mean its not that hard of a thing to do and it takes 10 mins. just get a comp with a hub and hook up 15 devices and do them all at once. build it into the process so that a device has to have it done to be deployed.