|
|
How can we manage this micro mess?Douglas E. WelchDatamation, Jan 15, 1993 v39 n2 p124(1) COPYRIGHT Cahners Publishing Associates LP 1993
Managing micros has turned into a nightmare. Large Is shops are being swamped when it comes to keeping an inventory of PC hardware and software, as well as performing software upgrades. We need a standard for managing these remote systems. Network managers have the Simple Network Management Protocol (SNMP) to monitor and control network devices. Why not create the Simple Microcomputer Management Protocol (SMMP) to manage micros? Any microcomputer manager can give you several reasons to establish SMMP. Software version control is just one of them. Microcomputer resources are so scattered that a simple software upgrade can take months to complete. Managers can't even poll networked micros to see what version of the software they are currently running. Paper records of installations are usually out-dated so quickly as to be almost worthless. Imagine how complex this becomes if you are upgrading multiple pieces of software. Hardware. configurations are another concern. Managers need to know how much memory and hard disk space each micro has and what type of processor it is using. Today, you would have to visit every microcomputer to find this information. The time required to perform this can stretch into man years. SMMP would provide a standard way for managers to poll each networked micro. This request would return standard information regarding hardware type, operating system versions and settings, as well as software versions and important configuration files. This database of information could then be used to generate reports and plans for future upgrades, create checklists for on-site personnel to work from and assist in developing a current inventory whenever necessary. SMMP should also provide for automatic updating of software for remote machines. There should be no need to send out a technician to install software if an automated procedure could do it during off hours. In some larger installations, this may be the only way to effectively complete a software upgrade: Cooperation from vendors is required if SMMP is to find a place in today's companies. Hardware and software manufacturers need to include code in their products that can respond to the standard SMMP console when it polls the machine. A standard set of information would have to be established and yet provide a method. for vendors to also include machine or software information that is specific to their products. The most important piece is to make the operating system SMMPaware. Standard calls could provide basic information about each micro directly from the operating system level. SMMP consoles need not be separate devices. In fact, it would be best to combine these functions with the SNMP consoles already in place in many larger companies. There is no need to make support people look in two different places for information. The only way SMMP will ever see the light of day is if microcomputer support people put pressure on vendors. We need to show vendors that there is a market and a growing need for this technology. As support staffs get swiped by the budget-cutting ax, we need to turn to technology for some assistance in managing the computer resources of our firms. Without tools like SMMP, Our networks will cease to grow as they'll no longer be manageable. Everyone--vendors, microcomputer managers and end users--stands to benefit from SMMP. Network markets could continue to grow; support resources could be better used; and end users would receive the best possible service, the most current software and the most productive workstation possible.
Douglas Welch is a support analyst for a major entertainment corporation in Los Angeles. Future Vision is a forum for our readers. If you'd like to contribute, please write to Chris Staiti at DATAMATION, 275 Washington Street, Newton, MA 02158 or call (617)-558-4508.
|