jamf/Setup-Manager
1
0
Fork 0
mirror of https://github.com/jamf/Setup-Manager.git synced 2026-02-03 14:13:24 +00:00
Code Issues 37 Actions Packages Projects Releases Wiki Activity

1.1 beta 455 works - 496 fails to run #92

New Issue
Closed
opened 2026-01-19 18:31:30 +00:00 by michael · 3 comments
michael commented 2026-01-19 18:31:30 +00:00
Owner
Copy Link

Originally created by @jakthemac on GitHub.

I have beta 455 working fine.

deploying 1.1 - 496 and it fails to run, its installed ok.

I note that the launch deamon plists that are installed are different..

455

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Label</key>
	<string>com.jamf.setupmanager</string>
	<key>Program</key>
	<string>/Applications/Utilities/Setup Manager.app/Contents/MacOS/Setup Manager</string>
	<key>RunAtLoad</key>
	<true/>
	<key>StandardErrorPath</key>
	<string>/Library/Logs/Setup Manager.log</string>
	<key>StandardOutPath</key>
	<string>/Library/Logs/Setup Manager.log</string>
</dict>
</plist>

496

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Label</key>
	<string>com.jamf.setupmanager</string>
	<key>ProgramArguments</key>
	<array>
		<string>/Applications/Utilities/Setup Manager.app/Contents/MacOS/Setup Manager</string>
		<string>-runningAt</string>
		<string>enrollment</string>
	</array>
	<key>RunAtLoad</key>
	<true/>
	<key>StandardErrorPath</key>
	<string>/Library/Logs/Setup Manager.log</string>
	<key>StandardOutPath</key>
	<string>/Library/Logs/Setup Manager.log</string>
</dict>
</plist>
Originally created by @jakthemac on GitHub. I have beta 455 working fine. deploying 1.1 - 496 and it fails to run, its installed ok. I note that the launch deamon plists that are installed are different.. 455 ``` <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>com.jamf.setupmanager</string> <key>Program</key> <string>/Applications/Utilities/Setup Manager.app/Contents/MacOS/Setup Manager</string> <key>RunAtLoad</key> <true/> <key>StandardErrorPath</key> <string>/Library/Logs/Setup Manager.log</string> <key>StandardOutPath</key> <string>/Library/Logs/Setup Manager.log</string> </dict> </plist> ``` 496 ``` <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>com.jamf.setupmanager</string> <key>ProgramArguments</key> <array> <string>/Applications/Utilities/Setup Manager.app/Contents/MacOS/Setup Manager</string> <string>-runningAt</string> <string>enrollment</string> </array> <key>RunAtLoad</key> <true/> <key>StandardErrorPath</key> <string>/Library/Logs/Setup Manager.log</string> <key>StandardOutPath</key> <string>/Library/Logs/Setup Manager.log</string> </dict> </plist> ```
michael added the bug label 2026-01-19 18:31:30 +00:00
michael commented 2026-01-19 18:31:30 +00:00
Author
Owner
Copy Link

@scriptingosx commented on GitHub:

yes, they are different. They needed to change to support new features.

v1.1 has been deployed and ran successfully with this LaunchDaemon on literally thousands of devices across many organizations. We would need more than "it fails to run" to figure out what is wrong with your deployment. log would be helpful.

Are you certain it installs? there was a bug in Jamf Pro 11.11.x where packages wouldn't get the md5 hash and then not install during prestage?

For support questions, I generally recommend joining the #jamf-setup-manager channel in the MacAdmins Slack. (Free signup here.)

@scriptingosx commented on GitHub: yes, they are different. They needed to change to support new features. v1.1 has been deployed and ran successfully with this LaunchDaemon on literally thousands of devices across many organizations. We would need more than "it fails to run" to figure out what is wrong with your deployment. log would be helpful. Are you certain it installs? there was a bug in Jamf Pro 11.11.x where packages wouldn't get the md5 hash and then not install during prestage? For support questions, I generally recommend joining the #jamf-setup-manager channel in the MacAdmins Slack. ([Free signup here.](https://macadmins.org))
michael commented 2026-01-19 18:31:30 +00:00
Author
Owner
Copy Link

@scriptingosx commented on GitHub:

Bit more info after discussion on MacAdmins Slack. Problem occurs on Intel VM (in VMware Fusion Pro) with macOS 15.x. I thought I understood what but then could recreate the issue on my Intel VM with macOS 15.2.

Testing will occur on physical devices to further isolate the issue.

@scriptingosx commented on GitHub: Bit more info after discussion on MacAdmins Slack. Problem occurs on Intel VM (in VMware Fusion Pro) with macOS 15.x. I thought I understood what but then could recreate the issue on my Intel VM with macOS 15.2. Testing will occur on physical devices to further isolate the issue.
michael commented 2026-01-19 18:31:30 +00:00
Author
Owner
Copy Link

@jakthemac commented on GitHub:

Hi, thanks for the reply. Yes.. the app installs ok. instance is latest JAMF cloud.. there are no logs.. the log file is created, but it's empty. By fails to run, I mean with the beta.. this launches as expected.. and runs through the config profile settings, with 496.. the pkg installs.. but it does not launch.. the only difference here is the pkg that is installed.. if I add the beta to prestage it works.. if I add 496.. it doesn't run..

@jakthemac commented on GitHub: Hi, thanks for the reply. Yes.. the app installs ok. instance is latest JAMF cloud.. there are no logs.. the log file is created, but it's empty. By fails to run, I mean with the beta.. this launches as expected.. and runs through the config profile settings, with 496.. the pkg installs.. but it does not launch.. the only difference here is the pkg that is installed.. if I add the beta to prestage it works.. if I add 496.. it doesn't run..
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
duplicate
enhancement
enhancement
question
Support
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
michael
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: jamf/Setup-Manager#92
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?