Recover a Student Mac from a Broken Setup

Test recovery before a failure, but do not erase, reinstall, or reset a working student Mac for practice. Run a non-destructive rehearsal that verifies account and FileVault responsibility, restores one disposable test artifact, clones one project to a new directory, checks the reproducible setup record, identifies device management, and records the correct macOS Recovery path.

If no setup artifact exists yet, first create the small, secret-free macOS setup record. A recovery rehearsal cannot verify documentation that exists only in memory.

An actual reinstall, erase, or full data migration is a separate operation. It requires a real need, verified backup, recovery access, official instructions, adequate time, power and network access, and institutional authorization when the Mac is managed.

Define what must recover

Use a small first pass:

Account and FileVault recovery owner:
One important file category and its backup:
One course project and its remote/data sources:
One required toolchain and its setup artifact:
Device-management status and support contact:

Then classify remaining items as must recover, useful later, or not needed. Recovery should restore required capability, not every application, plugin, cache, and forgotten experiment.

Never put a password, FileVault recovery key, multifactor code, private SSH key, backup password, or access token in the rehearsal report.

Know what each recovery source does

Keep backup, recovery environment, device management, and data restoration as separate layers. One cannot stand in for the others.

Verify account and encryption access

From another trusted device, confirm that the responsible person can reach:

• the approved Apple Account or institutional recovery process;
• the FileVault recovery method identified during safe setup;
• the backup password or approved credential store, when applicable; and
• the institution’s IT contact and device record.

Confirm access to the process without printing or copying the secret into the report. Do not intentionally lock the account or enter macOS Recovery to reset a password during this rehearsal.

Restore one disposable test artifact

Apple identifies Time Machine as the built-in Mac backup feature in Back up your Mac with Time Machine. Its availability, backup destination, encryption, retention, and latest successful backup should be checked on the actual Mac.

Use a disposable file containing no private data:

1. Create Recovery-Rehearsal/test-note.txt with a recognizable sentence.
2. Let the approved backup system include it and confirm the backup completed.
3. Rename the live file to test-note.current.txt; do not delete it.
4. Follow the backup system’s official item-restoration procedure.
5. Open the restored file and compare it with the renamed copy.
6. Record source, backup date, restored location, content check, and result.
7. Remove the practice artifacts only after the comparison and according to your normal file policy.

Apple’s current Time Machine item-restoration guide explains how selected items are returned to their original location. If the student uses another approved backup system, use that provider’s official restore instructions. A green sync icon or “backup complete” message is weaker evidence than an opened, compared restored file.

Restore one project separately

Clone one noncritical course or practice repository into a new directory. Do not reuse the already working checkout.

Verify:

• the remote and authentication method;
• committed source and history;
• documented source for ignored or external data;
• environment examples without real secrets;
• Brewfile or other package intent;
• course dependency installation;
• build, run, and test commands; and
• expected output.

If the new clone depends on an unrecorded local file, shell setting, or token, record a recovery gap. Fix the authoritative project or setup documentation, not only the rehearsal copy.

Rehearse the setup artifacts without applying them

From a new directory:

1. Read the macOS setup README from the beginning.
2. Run read-only verification.
3. If the target uses Homebrew, run brew bundle check --verbose against the reviewed Brewfile; otherwise record not applicable.
4. Compare configuration examples without replacing live dotfiles.
5. List manual and managed steps.
6. Record every assumption that depends on the original Mac.

Do not run the bootstrap, bulk package installation, or cleanup merely to complete the rehearsal.

Record the correct macOS Recovery path

Apple’s macOS Recovery overview describes a built-in recovery system with repair, reinstall, Time Machine restore, security, and other capabilities. Some choices are destructive.

First identify the Mac type in Apple menu → About This Mac:

• on Apple silicon, Apple currently directs the user to shut down, then hold the power button until startup options appear and select Options; and
• on Intel, startup key combinations are used.

Record the model type and bookmark Apple’s current startup instructions. Do not rely on a remembered key combination from another Mac.

An optional startup-only rehearsal is appropriate only when:

• current work is saved and backed up;
• the Mac can be restarted safely;
• no deadline or managed-device process is at risk;
• the student understands how to quit Recovery; and
• no repair, password reset, security change, disk operation, restore, reinstall, or erase option will be selected.

If those conditions are not met, record the official path without starting Recovery. That is a valid first-pass result.

Distinguish reinstall from data restoration

Reinstalling macOS addresses the operating system. Restoring selected files or migrating a user account addresses data and user state.

Apple’s Mac restoration guide explains that Migration Assistant can transfer personal files, applications, and user-account contents from a Time Machine backup. This is different from restoring one test item and from reinstalling macOS.

Apple’s deployment guidance for macOS installation also distinguishes a standard reinstall that attempts to preserve data from an erase-and-install path that does not. Even a standard reinstall should begin with verified backup. Neither path belongs in this exercise.

On a managed Mac, IT may automate setup, escrow recovery information, reinstall the system, or require reenrollment. Do not erase, remove management, disable security controls, or independently restore organizational data.

Produce a recovery gap report

# Mac recovery rehearsal

- Date:
- Mac type and management state:
- No erase, reinstall, or reset performed: yes

## Verified
- Account and FileVault recovery process:
- Disposable file restore:
- Practice project clone:
- Setup documentation and conditional Brewfile check:
- macOS Recovery instructions recorded:

## Gaps
- Missing dependency:
- Consequence:
- Corrective action:
- Responsible person or service:
- Review date:

Correct gaps at their source: backup configuration, project README, setup repository, credential recovery, or institutional support record.

Escalate an actual failure by layer

Do not escalate a small tool failure into an operating-system reinstall before testing the smaller layer.

Common mistakes

• Erasing a Mac to test documentation.
• Treating synchronization as a complete backup.
• Assuming Git contains uncommitted or ignored work.
• Treating a Brewfile as data restoration.
• Copying recovery keys or private keys into the report.
• Entering Disk Utility or reinstall options during a startup rehearsal.
• Assuming Apple silicon and Intel use the same startup procedure.
• Reinstalling a managed Mac without IT authorization.
• Stopping after installation instead of restoring and testing coursework.

Do this now

Begin with a readiness gate: confirm device ownership, backup access, Apple Account and FileVault recovery responsibility, management limits, and permission to inspect the Mac. Stop if access or authority is unresolved. Then restore one disposable file and record the result. Project restoration, setup-artifact inspection, and startup-path rehearsal are later stages. Do not erase, reinstall, reset, or remove management.

Log what you learned

The Mac recovery rehearsal and gap report are the learning log. Add each stage only after it runs, beginning with readiness and one file-restore result.