I was recently tasked with deploying dual-boot Macs to all new staff. Naturally, I wanted this to be as automated as possible so it was repeatable and consistent. I already knew how to use an answer file to fully-automate the Windows side of the deployment. And I also knew how to fully automate the Mac side of things.
I did need to learn how to make Windows 10 into a deployable
.pkg, which was the final piece needed to automate the entire dual-boot deployment process.
- Have DeployStudio installed
- Have a basic workflow setup for imaging a Mac
- Have a
.pkgwith a sysprep’d Windows 10 image
Setup Your DeployStudio Workflow
The first task should partition the drive to be 100% macOS (your Windows
.pkg will partition it later on to be able to fit Windows on the drive).
The next task should deploy a macOS image. The key here is to check the box for Add Generic BCD.
Finally, your last task should be to deploy the Windows 10
.pkg. You can add whatever Mac-side tasks you need before this, but I usually have Windows deploy at the very end.
That’s it! Image your machine and it will boot up to macOS. Restart holding Option and you will be able to choose the Windows partition. Assuming your answer file and sysprep work were done correctly, it will auto-configure itself.
Here is a time-lapse video of the entire thing in progress. Note, I wanted to keep macOS the default OS, so when Windows needs to restart during the initial setup, I have to hold the option key. This wouldn’t be necessary if Windows is set to