Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1.1 beta 455 works - 496 fails to run #73

Open
jakthemac opened this issue Jan 15, 2025 · 3 comments
Open

1.1 beta 455 works - 496 fails to run #73

jakthemac opened this issue Jan 15, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@jakthemac
Copy link

jakthemac commented Jan 15, 2025

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>

@scriptingosx scriptingosx added the Support support question label Jan 16, 2025
@scriptingosx
Copy link
Collaborator

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.)

@jakthemac
Copy link
Author

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..

@scriptingosx scriptingosx added bug Something isn't working and removed Support support question labels Jan 16, 2025
@scriptingosx
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants