I have been trying to get Barracuda Device Manager installed from JAMF on our companies macbooks. In order to install it manually you have run a script that Barracuda provides. I have no issues doing the manual install but I want to automate it now. I have tried just uploading the pkg I downloaded from Barracuda but that doesn't work. I tried to run the script manually before I installed from JAMF and it doesn't work. I uploaded the script and installed from JAMF that doesn't work. I have tried adding the script to the pkg when creating the software policy that doesn't work. I also used JAMF composer to create the pkg and tried all of the steps I mentioned before. I did check the logs I found this: Installing at base path / installer: The install failed. The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. So right now I am thinking of a couple of things that maybe happening it may be something on my end where some port is getting blocked when installing from JAMF or I need to reach out to Barracuda to get some help with this issue. The issue with the my 1st thought is if the a port is being blocked then I should run into the same error when doing it manually but I could be wrong. I just want to see if anybody else has run into this issue with Barracuda.
Unable to install Barracuda Device Manager from JAMF
+3Best answer by AJPinto
My suggestion with all software you are paying for (even if the software is free with the hardware you are buying) is to contact the manufacture for assistance if you have any issues.
It is likely very possible to deploy this, but without knowing a lot more about the application and access to the source files all I have is speculation. My suggestion is to look in to catching the zip file, and using a terminal command to run the SetupDM file and see where that gets you. However, unless the SetupDM has CLI switches for a silent install you won't get very far. Considering the macOS documentation is kinda tacked along side the Windows documentation, my hopes are not high you will have an easy path forward.
+7This should be a fairly straightforward process, but you probably need to modify the script that you were given.
There are a couple of ways you could do this. Probably the easiest way to, come to mind, is to package the software so that it is available in some location on the machine. This isn't going to install it, it's just to preload the installer that they're providing.
Once the package is in a known location on the device, you can then run the script. This is where you may need to modify the script. The script might be expecting the package to be somewhere specific. If so, you'll have to update the locations for wherever you put the package that's ready to be installed.
There's also a possibility that they're expecting you to run this script as the user and not as root. Remember, all scripts executed by Jamf are run as root. Again, you may have to mess with this a little for your script.
This is just an example, and you will have to modify it for your use.
#!/bin/bash
# Get the currently logged-in user
loggedInUser=$(stat -f "%Su" /dev/console)
# Check if a user is logged in
if [ "$loggedInUser" == "root" ] || [ -z "$loggedInUser" ]; then
echo "No user is currently logged in. Exiting."
exit 1
fi
# Example command to run as the logged-in user
# Replace `command_to_run` with the actual command you want to execute
sudo -u "$loggedInUser" bash -c 'command_to_run'
# Example: Running a script located in /Users/Shared/script.sh
# sudo -u "$loggedInUser" bash -c "/Users/Shared/script.sh"
echo "Script executed as $loggedInUser"
With the second part of the loggedInUser script, you could also put the script they want you to run in the same place as the installer, then execute it. I haven't installed that particular application, but it's not uncommon that the script and installer just need to be in the same place.
+26My suggestion with all software you are paying for (even if the software is free with the hardware you are buying) is to contact the manufacture for assistance if you have any issues.
It is likely very possible to deploy this, but without knowing a lot more about the application and access to the source files all I have is speculation. My suggestion is to look in to catching the zip file, and using a terminal command to run the SetupDM file and see where that gets you. However, unless the SetupDM has CLI switches for a silent install you won't get very far. Considering the macOS documentation is kinda tacked along side the Windows documentation, my hopes are not high you will have an easy path forward.
+3This should be a fairly straightforward process, but you probably need to modify the script that you were given.
There are a couple of ways you could do this. Probably the easiest way to, come to mind, is to package the software so that it is available in some location on the machine. This isn't going to install it, it's just to preload the installer that they're providing.
Once the package is in a known location on the device, you can then run the script. This is where you may need to modify the script. The script might be expecting the package to be somewhere specific. If so, you'll have to update the locations for wherever you put the package that's ready to be installed.
There's also a possibility that they're expecting you to run this script as the user and not as root. Remember, all scripts executed by Jamf are run as root. Again, you may have to mess with this a little for your script.
This is just an example, and you will have to modify it for your use.
#!/bin/bash
# Get the currently logged-in user
loggedInUser=$(stat -f "%Su" /dev/console)
# Check if a user is logged in
if [ "$loggedInUser" == "root" ] || [ -z "$loggedInUser" ]; then
echo "No user is currently logged in. Exiting."
exit 1
fi
# Example command to run as the logged-in user
# Replace `command_to_run` with the actual command you want to execute
sudo -u "$loggedInUser" bash -c 'command_to_run'
# Example: Running a script located in /Users/Shared/script.sh
# sudo -u "$loggedInUser" bash -c "/Users/Shared/script.sh"
echo "Script executed as $loggedInUser"
With the second part of the loggedInUser script, you could also put the script they want you to run in the same place as the installer, then execute it. I haven't installed that particular application, but it's not uncommon that the script and installer just need to be in the same place.
I will have to try that as the next step in the process
+3My suggestion with all software you are paying for (even if the software is free with the hardware you are buying) is to contact the manufacture for assistance if you have any issues.
It is likely very possible to deploy this, but without knowing a lot more about the application and access to the source files all I have is speculation. My suggestion is to look in to catching the zip file, and using a terminal command to run the SetupDM file and see where that gets you. However, unless the SetupDM has CLI switches for a silent install you won't get very far. Considering the macOS documentation is kinda tacked along side the Windows documentation, my hopes are not high you will have an easy path forward.
I am thinking that this is ultimately what I will have to do. But wanted to see if there is anything else before I engage them as some of colleagues have reached out them on other issues and they respond slowly sometimes
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.