The logs give you some interesting information you can look at. So let’s get started… xCode Device Logging Some you might have heard of and others maybe not.
Enabling Analytics/Full Diagnostics Logging. So my tool box for working through these issues are mostly straight forward. If necessary, this command will let you revoke a token for a user:Get-AzureADUser -SearchString towlesj | Revoke-AzureADUserAllRefreshToken These tokens are the lifeblood of Office 365 authentication and without then you are screwed. #2 it works on a two token system: (1) After authentication you are granted an access token that is good for a hour and (2) a refresh token is created which is good for 14 days, but with regular use can last up to 90 days. That doesn’t count access policies that a Identity Manager product might have created. What this means to you is #1 conditional access for non-Intune MDMs does not work anymore since it’s only supported for legacy authentication. Office Apps on iOS now use Modern Authentication. They are part of a group or “family” that work together and can share stuff with each other. The best example is the AirWatch Agent and Boxer or Content Locker. All iOS apps now use these things called App Groups and Keychain sharing to share credentials or key data that helps them work together. It’s one of the major tenets of their security model on iOS, but it ALSO means that it is a major pain in the ass trying to diagnose issues as a support engineer. App Data is containerized inside of the application. So to talk about Office Apps, theres a few things you should know: First we’ll talk about the basics of an iOS 3rd party application and what matters to you, second we’ll talk about your tools, and finally we’ll bring them all together. We will break it down into a few useful sections. I decided to focus this blog as your “Oh Shit Button” when something bad goes down with your office apps and what you can do. I hate to break it to the fine people at AirWatch, but NO WorkspaceONE cannot cure any of these things despite what some think. Much much much more….I would need a 12 chapter book to cover all of the challenges we REALLY have. Inability to control/regulate/or lock down the majority of devices. #MICROSOFT OFFICE FOR IPAD 2017 UPGRADE#
Fragmented versioning (which is why I love when people say oh Android O is the greatest thing since the birth of Steve Jobs and blah blah considering most devices that we are worried about won’t be able to upgrade to Android O anyways).Call me when your desktop application is impacted by Verizon Wireless switching to IPv6.
Ridiculous amounts of complexity from client to server.Pretty much no centralized logging capabilities (don’t use the SDK excuse because that only saves you on internal apps and your MDM vendor apps).Many of these challenges that we face are RAMPANT in iOS apps that make our users hate us at times and make life so extremely difficult for us. Do you remember the peons? I remember the peons! They think we’re these people! I mean c’mon!Īnyways, moving on back in the world of reality…mobility is the one area of IT that you cannot go to school for and you have the biggest challenges if you are truly an engineer and not some offshore help desk activating BlackBerrys (yes I went there). People think that mobile administrators are basically the peons from Warcraft. This has become so much more complicated in this day and age. Let’s be honest…Microsoft owns you and always will…just when you think you are OUT…they pull YOU back IN!
0 kommentar(er)
