Skip to main content
Question

Jamf Connect Notify + Dockutil

  • July 31, 2020
  • 6 replies
  • 24 views
M
Forum|alt.badge.img+9

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

    Cayde-6
    Forum|alt.badge.img+22
    • Cayde-6
    • Honored Contributor
    • July 31, 2020

    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.

      M
      Forum|alt.badge.img+9
      • mlambert
      • Author
      • Contributor
      • July 31, 2020

      Awesome, thanks!

        M
        Forum|alt.badge.img+9
        • mlambert
        • Author
        • Contributor
        • July 31, 2020

        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
        Forum|alt.badge.img+22
        • Cayde-6
        • Honored Contributor
        • August 1, 2020

        I'll check my daemon on Monday for you

        Cayde-6
        Forum|alt.badge.img+22
        • Cayde-6
        • Honored Contributor
        • August 2, 2020
        <?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>
        M
        Forum|alt.badge.img+9
        • mlambert
        • Author
        • Contributor
        • August 3, 2020

        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

        Terms & ConditionsCookie settingsAccessibility statement