Creating a Reference Machine for SCCM OSD

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

Creating a Reference Machine for SCCM OSD

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> Operating System Deployment >> Creating a Reference Machine for SCCM OSD

Page: [1]

Message

<< Older Topic Newer Topic >>

Creating a Reference Machine for SCCM OSD - 4/7/2008 3:13:27 PM

lbernal206

Posts: 1
Score: 0
Joined: 4/7/2008
Status: offline

I am creating a Windows XP Sp2 image to use with SCCM OSD. We usually use ghost and have MsOffice, Adobe Reader, and other apps like this loaded as our core image. We are implementing Config Manager and want to utilize OSD. When creating my reference machine do I want a machine with just Windows XP SP2 and Patches?

Post #: 1

RE: Creating a Reference Machine for SCCM OSD - 4/7/2008 5:40:11 PM

jsandys

Posts: 207
Score: 13
Joined: 3/24/2005
From: San Antonio, TX
Status: offline

My Best practice is to include everything in your baseline image that is common to every system that you will deploy. This typically includes Adobe Reader, Adobe Flash Player, Adobe Shockwave Player, Microsoft Silverlight, Microsoft .Net Framework 1.1 SP1, Microsoft .Net Framework 2.0 SP1, and IE7 (and sometimes office depending on the client). I also integrate all of the latest Windows patches into the XP source files used to create the imaged system using the /integrate switch. Including all of these in the actual image saves loads of times when deploying systems.

_____________________________

Jason
________________________________________
http://ihaveablog.wordpress.com

(in reply to lbernal206)

Post #: 2

RE: Creating a Reference Machine for SCCM OSD - 4/7/2008 6:18:57 PM

rbennett806

Posts: 601
Score: 8
Joined: 6/14/2006
Status: offline

I go the opposite route from JSANDYS. I install only the base OS with only the needed updates and hotfixes. The reason being is that I don't want to have to update the entire .WIM everytime an application has an update or needs to be changed. That and I can use the single .WIM file for a variety of configurations just by layering on a different set of application packages (maybe one for DeptA, and one for DeptB, and one for techies, etc...).

Also, if I want to do any testing on a machine I can quickly kick out just the bare OS and start testing applications or do whatever I want without having to wait for the entire large image to be installed.

Just my two cents though...

(in reply to jsandys)

Post #: 3

RE: Creating a Reference Machine for SCCM OSD - 4/10/2008 9:14:40 AM

egiroux

Posts: 130
Score: 4
Joined: 4/4/2006
From: Portland, Maine
Status: offline

Here you have it lbernal206. These two options represent what are reffered to as a Thick Image vs. a Thin Image. There are tradeoffs with each. I am somewhere closer to the Thick side with my images. I have the core common applications incorporated. For my business roles that have specific sets of applications I load those on top of the common WIM rather than having a WIM for each business role. As for the drawback of updated applications. I've had good success with installing updated core applications (like Adobe Reader or WinZip) on top of the existing WIM that contains prior versions. You don't necessarily have to re-create your WIM if one of the core applications changes. Test installing it on top.

(in reply to rbennett806)

Post #: 4