Casper 8.x -> 9.x Upgrade: JAMFHelper Utility Dialog Failures

clifhirtle
Contributor II

Anyone seen jamfHelper script failures after moving from 8.x to 9.x?

I'm seeing my existing jamfHelper dialog scripts (such as the one listed below) failing after moving from 8.x to 9.x JSS. This appears to happen specifically in script parameters with spaces in them, even given quoting. This was never a problem in 8.x, yet 9.x seems to change that.

Image Example:

external image link

Script Example:

#!/bin/sh

#### Casper User Dialogue (Utility Style)

#### Read in the parameters
mountPoint=$1
computerName=$2
username=$3
title=$4                # "string" Sets the window's title
heading=$5              # "string" Sets the heading of the window
description=$6          # "string" Sets main contents of window 
icon=$7                 # path Sets windows image filed to image located at specified path
button1=$8              # "string" Creates button with label (default button)
button2=$9              # "string" Creates button with label

#### Preconfigured Settings
dButton="1"                   # Sets default button to button1. Responds to "return"
windowType="utility"      # [hud | utility | fs]

/Library/Application Support/JAMF/bin/jamfHelper.app/Contents/MacOS/jamfHelper -windowType "$windowType" -windowPosition "$windowPosition" -title "$title" -heading "$heading" -description "$description" -icon "$icon" -button1 "$button1" -button2 "$button2" -defaultButton "$dButton" -windowType "$windowType" -startlaunchd

exit 0
1 REPLY 1

clifhirtle
Contributor II

Update: just got word back from JAMF Support that this is indeed a bugger in current 9.2.3 release. Hope to see resolution in upcoming release, but in meantime merely entering even a " " space in the empty parameter value will get around the issue of the JSS bumping the parameter values up one. Auditing the P values of our current scripts should be enough to get around this for now.