Compaq ProLiant ML350 Server General Troubleshooting Guide

Preventing Future Problems 7-3
Compaq Confidential – Need to Know Required
Writer: Susana Weinstein Salazar Project: Compaq Servers Troubleshooting Guide Comments:
Part Number: 161434-001 File Name: h-ch7 Preventing Future Problems.doc Last Saved On: 9/2/99 1:52 PM
Installing Servers Consistently through a
Replicated Install
When initially setting up a server, SmartStart can access the Integration Server
as the source of the system software instead of the system software CDs.
SmartStart on the target server connects to the Integration Server during the
Assisted Integration or Replicated Install interview process. SmartStart
examines the Integration Server to determine which software is available for
installation.
To setup a new target server using an Integration Server as the software
source, see the SmartStart Setup Procedure.
Server Software Maintenance
When you update an existing server located on the same network as the
Integration Server, the target server may access the Integration Server using
the Compaq Integration Maintenance Utility and apply updated software
stored on the Integration Server.
Other Ways to Minimize the Impact of Changes
Version Control
A preventive measure for out-of-date drivers is to advise the customer about
the version control feature in Compaq Insight Manager. It checks the versions
of Compaq operating system drivers, Insight Agents, Compaq Utilities, and
firmware on the server, compares them against a database of current software
and firmware versions, and indicates whether an upgrade is needed and why.
Server Design
Design your server setup to minimize the impact of downtime. Where
possible, divide the workload between several machines rather than just one. If
you can, group users across different servers in your network. Anticipate the
utilization rate and distribute servers based on that rate.
Minimizing Updates
Stay aware of the latest software updates for your operating system and
applications. Weigh the risks of updating versus the need for the changes. If
you never update the software, chances of getting a working system back after
a failure may be reduced. On the other hand, you should not update software
for fixes that you do not require.