Autonomous Single App Mode (ASAM) and TestNAV App

Supervised with Prestage, running testnav 1.3.2 and JSS is at 9.65.

Did you install the app via VPP? or push out?

We didn't even risk and just used Focus... in training last week however we appeared to be getting a 90% success rate with no rhyme or reason...

We use ASAM both with TestNav and the AIRSecure app (Ohio) and both work just fine. We have maybe one or two out of 200-300 kids that need to be focused with Casper Focus.

We're 1:1 so I just added the bundle id to the restrictions section of the configuration profile and redistributed the profile to everyone. It of course didn't work right off the bat so we had to use Casper Focus during the first couple days of PARCC. What ended up being the ah-ha moment for me was I have the app store restricted on all grades so once I allowed access to it ASAM worked right away. I haven't tried it with the app store restricted(off) since upgrading to 9.65, but I'm not going to try as I don't want to break something that's working when we're in the middle of testing.

I think the app store is the issue. I thought that was a bug pre-9.65 but it looks like it's not.

@galionschools You added the app store back on to your iPad's so ASAM would work? What are you doing after testing? Will you take the app store back off the iPad's and go delete all the games that were installed or stick with the open app store model? Trying to figure out if that is worth it here or not. Thanks for the advice.

Today we just went with having the kids lock themselves in through guided access over locking them in with Casper so they could get out of guided access and quit/reload the app easier if issues came up. It was 7th and 8th graders so they figured it out pretty quick.

We have left the app store open for our students. We have had minimal loading up of games on the devices, especially after they realized we knew what was installed and called a few of them out for it. The word quickly passes amongst them and the games are deleted.

We've been turning if off and on depending on testing schedules so it's not on throughout the entirety of the spring. To be honest though our acceptable use policy states they can't install apps or games. Kids will be kids though and some just skim the document but I rarely accept any excuses and the kids that have dealt with me are aware they'll never walk out of my office unscathed.

The restricted app store model has been a thorn in my side though and I'm looking into opening it up sometime down the road.

We have been working fine but we have the app store on for the moment. We are running 9.62. I want to turn off the app store after we upgrade. Why would having the app store restricted cause ASAM not to work? Do you think it has to do with ASAM using the bundle identifier when it locks the app?

That's the thing I'm trying to wrap around my head as I could get ASAM to work with a restricted app store policy when I enrolled it with Meraki MDM.

I have finally spent a day testing ASAM with AIRSecureTest. Grades 9-12 so the testing window doesn't open until 4/27.

I am pleasantly surprised to learn that Autonomous means exactly that - NO communication with JSS required to test!! This is a HUGE, HUGE benefit over Casper Focus or Single App Mode profiles, as the latter requires a WiFi communication in order to break out of the test. With ASAM, no bricked devices.

So far in my testing:

It does not matter if the app is Managed and installed by the JSS or Unmanaged and installed through the App Store. The Bundle ID is still the same.

iPads which go to sleep and are woken up are automatically broken out of the test with a message. If there is no passcode then you can even press the Home button to wake it up - Single App Mode has already been quit. If there is a passcode you have to use the Power Button to get the screen to wake up and enter the passcode. No restart required, which is different than what another poster on this thread mentioned (@brownbe).

I am not having any trouble on my test iPads with ASAM not working when the App Store is Disabled. I'm running JSS 9.65. I removed all profiles at least once on these iPads before enabling ASAM, perhaps that is part of the issue? Can anyone elaborate on how quickly ASAM failed? Immediately?

Thanks,

chris

I found some iPads that were not going into ASAM when initiating the practice test, "this is not a secure test environment". I removed ALL configuration profiles with Restrictions, and reinstalled them all (I love Casper's Exclusion scope) and now all is well. I assume I had a mix of old and new profiles on the iPad and they weren't meshing well.

chris

Latest update from my experiences:

Hi, on Friday April 3rd, I upgraded my JSS from 9.62 to 9.7. I also made some changes to a Restrictions profile that I use on my lab iPads currently being used for PARCC testing.

I wanted to prevent users from installing anything and to manage all apps through Casper. It seems that the unchecking of “Allow installing apps” prevented the devices that had the TestNav app pushed out to them (managed) prevented them from going into “Autonomous Single App Mode” whereas the devices that had the TestNav app manually installed continued to work. I would have thought, if anything, the exact opposite and that managed apps would continue to work. Either way many of the devices couldn’t lock down TestNav into single app mode and were holding up testing, so I removed that restriction and pushed that profile back out to all devices using the Restrictions profile.

I am curious as to why this restriction caused this behavior. Is this a bug or am I doing something wrong. Does it matter if TestNav was pushed out via Casper or manually installed through the app store? I'd like to restrict anyone from installing apps but I dont want to break ASAM again.

Thanks

Mark

@stoneacheck ,

I was curious how you made a policy to add those 2 lines to the deployment.properties file for Java. From the screenshot, it looks like you are using a policy to add the deployment.properties file to the machines which would overwrite any existing file. I could get the file off of my machine, modify it and push it out to my PARCC computers but there is some parts of the file that are specific to my machine such as deployment.modified.timestamp & deployment.version. Not sure how important those are if they dont match up with what is actually installed.

Thanks

Mark

@msnowdon, That is very interesting that the TestNav software could not implement ASAM if it was installed as Managed and the App Store was Disabled, but that it works ok if it was installed as Unmanaged.

Do you have any profiles installed that restrict these?
- Allow managed apps to store data in iCloud
- Allow documents from managed apps in unmanaged apps
- Allow documents from unmanaged apps in managed apps

chris

@cdenesha

I just have one restrictions profile and it doesn't restrict the items you mentioned although I was thinking about restricting all iCloud related settings.

Thanks

Mark

I just restricted everything possible in a Configuration profile for Restrictions, and was still able to use the SBAC AIRSecureTest with ASAM. It must be something in the way Pearson wrote TestNav. I suggest creating a ticket with them, perhaps they can get it fixed for next year.

chris

Ha! Chris you are funny. Most of the support techs at Pearson don't even know what ASAM is, let alone that you have to test in the TestNav app on an iPad and not through Safari (level two techs included).

<smile>
All you have to do is get the message to the right level or person! Perhaps use your state educational testing representative - we have a good one here and I was able to connect directly with the liaison for AIR.

chris

Reported ASAM wasn't working properly months ago to them. Response: "What's that?" Sent the docs showing it was the recommended way to test since the start of state testing... silence.