Just curious, but why did you decide to beak this up into 3 separate scripts? If the intent of your workflow is to generate a name for the computer using various commands to pull data from the Mac, and then name it, that can all be done within a single script. I'm not sure I see the reason for echoing out strings into files in each script and then pulling them back in to generate a name for the computer.

In any event, the likely issue with your script is that there seems to be a space between the = sign and the $ for the beginning of each command. By doing so, I don't think you're generating any variables. In bash, there needs to be no space between those to create a variable. You should probably also change the singlw quotes around path strings to double quotes.
For example, change:

model= $(cat ‘/name/model.txt' )

to

model=$(cat "/name/model.txt" )

Notice no space after the = sign.

Thanks mm2270.

I broke the scripts up more for learning purposes on my end mostly. Once I get more comfortable with my scripting abilities then I'll combine them. I knew it would be something simple. Thank you for your assistance.

#!/bin/bash

# collect asset tag from user input

while true
do
assetTag=$(/usr/bin/osascript -e 'Tell application "System Events" to display dialog "Enter the asset tag number located on the bottom of your Mac or select Cancel." default answer ""' -e 'text returned of result' 2>/dev/null)
    if [ $? -ne 0 ]     
    then # user cancel
        exit
    elif [ -z "$assetTag" ]
    then # loop until input or cancel
        /usr/bin/osascript -e 'Tell application "System Events" to display alert "Please enter the asset tag number or select Cancel... Thanks!" as warning'
    else [ -n "$assetTag" ] # user input
        break
    fi
done

# submit asset tag to JSS

/usr/local/bin/jamf recon -assetTag "$assetTag"

# determine computer type

if system_profiler SPHardwareDataType | grep MacBook
then
    computerType=LM
else
    computerType=DM
fi

# combine computer type & asset tag to match naming convention & submit name to JSS

/usr/local/bin/jamf setComputerName -name "$computerType$assetTag"

Since you used the term "zero-touch" & I believe you've created some kind of input method for the end user to enter the asset tag I've used those as requirements for this workflow. I know you're experimenting but all of the operations can be performed in 1 script.

1st, it's probably more efficient if you avoid writing out files. That said, if you are going to be generating a lot of data & returning it to the JSS as an extension attribute (or doing something like creating a report for populating a bunch of different extension attributes) writing out to a file & reading from it rather then lengthening the time it takes for the update inventory event at the JSS is a good strategy!

2nd, If the desired result is to both populate the asset tag in the JSS & create a device name in the JSS using the asset tag string you can do this without sending data to the JSS & then getting that data back from the JSS.

Last, I may be missing something (if I am please help us all to learn!) but I am not sure what sysctl command you are using. The sysctl mib needed to get model ID is actually hidden:

Gathering system information in Swift with sysctl

In my example I am using the system_profiler binary. Hope this helps!

Hi there Brock- Thanks for the input. I will definitely give that a go.

The sysctl command that I use (and I bet this is totally not "the correct" way of doing it) is running a "sysctl hw.model", output that to a variable, then I run a grep for the word "MacBook", which the result of the command gets placed into another variable and I just issue a simple boolean if statement. If the result is 1, then it's a macbook, and I will apply the name "LW", otherwise it's not a laptop, and it'll put the name DW.

The light is starting to flicker on in my "programming brain" and I think I might be starting to get the hang of this.

No I actually like that way of getting the model ID. That is probably what is populating system_profiler anyway. There isn't a way (at least on the sysctl man page) to generate the hidden mib so I feel like system_profiler for most scripters would be the easier solution but sometimes Google-fu is the way to go. :) Good luck!

1 last point - if you run this as the payload of a JSS policy you would probably want to add the Maintenance payload set to "Update Inventory". If so, watch out for setting Scope to "All Computers" & Execution Frequency to "Ongoing"...

I actually thought, despite it not showing up on the manpage for sysctl, that the hw.model mib was fairly common knowledge floating around. Perhaps or perhaps not.

FWIW, there's also ioreg for getting the model identifier.

ioreg -rd1 -c IOPlatformExpertDevice | awk -F'"' '/model/{print $4}'