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



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 guess you are not installing many apps/utils in the WIM image then? ... I presume you install the apps afterwards via SMS in the new OS? ... With OSD you can also use download and execute scenarios ...
    (microsoft.public.sms.tools)
  • Re: OSD error 1231 when Capturing
    ... Cross posting to the tools newsgroup where OSD questions are more regularly ... SMS 2003 Technical FAQ: ... DHCP is active and working on the network. ... > <![LOG[The local administrator account name is ...
    (microsoft.public.sms.admin)
  • Re: OSD error 1231 when Capturing
    ... Cross posting to the tools newsgroup where OSD questions are more regularly ... SMS 2003 Technical FAQ: ... DHCP is active and working on the network. ... > <![LOG[The local administrator account name is ...
    (microsoft.public.sms.tools)
  • 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)
  • Re: OSD - Image size... your thoughts?
    ... I guess you are not installing many apps/utils in the WIM image then? ... I presume you install the apps afterwards via SMS in the new OS? ... With OSD you can also use download and execute scenarios ...
    (microsoft.public.sms.tools)

Loading