Lost in translation... BDD, SMS, what?

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:

Lost in translation... BDD, SMS, what?

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

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> Operating System Deployment >> Lost in translation... BDD, SMS, what?

Page: [1]

Message

<< Older Topic Newer Topic >>

Lost in translation... BDD, SMS, what? - 6/10/2008 3:11:07 PM

zylo

Posts: 5
Score: 0
Joined: 7/27/2007
Status: offline

Ok, we run SMS 2003 at work and so far I have done all of my imaging through bootable Image Capture & Installation CD's. I'm just starting to experiment with distribution points and what not but i've been reading a little about BDD (and MDD) especially after getting frustrated with my last attempt at a mandatory advertisment for a WinXP deployment, and the need to begin imaging Vista Business in the following weeks.

Are these addons to SMS, or replacements? Everything I see points to them being free, but I really don't know. For simple imaging purposes, should I install these, or just stick with SMS? In laymans terms, what would BDD/MDD do for me? I have a hard enough time with SMS as it is, so i'm wary of adding to it. Don't know SQL, don't know what a MIF is, etc. dumb dumb dumb, I are.

Help?

Post #: 1

RE: Lost in translation... BDD, SMS, what? - 6/10/2008 5:38:40 PM

jsandys

Posts: 463
Score: 17
Joined: 3/24/2005
From: San Antonio, TX
Status: offline

The first thing to do is to define the two types of deployment that Microsoft has: LiteTouch and ZeroTouch. LiteTouch involves minimal, but some manual intervention for deployment on the PC where the OS is being deployed. ZeroTouch requires just that, no manual intervention on the PC being deployed to.

With that in mind, The Operating System Deployment (OSD) feature Pack for SMS2003 implements a ZeroTouch philosophy. The problem with the OSD is that it is limited in what it actually does: it simply creates images and deploys them. Anything extra, specifically application deployment and driver integration, are outsid of the scope of OSD.

This is where the Microsoft Deployment Toolkit (MDT) comes in -- BDD and MD are acronyms for older incarnations of this toolkit. MDT adds the ability to integrate drivers into the image deployment process thus making the deployment (nearly) hardware agnostic. It also implements automatic installation of SMS packages and the ability to query a database for all configuration information including drivers and applications to install on a system based upon system model, location, or other factors. MDT perfectly integrates with OSD.

In short, OSD 2003 is mostly just an imaging solution. MDT adds real deployment functionality that goes above and beyond simple images.

Also note that MDT also implements a LiteTouch functionality that is completely seperate from SMS.

I do recommend that you look at moving to ConfigMgr 07 as quickly as possible. The OSD functionality in ConfigMgr is so much better than SMS. MDT also integrates with ConfigMgr, but I actually prefer not to use the MDT with ConfigMgr.

_____________________________

Jason
________________________________________
http://myitforum.com/cs2/blogs/jsandys/default.aspx

(in reply to zylo)

Post #: 2

RE: Lost in translation... BDD, SMS, what? - 6/13/2008 5:19:42 PM

rbennett806

Posts: 784
Score: 13
Joined: 6/14/2006
Status: offline

While it's getting a little outdated, you might also take a look at the article located here: http://www.myitforum.com/articles/8/view.asp?id=11032

I like to think of BDD/MDT as a "helper" to SMS\SCCM, or as a standlone deployment mechanisim. You use SMS to manage the machines once they're out in your production environment, but you can use all sorts of different methods to get them out there (like using Symantec Ghost)...

(in reply to jsandys)

Post #: 3