An Error Occurred While Obtaining Automatic Configuration Settings | Fast Fix

You’ll see this message on the Remote Management screen during setup when your Mac tries to pull an automated enrollment profile. When that pull fails, setup stops and asks you to try again. It can feel random, but the causes tend to land in a few buckets: blocked network access, time and DNS trouble, proxy filtering, or an enrollment assignment that isn’t lining up with the Mac you’re holding.

This article walks you through a clean fix path. Start with the quick checks that solve most cases first, then move to resets and admin-side checks if the Mac is meant to enroll through Apple Business Manager or Apple School Manager.

What The Message Means During Mac Setup

The line “an error occurred while obtaining automatic configuration settings” is setup’s way of saying it couldn’t download the configuration it expected. In an automated enrollment flow, the Mac contacts Apple’s enrollment service, checks whether the serial number is assigned to an MDM server, then downloads an enrollment profile that points the Mac to your device management system.

If anything blocks that chain—Wi-Fi that needs a browser sign-in, DNS that can’t resolve Apple enrollment hosts, a proxy that intercepts secure traffic, or an assignment that hasn’t synced—the Mac can’t fetch the profile and you get the error.

Watch for these two hints while you troubleshoot:

• The error appears instantly — That leans toward DNS or a blocked host.
• The spinner runs for a while — That leans toward timeouts, proxy inspection, or a slow route to Apple’s servers.

If you also see “(null)” in the text on that screen, treat it as a signal that the Mac didn’t receive the expected server details. In that case, jump to the admin-side section after you finish the quick network checks.

An Error Occurred While Obtaining Automatic Configuration Settings On Mac Setup

If you’re staring at this screen, run these steps in order. Each one is safe, quick, and meant to narrow the cause.

1. Try a different network — Switch from office Wi-Fi to a phone hotspot, or plug in Ethernet if you have an adapter. Captive portals and strict Wi-Fi policies block enrollment a lot.
2. Restart the Mac — Power it off fully, wait 20 seconds, then power it on and try again. A full power-off beats a quick reboot.
3. Check date and time — A clock that’s off can break secure connections. If you can open a browser during setup, compare the date and time with your phone.
4. Remove VPN and filtering — If your router runs a VPN, DNS filter, or proxy, test once with a clean path to the internet.
5. Retry after a short pause — If a profile was just assigned, wait 10 to 15 minutes, then retry. Some changes don’t land on Apple’s side instantly.

If enrollment is required for that Mac, you may not be able to bypass Remote Management. In that case, keep going through the sections below until the Mac can retrieve its profile.

Fixing Automatic Configuration Settings Error On Managed Macs

Enrollment is picky about network access. You’re not just reaching a normal website; you’re reaching specific Apple services used for device enrollment and device management. Apple publishes a list of hostnames and ports that managed devices need to reach, and that list is a great checklist when a firewall or proxy is in the way.

Captive Portal And Guest Wi-Fi

Hotel, campus, and guest Wi-Fi often requires a browser login. Setup can connect to Wi-Fi but still fail enrollment until that sign-in is done. A phone hotspot is the quickest test because it avoids portal pages.

DNS And Name Filtering

DNS trouble shows up as “it fails right away” or “it never loads.” If your Wi-Fi uses filtered DNS, try switching to a clean network. If you manage the network, check that it can resolve and reach these common enrollment and management hosts on TCP 443:

• deviceenrollment.apple.com — Used for enrollment lookup and profile retrieval.
• deviceservices-external.apple.com — Used by Apple device services during activation.
• *.push.apple.com — Used for push messaging that managed devices rely on.

Proxy Inspection And Firewall Rules

Some proxies work fine for browsers but trip up enrollment when they intercept certificates. If you have TLS inspection turned on, test with a bypass policy for the enrollment and device-management hosts. If the error disappears on a hotspot, you’ve confirmed the block is on the network side, not the Mac.

Check	What It Tells You	Fast Way To Test
Hotspot vs Wi-Fi	Rules out captive portals and strict filters	Join a phone hotspot and retry Remote Management
DNS filtering	Rules out blocked enrollment hostnames	Try a different network and retry setup
Proxy inspection	Rules out certificate interception breaking enrollment	Test once on an unproxied path
Apple service outage	Rules out server-side issues	Check Apple’s System Status and retry later

If your org uses Apple Business Manager in a browser, that admin traffic uses different hostnames than device enrollment. If admins can’t sign in or the portal is slow, fix that first so assignment changes can sync cleanly.

Resets That Clear Stuck Enrollment

