I thought in the past you can almost always enroll the latest release of Apple devices even if you have not upgraded your AirWatch or Workspace ONE to a newer version. Am I correct?
If so, the upcoming ones must have something different that requires such compatibility patch to be installed first prior to enrollment.
Jason, I'd re-run the patches on your app servers ( DS/Console ) also run this query against your SQL to make sure it's the right version: SELECT * FROM database.version You should see the .17 release info if all went right there
I've updated to 9.6.0.7 with no issues. All I can think is one of your servers didn't really take to the update. Are you suing ACC's? They needed updates afterwards as well. The DS is the most likely suspect though.
Luke we only have a single server on prem environment. I have opened a case with Airwatch and they have requested the debug device logs, which I have sent over.
Device Wipe functionality may fail in environments with Advanced Remote Management enabled and the new hardware compatibility patch applied. and the fix notes were: Our product team has been engaged and is actively working to resolve the issue. The new hardware compatibility patch will be updated to include a fix for this issue and be released to resources portal for On-Premises customers. SaaS environments will be patched by our operations team. So they are not necessarily patched for all the posted patches be sure to check in the list of patches shown in the instructions after you download it
I just updated from 9.2.3_15 to 9.2.3_28 without any issues whatsoever. Everything ran smoothly, the services came up without problems and new iPhones (XS, XS max) can now be enrolled and seem to work correctly
Stefan - you said ' and new iPhones (XS, XS max) can no be enrolled.' Did you mean these devices can not be enrolled, or can now be enrolled? Please confirm if the new devices are working or not - many thanks!
I updated from 9.2.3.0 to 9.2.3.27 on our single server overnight and everything is working fine. Services automatically came back up and iPhone Xs and Xs Max both enrolled with no issues. Database Admin saw the following error when running the sql file but it ran successfully: Warning! The maximum key length is 900 bytes. The index 'UQ_Application_PkgIdLGIdVerHshDevTypId' has maximum length of 1228 bytes. For some combination of large values, the insert/update operation will fail. Create scheduled job AirWatch - ADP_Export ...cloudProfile.CloudProfileMetaData ...cloudProfile.CloudProfileTemplate ...DeviceSampleMask_MaskUpdate ...AppDeploymentConfiguration_DeleteDuplicateADPKeyForBoxer We did have to rerun the sql file as the console install did not recognize the updated version. Second attempt was successful.
