Showing results for 
Show  only  | Search instead for 
Did you mean: 
Engaged Sweeper
Simply put, the web site only goes into detail about pushing Windows packages and nothing else.
My shop is 90% Linux/UNIX based, and I have *many* versions of each to keep up to date AND to keep at their "release level." I literally have every supported release version of RHEL, SuSE, Solaris x86 and SPARC, AIX, and others to keep up with. Heartbleed and BEAST were not fun for me *at all.*

I currently use Webmin and Puppet to deploy software updates, but it should be much easier with Lansweeper, as it can assist with tracking OS version status. Granted there are many open source products out there, but I need an integrated solution to manage such a varied environment.

I'd like to hear from the "Community" as to their experiences when supporting a mainly Linux environment with Lansweeper.

How do you use Lansweeper in your every day management of UNIX/Linux hosts?
  • OS Maintenance?
  • Patch updates?
  • Which do you use, and do you script within Lansweeper to accomplish these tasks?
    • pkgadd
    • apt-get
    • yum
    • rpm
  • Do you separate out scripting per OS rev, per OS Flavor, or script for all possibilities in one Action?
  • Do you use Lansweeper to manage Production software deployments (like internally written software...?)
Champion Sweeper II
Short answer, useful, but not that much.

Long answer, from my particular case, although it won't help you much:

We have about 180 servers, 38 of those are Unix. Three older AIX boxes, running a legacy in-house application that refuses to die, and 35 Linux boxes, mainly proxy servers, and a handfull of application servers in the middle. The application servers are virtualized, the proxies are all physical servers.

We don't even have the AIX boxes in Lansweeper, so no help there, and for the Linux boxes, Lansweeper is used just for inventory. We get overall info like brand, model, warranties, that we can use for inventory purposes, but not that much else.

Outside of Lansweeper scope, all of our servers are running CentOS, I'm now upgrading the CentOS 5 machines to CentOS 7, pending the EOL on March. For all the servers, we use a kickstart minimum build, and we keep the servers updated using yum. The application servers are a bit more tricky, but since they are just a few, not that much work... We do patches and vuln scanners quartely, so they are always more or less updated.

We currently don't use any kind of patching/management tool (cfengine, puppet, chef), but our growing number of machines has us thinking of doing something... A former unix admin knew Puppet and did a little demo, but he left the company and no one picked that up... I would say we just crossed that line where the ROI of learning and deploying a tool like that is head to head in time of doing thinks manually...

Finally, even on Windows, we don't use Lansweeper to manage software deployments, just for one-off tasks.
We use a mix of WSUS/Retina for Updates and Patch Management, and EMCO for in-house software and applications not know to Retina, those are tools we already owned and used before LS had the deployment module...