Through testing Notify I seem to have got my Mac stuck in an infinate loop... It never completes from the attached image.
I manually installed a custom pkg with a post install script to activate the jamf notify machanism however I dont this it ingested the Notify script to tell it what to do. So now it is stuck here. I have tried reboot several times to no avail. Can someone help me recover from this?
I really appreciate for your help :)
The first link you senthttps://www.jamf.com/blog/zero-touch-deployment-with-jamf-pro-and-jamf-connect/ , its exactly wat is configured from our side.
This works very fine.
The configruration profiles are scoped directly to the prestage enrollments. But to scope it to the prestage enrollment, we have smartgroups.
My first try was also with depnotify, but I was unable to configure it.
Here is my script:
#!/bin/bash
#Variable List:
JAMFBIN="/usr/local/bin/jamf"
# Notify Mechanism:
# Change the default text displayed to the user
echo "Command: Image: /usr/local/Connect_Notify_Script/Logo_Farbig.png" >> /var/tmp/depnotify.log
echo "Command: MainTitle: Welcome to Adcubum!" >> /var/tmp/depnotify.log
echo "Command: MainText: Welcome to your new Mac.\\nSit tight as we do some basic setup to get you ready for success.\\nYou can see the status of the setup on the progress bar below." >> /var/tmp/depnotify.log
# Update the user of the status of the onboarding
echo "Status: Installing Jamf" >> /var/tmp/depnotify.log
# Check the path of the Jamf client binary. If not present yet, wait 2 seconds and
# check again.
until [ -f $JAMFBIN ]
do
echo "Status: Waiting on Jamf" >> /var/tmp/depnotify.log
sleep 2
done
# Notify the user that we will let Jamf Pro take over at this point
echo "Status: Passing command and control to Jamf Pro" >> /var/tmp/depnotify.log
# Call a custom trigger named "JamfConnectLoginInstalled" to start the onboarding
$JAMFBIN policy -event JamfConnectLoginInstalled
don't be confused about the multiple connect, authchanger profiles. They were created today for fixing this issue.
I think, that while updating jamf connect app, the authchanger will be checked and written new. I tested today with multiple configuration profiles and never had any issues after the reboot until I updated jamf connect app.
I am testing from my homeoffice and I do not have any special firewall.
@sam-sand wrote:Do you have the following in the AuthChanger config profile under the "com.jamf.connect.authchanger" Preference Domain?
<?xml version="1.0" encoding="UTF-8"?>
<plist version="1.0">
<dict>
<key>Arguments</key>
<array>
<string>-reset</string>
<string>-JamfConnect</string>
<string>-Notify</string>
</array>
</dict>
</plist>
yes I have this in the configuration profile, which is scoped to the Notify PreStage MacBooks.
and after that, this configuration profile stays on the machines.
Your inputs helped me very well. And I really learned a lot the last two days about jamf CONNECT and Notify
Thank you very much
