Skip to main content
Question

Prestage Enrollment QA testing with Big Sur

  • April 2, 2021
  • 3 replies
  • 27 views
G
Forum|alt.badge.img+4

Environment:
macOS 11.2.3
JAMF Pro 10.28

I've been working on building our first zero-touch deployment prestage enrollment and testing has become such a pain. I was initially able to use the serial/model changes + snapshots in VMWare Fusion to test, but things got weird when I started testing FileVault and the SecureToken. I switched to using actual hardware, which solved my FV/Token testing issues, but wiping/reinstalling takes a huge chunk of time out of my day. I've tried the method of installing macOS to an external drive so that I can make Time Machine snapshots, but I cannot get it to successfully boot. I install using the Install macOS Big Sur installer to my APFS/GUID Partition Mapping formatted USB drive, set the drive as my startup disk and just get stuck in a kernel panic loop until I give up and boot back to my normal disk.

How in the world are people successfully, and efficiently, testing prestage enrollments?!

3 replies

G
Forum|alt.badge.img+4
  • ghart
  • Author
  • New Contributor
  • April 3, 2021

I accidentally ended up answering my own question! Instead of trying to boot from a USB to make a Time Machine snapshot, I just opened the terminal from the Language Chooser with CMD+OPT+CTRL+T. A quick tmutil snapshot and I'm finally testing and restoring in minutes!

EDIT: Nevermind. It seems using the snapshot method causes problems with "ghost" UUIDs being granted the only secure token and preventing the configuration of FileVault. Back to square one, I guess. Any ideas?

M
Forum|alt.badge.img+1
  • maurits-pro
  • New Contributor
  • April 4, 2021

Too bad vfuse is no longer working for macOS 11, the scripted creation of a new VM was my favorite method.
My testing of big sure is done using a VMware Fusion VM, manually edit the serial and make snapshot before first boot.
After enrollment it can be tricky to revert a snapshot due to same UUID and history as known by Jamf. Testing policies works nice in VM snapshots (run recon after reverting snapshot, possibly flush all logs).
I used this link https://travellingtechguy.blog/macos-big-sur-on-vmware-fusion-12/

D
Forum|alt.badge.img+1

I use parallels on my main MacBook pro, a few tricks

  1. spoof serial number
  2. take snapshot of the machine before it boots the first time, and take the snapshot while the machine is off (the ensures that no prestage is cached in your testing) works just fine
  3. obviously this is on Intel only, we cant do this on M1 yet
Terms & ConditionsCookie settingsAccessibility statement