JAMF deployment user missing default dock

If you manage a fleet of Macs using Jamf Pro, you’ve likely run into this baffling enrollment glitch: A user completes Automated Device Enrollment (ADE), logs in for the first time, and looks down to find a completely barren Dock. No Safari, no Launchpad, no System Settings—just the Finder and the Trash icons.

Why Does This Happen?

This "stripped-down" Dock state happens because of a race condition during enrollment. When Jamf pushes a Dock payload before the macOS user template has fully initialized the desktop environment, the macOS Dock agent (com.apple.dock) panics. Unable to find application paths that are still installing in the background, macOS defaults to the absolute bare minimum configuration required to operate: Finder and Trash.

The Quick Fix: Reset the Dock Domain

You don't need to wipe or re-enroll the machine. If you are sitting at the affected Mac, you can bypass complex file paths by targeting the preference domain directly via the Terminal:

1. On the target Mac, open the Terminal application.
2. Type or paste the following exact command line:

defaults delete com.apple.dock; killall Dock

What this command does:

• defaults delete com.apple.dock: Targets the current user's cached preference domain and obliterates the broken layout data without throwing "file not found" errors.
• killall Dock: Forcefully restarts the Dock process. When it respawns, it pulls the fresh deployment layout dynamically assigned by your Jamf framework.

Preventing This Globally:

To stop this from happening to future enrollments, avoid using Jamf Policies triggered on "Enrollment Complete" to manage Dock items. Instead, deploy your Dock setup using an MDM Configuration Profile. Configuration profiles hook natively into Apple's management framework at a deeper level and are significantly less prone to timing bugs during first login.