Does anyone have an idea if we can prevent the following from happening:
We use SCCM to deploy software and we did a rollout of Jabber 10.6(4) to all desktops. I have 10 users that I use as beta testers for 11.5(2) which we will deploy soon.
The problem is that SCCM goes out to all the devices and checks the Jabber version and when it finds one of my Beta users it tries to install 10.6(4) on it but fails. This is correct as I don't want SCCM to downgrade my test users BUT the installer program, using the /QUIET keyword, actually kills the Jabber process. This causes a bit of frustration when my beta testers are on a call.
When I run Jabber 10.6(4) installer manually, the popup messages say you cannot downgrade and you have to uninstall and then reinstall the older version. You can then only select 'Ok' and 'Finish' to exit the installer. It seems the /QUIET option kills the current Jabber process at this point.
How can I prevent the newer Jabber release from being killed other than removing my 10 users from the SCCM distribution list?
Ingo
