vortiaccess.blogg.se

1. #USE APPLE CONFIGURATOR UPDATE#
2. #USE APPLE CONFIGURATOR PRO#
3. #USE APPLE CONFIGURATOR DOWNLOAD#
4. #USE APPLE CONFIGURATOR MAC#

Steps for new enrollments after February 10, 2021: This will ensure for a short period of time enrollment proceeds as necessary.

NOTE: In Microsoft Edge or Chrome, this can be done by clicking the padlock next to the URL, clicking "Certificate", selecting Baltimore CyberTrust Root certificate and then dragging the large icon to the Desktop. You can read more about getting the Baltimore Cybertrust root certificate here: Configure Trusted Roots and Disallowed Certificates | Microsoft Docs.

#USE APPLE CONFIGURATOR DOWNLOAD#

Download the Baltimore CyberTrust Root certificate.Here are the steps you’ll take on a macOS device per the instructions here: iOS/iPadOS device enrollment - Apple Configurator-Setup Assistant - Microsoft Intune | Microsoft Doc.: Steps for new enrollments between January 14, 2021- February 10, 2021:įor enrollment in the next few weeks until the new certificates described in MC225591 and also described in this blog post are fully deployed across the entire service, you’ll want to add the Baltimore CyberTrust Root Certificate back to the list of certificates in your profile to ensure that enrollment can complete through setup assistant. The error in device logs either indicates there’s no service response or enrollment can’t succeed so no errors are logged. You have an enrollment profile that has worked historically to enroll new devices, but now those new devices (userless or user-based) fail enrollment.You use Apple configurator – setup assistant – for enrollment.

#USE APPLE CONFIGURATOR UPDATE#

However, if you plan to enroll new devices in the next few weeks there’s one set of steps post incident to enroll new devices, and then when the certificate update is completed, a quick profile update to ensure new enrollments are successful. Existing devices remain enrolled as they have already established trust through the Apple configurator setup assistant workflow. Unfortunately, as part of this incident, we have confirmed that there is a certificate mismatch between Apple Configurator profiles and the Intune certificate issuing service for iOS/iPadOS enrollment through this setup experience. We recently posted IT234239 on the Service Health Dashboard. Only setup assistant workflow is impacted – all other iOS/iPad enrollment workflows are not affected. I see nothing on the MacBook, no boot chime, no recovery opens up, can't see disks, nothing.Blog Note – This only impacts the iOS/iPadOS device enrollment using Apple Configurator – Setup Assistant – as documented here: iOS/iPadOS device enrollment - Apple Configurator-Setup Assistant - Microsoft Intune | Microsoft Doc. Is there anything else I could try or does anyone know the reason for the Padlock on Apple Configurator 2 and what it means if the laptop keeps going back to it after every attempt at restore? I end up with a Padlock on the Apple Configurator 2 after every attempt at revive or restore and I don't know what that means since there's not much detail about that online. I thought it was a just a battery issue since I don't remember spilling anything on it or forcing anything on the laptop and it was working fine the night before, all i see is a black screen and I'm assuming the macbook still has life since I can click the touchpad and also since I can get the laptop to DFU mode in the Apple Configurator 2 but with no success of being able to boot it up with any of the options from Apple Configurator. The macbook suddenly died yesterday when I tried to turn it on.

#USE APPLE CONFIGURATOR MAC#

Host System - Mac mini late 2014 (using USB C to USB C with a C=>A adapter) (10.5.6) , 11.x (Big Sur, can't specify the exact version since I don't remember what the version was)

#USE APPLE CONFIGURATOR PRO#

Target System - Macbook Pro 13 inch Late 2019, Touchbar version.