[ToniVR]

Hi,

We have a Express server (5.0.1) running, on which we have 25 users configured.
On the Express server, I created a Software Policy that pushed an application as being required for all users. This worked very well.

Now we installed a Full Enterprise server (5.0.2), including 25 CALs, on which the Software Policy has that same application set as Optional.

The problem is, when we migrate users with the Transporter tool, the application gets pushed from the Full Enterprise server, but gets in conflict with the application from the Express server.
We can delete the version from the Full Enterprise server, but anything we try to get rid of the Required application of the Express server fails.

Is there a way, except by issuing a full wipe, to remove that application?

If I check in the Modules under Applications, there is a difference in the application name:
Express name : eofficeMobileDataAlerter42
Full name: eofficeMobileDataAlerter47

Any tips are welcome.

As a method to prevent this issue from migrating other users (we just did 6 now), I've set the application as Optional on the Express server. Hopefully we can manually delete the application on the other 19 devices we still have to migrate.

Thanks,
Toni

[martinpas]

you can not delete it from de devices? or from the express server?

[RadHaz75]

i have a ticket open with RIM right now for a similar issue. we have an app deployed as required. we are trying to deploy an updated version of the app to those users however it is failing. after opening the ticket, RIM said there is a known BUG in 5.0.2 for exchange (and possibly older versions and other platforms) that will cause this issue. even setting the old app to optional and then pushing the new one as required results in a failure (and no manual delete option on the device for the supposedly optional app).

the workaround provided is to set the old app to disallowed which will force the BES to yank it off the device. once confirmed the app is removed, then push the new app. the bug is supposed to be fixed in 5.0.2 MR3 and 5.0.3.

[ToniVR]

Hi RadHaz75,

Thanks for your info, setting the (correct version of) the app as disallowed did indeed remove it from the devices!

My life got a bit easier