MDT

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:

MDT

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

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> MDT

Page: [1]

Message

<< Older Topic Newer Topic >>

MDT - 7/8/2008 5:14:33 PM

nrunge

Posts: 55
Score: 0
Joined: 5/20/2008
Status: offline

If I have never used BDD or MDT before and now have SCCM at my disposal with the MDT integration is there any benefit to using MDT? In a lot of ways it looks to me like SCCM lite. I found some good documentation with it but have yet to see any real benefit to using it for OSD.

Post #: 1

RE: MDT - 7/8/2008 5:31:35 PM

ScottGill

Posts: 31
Score: 0
Joined: 3/1/2007
Status: offline

Deployment 2008 was made to compliment SCCM in some select ways. Mainly (for me at least) the PXE Filter which allows you to PXE boot machines not yet known to the SCCM database. It also adds a few other things to SCCM but I've never used them.

(in reply to nrunge)

Post #: 2

RE: MDT - 7/8/2008 6:30:04 PM

dhicks

Posts: 10
Score: 0
Joined: 2/6/2007
Status: offline

One of the other great features of MDT\SCCM integration is the use of the MDT Database to provide fields for things like role and make\model. What this does for example is; say you have a procurement person who is responsible for recording asset tag etc before it is given to I.T. for build out and deployment. The procurement person or tech if they are one in the same can input the system make and model (WMI friendly name) into the MDT database along with MAC and or serial number in addition to other potential custom values defined in the Database such as apps based on the user role the system is assigned to. (Assuming you have PXE enabled) You then take the system out on the floor, plug it in, power it up and WHALA! your system build is deployed through SCCM but leverages MDT database information to handle dynamic customization through out the build process. Allowing you to maintain one singlew image for multiple platforms. The benefit is that you do not have to modify the ZTI scripts (At least not from a Code dev level) you can add optional values pretty easily. In addition various ZTI scripts are designed specifically to reference the MDT database to look for custom values etc.

You are correct in suggesting that SCCM does alot of this already but the power to me at least is in the MDT Database integration.

Read the docs and go have a look see at the Deployment Guys blog. Lot's of good stuff on this topic http://blogs.technet.com/deploymentguys

I do not do it justice but as a consultant have had several opportunities to integrate the two on small and large clients and the value of the integration has been realized at both levels. (The tools are the key I'm just along for the ride.)

< Message edited by dhicks -- 7/8/2008 7:51:23 PM >

(in reply to ScottGill)

Post #: 3

RE: MDT - 7/9/2008 9:19:38 AM

nrunge

Posts: 55
Score: 0
Joined: 5/20/2008
Status: offline

The deployment model of which you speak is exactly my end goal. I will look more into the MDT database options.

(in reply to dhicks)

Post #: 4