LukeDC
Expert
Expert
‎10-02-2018 08:06 AM

https://imgur.com/a/Vd4TgvJ
Reply
0 Kudos
schcneder
Contributor
Contributor
‎10-02-2018 08:50 AM

Hi, Luke.  I'm on 9.5.0.17.  I've applied the patch and the Oct. 1st OS seed script.  Still getting users reporting ' invalid profile'  when trying to enroll the XS phones.  Any recommendations? 
Reply
0 Kudos
LukeDC
Expert
Expert
‎10-02-2018 09:02 AM

I'm on 9.6, can't help much there. 9.6.0.7 works great. Did you update all the pieces it requires in the deployment instructions? ACC's, DS and console?
Reply
0 Kudos
schcneder
Contributor
Contributor
‎10-02-2018 09:11 AM

I'm about to just update to 9.6 since it seems stable enough.  My last DB update was 9.5.  Do I need to update the DB to 9.6 prior to the console upgrade?
Reply
0 Kudos
Stansfield
Enthusiast
Enthusiast
‎10-02-2018 09:27 AM

You always need to do a database update when you update (even the patches have database patches), the only question is whether it is just one (9.5>9.6 is one)
Reply
0 Kudos
LukeDC
Expert
Expert
‎10-02-2018 09:32 AM

I always run it regardless, just in case. The Db Installer will tell you the minimum need Db to complete the update with. Which should be 9.3. But I  would run it anyways. Make it a habit.
Reply
0 Kudos
jasonrothstein
Contributor
Contributor
‎10-02-2018 09:35 AM

Cynthia I have the same version and had the same problem after applying the patch.  I opened a case with support and they confirmed that from the app server and database side the patch seemed to have installed successfully, but they had me rerun the DB script as well as the front end installer and now the server enrolls new phones fine.  I had assumed mine was a freak occurrence where the patch appeared to install fine but obviously didn't, but it would seem now that there is an issue with it that requires that it be installed twice... Try running the patch installer again..
Reply
0 Kudos
schcneder
Contributor
Contributor
‎10-03-2018 08:17 AM

Update:  I upgraded my dusty 9.0.4.0 environment to 9.6.0.8 and ran the patch against the DB after the console upgrade.  Still couldn't enroll XS devices (invalid profile).  The problem was that I didn't run the patch on the app server as well.  Once I did that, XS devices are now enrolling smoothly.  Also noticed a tremendous improvement in console performance after the upgrade.  Much quicker and smoother.  Thanks for the tips!  I often find better luck here than with support.  :confused_face:
Reply
0 Kudos
ThomasCheng
Enthusiast
Enthusiast
‎10-11-2018 07:30 AM

Patch 9.7.0.9 is out...
Reply
0 Kudos
BlakeKosiba
Contributor
Contributor
‎10-12-2018 02:08 PM

can anyone tell me if i need to run the .sql script that comes with the patch package? I am going from 9.2.2.0 and running the 9.2.2.26 patch. Airwatch support told me i did not need to do anything with the database but i am seeing that the instructions included say to run the SQL script included. cannot get a straight answer from Airwatch about this.
Reply
0 Kudos
BrianAbbottBria
Contributor
Contributor
‎10-12-2018 04:32 PM

Blake, I haven't tried running it without running the SQL script but I think you need to run the script. Airwatch support must be confused. A lot of people have said they needed to run the script more than once to get the XS devices to enroll.
Reply
0 Kudos
FlorianHirschma
Contributor
Contributor
‎10-24-2018 07:06 AM

Are there any updates on this? Just tried to install the 9.2.3.29 hotfix and iis services aren't starting afterwards
Reply
0 Kudos
DmitriAltum
Contributor
Contributor
‎10-24-2018 11:20 AM

Brian, we had a similar issue for On-Prem. We ran the iOS12 patch for 9.2.2 then a week later updated to 9.6. iOS12 devices could still enroll no problem, but all of a sudden Xs & Xs Max models stopped being able to enroll. Re-applying the patch for v9.6 fixed it.
Reply
0 Kudos
jeremygould
Contributor
Contributor
‎10-31-2018 06:23 AM

We are also seeing the ' ABProxyErrorDomain error 3'  (referenced by David W above)  in AW Browser on XS devices only. Latest patch on 9.7. Is anyone else seeing this or know of a fix?
Reply
0 Kudos
lukaszwa
Contributor
Contributor
‎10-31-2018 06:28 AM

Tunnel requires separate patch as per this KB: https://support.workspaceone.com/articles/360009438934
Reply
0 Kudos
ArunasStankevic
Contributor
Contributor
‎11-09-2018 05:36 AM

Our customer as well facing ' ABProxyErrorDomain error 3'  on XS. SaaS Version: 18.10.0.3 (1810) Build Information: AIRW-AWCREL24-44. Will report if patch helps

Reply
0 Kudos
admin
Immortal
Immortal
‎11-13-2018 02:25 PM

Just a heads up. VMware has confirmed that the seed script for Apple Device Model and Family info published under the heading '  Apple Device Model Information - Latest update: Seed Script for iPhone XS and XS MAX for 9.1, 9.2, 9.3, 9.4, 9.5, and 9.6 '  does not include model and family info for iPhone XR.
I have run the script in our 9.5 On Prem and XR still showing up as iPhone and nothing else.

Reply
0 Kudos
DaveBennewitz
Contributor
Contributor
‎12-14-2018 02:54 AM

Hello Arunas S., We have the same issue (ABProxyErrorDomain error 3) on an activated XR and we are on version 18.10.0.5 (1810) on premise. We did install the tunnel patch (https://support.workspaceone.com/articles/360009438934) but didn't solve the issue. Have you solved the issue?


The app tunnel part does work for the iPhone XR by the way

Reply
0 Kudos
ArunasStankevic
Contributor
Contributor
‎12-17-2018 05:13 AM

Dave B., unfortunately, the person who was complaining went to maternity leave, but other Xs user confirmed that everything works as it should be.

A.
Reply
0 Kudos
CharlesDrury
Contributor
Contributor
‎12-20-2018 03:55 AM

As per Dave B post above the ABProxyErrorDomain we have is ONLY on XR models (we don't ahve an XS to test).

Support are now testing with a test user in our environment.

Fingers crossed it's sorted soon.
Reply
0 Kudos