This is an introductory tutorial on using InstaDMG, a OSX package and image maker, to create clean never booted disk images of OSX 10.8 Mountain Lion.
Sep 25, 2019 Creating NetBoot image can be devided into three steps: Capture an OS X Boot Image. Add the OS X Boot Image to Configuration Manager. Distribute Content of the OS X Boot Image. Capture an OS X Boot Image: Download PmmOsdImageBuilder.dmg: Go to SCCM Administration Overview Parallels Mac Management Mac Client Enrollment.
Previous tutorials on InstaDMG and OSX 10.7 has three parts, base image, base image + user, base image + user and system modifications.
- 1) Create Automation partition by rolling out automation folder policy - Agents/Plugins All Agents and PLugins Deployment & Migration 2) Once this is complete boot to newly created automation partition it will be named as 'DSAutomation' and then install MOCUApp in 'DSAutomation' 3) From here create netboot image of required volume - 10.12 Sierra.
- Apr 12, 2012 I suggest you do this by putting the image on a external drive or another drive in the apple mac. I also suggest you use compression as images can get quite big. Once the image has finished you then can go onto your admin computer or server. In this example of using NetRestore I will be doing this from OS X 10.4 Server to make things easier.
- Several points about creating images with NetRestore I would like to pass on to others. 1) Using a Mac out of the box to create your image is not a good idea. The image is far larger than it would need to be (haven't figured out why yet). I have created an OS X 10.3.9 image from scratch.
For those not familiar InstaDMG is a powerful command line tool application used to produce clean never booted OS X images, these images can include OSX incremental upgrades as well as 3rd party software and scripts.
This guide is for getting a clean never booted up to OSX 10.8.4 Mountain Lion Image. You will need the OSX 10.8 installer which is named the InstallESD.dmg
Get InstaDMG
Navigate to your home and create a directory name ‘instadmg’ and change directory to it.
Download InstaDMG.
Updating InstaDMG
As new OSX updates are made available the InstaDMG code is changed to include the new upgrades, to update InstaDMG, move into the directory it is installed in and run the svn update command:
Preparing the Base OS X 10.8 Image
After the InstaDMG is downloaded the next step is to make a base installation image of OS X 10.8 Extract the InstallESD.dmg from the Lion.app after it is downloaded from the App Store and before it is installed, as when it is installed the app is then deleted – this guide shows how to reveal the InstallESD.dmg and also a guide to burn a generic copy of 10.8 to disk.
Move the InstallESD.dmg file from Mountain Lion in the path below in your InstaDMG location and move onto the next section:
Using the Catalog File
The catalog file is the all important file that contains the installer build numbers plus all the incremental OSX updates, the latest version of InstaDMG now has an OSX Mountain Lion 10.8 catalog file as at version revision 480.
– The OSX 10.8 Build number for the initial build is at the top, 12A269, 12B19, 12C54, 12D78, 12E55
– Below are the OSX incremental updates in the format of name, download link and SHA1 encryption key – these are tab separated on one line per item (grab shows them soft wrapped).
– If you don’t want to include a certain update in the build just add a comment (#) to the beginning of the line.
If you only have an older install build you can add the latest OSX 10.8.4 combo, by adding in the update in the OS Updates section just paste in the line below.
Make The OSX Image
Move into the InstaDMG location and to build the image you run the all important instaUp2Date command with sudo.
The .catalog extension does not need to be added in running the command. The command will take a while to run depending on your RAM and processor power. The OS X incremental updates are downloaded and stored on your local drive, future builds will only pull down new updates.
The disk image is spat out in the directory – “~/InstaDMG/OutputFiles” named “10.8 Vanilla.dmg” which is the all-encompassing new master image. The final output at the tail of the command in the Terminal will be like this:
And there you have it one OSX 10.8 image ready for deployment, which can be used in any deployment method including ASR, DeployStudio or as a NetBoot image.
You may get errors when running the command above such as:
But you do have the installer disc filed in the right place! – just reboot and try again.
Restoring via ASR
You could push this image to another drive using ASR – this will erase your target Volume:
Part 2 of this InstaDMG tutorial takes you through setting up a local user account on the images and adding files that allow you to bypass registration process.
Parallels® Mac Management for Microsoft® SCCM version 7.0 enhances the ability of the USB utility to boot a Mac to the Task Sequences and OSD images without the use of NetBoot®. Parallels Mac Management still uses NetBoot on the distribution point (DP) to handle images but not to boot. If you want to image from macOS® Mojave, you’ll need to upgrade to version 7.1 which has full support for macOS Mojave.
Note: Apple® left macOS High Sierra 10.13 with a broken ASR process that builds images from macOS. It isn’t until macOS Mojave 10.14 that you can build images. Apple came out with T2 chips on 2017 iMac® and 2018 MacBook® Pro. Most recently, MacBook® Air and Mac mini all have T2 chips and effectively kill NetBoot.
The latest release of Parallels Mac Managementis version 7.2. See our release notes for all the new features. The only way to image a Mac with a T2 chip set with Task Sequences and OSD images is with the Parallels Mac Management USB utility.
In this case, you need a macOS Catalina ISO image for VirtualBox & VMware. As you know that you are free to update your Mac from App Store if you have a Mac computer. Virtualbox can i use dmg windows 10. .Download macOS Catalina ISO For VirtualBox & VMwareThere are different methods of installing macOS Catalina on Windows. However, you will be able to download it from the given link below.
If you want to deploy macOS High Sierra 10.13 you’ll need to build boot and restore images from macOS High Sierra 10.13.3 or older. You can then use WSUS to upgrade to macOS High Sierra 10.13.6, the highest patched version.
Workflow Overview:
- Create a bootable USB drive (flash drive or HDD). Be careful, it will re-format the media used. A minimum 2 GB RAM device is required.
- Start the Mac and boot into Recovery
- Relax Secure Boot settings and External Boot on the Mac in Recovery
- Boot from the USB stick by re-starting the Mac, holding the Option button, and selecting USB as the boot drive.
Creating a Bootable USB Drive
If for any reason you can’t use a network boot during OS deployment, you can create a bootable USB drive (flash drive or HDD) and boot each Mac computer from it.
To create a bootable drive, download the Image Builder utility to the Mac:
- In the Configuration Manager console, navigate to Administration / Overview / Parallels Mac Management / Mac Client Enrollment
- In the Mac Client Enrollment list, right-click the Mac Client installation package download URL and then click Properties in the context menu
- Copy and paste the URL into a text editor. Replace “pma_agent.dmg” with “PmmOsdImageBuilder.dmg”
- On the Mac, open the resulting URL in a web browser to download the PmmOsdImageBuilder.dmg disk image file
- After downloading the disk image file, mount it in macOS. You are now ready to use the utility to create a bootable USB drive.
This utility allows you to create two kinds of bootable drives:
- Regular bootable drive
- Bootable drive with SSH access (see the Parallels Mac Management Administrator’s Guide for syntax).
To continue, open Terminal and change the directory to the PmmOsdImageBuilder.dmg image mount point (e.g. /Volumes/Parallels OSD Image Builder 7.0.xxxx.yyyyyy). To create a regular bootable drive, execute the following command in Terminal:
$ sudo ./pmm_osd_image_builder usbboot -t /Volumes/<usb volume name>
After creating the bootable drive, leave the USB media in the USB port ready to use after you change the settings for Secure Boot–Booting a T2 Mac. Note: a NetBoot image must be captured from a T2 Mac running macOS Mojave.
Booting a T2 Mac
Tip: Be sure you have set an Administrative local account on the Mac prior to going into Recovery Mode.
Secure Boot settings are available in the Startup Security Utility:
- Turn on the Mac, then press and hold Command (⌘)-R immediately after you see the Apple logo to start up from macOS Recovery
- When you see the macOS Utilities window, choose Utilities > Startup Security Utility from the menu bar
- When you’re asked to authenticate, click Enter macOS Password, then choose an administrator account and enter its password
Boot into recovery and relax (nice way to say turn off) Secure Boot and Allow USB. If you don’t make the changes to Secure Boot and External Boot you will receive this error –
Close the Startup Security Utility.
Close the macOS Utilities window.
Select Boot from Startup Disk.
Select the newly created USB device, Parallels Mac OSD then press Restart.
Create Netboot Image From Dmg Download
The Mac will reboot using the USB stick and after a short period present the Task Sequence Login Screen.
The actual OSD restore image building process is still the same for Mojave as outlined in the Administrators Guide.
You have 2 options:
- Use the OSD Image Builder on a Mac to build the image from Terminal commands
- Use a Task Sequence to capture the image.
Create Netboot Image From Dmg Software
Image Capture and Deployment for T2 Mac Computers
The actual image to be captured has to be from a non-T2 Mac due to the file encryption scheme Apple uses with the T2 chipset. We recommend that this non-T2 Mac is running macOS High Sierra 10.13.6 or later. Every file is encrypted on a T2 Mac and therefore can’t be imaged, so you have to capture a macOS Mojave image from a non-T2 Mac and deploy it to a Mac with a T2 chipset. Note that a T2 Mac won’t be installed with anything earlier than macOS High Sierra 10.13.6.