(imported comment written by ericvb91)
Can anyone confirm this working on mac osx 10.5?
(imported comment written by Doug_Coburn)
It looks like there had been an issue with the logic that caused the script to not realize it had correctly determined the OS for Mac and giving the erroneous message. I`ve fixed that and have uploaded a new version.
Updated version 2.1.0.37:
http://support.bigfix.com/download/bes/util/UnixLinuxClientDeployTool-2.1.0.37.zip
Changes:
–Fixed an issue where logic for determing Mac OSX was not being correctly caught
–Updated tool to work with 7.2 version (new command line version of -7 72)
–Updated the InstallBESAgent.sh helper script for installing the BES Agent on all Mac platforms
–Updated logic for doing the OS mapping so that there won’t be confusing errors displayed about files not found.
(imported comment written by Doug_Coburn)
It looks like for some reason on some Windows systems when download the agent files with the Perl Module LWP::Useragent (what I’m using in the script) some of the agent installers are getting corrupted. If this happens to you just download the agent file manually and put it in the same folder as the tool.
For the Mac you have to use the upgrade file which for 72 can be found here:
http://software.bigfix.com/download/bes/72/BESAgent-7.2.2.31-BigFix_MacOSXUpgrade.dmg
(imported comment written by angeand91)
Hi,
I downloaded the ulainstaller-2.1.0.37.exe program but I have some problem to use it.
I run form command line this
ulainstaller-2.1.0.37.exe -v 72 -c config.txt -h hosts.txt
I download the client_files.txt file but I continue to have the message ‘Masthead was not found in this folder’ in ulainstaller.log file. In my directory I don’t see the masthead.afxm file.
How can I do to resolve the problem ?
Thanks for your support
Andrea
(imported comment written by angeand91)
I copied actionsite.afxm and I renamed it in masthead.afxm. Now it seems work.
I tried the application on UBUNTU 8.10 machine but I have the errore below:
C:\appo\UnixLinuxDeployTool>ulainstaller-2.1.0.37.exe -v 72 -c config.txt -h hosts.txt
Determing remote O/S: 10.180.43.170
Trying SSH:
Success
Use of uninitialized value in string eq at ulainstaller-2.pl line 326.
Use of uninitialized value in hash element at ulainstaller-2.pl line 341.
Use of uninitialized value in concatenation (.) or string at ulainstaller-2.pl line 341.
Downloading the BES Agent.
Use of uninitialized value in hash element at ulainstaller-2.pl line 371.
Use of uninitialized value in concatenation (.) or string at ulainstaller-2.pl line 371.
Use of uninitialized value in hash element at ulainstaller-2.pl line 373.
Use of uninitialized value in concatenation (.) or string at ulainstaller-2.pl line 373.
Use of uninitialized value in string eq at ulainstaller-2.pl line 379.
Use of uninitialized value in hash element at ulainstaller-2.pl line 382.
Use of uninitialized value in concatenation (.) or string at ulainstaller-2.pl line 382.
http://software.bigfix.com/download/bes/72/
Use of uninitialized value in hash element at ulainstaller-2.pl line 386.
Use of uninitialized value in -f at ulainstaller-2.pl line 386.
Use of uninitialized value in hash element at ulainstaller-2.pl line 387.
Use of uninitialized value in list assignment at /<C:\appo\UnixLinuxDeployTool\ulainstaller-2.1.0.37.exe>LWP/UserAgent.pm line 389.
Use of uninitialized value in scalar assignment at /<C:\appo\UnixLinuxDeployTool\ulainstaller-2.1.0.37.exe>Carp/Heavy.pm line 104.
A :content_file value can’t be undef at ulainstaller-2.pl line 387
Is there the Agent for Ubuntu ?
Thanks
Andrea
(imported comment written by Doug_Coburn)
Hello angeand,
Ubuntu/Debian is not currently a supported platform for BigFix so there is no supported agent available for it. The tool I wrote will only work with supported platforms.
Doug
(imported comment written by darrelh91)
What would it take for BFX to offically support the unix client deploy tool…you can take a portion of my support fees and give to Doug =)
(imported comment written by Doug_Coburn)
Hah! I like the idea, all though I don’t think they’ll pass me the support fees, there have been talks about doing this but not formal decision yet.
Doug
(imported comment written by Doug_Coburn)
Hi All,
updated InstallBESAgent.sh for Mac installs. Please replace the previous one that is in the zip with the attached version.
(imported comment written by louspag91)
Hello, I am having a problem when I execute ulainstaller-2.1.0.37.exe -v 72 -h hosts.txt -c config.txt
It executes fine but nothing really happens. I get trying SSH followed by success and then the prompt. In reading the posts I do have the correct masthead and even copied the actionsite.afxm to masthead.afxm just incase and still have the same problem. The agents I need are in the same folder and the cleint_files.txt does get populated.
The log states the following(see below). What am I missing? The desktop machine I’m using is a wintel XP. Do I need something else, like perl installed? Thanks for the help
Starting
client_files.txt does not exist, downloading.
(imported comment written by SystemAdmin)
Trying this tool for the first time. Keep getting this after steping through the install twice.
Trying SSH:
Success
InstallBESAgent.sh | 1 kB | 1.5 kB/s | ETA: 00:00:00 | 100%
BESAgent-7.2.2.31-BigFix_ | 10023 kB | 5011.6 kB/s | ETA: 00:00:00 | 100%
masthead.afxm | 8 kB | 8.9 kB/s | ETA: 00:00:00 | 100%
Connecting to system with SSH.
hdiutil: attach failed - not recognized
cp: /BESAgent.pkg: No such file or directory
cp: /tmp/BESAgent.pkg/Contents/Resources/actionsite.afxm: No such file or directory
hdiutil: detach failed - No such file or directory
installer: Error the package path specified was invalid: ‘/tmp/BESAgent.pkg’.
Any ideas?
(imported comment written by NoahSalzman)
Are you using ulainstaller-2.1.0.37? Are you using the InstallBESAgent.sh posted in this thread on June 17th?
However, the likely case is that you are using a version of Mac OS X that has a hdiutil (a command line utility for mounting disk mages) that is “not recognizing” the BES Agent disk image.
Try this on the command line of your Mac:
hdiutil verify -verbose /tmp/BESAgent-7.2.2.31-BigFix_MacOSXUpgrade.dmg
(imported comment written by SystemAdmin)
Noah,
We are using ulainstaller-2.1.0.37 and InstallBESAgent.sh posted in this thread on June 17th.
We tried both mac clients BESAgent-7.2.2.31-BigFix_MacOSXUpgrade.dmg and BESAgent-7.2.2.38-BigFix_MacOSXUpgrade.dmg. The process fails when using BESAgent-7.2.2.31-BigFix_MacOSXUpgrade.dmg but it succeds with BESAgent-7.2.2.38-BigFix_MacOSXUpgrade.dmg.
When I run the verify on BESAgent-7.2.2.31-BigFix_MacOSXUpgrade.dmg, that seems to work. I have a couple more test machines and will try to dupilicate again.
What I found was that once we run the the “ulainstaller-2.1.0.37.exe -v 72 -c config.txt -h hosts.txt” from a Windows machine and it fails, the 3 files (BESAgent-7.2.2.31-BigFix_MacOSXUpgrade.dmg ,InstallBESAgent.sh ,actionsite.afxm ) are copied succesfully, but results in the error posted previously. Using BESAgent-7.2.2.38-BigFix_MacOSXUpgrade.dmg fixes the issue.
Your “ulainstaller-2.1.0.37.exe” still pulls the .31 version of the Mac OSX client so we had to manually modify the client_files.txt file to pull the .38 version.
(imported comment written by dperez91)
Doug,
I get the follow error trying to install on a redhat box.
/tmp/BESAgent-7.2.5.22.i386_rhe4.rpm: not an rpm package (or package manifest):
I logged on to the box and did a file on the rpm and it looks like it is corrupted during transfer.
root@bigfix tmp
file BESAgent-7.2.5.22.i386_rhe4.rpm
BESAgent-7.2.5.22.i386_rhe4.rpm: data
Here is a file on an RPM i downloaded directly from the client
BESAgent-7.2.5.22.i386_rhe4.rpm: RPM v3 bin i386 BESAgent-7.2.5.22-1
(imported comment written by Doug_Coburn)
Hi All,
A new version of the tool has been created of the Unix/Linux/Mac Client Deploy tool which will now have a GUI interface! It can be downloaded from http://dactbc.com/bigfix/ULAInstallerGUISetup.msi
Summary:
The *NIX Client Deploy tool allows you to be able to deploy the BigFix Agent to supported Unix, Linux, or Mac devices using ssh/scp. In this latest revision there is now a GUI front end that walks you through the different options for deploying the BigFix Agent out to your clients. From the one tool you can push the agent out using ssh/scp to multiple systems on multiple platforms as long as they have the same username/password. If the username and password is not the same you will need to rerun the tool for each username/password combination.
http://dactbc.com/bigfix/pics/welcome.jpg
How to use the tool:
- Input your username and password. This must be a user with the ability to install packages and start the agent, the agent runs as root. You will also need to specify the location of the actionsite.afxm (or also called masthead.afxm). This can be found on the server.
http://dactbc.com/bigfix/pics/userinfo.jpg
- Here you can select which version of the client to install. The tool automatically downloads a file called client_files.txt to fine the names of the latest versions of the agent installer. If you do not have internet access you will need to precache the file and agent binaries.
a. Clientsettings.cfg or besrelay.cfg this file should be in the same format as the ones used for the Windows Client Installer (http://support.bigfix.com/cgi-bin/kbdirect.pl?id=454 and http://support.bigfix.com/cgi-bin/kbdirect.pl?id=244)
b. Attempt to use sudo – If you are not using root to do the install process the echo PASSWORD | sudo -S for scripting using sudo must work. If this is not supported on the platform you are installing on then you will have to use the root account for installing.
c. The Reinstall options allows you to upgrade from a previous version if you did not want to use the Fixlet to upgrade for some reason.
d. Use External Tools uses pscp and plink from http://www.chiark.greenend.org.uk/~sgtatham/putty/ for the connections for ssh and scp instead of being handled within the code.
http://dactbc.com/bigfix/pics/sudo.jpg
- The host list currently only supports one entry per line and does not currently support doing cidr or ranges.
http://dactbc.com/bigfix/pics/hosts.jpg
- In the computer selection screen the Client Deploy Tool attempts to connect to the systems specified in the host entry screen. If it is able to connect using ssh and the credentials provided it will figure out what platform the IP (or hostname) is and whether or not the client is installed. Only the computers highlighted when you click next will show up on the Installation screen which is the next screen.
http://dactbc.com/bigfix/pics/select.jpg
 
- The installation screen allows you to start the install process. If the BigFix agent package is not already downloaded the tool will automatically download the agent binaries from our website. If you do not have Internet access you will need to precache the files manually.
(imported comment written by BenKus)
Hi everybody,
See http://forum.bigfix.com/viewtopic.php?pid=21689#p21689
This tools is now available at:
http://support.bigfix.com/labs/Unix_Client_Deploy_Tool.html
Ben
(imported comment written by freespirit198591)
Hi, even I am getting this message “Masthead not found” in ulainstaller-2.1.0.37, Any help would be appreciated…
(imported comment written by MrBB91)
I am also having difficulty with the ulainstaller-2.1.0.37. I installed it to the BigFix Enterprise directory, but it just crashes when I try to run it. I assume I am doing something wrong here, but I am simply trying to install and run it. I am on version 8.1.608.0
Thank you,
Brett
(imported comment written by Jinggo)
hi all,
i have problem with push agent for RHEL, the problem is my customer can’t use root for push agent. i have request to create new account, but i have log issue :
Executing: echo XXXXXXXX | sudo -S chmod 777 /tmp
sudo: sorry, you must have a tty to run sudo
Copying Files
Copying BESAgent-9.0.649.0-rhe5.x86_64.rpm
Copying Masthead file
Connecting to system with SSH.
Executing: echo XXXXXXXX | sudo -S rpm -ivh /tmp/BESAgent-9.0.649.0-rhe5.x86_64.rpm
sudo: sorry, you must have a tty to run sudo
Executing: echo XXXXXXXX | sudo -S mkdir -p /etc/opt/BESClient; mv /tmp/actionsite.afxm /etc/opt/BESClient/actionsite.afxm
sudo: sorry, you must have a tty to run sudo
mv: cannot move /tmp/actionsite.afxm' to/etc/opt/BESClient/actionsite.afxm’: No such
anyone can help?