conorofarrell Posted August 12, 2015 Report post Posted August 12, 2015 Hi I am trying to manage my IOS devices with Intune and I want to lockdown the likes of iMessage, Facetime etc. I have found the relevant OMA setting (allowChat) on the Apple developer site (https://developer.apple.com/library/ios/featuredarticles/iPhoneConfigurationProfileRef/Introduction/Introduction.html), but I am unsure of how to add this setting to the Configuration Item. I have tried using an OMA URI setting with the "allowChat" and "False" rule, but to no avail. Is there a longer string I need to use? Is this not possible on IOS (I suspect this is the answer, but hope not)? The deployment monitor just tells me that the device is non compliant. Is it possible to achieve what I'm trying to do or am I wasting my time? Thanks Con Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted August 12, 2015 Report post Posted August 12, 2015 AFAIK this won't work for iOS, yet, simply because there are no useable OMA-URIs available. Quote Share this post Link to post Share on other sites More sharing options...
conorofarrell Posted August 13, 2015 Report post Posted August 13, 2015 Thanks Peter, I feared that this was the case. Does anyone know if it possible to do this with the Apple Configurator (.mobileconfig) file? From what I've read, it should be possible, but I cannot get any joy here. Con Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted August 19, 2015 Report post Posted August 19, 2015 Yes, you should be able to use the the Apple Configurator to create a configuration for your devices. Quote Share this post Link to post Share on other sites More sharing options...
conorofarrell Posted August 31, 2015 Report post Posted August 31, 2015 Thanks Peter I was able to apply the setting from the XML file eventually. I think my issue was 1 of 2 things: either I did not have the phone in supervised mode correctly or it was something to do with the "deployment time" bug in SCCM 2012 R2 SP1. I suspect it was the latter because, I'm 99% sure I did have it in supervised mode correctly. Thanks again Con Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted August 31, 2015 Report post Posted August 31, 2015 The "deployment time" -bug is only applicable to operating system deployments, so my guess would be the first Also, if it has something to do with deployment times then it should be fairly easy to reproduce. Quote Share this post Link to post Share on other sites More sharing options...