WineGeek
asked on
Organizing Microsoft Deployment Toolkit folders
I'm setting up MDT 2012 (with WDS & WAIK) as our computer building/imaging solution. We have several models of Dell Desktops & Laptops & some Panasonic Toughbooks. We deploy Windows XP x32 & x64 and Windows 7 x32 & x64. We have a collection of applications that Engineers get, another collection of applications that Finance people get, etc. And of course there are the drivers for each model of computer. Now I need to organize all these items so that the tech building a computer has all the needed menu selections/options as he builds the computer.
I'm trying to understand how best to layout the folders in the MDT Workbench Environment. For example:
Would it be best to create a Deployment Share for each O/S version, or would I also need unique Deployment Shares for the different collection of applications for each department or could that be handled with just some unique Task Sequences? That's the sort of organization information I'm looking for. Thanks!
I'm trying to understand how best to layout the folders in the MDT Workbench Environment. For example:
Would it be best to create a Deployment Share for each O/S version, or would I also need unique Deployment Shares for the different collection of applications for each department or could that be handled with just some unique Task Sequences? That's the sort of organization information I'm looking for. Thanks!
Would it be best to create a Deployment Share for each O/S version, or would I also need unique Deployment Shares for the different collection of applications for each department or could that be handled with just some unique Task Sequences? That's the sort of organization information I'm looking for. Thanks!
I keep them all together and do the customization with task sequences. In my mind this keeps everything together to reduce the amount of duplication and saves me the effort of hunting for something that may be on another deployment share.
I keep them all together and do the customization with task sequences. In my mind this keeps everything together to reduce the amount of duplication and saves me the effort of hunting for something that may be on another deployment share.
ASKER
@ve3ofa - you keep what all together? I need details please. Spell it out for me please. Thanks!
@Mutawadi - same thing - I need details. so, when you say "I would build over these images to install the specific specialty apps" what exactyl do you mean? How are you using/categorizing deployment shares, task sequences, other types of profiles in MDT? I need to know how you have all your MDT components setup in MDT. Thanks!
@Mutawadi - same thing - I need details. so, when you say "I would build over these images to install the specific specialty apps" what exactyl do you mean? How are you using/categorizing deployment shares, task sequences, other types of profiles in MDT? I need to know how you have all your MDT components setup in MDT. Thanks!
Create one image for each department.
Drivers are easy to plug in for new hardware so one imgae for each hardware is not needed. Some work is needed for laptops but not a separate image.
Drivers are easy to plug in for new hardware so one imgae for each hardware is not needed. Some work is needed for laptops but not a separate image.
ASKER
Did I ask too big a question? :)
ASKER
I've requested that this question be deleted for the following reason:
I need to re-word my question into smaller bite-size chunks. The wording of this question is not producing the answers I need.
I need to re-word my question into smaller bite-size chunks. The wording of this question is not producing the answers I need.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Then I would build over these images to install the specific specialty apps for each department.
This way you will reduce the amount of images you will need to maintain in the future: the number of models vs. the number of models you have multiplied by the number of departments.
If the number of departments are low where each department uses a specific model then go for the images built specific for each department.