ChrisHuhnChrisH
Contributor
Contributor
‎09-24-2018 05:52 AM

I understand that full process, I was hoping for less intrusion during 'little patches' - oh well. Agreed on speed of little patches.
We moved to improve the User experience during new Device and iOS releases... MI was always behind, one time by four months after iOS 8 broke the secure browser. The main comments after our AirWatch migration were 'smoothest migration ever'. 2,000 devices over a month as we treaded lightly and polished our Docs, then 9,000 devices in 3 weeks. 11,000 devices with 120 complaints. AWESOME!
Reply
0 Kudos
ThomasCheng
Enthusiast
Enthusiast
‎09-24-2018 06:10 AM

Wow, you run a big shop. Curious to know how many sites/servers you have in your environment. I have 2 in active/passive mode and I plan on moving them to the same subnet so we can have active/active set up.
Reply
0 Kudos
ThomasCheng
Enthusiast
Enthusiast
‎09-24-2018 06:11 AM

And I'm a bit surprised by your comment on MI as they are second to AirWatch in the marketplace.
Reply
0 Kudos
ChrisHuhnChrisH
Contributor
Contributor
‎09-24-2018 06:25 AM

Lets take this conversation off of here. Didn't intend to deviate from purpose of thread. See your WordPress for new Invite.
Reply
0 Kudos
JamieAndersonJa
Enthusiast
Enthusiast
‎09-24-2018 06:28 AM

has anyone on 9.2.3.x successfully applied the .27 or .28 patch yet? if so, what patch version were you already on? our Dev environment is still dead in the water. Majotiry of the application services are failing with this error.... Error AirWatch.Security.CodeSigning  Unable to retrieve publisher or publisher not trusted. Assembly: WanderingWiFi.AirWatch.BusinessImpl, Version=9.2.3.28, Culture=neutral, PublicKeyToken=null
Reply
0 Kudos
jasonrothstein
Contributor
Contributor
‎09-24-2018 09:13 AM

I was on 9.5.0 and applied the compatibility patch and seed scripts, so now 9.5.0.17, but IOS 12 devices still fail enrollment at the Workspace One profile install with ' invalid profile' .  Devices already enrolled upgraded to 12 work fine.
Reply
0 Kudos
ThomasCheng
Enthusiast
Enthusiast
‎09-24-2018 09:18 AM

Jason, are you getting ' invalid profile'  when enrolling the newly announced devices only? Or that error applies to devices such as iPhone 8 with iOS 12 installed?
Reply
0 Kudos
jasonrothstein
Contributor
Contributor
‎09-24-2018 09:28 AM

I have not yet had a scenario where a user with an older iphone has upgraded to 12 yet wasn't already enrolled. All the incidents so far are new Iphones pre-loaded with 12 failing to enroll.  As mentioned, older Iphones already enrolled continue to work after being upgraded to 12.
Reply
0 Kudos
jasonrothstein
Contributor
Contributor
‎09-24-2018 09:35 AM

Seeing this in the event log.  Guess the patch didn't fix the UUID issue.
Identity:notauth::
Module:WanderingWiFi.AirWatch.DeviceServices.Enrollment.Handlers.DeviceMdmConfigurationHandler.ProcessRequest
Message: Could not identify the device uid from the text.
Reply
0 Kudos
Stansfield
Enthusiast
Enthusiast
‎09-24-2018 09:40 AM

Jason to be clear were the device that were failing to enroll the iPhone Xs, Xs max, or iPhone Xr?
Reply
0 Kudos
jasonrothstein
Contributor
Contributor
‎09-24-2018 09:45 AM

Iphone XS
Reply
0 Kudos
SHAUNCHAN
Contributor
Contributor
‎09-24-2018 09:53 AM

I'm getting for both XS and XR.

Reply
0 Kudos
ThomasCheng
Enthusiast
Enthusiast
‎09-24-2018 10:07 AM

Shaun, what's your console version?
Reply
0 Kudos
SHAUNCHAN
Contributor
Contributor
‎09-24-2018 10:11 AM

Thomas


old... I'm going to engage my rep to see what options i have to upgrade. (9.0.3.0)


 


so far i've tried ios 12 iphon 6 s +, no problem at all. I can try my 7+ when i get home tonight if  required.


Reply
0 Kudos
ThomasCheng
Enthusiast
Enthusiast
‎09-24-2018 10:14 AM

I've heard others are running even older version like 8.3.
In your case, I suggest moving to the latest version (i.e. 9.6) with the latest patch. Until then, I wouldn't count on enrolling any newly announced iPhone.
Reply
0 Kudos
SHAUNCHAN
Contributor
Contributor
‎09-24-2018 10:23 AM

yeh sounds like that's my only option.
Reply
0 Kudos
jasonrothstein
Contributor
Contributor
‎09-24-2018 10:28 AM

So does Airwatch have a statement regarding this?  Need to know what to tell users on ETA for getting their devices enrolled, and depending on said ETA, warning them not to buy a new phone until given the all clear.
Reply
0 Kudos
MICHAELNICKELS
Contributor
Contributor
‎09-24-2018 10:34 AM

Has anyone successfully installed the patch? We are on 9.4.0.10 and plan on patching our QA later this week, but it sounds like the patch may not work?
Reply
0 Kudos
ThomasCheng
Enthusiast
Enthusiast
‎09-24-2018 10:37 AM

We hope to secure the XS soon for testing as we already upgraded our QA to 9.6 with the latest patch.
Reply
0 Kudos
BrianAbbottBria
Contributor
Contributor
‎09-24-2018 10:56 AM

Can you keep us posted J a.? I am on 9.2.3.0 and I'm worried to install the patch since you said your dev server is dead in the water.
Reply
0 Kudos