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

No apps, except OS updates, MP 10, SMS client, etc...

I install all apps in the state restore phase of osd (rapid
deployment)

For each MUI pack installed the wim-file increases with approx 40 - 50
MB...

regards

Johan Arwidmark
Microsoft MVP - Setup/Deployment


On Mon, 6 Feb 2006 07:44:28 -0800, "MilkyMagic" <bob@xxxxxxxxx> wrote:

Thanks for the info.

I guess you are not installing many apps/utils in the WIM image then? As
500-600mb seems very small. I've just created a basic XP installation with
Office, email, etc, and it's 3GB (not compressed).

I presume you install the apps afterwards via SMS in the new OS?

I am trying to create a single global image, which doesn't help, as I have
to add the extra language support.

Thanks.

"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: New Domain
    ... That sounds like a good model for OSD to assist in migration. ... > And i installed SMS Client on that PC with GPO. ... And install the new Winxp client from that ...
    (microsoft.public.sms.setup)
  • Re: OSD - Image size... your thoughts?
    ... 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? ... WIM image down over the network? ...
    (microsoft.public.sms.tools)
  • SMS 2003 OSD Win2k3 64bit OSD capture issues
    ... New to SMS 2003 OSD Feature Pack ... Current install: SMS Install SMS2003 w/ SP2 ... Pack update for x64bit support ...
    (microsoft.public.sms.tools)
  • Re: SMS 2003 OSD Win2k3 64bit OSD capture issues
    ... Microsoft MVP - Setup / Deployment ... Current install: SMS Install SMS2003 w/ SP2 ... ~ Need to capture Win2K3 STD x64bit edition and had to run OSD Feature ...
    (microsoft.public.sms.tools)
  • OSD
    ... As you can tell by my posts, I am evaluaitng the OSD for SMS. ... SWD to install applications after the OS package is pushed and installed on ... once a machine is rebuild that it would then ... Are there any other docs out there besides the SMS OSD Feature Pack Users ...
    (microsoft.public.sms.tools)
Loading