SCCM 2007 capture custom image

Hello,

I've been working with SCCM for a few months now but there has always been one thing bugging me about building and capturing wims.

Every walkthrough/tutorial I read regarding building and capturing a custom wim recommend you create a task sequence which installs your os, apps, customizes it in which ever way you want then captures it so it can then be deployed.. what I don't understand is...

1. Why can't you deploy the raw OS wim and add these customizations in the task sequence of the final build.. its effectively the same thing
2. Why can't you build up an OS install with customizations, sysprep it, boot into WinPE and capture it (I'd much prefer to do it that way, more control over image).

Thanks if anyone can shed some light on this!
AdamBockAsked:
Who is Participating?
 
MarkieSCommented:
Hi,

There's a step by step guide here for OSD stuff.

http://blogs.technet.com/b/configurationmgr/archive/2009/07/27/a-step-by-step-for-using-osd-through-system-center-configuration-manager-2007.aspx


WMI is used to test for makes/models and can be used to test PCI/VendorID to select the correct WinXP Criticalboot device drivers (Win7 doesnt suffer from that)

If you're on Dell machines this is a useful reference (Other manufactures have similar)
http://www.delltechcenter.com/page/Operating+System+Deployment+-+XP+Mass+Storage+Driver+Reference

I cant give specific examples from my setup at the moment as the site is down due to maintenace but I'll post further details later if you want.

Strictly speaking you are correct - it should be in TS2 but this is the organic way this was setup and grown and it's stuck that way ..!  (It's in one of my remits to change it over!)

cheers
0
 
MarkieSCommented:
Hi

1 - Very true.  You can do it this way.  But do you want 1 build and capture to take 2 hours - then every deployment takes 20 minutes.  Or do you want every deployment to take 2 hours each?

2 - Isn't that what you are doing with SCCM.


My setup does the following.  
Task Sequence 1 covers all makes and modesl of HAL as I test using WMI what machine I am dealing with and add drivers as required.  I install the OS. I install generic applications (Office/Phone stuff/Adobe/Flash etc etc).  It gets sysprepped then it takes a WIM image.
Task Sequence 2 - gets deployed to the masses.  It slaps the relevant WIM file on then does a few customisations as required to whatever team/department the machine is to be sent to.

cheers
0
 
AdamBockAuthor Commented:
1. ah ok so the advantage is - its quicker to apply a wim that has basic apps/customizations installed than it is to install them each time like I was suggesting?

2. I guess so.. I suppose I feel better about physically preparing an image myself.. but when you spell out your process it sounds like the only logical way of doing it so I'll stick to that

Would you mind going into your driver/HAL process as I would have thought drivers are taken care of in TS2?

Cheers MarkieS
0
 
AdamBockAuthor Commented:
thanks a lot for your help!

makes a lot of sense :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.