Slashdot Mirror
Systems Management Server Equivalent for Linux?
em_tasol asks: "While tearing my hair out trying to manage an expanding network and keep the 'Standard' in 'Standard Operating Environment', someone suggested we use Microsoft's Systems Management Server for many tasks that we currently run around doing manually. We are using a Linux-based Samba PDC at the moment, and installing SMS would require a total infrastructure rethink, because it appears to require a Windows PDC to install itself and SQL Server. Does anyone know how I might put something together in the Linux environment that will be compatible with a Samba NT4 domain environment that will perform the same sort of functions as SMS?"
If you need software distribution, inventory collection, etc. Novadigm's products are thoroughly cross-platform (Windows, Solaris, HP-UX, AIX, Linux, etc.) and best-of-breed. Kind of pricey though. How big is your installation?
IBM Tivoli encompasses a suite of systems management products that work much like SMS.
since you dont give us much to go on in terms of what you want to do, or how much you want to pay, tivoli should cover all the bases. otherwise have you checked sourceforge? or even google?
SMS is costly and difficult. Depending on the size of your IT department, SMS is probably overkill. After investigating SMS, we went with Citrix, which provides an architecture for Windows which is similar (please forgive the gross generalization) to X (client-server remote apps).
Install the software once, and all users have remote access. Citrix allows for all sorts of OSs to connect, as well. There are Windows, Mac, Linux, Win CE, PocketPC, etc clients, so all of your users have access to a Windows Desktop with Windows apps.
If you have no need for non-Windows clients, check out Microsoft Terminal Server. Same thing, but only Windows clients. The benefit is cheaper licensing -- if you buy Citrix for Windows 2000, you have to pay Terminal Server licensing as well. (Sorta like paying the mob for "protection").
Citrix is much easier to manage than SMS, and does not require an entire Windows infrastructure -- just a few servers. Figure 50 users (Office, Internet, Custom Apps, NOT streaming media or video games) per server. An office of 150 people will need ~3 servers (give or take, depending on usage.)
Combo Citrix with a good Windows X server (Cygwin is free), and you have a great cross-platform solution for any desktop using apps for Windows and Unix, simultaneously!!!!
10b||~10b -- aah, what a question!
SMS's features are, according to MS:
.dat file to the correct directory.
= /library/en-us/script56/html/wsconwshwmi.asp ) describes this.
- Software distribution
- Asset Management
- Remote Troubleshooting
Lets look at the software distribution bit first. Mainly this is used for os patches and virus scanner updates. If your people have access to WindowsUpdate.com they already can get the first lot, and for the second, you can often just copy the
For asset management, microsoft's software inventory amounts to scanning for files with a given extension. Matching this to software versions is trivial with a perl script, and a bit of data capture to start with. Hardware inventory is barely more complex and its easy to write a script to do the job.
Remote troubleshooting amounts to the same functionality you get from VNC.
So to sum up, to emulate SMS you need a hook to run some scripts and copy files to & from the net when the user logs in, plus VNC. Your samba environment has a login script directive which you can use as the startup hook. Clearly you have file sharing down. So all thats left is to get some appropriate scripts to run.
This is partly a matter of your personal preference. SMS itself uses the WMI interface to gather info, which coincidentally is easily accessible via windows vbs/js scripting, and it should already be installed on all these machines. The WSH manual ( http://msdn.microsoft.com/library/default.asp?url
If your environment is small and reasonably well controlled you have other options available. Booting machines off the network, for example. Mounting a central apps drive is another, though crappy for laptop users - then you only need to manage the registries remotely, which regedit can already do. Manipulating multiple registries remotely, eg using perl, isnt difficult, and you can do this to set 'runonce' scripts up over the network to do installs.
Anyway hope this gives you some ideas.
Arguably the king of Perl programming in the windows environment, Dave Roth a few years ago wrote a perl and SQL based solution that provides much of what SMS can do. I don't know if he still has it anywhere on his site anylonger. If he does the full code that he used as well as a lengthy description of how to configure it was provided. You might want to have a look there. Dave is the author of some of the most essential Perl Modules for any Witendoze systems administrator's toolbox. Good Luck.
01010100 01101000 01101001 01110011 00100000 01101001 01110011 00100000 01101101 01111001 00100000 01010011 01001001 010
The typical provincial or county government has departments that span 50 different vertical markets, each with their own specialty software vendors competing for a chunk of the budget. I don't doubt that it is an IT nightmare but the diverse demands of government go a step or two beyond the typical corporate user.
Bleh!
You can get the Snapshot functionality for Linux from Moonlight Systems. See their Moonlight3 product. I was asked to do a quick evaluation of it last year, but company politics would have prevented us from properly taking advantage of it...
Keeping consistency (within reason) across an enterprise is both extremely difficult, but also has the potential to save an organization a whole lot of money. In my organization, we do enforce certain standards to make it possible for our business to be conducted efficiently. We do not allow users to install their own software, for example. Why, you ask? It's certainly not because we're "Nazis". We want to avoid potential legal (licensing) problems, potential security problems and want to keep as much stability as we can so that business can be conducted.
This isn't completely about control -- this is about providing users with the tools that they need to do their jobs while at the same time protecting the company from legal liability and providing adequate security.