[Are MDT + SCCM task sequences worth the effort?]

On 5/9/2014 at 4:22 PM, Apexes said:

Example why i cannot live without MDT:

MDT gives you the ability to have a variable image over multiple sites by running only one task sequence, sure - it takes some configuration in the first part, but in that MDT Database, i have settings which ensures the correct time zone is applied for each region, keyboard settings, input locale's etc. If i detect you connecting from a default gateway based in china, you get the chinese language packs for Office 2010, IE9 and Windows 7 by default. At the same time i've got a user in germany running the exact same sequence, getting only whats specific for his region - How do I apply this configuration, is this documented somewhere?

 

Quote

I work for a large financial organization, i'm heading up a migration project from WinXP to Windows 7 and am the sole contact for SCCM & Automation.

 

My MDT Task sequence contains 196 steps, and takes around an hour to install a fully new image, ready to go for users.

 

I've got 27 site DP's across 17 countries, so customization with minimal effort is a must.

 

MDT gives you the ability to have a variable image over multiple sites by running only one task sequence, sure - it takes some configuration in the first part, but in that MDT Database, i have settings which ensures the correct time zone is applied for each region, keyboard settings, input locale's etc. If i detect you connecting from a default gateway based in china, you get the chinese language packs for Office 2010, IE9 and Windows 7 by default. At the same time i've got a user in germany running the exact same sequence, getting only whats specific for his region

 

If i was to create a seperate TS for each region - it would have taken me probably 20x longer than it would have to of created an MDT integration.

 

I'm also able to monitor any OSD image at any time, no matter where i am - I injected DaRT 8.1 into MDT, which gives me remote control abilities, so i can troubleshoot clients remotely if they fail, even in WinPE stage.

 

Monitoring - i can see at any point what machine is imaging, how far it's into the image, and when completed.

 

Log file copying, all MDT logs go to a log share on my primary site.

 

Application & Package variation across locations - add in any package i want for a specific office.

 

Also by keeping just one task sequence, rather than 17 - means that if i need to update an application in my base image, i only do it once on my main task sequence, rather than 17 times.

 

I think MDT works for some people, but not for all. Certainly in my role i'd be lost without it, everything is so much easier with it in place. I agree with you that it can be fiddly at times, and it takes some getting used to, but i can reel off the log locations by heart now just by looking at what background i have in OSD

 

Stick at it, it's a great tool to use and once you've got your head around it you can take that on your CV to other job roles and it'll make your life alot easier and offer you perhaps a few more opportunities career wise if you can use it.