[ Date Index ][
Thread Index ]
[ <= Previous by date / thread ] [ Next by date / thread => ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Adrian Midgley wrote: > On Wednesday 22 October 2003 06:36, Kai Hendry wrote: > > I think it is more that they want a brand name on it, and to have a > contract saying that someone will always be avialable to update their > update-script when something changes, and to tell them regularly that > nothing has changed. > > And that is a reasonable requirement, what with due dilligence and so on. HP OpenView is ported I believe, although for all but the biggest organisation I think it is pretty much overkill. IBM have ported their tools. What sort of brand names do you want. There is a desktop/server split here. Many of the tools for managing big servers were written by BMC (worlds 10th largest software house when I dealt with them), or had components from BMC. It was focused on big iron (read IBM mainframe compatible) and also Unix (and other mid range servers, VMS), as well as databases (DB2, laterly Oracle and the like). In this market NT was a late comer, and Linux was just another *nix, so guess which has the best support ;) Away from server the desktop is slightly different environment. Although where there are N identical desktops I really don't think it is that challenging for *nix admins. Where you have arge numbers of clusters of desktops that is where Openview or thin clients make a killing. > So how does one generate that out of the anarchic environment we like? It isn't as anarchic as you might think ;) > GIven how badly it operates under apparently strict controls and rules, it > is wholly credible to me that a better way of ensuring it works could be > fashioned from statistical calculations and affinities, but I don't think > I can do it myself. What are you wittering about here... Most set policies and have mechaniss to see if those policies are complied with, and schemes to notify admins, or autocorrect the situation. The "for aserver in serverlist" approach is no hoper on big networks, you need to account for some servers being down, so updates have to be queued. Although in some cases updates may need to be synchronous across a network! I think Microsoft have an edge in integration with ADS, LDAP tools exist for big enterprises, but they often don't save as much as you expect, some big networks still use NIS/NIS+ for most people it is sufficient and it is interoperable (Unix/Linux etc). Simon -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/lrxwGFXfHI9FVgYRAr3fAJwI1OIdIWAAo6veFAGeIjO48FprWgCg0reh OOSWI2G6+yUya1+4aSq3fm4= =XLf0 -----END PGP SIGNATURE----- -- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe.