Hi all,

I’m just about 100% sure this isn’t a Jamf issue, but wanted to see if anyone else had any thoughts. We are attempting to get Nexthink installed on our Macs through Jamf. I created a folder in /private/tmp/Nexthink and put the csi.app and the customer key.txt file there and created a pkg through Composer and uploaded it to Jamf. I created a very simple install script to deploy with the pkg file:

#!/bin/bash
/private/tmp/Nexthink/csi.app/Contents/MacOS/csi \
  -address like.to.our.portalurl \
  -tcp_port 443 \
  -key "/private/tmp/Nexthink/Customer Key.txt" \
  -use_assignment=true \
  -ra_execution_policy=signed_trusted_or_nexthink \

Nexthink installs and Jamf reports back that it completed with all the correct settings including the Engine IP address and Customer key. However, when looking at the local config.json file the customer key has added in a “\” character anytime there is a “/” character in the customer key (so it now shows \/), and causes it to not report in, if I view the log on the deployment in Jamf, the “\” character doesn’t show up.

Does anyone have any thoughts on this? I’ve tried opening the customer key before adding it to /tmp/ and find and replace the “/” character to hopefully rule out any syntax that was in the key but no matter what I do, it seems to always add the “\” character. I’ve downloaded the Customer Key.txt file and tried changing to csv as well, but I’m running out of ideas while I wait for Nexthink support to get back to us.