Just to let you know I already distribute a script that does exactly what yours is trying to do. It can use `--fetch-full-installer` or installinstallmacos.py to obtain the installer, and it is updated to handle installation on M1 via dialog boxes to obtain the username and password.
Take a look at https://github.com/grahampugh/erase-install
Just to let you know I already distribute a script that does exactly what yours is trying to do. It can use `--fetch-full-installer` or installinstallmacos.py to obtain the installer, and it is updated to handle installation on M1 via dialog boxes to obtain the username and password.
Take a look at https://github.com/grahampugh/erase-install
What @grahamrpugh said. I can't kudo his erase-install script enough for dealing with M1 re-imaging via Self Service.
Just to let you know I already distribute a script that does exactly what yours is trying to do. It can use `--fetch-full-installer` or installinstallmacos.py to obtain the installer, and it is updated to handle installation on M1 via dialog boxes to obtain the username and password.
Take a look at https://github.com/grahampugh/erase-install
Hi Avogel,
I use erase-instal mention above and it works like a charm for intel or silicon based Mac. Quick Link to access
Hope this will help
-Samstar777
Hi Avogel,
I use erase-instal mention above and it works like a charm for intel or silicon based Mac. Quick Link to access
Hope this will help
-Samstar777
Just to let you know I already distribute a script that does exactly what yours is trying to do. It can use `--fetch-full-installer` or installinstallmacos.py to obtain the installer, and it is updated to handle installation on M1 via dialog boxes to obtain the username and password.
Take a look at https://github.com/grahampugh/erase-install
Im looking at trying this out. Is it possible to modify the DEPNotify window? Based on the users choice of course.
Im looking at trying this out. Is it possible to modify the DEPNotify window? Based on the users choice of course.
What do you want to modify? You can of course directly edit the script if you choose to add the script directly to Jamf, but then you'd have to keep track of your modifications when the script is updated (e.g., you could fork it).
Or if you think there is some kind of optional parameters to change the notifications that would be useful to many people, feel free to raise an issue/pull request. Note I already have language localisations, and would welcome PRs for more languages (we currently have English, German, French and Dutch).
Somebody is currently working on adding progress feedback to the DEPNotify window which I will definitely add once it's ready.
What do you want to modify? You can of course directly edit the script if you choose to add the script directly to Jamf, but then you'd have to keep track of your modifications when the script is updated (e.g., you could fork it).
Or if you think there is some kind of optional parameters to change the notifications that would be useful to many people, feel free to raise an issue/pull request. Note I already have language localisations, and would welcome PRs for more languages (we currently have English, German, French and Dutch).
Somebody is currently working on adding progress feedback to the DEPNotify window which I will definitely add once it's ready.
Hi,
Thanks for the quick reply.
My coding skills isnt up to your level. So i was mainly after a specific thing. When we erase macs, we set the asset tag to "Spare", and it would be super dope if its possible to add a recon at the right place when the user confirms they want to erase the mac. Nothing more really.
Apart from the above, it works like a charm!
Hi,
Thanks for the quick reply.
My coding skills isnt up to your level. So i was mainly after a specific thing. When we erase macs, we set the asset tag to "Spare", and it would be super dope if its possible to add a recon at the right place when the user confirms they want to erase the mac. Nothing more really.
Apart from the above, it works like a charm!
That's quite a good idea. I could see value in sending a command prior to erase.
How about a parameter called `--preinstall-command`, which you could add whatever command you like? (I don't think this needs to be tied to the `--confirm` parameter). This would allow people to run different recon parameters (e.g. those who want to set the Department to "Spare" etc), or those not using Jamf at all to run some completely different shell command.
In your example you could then add `--preinstall-command="jamf recon -assetTag"` along with all your other parameters.
That's quite a good idea. I could see value in sending a command prior to erase.
How about a parameter called `--preinstall-command`, which you could add whatever command you like? (I don't think this needs to be tied to the `--confirm` parameter). This would allow people to run different recon parameters (e.g. those who want to set the Department to "Spare" etc), or those not using Jamf at all to run some completely different shell command.
In your example you could then add `--preinstall-command="jamf recon -assetTag"` along with all your other parameters.
Glad my idea was good!
It is one of those little "nice" things for customization.
As for now, is it possible to add such a recon at the right place?
I can use composer to package it all again, but curios where in the script the right place would be.
That's quite a good idea. I could see value in sending a command prior to erase.
How about a parameter called `--preinstall-command`, which you could add whatever command you like? (I don't think this needs to be tied to the `--confirm` parameter). This would allow people to run different recon parameters (e.g. those who want to set the Department to "Spare" etc), or those not using Jamf at all to run some completely different shell command.
In your example you could then add `--preinstall-command="jamf recon -assetTag"` along with all your other parameters.
@grahamrpugh Having a `--preinstall-command` would be a great addition. For Mojave->Catalina updates I had modified the macOSUpgrade script to have a "Last Call" parameter for a Jamf Pro policy trigger (necessary to remove McAfee as it tended to bork the macOS installer) and had been meaning to do the same for erase-install, but having the option to run an arbitrary command would be much more versatile.
Glad my idea was good!
It is one of those little "nice" things for customization.
As for now, is it possible to add such a recon at the right place?
I can use composer to package it all again, but curios where in the script the right place would be.
If you're just adding your own command directly, I guess it would go on line 1450, like this
# run it!
if [[ $test_run != "yes" ]]; then
jamf recon --assetTag
if [ "$arch" == "arm64" ]; then
# startosinstall --eraseinstall may fail if a user was converted to admin using the Privileges app
# this command supposedly fixes this problem (experimental!)
@grahamrpugh Having a `--preinstall-command` would be a great addition. For Mojave->Catalina updates I had modified the macOSUpgrade script to have a "Last Call" parameter for a Jamf Pro policy trigger (necessary to remove McAfee as it tended to bork the macOS installer) and had been meaning to do the same for erase-install, but having the option to run an arbitrary command would be much more versatile.
OK, I created an issue:
https://github.com/grahampugh/erase-install/issues/119
Just to manage expectations, given my current schedule, I probably won't visit this for a couple of weeks. But I do like the idea.
If you're just adding your own command directly, I guess it would go on line 1450, like this
# run it!
if [[ $test_run != "yes" ]]; then
jamf recon --assetTag
if [ "$arch" == "arm64" ]; then
# startosinstall --eraseinstall may fail if a user was converted to admin using the Privileges app
# this command supposedly fixes this problem (experimental!)
That looks about as simple as i had it in my head ^^
ill test it out and see how it goes! Super thanks for the quick replies and all!
If you're just adding your own command directly, I guess it would go on line 1450, like this
# run it!
if [[ $test_run != "yes" ]]; then
jamf recon --assetTag
if [ "$arch" == "arm64" ]; then
# startosinstall --eraseinstall may fail if a user was converted to admin using the Privileges app
# this command supposedly fixes this problem (experimental!)
Hi again!
Did the first test with the added line. Works great! Does open up some great ideas on how to take it even further!
How well does erase-install.sh and installinstallmacos.py interact with Content Cache?
In my environment installinstallmacos.py does not seem to pull from my content cache.
softwareupdate --fetch-full-installer does pull from the content cache.
Does installinstallmacos.py pull down the macOS installers using curl or software update?
How well does erase-install.sh and installinstallmacos.py interact with Content Cache?
In my environment installinstallmacos.py does not seem to pull from my content cache.
softwareupdate --fetch-full-installer does pull from the content cache.
Does installinstallmacos.py pull down the macOS installers using curl or software update?
It uses curl, from the software catalogs. So it's not going to use content caching.
However, you can run erase-install.sh with the `--fetch-full-installer` option too if you want to attempt to benefit from content-caching.
Do anybody know about parameter called `--preinstall-command` . Was it implemented?
Details here: https://github.com/grahampugh/erase-install/wiki/7.-Erasing-and-reinstalling-macOS#--preinstall-command
I am trying to execute command
/Library/Management/erase-install/erase-install.sh --os=12 --move --confirm --erase --current-user --depnotify --check-power --test-run --no-curl --update --preinstall-command "jamf recon -department Spare"
The target is to update inventory before reinstalling but it won't to update inventory . Log:
| Running command /Library/Management/erase-install/erase-install.sh --os=12 --move --confirm --erase --current-user --depnotify --check-power --test-run --no-curl --update --preinstall-command "jamf recon -department Spare"... |
Result of the command:
Preinstall: jamf recon -department Spare but it doesn't update inventory. What I am doing wrong? |
I am trying to execute command
/Library/Management/erase-install/erase-install.sh --os=12 --move --confirm --erase --current-user --depnotify --check-power --test-run --no-curl --update --preinstall-command "jamf recon -department Spare"
The target is to update inventory before reinstalling but it won't to update inventory . Log:
| Running command /Library/Management/erase-install/erase-install.sh --os=12 --move --confirm --erase --current-user --depnotify --check-power --test-run --no-curl --update --preinstall-command "jamf recon -department Spare"... |
Result of the command:
Preinstall: jamf recon -department Spare but it doesn't update inventory. What I am doing wrong? |
`--preinstall-command` is not run with `--test-run`.
Has anyone successfully executed two commands with --preinstall-command? For example, I need to create the file and run jamf recon and for some reason, I can't do it. I have tried all impossible scenarios like --preinstall-command "touch /Library/dir/file; jamf recon" (creates file with ; semicolon ) bud didn't executes jamf recon and --preinstall-command 'touch /Library/dir/file; jamf recon' also I have tried two preinstall commands --preinstall-command "touch /Library/dir/file" --preinstall-command "jamf recon" but it only executes the last command
Why not just run a recon on startup? That's what I do. Then you get the bonus of the OS version being recorded correctly after the upgrade.
Why not just run a recon on startup? That's what I do. Then you get the bonus of the OS version being recorded correctly after the upgrade.
I need recon after creating the file for creating EA that will monitor erase with flag true or false
I need recon after creating the file for creating EA that will monitor erase with flag true or false
So create the file with --preinstall-command, and do the recon at startup.
Edit: ah, no, sorry, I forgot you're talking about an erase, so that won't work.
Please add a feature request for the ability to add multiple commands. I'll look into it.
(in the meantime you could lay down a script on the client which is called by --preinstall-command. That can then do as many things as you want).
So create the file with --preinstall-command, and do the recon at startup.
Edit: ah, no, sorry, I forgot you're talking about an erase, so that won't work.
Please add a feature request for the ability to add multiple commands. I'll look into it.
(in the meantime you could lay down a script on the client which is called by --preinstall-command. That can then do as many things as you want).
After creating the file I need recon fo EA "Erase install check (false or true)" and after reboot I can monitor if the machine was enrolled again or something went wrong (I will see EA true)
