Pre-OS desktop management agents themselves may reside either within the
image, or may be executed in place from a mapped network drive.
Pre-OS environments are supported by MBA configured for: TCP/IP (BOOTP,
DHCP), PXE, or NetWare protocol configurations. RPL configurations are not
supported.
PC Pre-OS Bootup Sequence
Boot image files that create a Pre-OS connection cause the PC to:
7.
Load a temporary version of DOS
8.
Perform the specified maintenance tasks
9.
Unload DOS
10.
Resume (with the PBOOT utility rather than user intervention) loading the
operating system from the hard drive whatever form that operating system
takes
Connection, in a way, is like booting from a floppy drive, removing the boot
floppy, and then rebooting from a hard drive.
From the user's point of view, the sequence is as follows:
11.
The end-user powers on or restarts the client PC.
12.
A Pre-OS connection is created by the boot image file on the server. No end-
user intervention or awareness is required.
13.
The specified desktop maintenance applications are executed and the required
actions can be taken.
14.
Control is passed from the Pre-OS image to the hard drive.
15.
The PC loads the end-user's operating system from the local hard drive.
16.
The end-user logs into the network as usual.
C
C
r
r
e
e
a
a
t
t
i
i
n
n
g
g
P
P
r
r
e
e
-
-
O
O
S
S
B
B
o
o
o
o
t
t
I
I
m
m
a
a
g
g
e
e
s
s
Creating Pre-OS boot image files involves two steps very similar to creating
remoteboot images:
Copying needed files onto a DOS-formatted system diskette
Taking a snapshot of this disk with the Boot Image Editor
Refer to the Boot Image Editor online help for instructions.
49
