We will be using it soon on unix, (not sure on linux yet), for inventory purposes mainly.
Yes, I have one customer is using both linux and unix clients.
I worked as the Product Support Expert for the Linux/Unix agent for a while, and there are good number of customers. We have customers who use them as Point of Sale (POS) devices, and customers who use them as desktops, and customers who use them as servers...so a wide variety.
Hopefully some of them speak out here. If not, have your Sales Engineer find a customer who is uses Linux and will talk to you.
we are using it to inventory our linux machines. Our linux users get very, very nervous when anyone wants to install anything on their boxes, so we found a way around it. One of our linux gurus cooked up a shell script that runs the linux inventory scanner without doing an install.
1 of 1 people found this helpful
We use LANDesk agent on around 400 Linux servers, mainly RHEL4 32b & RHEL5 64b.
At the moment we use it for inventory purpose & to launch scripts on all servers. We intend to go for OS Deployment.
The main issue we have is that our machine are quite heterogenous as a configuration so we got a lot of issues. Also, Linux is not as known as windows environment within the support or community and our case / request may be very long to be solved...
would you be willing to share the script that performs the linux inventory scanner without doing an install?
Sanitized to protect the server names......
# Landesk Linux desktop inventory script
# Exit out if the script is not being run by superuser
if [ $UID != 0 ]
then echo "This script must be run by root"
#grab a fresh copy of linuxscan script and put in /tmp
chmod +x linuxscan.sh
#add cron job for weekly scans at 10pm on Mondays
cat > /etc/cron.d/landesk << EOF
00 22 * * * root /usr/local/bin/linuxscan.sh
#create a temp copy of ldiscan and make it executeable
chmod +x /tmp/ldiscan
#start the inventory scan passing the coreserver FQDN and location of the ldappl.conf file
/tmp/ldiscan -ntt=coreserver.fqdn -i=/tmp/ldappl.conf
#remove temp files used to run scan
For security reasons, you should probably also create a hash of the file. Then compare the hash before running it. Not only does this prevent someone from replacing the ldiscan file with a malicious one, but it prevents trying to run a partial or corrupted download.