You can restart a single messaging agent by looking in the agent log for "current process id" to find the PID, then in Task Manager, add the column for PID and look for the appropriate PID to tell you which agent to stop. Dispatcher should automatically respawn a new agent after you kill it.

Yeah, but its an administrative nightmare and only gets worse the more apps you push.

Oddly enough I think most organizations allow BIS + BES. As far as managing the two, you set clear policies that state "if you're on the BES, we effectively own your device"

That's already possible using software configurations and application policies.

Enjoy your days away!

The ability to push 3rd party applications from the BES while at the same time restricting end-users from installing 3rd party apps on their own.

I don't think you are alone, but from an admin perspective, I am not sure I want to support this. This pops up from time to time in my environment. I don't meant to hijack your post here, so I will leave it simple. The basic issue is what happens with the mix of personal and business when the business part breaks down and the two parties seperate under less than amicable terms? Or under terms where the field dictates clients and profitable business?

I'm also curious to see if any BIZ wizards have a way to make managing the two simple. Thanks!

We have an Security & Risk unit who review the recommendations I suggest as the BES Admin. They either agree or disagree & then I set the IT Policies accordingly.

I totally agree with applying the same rules that exist with network user accounts e.g. password complexity, maximum password attempts, security timeout etc.

devans, thanks for the comments ... and I'm sorry you've got to deal with GroupWise + BES

Damn. I just realised that the Synchronisation Request Tool is not a feature of v4.1.4 of the Analysis, Monitoring & Troubleshooting Tools for GroupWise. Man I'll be glad when we migrate to Exchange & I don't have to wait 12 months longer for RIM to release updates for BES for Novell GroupWise.

Thanks hdawg. I was searching the BTSC for this information late last year.

In regard to your comment about that there may be a delay in executing subsequent or repeat commands, see below:

Requests for synchronization have low priority, so forcing a transmission requires you to stop and restart the BlackBerry Synchronization Server. The synchronization request is processed within minutes of restarting the service. The exact time is determined by the value of DWORD registry key HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\SyncServer\ServerBatchSyncInterval; the default time is 10 minutes.
1.At the command prompt, navigate to the folder that contains SyncRequest.exe.
2.Run the SyncRequest file with one of the -list or -sync parameters.
3.If you used -sync, stop and restart the BlackBerry Synchronization Service.

I'm guessing it should be ... but I wouldn't put it past RIM to remove the required tables / sql information to support this ...

As BESX is based on BES 5.0.0 MR1, I am quite sure you will be able to use at least BlackBerry Enterprise Transporter to move users from an existing BES domain to a new BESX domain. Does anyone have an information if BET is supported with BESX?

Oh the government makes security so black and white

Here you go
Security Checklists
BlackBerry STIG it is

Yes, but I don't think you can actually "upgrade"

They already had BES Express ... and now we have it again ... part deux!

Is this actually an upgrade from the previously known BlackBerry Professional Software for Small Businesses? RIM marketing really likes to confuse people...

Very good information. Thanks.

That's one of the nerdiest things I've heard!

I like it!

ok ... but when I make a change, I want it to take effect immediately under most circumstances. Why / when would I want to change a policy multiple times within a 15 minute interval?

Yes, you can set the delay to 1 minute, but that isn't the point ... it is still a delay and frankly I don't want to make that change so that it does queue processing every minute; especially if I have a large set of changes to do. I'd rather make the changes in batches and know they're getting queued immediately. Not having the ability to manage the queue is the problem with using a queuing system that bugs me.