Instead, the vast majority of software problems can be solved remotely and
rapidly. Because boot failures typically make it impossible for users to connect
with the network, even the most sophisticated enterprise management tools at
the administrator's disposal are of no use.
MBA guarantees that every PC on the network—even those with damaged
operating systems and new PCs with no OS and unformatted hard disks—will
connect to the network. The ability to boot under management control also
protects PCs when they are most vulnerable to boot sector viruses. In addition,
MBA improves IS productivity by enabling administrators to configure or update
any number of PCs very efficiently by making changes to a single image on a
network server.
How MBA Works
PCs can be configured to boot from a server using a combination of configuration
files, boot image files, and software residing on the server's hard disk. MBA
retrieves the required information (for example, an operating system, memory
managers, network drivers) from these files on the server when the PC starts.
This process has commonly been described in the past as remotebooting.
Traditional remotebooting may not be adequate in establishing a complete work
environment due to requirements imposed by today's GUI operating systems and
applications. In this case, MBA can become a compelling administrative tool when
configured to perform a Pre-OS boot prior to every local boot. Using MBA software
and utilities including Pre-OS, a network administrator can make use of
diagnostics, configuration, or maintenance tools prior to completing the local boot
process.
F
IGURE
1: H
OW
MBA W
ORKS
Standards Supported
MBA supports Wired for Management (WfM). It also supports all major boot
protocols, including not only Preboot eXecution Environment (PXE) protocol
originally defined in the Net PC specification, but also existing protocols such as
BOOTP, DHCP, RPL, and NCP/IPX. Customers thus have the flexibility to use
18
