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 h...
See more...
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..
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.
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 g...
See more...
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.
Seeing this in the event log. Guess the patch didn't fix the UUID issue. Identity:notauth:: Module:WanderingWiFi.AirWatch.DeviceServices.Enrollment.Handlers.DeviceMdmConfigurationHandler.Proces...
See more...
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.
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 m...
See more...
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.
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' . Devic...
See more...
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.
