Today we released Casper Suite 9.9, adding new features for iOS 9.3, improved OS X pre-stage deployment, and more. Check out the release notes in My Assets.
For customers running their JSS on Windows Server, we’ve also updated the Windows JSS installer to make your upgrade path even smoother.
Same issue as above. Students show up as offline. Hooked up my iPad to Configurator 2 to read the console logs and it appears as though it doesn't like unsupervised devices using Classroom. Also check that the student's iPad has the EDU profile installed on it. The students I assigned to my test class didn't get that profile pushed to them for some reason or another.
A Profile Manager instance worked like gangbusters with this so it must be something in JAMF's implementation that we don't have correctly setup.
Ours are all supervised and have the EDU profile, but still no dice. The edu profile didn't go on until I manually added the students to the classes. The smart mobile device group (via LDAP) didn't send them out.
It's also worth noting that I discovered adding ios 9.3 features to a profile that went out to 9.2 devices made the old devices confused and they lost all restrictions. Not the smoothest transition so far (especially with apple pushing out 9.3, then pulling it back causing the downloaded updates to fail, then pushing out a different 9.3, then a 9.3.1). Ugh.
Mystery solved. I forgot the Classroom app utilizes bluetooth. So you need to be within 30ft(bt radio distance) of the students iPad for the app to send commands and not show students in a perpetual offline state.
JAMF's documentation doesn't mention this but it does link to Apple's documentation that does mention bluetooth is required.
I don't think that was the issue, since my iPad was literally on top of the one I was testing... But it's possible Bluetooth was turned off, as we've had better AirPlay experiences when it's disabled. It sure would be nice, especially in the light of this information, if apple would allow us to prevent airplane mode and toggling wifi and Bluetooth. That's our kids' favorite new trick to avoid being focused. It's also caused several to get stuck in focus when the timing is just wrong (profile hits device, kid turns off wifi, profile activates and focuses). Had to build a "ipad defibrillator" with the Lightning-to-USB-camera adapter -> USB hub -> usb Ethernet adapter setup suggested elsewhere on these boards to wake them back up!
I won't say it's a silver bullet fix, but I did test it out by turning off bluetooth on an iPad I enrolled on a whim and assigned to my test class. Turning off bluetooth made the student/ipad show offline. Turning it back on made it come alive in the app. Again your mileage will vary.
I see our more enthusiastic teachers telling kids to turn bluetooth off to save battery life. It would be nice to restrict that although I suspect I would get numerous calls every other day asking why kids can't turn it off anymore. Airplane mode hasn't been a big issue for us. Kids used it last year to load cached game sites they loaded at home away from our soul crushing web filter.
Kids used it last year to load cached game sites they loaded at home away from our soul crushing web filter.
Clever! I wish there was a way to create a tripwire type of app or profile that sat in the background until it couldn't phone home for a set period of time. Then it'd activate a "bring this device to home base" focus screen. But alas, Apple doesn't like making kernel-level stuff available to developers...
Yes, but with Casper Focus, a teacher would only tell students to go to a website, to make sure they're online, and could them focus them. If we would have a chance to prohibit disabling of Bluetooth, that would be perfect, but we can't for the moment. Of course, the teacher could always reach out to the student, asking them why their iPad is offline...We'll see, have to test it out :)
Any update on the issue GSSRyan mentioned about sending out updated profiles with features enabled for 9.3 and it removing all restrictions on older versions. We want to start testing the 9.3 features but still have several devices on older iOS versions and obviously do not want to impact the restrictions on those devices but we can't guarantee every iPad in our groups will have 9.3 at the time we update the profile. I want to be able to start rolling out the changes but not worry if we miss a few iPads in a group they will be running unrestricted.
I wonder if one or several of these topics would actually be best moved to a new thread...
So it appeared to be the Bluetooth issue in terms of why the students who had the EDU profile pushed out were showing as "offline." Once it was enabled on both devices, we were live!
It's still the case that our classes which were already assigned (Mobile Device Smart Groups via LDAP) aren't sending out the profiles until the students are manually added. They all show up on the teacher's Classroom app as "Offline", but don't receive the EDU profile until they're added as individual students.
@mkempster : The way I dealt with this was by cloning the 9.2-compatible profile, then adding the 9.3 features to the new cloned profile. The original profile is scoped to a Smart Group of devices for which iOS Version "9.3" and the new one is scoped to devices for which iOS Version "9.3". For safety's sake, you might want to create another Smart Group that checks for one of the apps you've disallowed in the profiles. That way you can see if anyone's roaming free.
The biggest headache I've encountered so far is with devices which received the pulled version of 9.3 when I sent out the auto-update command via JSS but didn't install before they pulled verification and got stuck in a kind of limbo. I'm having to manually go into Settings->Storage and delete the downloaded update, then it'll check again for 9.3.1 and update. It's especially weird that the update I'm deleting is over 1GB, but the replacement is only like 24MB. Not sure what to make of that.
All said, the Classroom features are really cool (especially the screen viewing), but I'd strongly suggest waiting a bit to see if Apple pushes out any more dot updates if you have any significant number of iPads to manage.
Another "fix": I created an "All Students" class and manually assigned everyone to it. Then, when the EDU profile went out, it respected the Mobile Device Smart Groups for the various classes. At least, that's what appears to have happened. It looks like JSS just needs to implement an initial check for all devices' class membership when the feature is enabled in the JSS settings.
Has anyone noticed Spotlight acting up since upgrading to 9.9? Especially when waking from sleep. My MBP Retina's fans have been going non-stop and it's the only change I made on my system. My co-worker is seeing it too.
Now seeing this in my logs on 10.11.4:
kernel: process Spotlight caught causing excessive wakeups. Observed wakeups rate (per sec): 256; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 480202
It's also worth noting that I discovered adding ios 9.3 features to a profile that went out to 9.2 devices made the old devices confused and they lost all restrictions.
I'm testing specifically for this with a test cloud instance of JSS 9.9. I enrolled an iPad with 9.2.1 and installed the normal student restrictions. I then deployed a new profile with a test restriction of disallowing Notifications and Chrome. I still see the same 20 restrictions listed in General -> Device Management, and it seems like the iPad is acting normally. It doesn't list the 9.3 specific restrictions, so it is ignoring them.
Can you elaborate on how your devices became 'confused'?