Install the latest macOS that was installed on your Mac, without upgrading to a later version. Guessing some folks are going down the convoluted/inefficient road.IMHO. For details, run startosinstall with the -usage flag." ![]() Use this flag to erase and install macOS on a disk. "Adds the -eraseinstall flag to the startosinstall command in the macOS Installer app at Contents/Resources/startosinstall. About the macOS High Sierra 10.13.4 Update "Apple doesn't recommend or support monolithic system imaging as an installation method, because the system image might not include model-specific information such as firmware updates." How to install macOS at your organization Evolve.ġ0.13.4 went a long way in turning bible thumping, soap box "The sky is falling" preaching into a practical opportunity to finally shift gears.įirmware is one reason.a pretty big one. ![]() Moral of the story: if you have not yet started aligning your workflows to the post 10.13 world of Apple provisioning, you are going to be in the hot seat when there is no other way to accomplish things on newly purchased Macs. There is going to come a point (secureboot) where hacking around "the writing on the wall" is going to go down in flames, and I would not want to be on that plane when it impacts. I feel like being 100% straight-forward (as much as that is a thing with the info Apple trickles out) with leadership on the need to align processes with Apple, despite the loss of full automation will be your best course of action. If we can do it for thousands and thousands of Macs globally (including fully automated secureToken based FileVault enablement), it CAN be done. USB boot media / Internet Recovery / Recovery Drive / 10.13.4+ policy/app based restore -> set up a standard temp admin account in Setup Assistant -> enroll via the Jamf User Initiated Enrollment portal -> policy based provisioning takes over. CCC can copy virtual machine container files, but copying to or from a virtual machine is not supportable.Agreed that DEP can be a long slog, especially in a global organization.If Apple doesn't support it, we cannot support it. Likewise, you cannot clone Mojave onto a 2019 MacBook Pro that shipped with Catalina. For example, we cannot help you get Catalina running on a 2008 MacPro. We can only support cloning versions of macOS that are supported by Apple on your hardware.Apple discourages this sort of deployment and offers additional resources here, and there are alternative solutions to consider. Performing mass deployments with CCC is not supported.CCC is not a two-way synchronization solution designed to keep two Macs in sync with each other - this is not a supported configuration.macOS Mojave and later cannot boot from a RAID device.WebDAV, FTP, NFS and other "cloud" destinations are not supported.CCC will not backup directly to optical media (e.g.Cloning Windows system files is not a supported configuration.CCC will not clone to or from an unformatted or unmounted device - the source and destination must have a filesystem recognized by macOS and visible in the Finder.These restrictions apply to the ability of the device to boot a Mac, any of these devices are suitable for general backup. See the Preparing a hard drive for use with Carbon Copy Cloner and Help! My clone won't boot sections of the CCC documentation for more information on disk formatting, partitioning, and general bootability concerns. A minimum screen resolution of 1024x768 is requiredġ: APFS performs poorly on HDDs with a rotational speed of less than 7200RPMĢ: macOS Catalina+ does not support booting a Mac via a FireWire-attached deviceģ: Not all hard drive enclosures are capable of booting macOS.CCC is supported only on Apple Macintoshes that officially support OS X 10.10 Yosemite (or higher). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |