Jump to content

FutuJaniAdmin

Members
  • Posts

    3
  • Joined

  • Last visited

Areas of Interest

  • Areas of Interest
    Horizon 8
    Horizon Cloud
    Workspace ONE
    App Volumes
    Dynamic Environment Manager
    Digital Employee Experience (DEX)
    Security

FutuJaniAdmin's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • One Month Later
  • Week One Done

Recent Badges

  1. Actually just I was writing this and after doing some troubleshooting steps now in the latest attempt it went through for the first time without issue. (Also having the await for configuration "on" for on the deployment profile"). Still need to investigate what was the root cause and has this somewhat fixed the issue. But some relevant troubleshoothing steps taken: Removed not all, but most all the most recent changes to profiles that were recently changed and targeting my test user and devices. Deleted the duplicate placeholder device profile in UEM which was generated after the innitial failed enrollment attempt which hanged. Re-uploaded the Enrollment token from ABM (the old token was not expired yet, but did this also just in case. most likely not relevant in this case since iOS enrollment did not have any issues.) Re-synched all devices and re-fetched all devices from ABM to UEM (did not delete any data on UEM side with the exception of the device profiles that never managed to perform the enrollment). I noticed that for some reason our default MacOS enrollment profile was seemingly missing some information which I am sure was there before. it is as if the autofill field was reset to disabled and as such the username and display name fields were blank. Also the Create a new admin account field was also set to no which is definitely not how it used to be. Fixed these information and updated the default deployment profile. Now, I am not sure if any of this helped, or which one, but I will continue the investigation. AI also have my own open ticket in support with ID 00866612
  2. We actually have the same issue in our organisation now and I am in a way glad to see that I am not the only one having this issue. This only seems to affect MacOS devices since iOS and windows for example are unaffected. As other already mentioned, this is quite a problem since MacOS devices cannot be compliant out of the box. We have also tried similar troubleshooting steps ourselves but no success there yet. Next scheduled update in our SaaS tenant is currently scheduled for november 12 which is quite long way off still.
×
×
  • Create New...