Jamf Connect Notify + Dockutil

mlambert
New Contributor III

Hopefully someone here has experienced this before. I have a pre-stage setup that installs Jamf Connect Login and then uses the Notify portion to fully configure the system.

One of the problems I'm running into is the policy I use to setup a default dock (using dockutil) for initial setups isn't getting applied. I'm assuming this is because the user hasn't logged in yet. Anyone have recommendations of how to trigger this? I don't want have it run again after the first time, since people will customize it from where it's set.

6 REPLIES 6

Cayde-6
Valued Contributor

It is, we use a launchdaemon that's installed during the notify stage.

The launchdaemon runs a script which waits for the finder process to start before running our dockutil policy.

mlambert
New Contributor III

Awesome, thanks!

mlambert
New Contributor III

Struggling to get this right. I see both of them show up, but the daemon never executes the script

<?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.dock-intune.app</string>

        <key>ProgramArguments</key>
        <array>
            <string>/Library/Scripts/dock-intune.sh</string>
        </array>

        <key>RunAtLoad</key>
        <true/>
</dict>
</plist>

Cayde-6
Valued Contributor

I'll check my daemon on Monday for you

Cayde-6
Valued Contributor
<?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>GroupName</key>
    <string>wheel</string>
    <key>InitGroups</key>
    <false/>
    <key>Label</key>
    <string>LD_Dock_OOBE</string>
    <key>Program</key>
    <string>/usr/local/bin/dock.sh</string>
    <key>RunAtLoad</key>
    <true/>
    <key>StandardErrorPath</key>
    <string>/var/log/LD_Dock_OOBE_error.log</string>
    <key>StandardOutPath</key>
    <string>/var/log/LD_Dock_OOBE.log</string>
    <key>StartInterval</key>
    <integer>5</integer>
    <key>UserName</key>
    <string>root</string>
</dict>
</plist>

mlambert
New Contributor III

Thanks, I ended up getting it to run by adding a launchctl command to load the plist in the policy I was deploying it from