(imported topic written by mc116991)
I was wondering if there is a client deploy tool for non-Windows systems? I need to deploy the agent to over 150 systems and they are an assorted flavor of Unix / Linux. If there is no tool, as I suspect, are there plans for one or does anyone have any scripts i can use to deploy? Suggestions are very welcome.
Thanks!
(imported comment written by mc116991)
Anyone?? Going once, twice???
(imported comment written by Doug_Coburn)
Hello,
I’ve just about finished a script that I’ve been working on and will post it later today.
Thanks,
Doug
(imported comment written by mc116991)
Awesome!
(imported comment written by Doug_Coburn)
Anyone who gets a chance to try my tool please give me feedback on how well it works for you!
Thanks,
Doug
(imported comment written by Doug_Coburn)
More Info:
Uses:
This can be used to deploy the BES Agent to multiple remote non-Windows systems. Currently it can only do one platform at a time but this does mean you could automate deploying the BES Agent per O/S. The default options for the tool uses SSH and SCP to copy the needed files to the remote machine and configure the install. Other options include using Telnet/NFS, Telnet/Custom Command, and SSH/Custom Command to try to give as many ways to deploy the agent as possible.
Changes:
Added more error checking
Added verbose messaging to help point the end user to the proper use of the tool if they make a mistake.
Optimized the way the code was written to make things less error prone
Made the config file a configurable variable with -c.
Changed the tool to not have the filenames hard coded into the file so that as we release new agents it is easier to have the tool continue to work with little to no changes.
Added -v flag for versions 6 and 7
Fixes:
Fixed an issue where if you used the -o flag and a config file most of the other settings got lost.
Fixed issues where the custom command logic was not being detected correctly.
Fixed a problem where if you tried to use telnet it would not actually go down the correct path.
Added the support for using a custom command with ssh which had been left out.
Updated usage information.
You can do successfully use the Command Line Options to deploy to one agent using telnet/nfs or SSH/SCP.
Correct logic for using sudo during the process but this still needs to be tested across all non-Windows platforms.
Again anyone whose uses this please inform me of Questions/Problems with the tool so that I can continue to work to improve this for everyone!
(imported comment written by saravanan@safezone91)
Hi every body,
Is there any options for remote client deploy for non-windows, ie ., linux, aix and other platforms. Is bigfix detect other softwares running on linux machines, with details., I wnt details Any body help me.,
Saravanan.,
(imported comment written by saravanan@safezone91)
Is there any options for remote client deploy for non-windows, ie ., linux, aix and other platforms. Is bigfix detect other softwares running on linux machines, with details., Oracle detection, Wepsphere software etc, I wnt details Any body help me.,
Saravanan
(imported comment written by BenKus)
Hi Saravanan,
See http://support.bigfix.com/bes/install/besclients-nonwindows.html for info about the non-Windows agent. Read the post above for info on how to remotely deploy Unix/Linux agents.
Ben
(imported comment written by Doug_Coburn)
At long last a new version of the Client Deploy Tool for Unix/Linux is available!
It is available here: refer to latest post.
The tool now attempts to connect via SSH and determine the O/S. If SSH is not working it then attempts a telnet connection. I’ve removed the extra options so that the tool is easier to use and since they were no longer needed.
Supported O/S’s:
Solaris 7-9 (Sparc)
Solaris 10 (x86/Sparc)
RedHat Enterprise Linux 3/4/5 (x86/x64)
Fedora Core 3/4/5/6 (x86/x64)
SuSe 9/10 (x86/x64)
HP-UX 11.00/11.11/11.23 (pa-risc)
AIX 5.1, 5.2, or 5.3
OSX 10.3+ (ppc/x86)
Readme:
Usage: ulainstaller.exe -v 6|7 -h hostfile -c config.txt -h Specify the location of the host file which must have one host per line of either hostname or IP address. -c Specify the location of the confiruation file.
" The following files must be in the same folder as the tool: masthead.afxm pscp-bf.exe plink-bf.exe InstallBESAgent.sh(imported comment written by sonny.mcmanigle91)
I wrote a remote installer for MAC 10.x’s… it assumes that ssh is enabled and that the users knows the credentials to an account in group 80 (admin)… if it’ll help let me know… it uses the putty command line tools to run from windows across platform.
(imported comment written by Doug_Coburn)
Hi Sonny,
The tool I’ve posted will also deploy remotely to a Mac using SSH/SCP and using the command line versions of plink and pscp.
Thanks,
Doug
(imported comment written by Doug_Coburn)
Updated version 2.1.0.2: Refer to latest Post
Fixed:
–Uninitialized variable errors when running tool
–The install option for solaris was missing the argument “all” so silent install was not happening
–Added a check that if the client_files.txt exists it would not be redownloaded. This allows pre-caching the client_files.txt and BES Agent files from the internet to get around proxy/airgap situations.
(imported comment written by Doug_Coburn)
Updated version (See Below)
Changes:
–Added support for proxies (not including auto proxy config scripts)
–Changed the behavior to automatically delete and redownload the client_files.txt on each run of the utility. This ensures that the latest version of the file is downloaded so that the latest version of the BES Agents are installed.
–Added option to disable the behavior of automatically redownloading the client_files.txt if you needed/wanted to pre-cache the file beforehand.
Latest Documentation:
#Username
for connection # user=root #Password
for connection # password=bigfix #Attempt to use the sudo command during the install process. This option uses
"echo password | sudo -S"
if #the O/S does not support
this then it will fail. # #sudo=sudo #Specify whether to only use telnet instead of first attempting to
do ssh then telner in O/S detection. #(not recommended) # # 0 = off # 1 = on #telnet=1 #If connecting with telnet the files must be precached in /tmp or the custom option must be used # # 0 = off # 1 = on #cache=1 #The custom option allows you to be able to download/cache the masthead and agent file in another way besides #using the
default scp option. # #custom=wget http:
//SERVER:PORT/masthead/masthead.afxm#mv masthead.afxm /tmp/actionsite.afxm#wget http://support.bigfix.com/download/bes/7/clients/BESAgent-version-os.*# mv BESAgent* /tmp #Turn on Whether to use the proxy or not. # yes=on # no or not set = off #proxy=yes #If proxy is set to proxy=yes then you must specify the server in the following format. #proxy_server=http:
//SERVERNAME:PORT #If your proxy is an authenticated proxy then you must set the username and password variables. #proxy_user=USER #proxy_pass=PASSWORD #This setting controls whether or not to download a
new copy of the client_files.txt on every run of the tool. If you have an old version of the client_files.txt you will be installing an older version of the BES Agent. keep=Keep old file #download or unset=download
new version of client_files.txt client_files=keep #Enable or disable using a
private key file instead of a password. This likely will not work with sudo. #options are
"1" or
"0" #1=on #0=off #key_file_use=1 #If key_file_use is enabled then you must specify the location to the key file. #This must be a key file supported by putty/plink which means the key has to have been made in puttygen (more info: http:
//the.earth.li/~sgtatham/putty/0.60/htmldoc/Chapter8.html#pubkey) #key_file=
"C:\Path\to\key\file.pem"(imported comment written by Doug_Coburn)
Updated version 2.1.0.12: (See below)
Changes:
–Added support for BigFix 7.1 Unix/Linux Agents
–Added InstallBESAgent.sh script back into zip for Mac deployment
–Added the “all” command to the Solaris install commands so that deployment to Solaris machines is automated
I’m on the road at the moment so haven’t gotten to test these changes against my test environment like I normally like to do. Please give the script a shot and let me know if you run into any problems!
Thanks,
Doug
(imported comment written by Doug_Coburn)
Updated version 2.1.0.13:
Changes:
–Fixed automation of Solaris install of the BES Agent
–Fixed automation of AIX install of the BES Agent
Thanks,
Doug
(imported comment written by Doug_Coburn)
Updated version 2.1.0.14: see latest post
Changes:
–Added support so if the password= option in the config file is not selected the script will prompt you for a password.
–Added support to use the clientsettings.cfg (for relay settings only) and the besrelay.cfg when running the script
Information on configuring the .cfg files can be found at
http://support.bigfix.com/cgi-bin/kbdirect.pl?id=244
but again right now the script does not support anything except the relay options!
(imported comment written by Doug_Coburn)
Updated version 2.1.0.19: See below
Changes:
–Fixed an issue where SuSe Enterprise was not being correctly determined
–Added logic so that if an O/S can not be determined the tool will log this but continue on with the next one in the list
–Added more logging
Some more information on how to use the relay settings. I made them to be very similar to how the clientsettings.cfg and besrelay.cfg work for Windows. You are not passing the Unix config file options but passing the options in the same way as the respective files should be configured.
Clientsettings.cfg
Relay IP=http://besrelayserver.domain.com:52311/bfmirror/downloads
Relay IP2=http://besrelayserver2.domain.com:52311/bfmirror/downloads
besrelay.cfg
IP:http://besrelayserver.domain.com:52311/bfmirror/downloads/
IP2:http://besrelayserver2.domain.com:52311/bfmirror/downloads/
(imported comment written by Doug_Coburn)
Updated version 2.1.0.24: See below
Changes:
–Fixed an issue where SuSe was accidentally hard coded as the O/S type causing the wrong agent to be downloaded.
–Fixed finding the new versions of the Mac agent.