|
One of the bigger new contributions by the AppConfig Community will be a standard XML schema for configuring managed iOS apps. iOS managed app configuration allows developers to define settings in an app that can be configured when apps are deployed using MDM. This is useful for filling out information like server addresses or port numbers, or otherwise customizing enterprise apps.
These app configuration settings can be anything a developer wants them to be, which is very powerful, but results in a certain amount of work for IT to do—they have to figure out the settings and get them all loaded into their MDM server to push down with the apps. With the AppConfig Community’s XML schema, common configurations are standardized, and can be built directly into an MDM server and admin UI, simplifying the deployment process.
|
Source: http://www.brianmadden.com/opinion/AirWatch-MobileIron-IBM-and-JAMF-are-forming-the-AppConfig-Community
Hi,
We're also highly interested in customly configuring certain Jabber Mobile settings in our environment, since the default values are not suited for our daily operations. Since we can't manage certain default JM settings the whole setup is basically an ongoing maintenance nightmare. Don't get me wrong, we love JM but having a way to centrally manage the settings certainly would make our lifes a lot easier.
Let me quickly draw our situation. We manage 1'000+ JM devices on site. On each device we have to change a couple of the default settings by Hand before we hand the device out to the user (which by itself is ridiculous and a huge source for human Errors). But it gets better.
Our password policy requires our users to change their PW every 90d and each time they have changed their PW they need to reset JM in order to enter their new PW. I bet you have already guessed what happens next.
By resetting JM every 90d all of their settings are reset to default values as well (and of course our users have not the slightes clue that they are supposed to change certain JM settings every time they change their PW - and we Technicians have not the slightes control over what kind of JM settings are defined on the devices once a device is out in the field).
Add another 20-40 people that start working in our company each month on top of that and we are somewhere at around 6'000 - 8'000 manual changes of Jabber Mobile settings each year. That is the ongoing maintenance nightmare i was talking about.
As much as we love JM but honestly - it's crazy that we are running this kind of setup in a business environment.
It is a pity that you can control most of the Jabber settings for Jabber Desktop but only a hand full of them for Jabber Mobile.
(Especially the default value "Set to away after 15min of inactivity" is a huge pain to us. Our users are basically required to play on the phone non-stop in order to stay "Available". Turning this setting completely off by default would dramatically improve our situaiton)
Having a way to centrally manage all those settings (Skipping the setup screen, never setting the status to away, no video, etc.) would make our lifes a lot easier.
AppConfig looks very promising in theory but like Charles already mentioned a year ago there is no useful documentation to be found on it. Does anyone know if any good documentation has become available since then?
Or is there any other way to manage (all of) the Jabber Mobile settings?
Best regards,
Dave
