![]() ![]() It seems to be a consistent point of confusion about how best to get macOS installers onto devices into the right location. FWIW, I see this type of question asked very frequently here. Just like macOS Mojave 10.14 Update, Apple has made significant changes in its latest Xcode 10 development tool to help developers make apps and games much faster and easier across all platforms of macOS, iOS, tvOS, and watchOS. Hope that makes sense and clears things up. dmg into /Library/Application Support/Downloads/, run the pkg or dmg and "install" it's contents, which in this case is the macOS installer app, into the Applications folder, and finally do a cleanup. Then upload and deploy it using the 'Install' action, NOT 'Cache'. app to match the rest of the Applications folder (always a good idea) and then build the package or DMG. From there you can adjust permissions on the. app file into Composer's sidebar, where it will create a new source, and copy the installer in along with the path in Applications. First, place/copy your macOS installer into /Applications/, then in Composer, just drag the installer. If you want to "cache" a macOS installer to /Applications/ for your clients, the easiest way I've found to do this is to create a new pkg in Composer. then choose a destination to save it to (if youre planning to make a USB installer. pkg file, then follow the onscreen instructions to install the macOS installer into your Applications folder. In the case of 'Install' as the action, the policy downloads the package(s) into /Library/Application Support/JAMF/Downloads/ The difference is the policy then directs the jamf binary to run the packages or DMGs to install the contents immediately after, then removes the files when finished (success or fail). Confirm that you want to download the complete 6.5 GB MacOS Mojave installer. dmg file to open it and see the package (.pkg) file within. The simplest way to understand this is that when a policy uses the 'Cache' action, the package payload(s) in the policy get downloaded into /Library/Application Support/JAMF/Waiting Room/ and will sit there, waiting for some additional action later to run the installations, such as another policy that uses the 'Install Cached' or 'Install All Cached' actions, or a script calling the jamf binary, etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |