Re: OSD - Image size... your thoughts?

Ah I see. I didn't think much of the I386 folder.

My SOE is built using BDD2.5 also. The main reason I've left network drivers
in the image because it won't download the network drivers during post
install because it won't connect to begin with and I've been unsuccessful in
adding 'additional network drivers' to the image package. I have been able to
filter down exactly which files are required for all the different models
used here (PC age hasn't been a problem) and the whole network driver folder
is about 3mb in size. Most models will share or use similar network drivers.
Everything else is injected in via ZT so we only require 2 images - 1 for all
laptops and 1 for all desktops.

You mentioned about having to add storage drivers and core io drivers, like
intel chipset drivers to the image. I haven't come across a need for this or
prehaps I don't know enough about it.

Cheers


"Johan Arwidmark" wrote:

I use a fully patched XP SP2 install (Build from BDD 2.5 Computer
Imaging System). Including MP 10, WinInst 3.1 and .Net Framework
updates, SMS client etc...

I Never, ever, include additional drivers in the the image (except
storage drivers and core io drivers, like intel chipset drivers). I
inject them at deploymen time using the hardware detect features of
ZTI (OSD extensions from BDD 2.5). I think it's more efficient to keep
the drivers outside the image and keep a "clean" image....

I do have a post installation script (action) that removes the i386
folder before capturing the image.

regards

Johan Arwidmark
Microsoft MVP - Setup/Deployment


On Mon, 6 Feb 2006 14:39:09 -0800, "ANguyen"
<ANguyen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

I've been creating fully patched WinXP SP2 wim images which are about 900mb
in size. That just the base OS + patches (integrated) + antivirus + network
drivers. I'm a little curious as to what Johan's image contains if it's only
500-600mb in size. I'm very interested in reducing the size of the SOE where
possible considering the flood of applications to follow the installation of
the SOE.

Cheers



"Johan Arwidmark" wrote:

The WIM-Image is normally around 500 - 600 MB compared with 800 - 900
MB using Ghost, PQIDeploy or ImageCast.

Laying down the wim-file takes over a 100 mbit network typically takes
only a few minutes.

With OSD you can also use download and execute scenarios (for Refresh)
and take use of SMS Client caching techniques to preload the wim-file
into the sms client cache...This leverages the BITS capabilities
introduced into Windows 2000 and later operating systems.

It is also possible to store the OSD Image package on a CD or DVD (not
support by msft though).

See my article on myitforum...

How to automate OSD FP when storing the Image Package on a DVD
http://www.myitforum.com/articles/8/view.asp?id=8807

regards

Johan Arwidmark
Microsoft MVP - Setup/Deployment


On Fri, 3 Feb 2006 07:03:42 -0800, "MilkyMagic" <bob@xxxxxxxxx> wrote:

Hi there.

I am in the early stages of planning OSD with SMS 2003. I would like to
image workstations with XP Pro SP2 using SMS 2003/OSD.

I am interested in any comments/feedback from people who have already done
this. What sort of size is your WIM image? What are you including/excluding
in your XP reference image?

What sort of transfer rate/bandwidth issues are you seeing when pushing the
WIM image down over the network? ie, Is a 2-3GB WIM image being transferred
over the local subnet acceptable?

I am currently using a non-SMS solution for XP deployment (Ghost). I have to
use a dedicated isolated network to ghost my machines, due to the bandwidth
consumed. I am particularly interested in how SMS 2003/OSD works over the
production network, when pushing out the WIM images.

Thanks in advance.




.

Relevant Pages

  • Re: OSD - Image size... your thoughts?
    ... I Never, ever, include additional drivers in the the image (except ... With OSD you can also use download and execute scenarios ... and take use of SMS Client caching techniques to preload the wim-file ... What sort of size is your WIM image? ...
    (microsoft.public.sms.tools)
  • Re: OSD - Image size... your thoughts?
    ... I Never, ever, include additional drivers in the the image (except ... I do have a post installation script that removes the i386 ... With OSD you can also use download and execute scenarios ... and take use of SMS Client caching techniques to preload the wim-file ...
    (microsoft.public.sms.tools)
  • Re: Not able to connect to internet
    ... Do you connect directly to the cable modem, or do you have a router/firewall ... It would be possible to get network drivers if you knew which network ... the web site should have the latest XP drivers for it. ...
    (microsoft.public.windows.mediacenter)
  • Re: Upgraded to unstable - lost network connectivity
    ... Running modprobe to force the network drivers to be ... I had thought perhaps your dist-upgrade had replaced your modutils with ... Unless things have changed, modutils is for modules ...
    (Debian-User)
  • Re: Mindboggling weirdness
    ... and icons going. ... the graphics drivers. ... So unless you decide to install the graphics ... drivers you never see the network drivers. ...
    (microsoft.public.windowsxp.general)