6 Replies Latest reply: Sep 22, 2015 11:57 AM by chcn
Max Beckman-Harned Level 4 Level 4 (1,200 points)

I got an alert from AT&T telling me that I was nearing my data usage limit, and checking iOS 7's new "Cellular Usage" section I found that the "Corporate Accounts" system service used over 100MB of cellular data. This is a seperate item from "Exchange Accounts", and I'm not sure what it is? Is this related to my (corporate) configuration profiles? Can anyone shed light on this?

  • se20-mba Level 1 Level 1 (0 points)

    had the same issue, in our case it was my MDM solution provider centrify.com and not my corporate email.


    i had it much worse, 1.2gb while the user was roaming, so hefty bill


    if corporate account bandwidth usage is high in my case it meant 2 things


    1) MDM solution did not work properly

    2) battery life was really really bad, 2 or 3 hours max on a full charge


    removing MDM solutin and reapplying seems to have fixed the issue


    hope this helps and if there are any other corporate acounts usage cases i love to hear about them

  • rik73sta Level 1 Level 1 (0 points)

    We too are having this issue. In my case it was a matter of 1GB of data within a 24 hour period, which blew my monthly data limit. Interestingly, out of a fleet of 170 iOS devices enrolled in Airwatch, it's only happened to a single device (so far).


    The question I'd like to know is, who's to blame? Apple or our MDM provider? For starters Apple could use a less ambiguous name for "corporate data", such as "MDM Data". AND if it IS related to MDM profiles in any way, why is it not recorded under data usage for the MDM app itself? i.e.Under "Use cellular data for:" the Airwatch app had only used 5 MB, however under system services, "corporate usage" had used 1.3GB

  • Jieinseattle Level 1 Level 1 (0 points)

    I had the same alert sent to me by AT&T. I enrolled my iPhone 5 to Windows Intune (well, not famous MDM solution by a company called Microsoft, whatever) earlier last week, then I "retired" it through Intune on Thursday or Friday. Somehow this retirement was not successful, the last date Intune could even find my iphone was on Tuesday. Anyway, under corporate accounts, it showed 1.0GB data usage on Sunday (two days before). Now it's 1.7GB. I just removed the profile installed by Windows Intune company portal to see if it can fix the problem. I guess I have to pay additional 20 dollars at least to ATT.


    So timeline:


    10/22 added iPhone to MDM. The device somehow cannot be contacted by MDM after this date

    10/24 or 25 tried to retire iPhone from MDM, not successful.

    10/27 Got the message from AT&T. Changed 2GB plan to 3GB, found the 'Corporate Accounts' has 1.0GB usage.

    10/29 'Corporate Accounts' now shows 1.7GB. In AT&T usage table it shows I used 700MB+ in two days, match the change to corporate accounts. Removed corporate profile from iPhone.


    Here's what's in my att data usage log:


    10/29/2013 07:52PM


    Internet/mobile web43555.0 KBs0.00
    10/29/2013 07:46PM


    Internet/mobile web19925.0 KBs0.00
    10/29/2013 07:04PM


    Internet/mobile web58504.0 KBs0.00
    10/29/2013 06:43PM


    Internet/mobile web27211.0 KBs0.00
    10/29/2013 06:17PM


    Internet/mobile web38859.0 KBs0.00
    10/29/2013 05:52PM


    Internet/mobile web27703.0 KBs0.00
    10/29/2013 05:34PM


    Internet/mobile web27133.0 KBs0.00
    10/29/2013 05:17PM


    Internet/mobile web22915.0 KBs0.00
    10/29/2013 04:52PM


    Internet/mobile web26199.0 KBs0.00
    10/29/2013 04:03PM


    Internet/mobile web29429.0 KBs0.00
    10/29/2013 03:44PM


    Internet/mobile web36579.0 KBs0.00




    Terrible. Before 10/22, my data usage was just 10~20MB per day. Now it's 200MB~300MB per day. I don't know if this is MDM's problem or Apple's problem, but to me it feels like a bug in Apple's MDM API.

  • Jieinseattle Level 1 Level 1 (0 points)

    The Airwatch app (or in my case, Intune portal) only install the profile and set the device to be managed by the MDM solution. It's the agent on iOS itself kept trying to talk to somewhere and generated so much traffic. And that, is implemented by Apple. 


    My theory: during the MDM enrollment process, there's a chance to break. iOS 7 MDM agent does not have the correct logic to handle the exception (report error then stop trying) so it will always keep trying, nonstop. Apple needs to fix it -- but can they reimburse my loss?


    The worst thing is, there's no way to stop it from using cellar data if you don't have WIFI coverage. I analyzed the data usage pattern - when I was at home, the data traffic was not that bad. If I was in my office or outside (see above data usage table) where doesn't have WIFI or very poor WIFI reception, then it became a huge pain.

  • Max Beckman-Harned Level 4 Level 4 (1,200 points)

    I've spent the past couple of months tracking this down with my internal tech support group. "Corporate Accounts" is definitely Mobile Device Management a.k.a corporate configuration profiles; and I thought it might be useful to detail a couple of the tools we found useful; in case it helps you as well:


    1. the iPhone Configuration Utility (Mac, Windows) will show you the phone's console—mdmd (the mobile device management daemon, I assume) was spewing out a huge number of errors to the console and it was pretty clear what was going on from there.
    2. I also used Fiddler on Windows, a free HTTP(S) proxy tool, to capture all the HTTP and HTTPS traffic coming from my phone; which showed the full request and response bodies of the MDM traffic.
  • chcn Level 1 Level 1 (50 points)

    I've had this issue happen twice, both on an iPhone 6 under iOS 8, with Blackberry BES MDM software.

    The first time we fixed it by deactivating my device, uninstalling the device management profile, and then setting things up again.

    The second time it happened the IT people just rebooted the BES server and that stopped the problem. Unfortunately the participation of IT is required in either case, so it's not something and end-user can fix on their own.

    I find it interesting that rebooting the BES server worked. (That seems to work for a number of problems, not just thing one.)