InstallESDChecksum="$7" Error in the Log on clients. #Example Command: /sbin/md5 /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/InstallESD.dmg #Leave the variable BLANK if you do NOT want to verify the checksum (DEFAULT) #This should match a custom trigger for a policy that contains an installer Use Parameter 6 in the JSS, or specify here. Use Parameter 5 in the JSS, or specify here.
DISK INVENTORY X FOR 10.13.6 INSTALL
The JSS says the upgrade completes but the client is still running the same version after install of package and running of script. I am stuck here sir I don't know what is going wrong. Otherwise you can get a package of the installer with helper script as shown below and deploy the package via Jamf Pro.įorkers themacadmin darklordbrock smithjw Airr haircut jamescchh hhandal patgmac smashism johnlunney franton ChrOst gabe2385 da4ftso tkuennen cemoulto moultondigital wafindotca SteveChristian70 kevinstrick Timothycocores baconflip joel-Y thecececollins scifiman kenchan0130 julio575 taniguti daydr3am3r willpolley SmithersJr bgrande12 Lotusshaney USicilianU sevenluckz ecanault STLVNUB conor-machugh brodriguez255 ferriterj1 moritz-Z monodata sdagley fabiola-ias bikram990 bwiessner eabraun ryangball kerdelzone fulltimecasual gzilla13 kennethdean2010 cubandave sggr57a hackerman518 aaronalquillera Inalcanzab1e mactender erefneb nichiera takhozu10 sjha967 cranappras kevindigg arekdreyer alsyundawy vailster madscipter syoung-quizlet caffine247 Zer0Cool-85 thereal-kcsantos timelost11 jfiliceatcsumb dwshore-personal mistacabbage lincolnep jrreid jmahlman NISHMANGAL smwaldman Hambeard erikbaarstad AZNH7 ayotec2015 amattahcj matinsa froegelein mrazishere tsinghzf XxMSDOSxX sfdc-cpe almostjulian Bdaskal jamesaIQ jotai73 BirdsofaFeather stugster tomaszgruszka pseudopunk One of the easiest ways to achieve this is to package the installer as seen below and deploy the package via Jamf Pro.
DISK INVENTORY X FOR 10.13.6 MAC
In order for this script to work, you will have to have a copy of the macOS Installer that is available from the Mac App Store located in /Applications. Essentially this will wipe and reload the system to factory defaults. Also, don't forget to setup a policy with a custom trigger specified as defined in the user variables.Īdded in v2.6.0 - You can now specify to use the -eraseInstall parameter when using macOS Installer 10.13.4 or later and the client is running macOS 10.13 or later. Here you can specify the message that is displayed to the end user while the script is running and preparing the computer to upgrade to macOS Sierra, as well as the variables used to determine the version and path for the macOS Installer. When you open the script you will find some user variables defined on lines 60-118. While the devices are encrypting, you will not be able to upgrade macOS until after encryption is completed. laurentpertois/Mojave-Compatibility-CheckerĪlso, if you are encrypting your macOS devices (which I hope you are), you will want to ensure your scope also includes devices that are not currently encrypting.laurentpertois/High-Sierra-Compatibility-Checker.At that very least, you'll want to create a Smart Group to determine if the target system(s) meet the system requirements for the macOS upgrade. When you start deploying this script to your end-users you will want to ensure that it is scoped properly. As of v2.5 of this script FileVault Authenticated reboots work again! This script was created to adhere to Apple's requirements of the startosinstall binary. Because of this change, many common ways that have been used and worked in the past no longer do. Starting with macOS Sierra, Apple has begun enforcing the way in which you can silently call for the OS upgrade process to happen in the background. Tested with macOS 10.13.4 and you will get errors in that the process couldn't establish a connection to the WindowServer. This workflow will not work if a user is not logged in since the startosinstall binary requires a user to be logged in. Look over the USER VARIABLES and configure as needed.eraseInstall option is ONLY supported with macOS Installer 10.13.4+ and client-side macOS 10.13+.
This script was designed to be used in a Self Service policy to ensure specific requirements have been met before proceeding with an in-place upgrade to macOS, as well as to address changes Apple has made to the ability to complete macOS upgrades silently.
MacOS Self Service Upgrade Process Workflow for doing an in-place upgrades.
0 kommentar(er)
