Welcome to Port3101.org : Your BES Connection Mark forums read | View Forum Leaders
Port3101.org : Your BES Connection



Reply
LinkBack Thread Tools Display Modes
Erase Data & Disable handheld
 
  #1 (permalink)  
Old 02-23-2009, 05:26 PM
What am I doing?
 
Join Date: Jan 2009
Posts: 44
Default Erase Data & Disable handheld

Can someone confirm how this functions. I always assumed once issued it would carry out regardless if the user account is left on the BES or not. I was told today that if you remove the account the command will not deliver.

If that is so how do you ever get the user another device as often the lost/stolen device could be out of coverage or off?
__________________
Reply With Quote
Sponsored Links
  #2 (permalink)  
Old 02-23-2009, 05:34 PM
BES Activated
 
Join Date: Jan 2009
Location: Minneapolis, MN
Posts: 2
Default

When my users call me with a stolen or lost bb... I send the Erase Data and Disable Handheld right away and then I do a Disable Redirection (-vs- deleting the user from the BES). Not at all sure that is the correct way to handle the problem.

I also watch the Last Contact Time to see if the device ever phones home in-between the time it was stolen and when I'm ready to re-activate a new one. I have to believe as soon as it is powered back on and it contacts RIM it will get the kill command and wipe itself out.

I'm would also like to know the correct answer to your question.
Reply With Quote
  #3 (permalink)  
Old 02-23-2009, 05:44 PM
Otto's Avatar
Proprietor
 
Join Date: Nov 2008
Location: Atlanta, GA
Posts: 2,033
Blog Entries: 14
Default

That is correct. Once a user is removed from the BES, all of the pending policy commands are removed, as well. Using a password policy is the best way to guard against these devices. Given the 10-and-wipe policy, its a reasonable liability to assume. Wipe it if you can. If not, contact the carrier to have the line suspended and new device ordered. The benefits of leaving the user on the server is for the wireless backup data and pre-population.
__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.
Reply With Quote
  #4 (permalink)  
Old 02-23-2009, 11:09 PM
BES Administrator
 
Join Date: Jan 2009
Location: Trinidad and Tobago
Posts: 28
Default

I had to do 5 of these commands for this month alone for a few internal users....the user account must be on the BES server...this command actually wipes all the data on the lost/stolen handset as well as IT policies...it also disables the handset and user account on the BES server.

However, in order for this to work, the handset must be on and within a good network coverage. If the phone is off or the handset is not in a good network coverage, then the command would remain in queue until the handset is turned on or is present within a good network coverage...
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
SQL Script to grab user / handheld data hdawg Scripts & Tools / Hints & Tricks 15 10-04-2010 02:47 PM
KB19077 - Erase Data and Disable Handheld Command is received on a newly activated BB hdawg Featured BlackBerry KB Articles 0 08-22-2009 02:28 PM
KB14058 - Delete all data and applications from the BlackBerry using Wipe handheld hdawg Featured BlackBerry KB Articles 1 08-20-2009 04:13 PM
KB10970 - Log file entries to confirm the Erase Data and Disable Handheld command hdawg Featured BlackBerry KB Articles 0 08-17-2009 05:51 PM
KB04529 - Use the Erase Data and Disable Handheld command hdawg Featured BlackBerry KB Articles 1 07-20-2009 03:04 PM


All times are GMT -4. The time now is 08:31 PM.
Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2019, vBulletin Solutions, Inc.


 

SEO by vBSEO 3.3.2 PL2