The network-staging folder, Deployment and installation overview, Network-staging – Lenovo ThinkPad R400 User Manual
Page 49: Folder, Deployment, Installation, Overview, Standard, Network-deployment, Process

Access
to
the
service
partition
is
controlled
by
a
boot-manager
program.
The
network-staging
folder
The
network-staging
folder
has
one
purpose;
during
a
direct-network
installation,
it
provides
a
temporary
storage
area
on
the
network
to
unpack
the
maps
and
modules
that
control
the
installation
of
the
image.
By
default,
a
separate
network-staging
folder
is
created
for
each
target
computer
in
the
NETDEPL
folder
located
under
the
repository
being
used.
The
name
assigned
to
the
network
staging
folder
is
based
on
the
last
11
characters
of
the
target
computer
MAC
address.
Note:
If
necessary,
you
can
define
a
location
outside
of
the
repository
where
the
network-staging
folders
will
be
created.
See
for
more
information.
Unlike
deployment
to
a
service
partition,
the
person
at
the
target
computer
who
is
controlling
the
direct-network
deployment
makes
choices
from
the
installation
menu
system
before
any
modules
are
sent
to
the
target
computer.
Then,
only
those
modules
required
for
the
selected
image
are
obtained
from
the
repository,
unpacked
dynamically,
and
installed
on
the
target
computer.
The
target
computer
must
remain
connected
to
the
network
throughout
the
entire
deployment
and
installation
process.
When
the
installation
process
is
complete,
the
network-staging
folder
is
automatically
erased.
A
direct-network
deployment
does
not
require
that
a
service
partition
be
present
on
the
target
computer.
The
use
of
a
service
partition
is
optional,
and
if
used,
its
only
purpose
is
to
store
maps
and
modules
for
client-side
recovery.
A
service
partition
is
not
used
as
a
staging
area
during
a
direct-network
installation
process.
v
If
you
do
not
want
maps
and
modules
copied
to
a
service
partition,
you
minimize
the
deployment
time,
but
you
will
not
have
client-side
recovery
for
the
image
you
deployed.
v
If
you
want
only
those
maps
and
modules
that
are
required
to
recreate
the
installed
image
copied
to
a
service
partition,
deployment
time
will
be
longer,
but
you
will
have
client-side
recovery
for
the
specific
image
that
is
installed
on
the
target
computer.
v
If
you
want
the
complete
Smart
Image
copied
to
a
service
partition,
deployment
time
will
be
longer
yet,
but
you
will
have
client-side
recovery
for
any
of
the
images
that
can
be
installed
from
the
Smart
Image.
For
additional
information
about
these
settings,
see
and
look
for
the
information
about
the
Image
Cleanup
tab.
Deployment
and
installation
overview
This
section
provides
an
overview
of
the
various
deployment
and
installation
processes.
Standard
network-deployment
process
with
local
installation
The
following
illustration
shows
the
standard
network-deployment
process
with
local
installation.
Notice
that
the
service
partition
is
used
as
the
staging
area
for
all
maps
and
modules
required
for
the
Smart
Image.
Chapter
3.
Staging-area
behavior
and
logic
35
- THINKPAD X60 ThinkPad T43 ThinkPad R61e THINKPAD T61 ThinkPad X301 ThinkPad R50e ThinkPad R50p ThinkPad X40 ThinkPad SL300 ThinkPad SL400 ThinkPad X200 ThinkPad T500 ThinkPad R51 ThinkPad T41 ThinkPad T60 ThinkPad X61 Tablet ThinkPad X41 Tablet ThinkPad X61s THINKPAD X61 ThinkPad R61 ThinkPad X200 Tablet ThinkPad Z61e ThinkPad T400 ThinkPad R61i ThinkPad R52 ThinkPad R50 ThinkPad W700 ThinkPad R500 ThinkPad SL500 ThinkPad X200s THINKPAD Z60M ThinkPad W500 ThinkPad T61p ThinkCentre A30 ThinkPad T42 THINKPAD T40 ThinkPad X300 ThinkCentre M55e