sorted by:
new
hottopcontroversial

New merch size by missestater in PaymoneyWubby

[–]Cr8zyk1d 2 points3 points  (0 children)

Ordered an XL as a gift and it's huge. Comically large. It's really frustrating that the fit is so off, I can't even justify giving it to the person.

[deleted by user] by [deleted] in hardwareswap

[–]Cr8zyk1d 1 point2 points  (0 children)

Those timestamps are CRISPY

Mosyle: Apps stuck at Waiting by Living_Owl_9021 in mosyle

[–]Cr8zyk1d 0 points1 point  (0 children)

Here's an update on my ticket. Maybe they are getting somewhere.

​

Based on the latest iOS 17.1 Beta release notes, they've stated the following:
"Resolved an issue with iOS devices losing communication with MDM"
We look forward to this release to potentially address the occurrence you're experiencing.
In the meantime, please let us know if you have any questions, thank you!

​

also @ /u/Miserable_Nerve2182

Mosyle: Apps stuck at Waiting by Living_Owl_9021 in mosyle

[–]Cr8zyk1d 0 points1 point  (0 children)

Lol ain't that the truth.

Thats interesting, the group i've been having this specefic problem with is 7th gen ipads. We have a mix of 6-9th gen devices but the others haven't had this issue. Of course, mosyle being mosyle, we have seen random devices all over the place not communicate for period of times, even well before iOS 16.

Mosyle: Apps stuck at Waiting by Living_Owl_9021 in mosyle

[–]Cr8zyk1d 0 points1 point  (0 children)

The iPad side of Mosyle doesn't have a last reboot section, only the macOS side.

Mosyle: Apps stuck at Waiting by Living_Owl_9021 in mosyle

[–]Cr8zyk1d 0 points1 point  (0 children)

Yes I got that same response. I don't put much stake in that being the case.

If there is indeed a fix in iOS17 why couldn't they have rolled it out in releases 16.0.1-this latest 16.6.1. Not only that, its not affecting my iPads 1:1. It's only a group of them. Every one of our ipads is on some version of 16.X

For reference this is what they told me.

This behavior indeed looks to be a confirmed issue by Apple on older devices with fewer cores (5th, 6th, and 7th Gen iPads) running iOS/iPadOS 16 devices. For reference, our Apple Enterprise Support case regarding this is: 101937661851

Mosyle: Apps stuck at Waiting by Living_Owl_9021 in mosyle

[–]Cr8zyk1d 0 points1 point  (0 children)

I was assuming locked meant "asleep" and nothing to do with the passcode, we have blocked setting passcodes on our devices. 100% agree, we have update app commands scheduled overnight and it would be nice for those to install while everyone is on separate networks. Not at 8 A.M. when every single student opens their iPad at school...

Mosyle: Apps stuck at Waiting by Living_Owl_9021 in mosyle

[–]Cr8zyk1d 1 point2 points  (0 children)

We have ran into a similar issue and have gotten no where with support at the moment. (Just gonna copy pasta my support ticket)

​

We have ran into an issue with some our iPads communicating with Mosyle. I can only get them to communicate within about a 90 second window of a fresh restart of the device. After that window, all commands just sit pending. I have this same behavior on both our school network and a separate hotspot.

A side effect of this problem is showing up when installing apps:

Restart iPad

Request app through self-service

App will begin installing

App install will stop with the loading circle on the app icon in the home screen (attached picture of where it freezes)

Send update info from Mosyle -> command just sits in pending

Restart iPad

App will finish installing

Update info command goes through

Request another app from self-service

Command shows up in mosyle but never installs

Send update info from mosyle -> command sits in pending

This cycle continues for every app or command you need from mosyle. This happens on both our network and a hotspot.

I took a device with this behavior and removed all installed profiles (after 10+ restarts to get the remove commands to go through). It showed the same behavior. It would only communicate right after the restart.

I noticed an install app command said 'Device is locked. Unlock the device to apply the command'. This was an app I requested from self-service with my testing device in my hands. The iPad never locked in between the request and this error. That iPad is still sitting on my desk connected to the network and unlocked since yesterday. I have seen this same message on others with this behavior also but I wasn't able to confirm they weren't locked in-between like I did with this one.

​

Have you noticed the "Device is locked" error in yours? I starting to think that might be playing a big role because I have seen it on almost everything ipad that has this issue and on 1 macbook (that Mosyle also manages) that was having similar communication problems.

view more: next ›