View Single Post
Old 07-27-2010, 01:49 PM   #1 (permalink)
New Member
Join Date: Jun 2006
Model: 8330
Carrier: Sprint
Posts: 13
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default Deploying AND Updating 3rd Party app via BES 5

Please Login to Remove!


On 5.01, SP2. ~3000 users across 5 BES servers, flat domain, MS SQL2005.

Deploying various 3rd party apps without any real problem. This issue we are seeing is this:

Scenario 1:

Load App to BES
Create SW Config, add app
Assign to activated user --> SUCCESS

Update app to new version
Job/Task is created, but FAILS Looking at the job/task status, the logic of what the BES is trying to do makes no sense (some of it at least).

--> Task1 ... install IT policy
--> Task2 ... install app (new version)
--> Task3 ... uninstall app (old version)
--> Task4 ... install IT policy

Task 1 and 4 make sense, but why would the logic be to install the new verison of the app, then uninstall the old version of the app. Would make sense to uninstall then install.

We have seen this on 2 specific apps that we have focused on in our testing.

Scenario 2:

Load App to BES
Create SW Config, add app
Create Group, add SW config
Assign Group to activated user --> SUCCESS
Edit Group to remove software. Wait XX mins --> SUCCESS in unistall
Edit Group to add new version of software. Wait XX mins --> SUCCESS with install

Anyone else use this method to distribute. This is crazy if this is the method to manage SW distribution via BES, especially for large groups of users -- I would argue this method would not realistically work as certain users would not be updated correctly (assuming some would be off-line or would fail and need to be rebooted, etc).

Thoughts anyone? RIM docs do not discuss this idea (updating an existing application). What am I missing?

Thanks in advance for any assistance.

Offline   Reply With Quote