Replies: 5 comments 6 replies
-
My reason for this question being I have more commands than will fit in parameters 1-10 |
Beta Was this translation helpful? Give feedback.
-
Hi @GabeShack. Both are accurate. If you upload erase-install.sh directly into Jamf, you have to supply each parameter separately. Equals signs are required for those parameters that require a value, e.g. However, if you deploy erase-install as a package, you can upload the Alternatively you can also deploy erase-install as a package and just use the "Run Command" field to provide as many parameters as you like, e.g. |
Beta Was this translation helpful? Give feedback.
-
Thank you. Im toying with the idea of using the extras folder for signed package installers which would save us another script i call during enrollment complete, which pushes the base apps of our image. Doing this before would save some startup and login time so just starting to play around with my next years image. |
Beta Was this translation helpful? Give feedback.
-
Would you be able to tell me the error message that gets displayed when you try to use an unsigned package in the extras folder? |
Beta Was this translation helpful? Give feedback.
-
Im seeing some conflicting info regarding using the Jamf-Pro script and parameters:
The Wiki states:
"Just to reiterate, any parameter can be supplied in any order in the policy's Script Parameters section, and only one parameter can be supplied into each Parameter field."
However the sample script says:
"You can use Jamf Pro parameters 1-10 to supply arguments to erase-install,
and you can supply multiple arguments in one Jamf Pro parameter."
Wondering which is accurate?
Beta Was this translation helpful? Give feedback.
All reactions