Using a different Software Update catalog The script then runs through its actions and creates a compressed disk image with only the macOS Installer application stored inside.
In this example, I’m also selecting option 1 to download the standard macOS Installer application for macOS 10.13.3. path/to/installinstallmacos.py -compress To use this option, please run the command shown below with root privileges: Using the –compress option will allow installinstallmacos.py to generate a compatible disk image. Update – 2-27-2018: Greg reached out to let me know that the –compress option’s primary function is to produce a disk image which is compatible with Munki and Imagr.īoth tools expect to find the macOS Installer application at the root level of a read-only disk image. This option will create a compressed read-only disk image, with only the macOS Installer application stored on the disk image. If it’s desirable to save space, the script includes a –compress option. If desired, this folder may be discarded once the disk image has been created. Note: A content folder owned by root is also created, which was used by the script to store the various downloaded components. In this example, I’m selecting option 1 to download the standard macOS Installer application for macOS 10.13.3. Once an option has been selected, the script then runs through the rest of the actions described above and creates a disk image with the macOS Installer application stored in the Applications directory of the disk image. As of February 27, 2018, the following macOS installer choices are displayed: You have the ability to use no options, one option, or combine multiple options when running the script. To run the script without any options selected, please run the command shown below with root privileges:īy default, this will use the Software Update catalog specified in the script. Once you have it downloaded, please run the following command with root privileges to display the available options: The script is available from the following location: Stores the disk image in the current working directory (this is likely going to be the logged-in user’s home folder.)įor more details, please see below the jump. Installs the packages onto the disk image.ĩ. Downloads all the relevant packages from the Software Update feed for the specified macOS installer.ħ. Creates a disk image and names it with the appropriate information for the specified macOS installer.Ħ. Once you’ve selected from the available options, the script does the following:Ĥ. Identify the listed products which appear to be macOS installers.ģ. Parse a specified Software Update feed.Ģ. installinstallmacos.py is designed to do the following:ġ. To assist with this task, Greg Neagle has written a Python script named installinstallmacos.py. This means that it’s possible to download macOS installers, including those for macOS betas or hardware-specific macOS builds, using the command-line softwareupdate tool.
Using the latest unlocker, install the Mac OS support.Īnybody with experience in this conundrum, I'm all ears.Starting with macOS Sierra, Apple moved the macOS Installer applications from being exclusively an App Store download to now being included in the regular Software Update catalogs. So, any suggested recovery options? It seems to me that I've got a mismash of the VMWare installation, and I need to: " Well bless my soul, I'll bet my Mac OS is fine, and I just f'd up VMware. Failure to do this could render VMware unusable. So, I finally read the readme.txt (yes, poking fun at myself) and come across: "Always uninstall the previous version of the Unlocker before using a new version. At this point, I've made so many changes I've made a mess. Okay, obviously something is wrong with VMWare.
At this point, I'm figuring that something got hosed in the Mac OS image. Following a recovery document, I configured my machine to boot a recovery ISO. In a brilliant brain cramp, I figured that I just needed to go get the latest unlocker. The Mac just cycles through boot attempts. This promptly nuked my Mac OS VM all of the others boot normally. Fast forward to a month ago, and I made the mistake of upgrading my licensed VMware Workstation 14.5 to 14.6. I was following a bulleted list, and it just worked.
Now I admit that back in 2018 I didn't read much about the unlocker tool. I've got 1/2 dozen VMs on my laptop - Xp, 7, 10, Linux and Mac OS.
Late in 2018 I started playing around with the Mac OS, mainly just to see what it is like. I need some advice to repair my VMware situation.