If network swaps don’t change anything, the next move is to clear local state that can hold onto stale enrollment data. The right reset depends on whether your Mac is Intel-based or Apple silicon.

Reset NVRAM Or PRAM On Intel Macs

On Intel Macs, resetting NVRAM/PRAM can clear settings that affect setup and networking. Apple lists the startup shortcut Option (⌥) + Command (⌘) + P + R for a reset of NVRAM or PRAM.

1. Shut down the Mac — Power it off and wait a few seconds.
2. Start and hold the shortcut — Press power, then hold Option (⌥) + Command (⌘) + P + R.
3. Keep holding through a second start — Release after the Mac restarts again or you see the logo appear again.
4. Retry Remote Management — Join a clean network and try setup again.

Apple Silicon Macs

Apple silicon models don’t use the same PRAM reset method. On Apple silicon, start with a full shutdown, wait 20 seconds, then boot again and retry on a clean network. If you can reach Recovery, reinstalling macOS can refresh setup files without changing the device’s enrollment assignment.

Erase And Reinstall When Setup Is Corrupted

If you erased the Mac recently and this error appears every time, reinstall macOS from Recovery so the setup assistant and networking components are fresh. Keep the Mac plugged into power, use a stable network, then run setup again from the start.

If you’re dealing with a lab of Macs, try these resets on one device first. If the one test Mac clears the error, you can repeat the same steps for the rest instead of changing ten settings at once.

Admin Side Checks In Apple Business Manager And MDM

If the Mac is meant to enroll automatically, there’s a second half to the story: the assignment and sync between Apple Business Manager (or Apple School Manager) and your device management system.

Confirm The Mac Is Assigned To The Right MDM Server

Automated enrollment works when the device is assigned to an MDM server and an enrollment profile is available. If the Mac was moved between servers, or if a token expired, the Mac may reach Apple but still fail to pull the profile it expects.

• Check the serial assignment — In Apple Business Manager, confirm the device is assigned to the correct MDM server.
• Reassign and wait — If you change assignment, wait 10 to 15 minutes, then retry setup on the Mac.
• Sync the MDM — Trigger a device sync in your MDM so it pulls the newest assignment from Apple.

Jamf Pro Steps To Verify

In Jamf Pro, enrollment depends on the Automated Device Enrollment token and the device being mapped to a PreStage. If a Mac can’t pull its PreStage, the fix is often a token refresh, a sync, or a quick reassignment of the device to the right PreStage.

1. Verify the ADE token — Check that the token is valid and syncing without errors.
2. Verify device assignment — Confirm the device is assigned to your Jamf Pro MDM server in Apple Business Manager.
3. Verify the PreStage — Confirm the device is assigned to the correct PreStage enrollment.
4. Sync and retry — Run a sync, wait a bit, then retry setup on the Mac.

Microsoft Intune Steps To Verify

If you’re using Microsoft Intune, the Automated Device Enrollment profile in Intune must match the Apple Business Manager assignment. If devices are assigned to the wrong MDM server in Apple Business Manager, Intune won’t receive the right enrollment handshake, and setup can stall on Remote Management.

• Check enrollment tokens and certificates — Make sure the Apple enrollment token and certificates in Intune are current.
• Confirm the profile target — Verify the macOS enrollment profile is assigned to the right Macs.
• Sync, then retry — Trigger a sync, then retry setup on the Mac after a short wait.

Preventing The Error From Coming Back

Once you get past setup, a few habits cut down repeat failures. The theme is simple: keep enrollment traffic unblocked, keep tokens current, and keep assignments tidy.

• Keep an allowlist for enrollment hosts — Mirror Apple’s published hostnames and ports in your firewall and proxy rules, then test from the same Wi-Fi you use for new setups.
• Track token renewals — If your MDM uses an Automated Device Enrollment token, record the renewal date and renew it early.
• Use a setup network — A dedicated Wi-Fi SSID with no captive portal and minimal filtering saves time during onboarding.
• Test one Mac after changes — After editing profiles or assignments, test start to finish with one Mac before you roll changes across many devices.

If you still hit the same screen after all of this, go back to the first two checks: test on a hotspot and confirm Apple’s System Status is green. Then verify assignment and token sync again. When you hand the issue to an IT admin, share the Mac model, whether it’s Intel or Apple silicon, the network used, and the time of the failure so they can match it to logs.

After you get past Remote Management, you should be able to finish setup normally. If you see “an error occurred while obtaining automatic configuration settings” again on the same Mac after a full erase, treat it as a network or assignment issue first, since local resets have already been tried.