- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 04-04-2018 05:22 AM
I'm in the process of scripting deployments of our Jamf Pro Servers (RHEL6) and I keep getting prompted with this:
To be installed into /usr/local/jss:
* Tomcat 8.0.50
* Jamf Pro
* Jamf Pro Database Utility
*
* NOTE: When upgrading to Tomcat 8 for the first time, the account and group named 'tomcat7' will be renamed to 'jamftomcat'
Proceed? (y/n):
Is there any way to run the installer script without prompts or with an answer of 'y' to the prompt?
thanks,
Jack
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 04-04-2018 12:51 PM
I chatted with support and they pointed me to files in the archive. Running the installer command with --info dumps all of the information in the makeself archive.
[root@myserver build]# ./jamfproinstaller.run --info
Identification: Jamf Pro Installer
Target directory: build
Uncompressed size: 170720 KB
Compression: gzip
Date of packaging: Fri Mar 23 18:35:03 UTC 2018
Built with Makeself version 2.2.0 on
Build command was: /usr/bin/makeself
"build"
"artifacts/jamfproinstaller-10.3.0-t1521825567.run"
"Jamf Pro Installer"
"bash"
"install.sh"
Script run after extraction:
bash install.sh
build will be removed after extraction
The install.sh command takes a -y, disabling interactive mode and answering yes where applicable. So, my deploy 'script'* will build the archive with the correct arguments and then deploy.
~/makeself-2.3.1/makeself.sh build jps.run "Jacks JPS Installer" bash install.sh -y
This actually works out better as I can make other changes to the test deployments at the same time.
- script is in quotes as I'm using an ansible playbook to do the work.
I hope this helps someone!
Jack

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 04-04-2018 10:36 AM
I’m sure someone will chip in with a more elegant solution, however in a pinch you can pipe the command ‘yes’ (man yes for details) to your install script call. This does as you suggest and just answers yes to any question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 04-04-2018 12:51 PM
I chatted with support and they pointed me to files in the archive. Running the installer command with --info dumps all of the information in the makeself archive.
[root@myserver build]# ./jamfproinstaller.run --info
Identification: Jamf Pro Installer
Target directory: build
Uncompressed size: 170720 KB
Compression: gzip
Date of packaging: Fri Mar 23 18:35:03 UTC 2018
Built with Makeself version 2.2.0 on
Build command was: /usr/bin/makeself
"build"
"artifacts/jamfproinstaller-10.3.0-t1521825567.run"
"Jamf Pro Installer"
"bash"
"install.sh"
Script run after extraction:
bash install.sh
build will be removed after extraction
The install.sh command takes a -y, disabling interactive mode and answering yes where applicable. So, my deploy 'script'* will build the archive with the correct arguments and then deploy.
~/makeself-2.3.1/makeself.sh build jps.run "Jacks JPS Installer" bash install.sh -y
This actually works out better as I can make other changes to the test deployments at the same time.
- script is in quotes as I'm using an ansible playbook to do the work.
I hope this helps someone!
Jack

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 04-27-2018 01:30 PM
Thanks for sharing, Looks like you have been making more progress than me!
