Skip to main content
Solved

need help with script

DBrowning
Forum|alt.badge.img+24

have a script that I'm calling via Self Service and it works perfectly. When I have another policy call the same script, it doesn't work quite right. I'll see in the logs a line:271:370: execution error: No user interaction allowed. (-1713)

below is the script. It has Apple Script at the beginning to popup a window with a list of selections and then ends with basic shell scripting.

#!/bin/sh

nameCode=`/usr/bin/osascript <<EOT
set locations to {"Office 1", "Office 2", "Office 3"}

set choice to (choose from list locations with prompt "Please select the Office that best describes your location")
set city to the result
set code to city as text

if (code = "Office 1") then
    set nameCode to "DAL"
else if (code = "Office 2") then
    set nameCode to "ATL"
else if (code = "Office 3") then
    set nameCode to "BUR"
else
    set nameCode to "CORP"
end if
EOT`

sn=$(system_profiler SPHardwareDataType | awk '/Serial/ {print $4}' | cut -c 5-)
model=$(system_profiler SPHardwareDataType | awk '/Model Name/ {print $3}')

if [[ $model == "MacBook" ]]; then
    modelCode="L"
else
    modelCode="W"
fi
os="mac"

computerName=$modelCode$nameCode$os$sn

echo "computerName has been set to: $computerName"

networksetup -setcomputername $computerName
scutil --set LocalHostName $computerName
scutil --set HostName $computerName
sudo defaults write /Library/Preferences/SystemConfiguration/com.apple.smb.server NetBIOSName $computerName

Best answer by joshuasee

The error is likely triggered by the "choose from list" command, which wants to work in the GUI, which is often forbidden by osascript and restricted by execution context. Wrappering osascript in a bash shell usually helps, but not always, as you discovered.

First, try having Self Service pop up the list. If that doesn't work, try the Launch Services command line interface to get in the correct context. Both tweaks are shown below, but untested.

nameCode=`/bin/launchctl asuser $(/usr/bin/stat -f%u /dev/console) /usr/bin/osascript <<EOT/usr/bin/osascript <<EOT
set locations to {"Office 1", "Office 2", "Office 3"}

set choice to (tell app "Self Service" to choose from list locations with prompt "Please select the Office that best describes your location")
View original
    Did this topic help you find an answer to your question?

    2 replies

    J
    Forum|alt.badge.img+17
    • joshuasee
    • Valued Contributor
    • 231 replies
    • Answer
    • May 10, 2018

    The error is likely triggered by the "choose from list" command, which wants to work in the GUI, which is often forbidden by osascript and restricted by execution context. Wrappering osascript in a bash shell usually helps, but not always, as you discovered.

    First, try having Self Service pop up the list. If that doesn't work, try the Launch Services command line interface to get in the correct context. Both tweaks are shown below, but untested.

    nameCode=`/bin/launchctl asuser $(/usr/bin/stat -f%u /dev/console) /usr/bin/osascript <<EOT/usr/bin/osascript <<EOT
set locations to {"Office 1", "Office 2", "Office 3"}

set choice to (tell app "Self Service" to choose from list locations with prompt "Please select the Office that best describes your location")
    DBrowning
    Forum|alt.badge.img+24
    • DBrowning
    • Author
    • Esteemed Contributor
    • 668 replies
    • May 10, 2018

    Thank you @joshuasee !!

    I've been wracking my brain as to why this wasn't working. The launchctl command worked.

    Reply


    Most helpful members this week

    Terms & ConditionsCookie settingsAccessibility statement

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings