Improving boot time with XPe

  • Thread starter Thread starter Augusto Alvarez
  • Start date Start date
A

Augusto Alvarez

I was able to prepare a Windows XPe image to boot from the network
correctly, using virtual machines as server and client, connected using a
virtual network. I added to the image only the basic components that I need,
and the complete size of that image (after running FBA) stays in 450mb. And
it translates to about 10mins of boot time for the clients: 9 of those 10
mins are the files transferring from the server to the client.

Is there any way that I can reduce that boot time performance?

Thanks!
 
Augusto,

First, your image size seems quite big. Are you sure you can't reduce the image footprint?

Second, current implementation of the RBS (remote boot feature of XPe) doesn't allow parallel image downloads to multiple clients.
Only 3rd party solution I know of is Ardence's BXP platform. Not sure if they still sell it, though.
 
I try to remove several unnecesary components from the image with "target
designer" but some of them were added again by the tool when I ran the
dependency check.

After building this image, the size is 260mb. But when I ran it for the
first time, to use FBA, the image increase to 450mb.

Note: I added the .Net Framework 2.0 component that is necessary for my
image, do you think that is reason for the big image?

Thanks!

--
augusto alvarez | it pro | southworks s.r.l.
http://staff.southworks.net/aalvarez

KM said:
Augusto,

First, your image size seems quite big. Are you sure you can't reduce the
image footprint?

Second, current implementation of the RBS (remote boot feature of XPe)
doesn't allow parallel image downloads to multiple clients. Only 3rd party
solution I know of is Ardence's BXP platform. Not sure if they still sell
it, though.
Click to expand...
 
Augusto,

I can't answer your question about .Net 2.0. It is a huge beast indeed but you should know better whether you need it in the image
or not - explore your image application dependencies.

Beside removing the whole stack of components so that dependencies stop getting pulled in by the TD Dependency Checker. You can also
turn off the auto-resolving dependency feature in TD options.
Here you can find a description of some tools useful in dependency exploring process:
http://km-dev.blogspot.com/2007/03/xpe-tip-2-let-me-continue-about.html

--
=========
Regards,
KM

I try to remove several unnecesary components from the image with "target designer" but some of them were added again by the tool
when I ran the dependency check.

After building this image, the size is 260mb. But when I ran it for the first time, to use FBA, the image increase to 450mb.

Note: I added the .Net Framework 2.0 component that is necessary for my image, do you think that is reason for the big image?

Thanks!
Click to expand...
 
I have one question related on the components of XPe, I want to give each
client the minimum components possibles of networking. Basically so they can
connect with other clients and with the server. Which is/are the component/s
necessary for that?

Thanks!
 
I have one question related on the components of XPe, I want to give each
client the minimum components possibles of networking. Basically so they can
connect with other clients and with the server. Which is/are the component/s
necessary for that?

Thanks!
 
Augusto,

The list of recommended components in your case would depend on what type of connectivity you are looking for from/to your client
machines.
If it was MS Windows based network, then you'd probably want to stick to "Microsoft Network Client" macro. Just make sure to resolve
its dependencies. You can later remove some dependencies unnecessary for the functionality you are targeting. However, reducing
footprint this way is typically a pretty laborious process and not suitable for rapid development if you will.
 
Back
Top