+ Post New Thread
Results 1 to 14 of 14
Windows Thread, mdt & wds in Technical; Im confused, mdt & wds seem to do the same thing, apparently re: all my previous questions about wds , ...
  1. #1
    browolf's Avatar
    Join Date
    Jun 2005
    Location
    Mars
    Posts
    1,524
    Thank Post
    106
    Thanked 88 Times in 74 Posts
    Blog Entries
    46
    Rep Power
    40

    mdt & wds

    Im confused, mdt & wds seem to do the same thing, apparently re: all my previous questions about wds, turns out we were using mdt (but had wds installed as well) :-S

    since it had broke I figured I'd start with wds by itself. followed instructions on here, captured an image, when it comes to deploy it back it doesnt work. think boot.wim needs drivers injecting cos there's driver failures in setupapi.log

    thing is injecting drivers in wds seems to be a massive pain in the ass, whereas mdt pretty much does it itself, put them in a folder, update files in workbench.

    wondering if I should uninstall wds and just use mdt, it seemed a whole lot easier to manage everything. what's the point of wds then?
    Last edited by browolf; 16th January 2009 at 03:48 PM.

  2. #2


    Join Date
    Oct 2006
    Posts
    3,411
    Thank Post
    184
    Thanked 356 Times in 285 Posts
    Rep Power
    148
    IMO WDS is very bad at what it does, its long winded, needs to boot an OS in order to install another OS and is generally a backwards step in many aspects...

    Are you deploying Vista? If not id recommend a gander at RIS (WDS legacy) with Autoimage RogueSpear's Forums • Index page

  3. #3
    browolf's Avatar
    Join Date
    Jun 2005
    Location
    Mars
    Posts
    1,524
    Thank Post
    106
    Thanked 88 Times in 74 Posts
    Blog Entries
    46
    Rep Power
    40
    no we're deploying xp

    turns out you still need wds as mdt doesnt do PXE booting but all you have to do with wds is install the litetouch boot image in the boot section, and then when they network boot the clients automatically connect with mdt.

  4. #4

    Gatt's Avatar
    Join Date
    Jan 2006
    Posts
    6,658
    Thank Post
    858
    Thanked 646 Times in 429 Posts
    Rep Power
    498
    MDT is excellent for creating new builds - it can slipstream drivers into Vista so they dont get lost when you Sysprep it, deploy an image automatically depending on its make & model or even its Role.

    Takes a bit of work at first to get it working, but once configured its a breeze..

  5. #5

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,076
    Thank Post
    853
    Thanked 2,676 Times in 2,270 Posts
    Blog Entries
    9
    Rep Power
    769
    Agreed, MDT is really good and simplifies a lot of things. It is a easy software layer that takes care of building the deployment images and controling their behavior/content without needing to do everything manually. This then creates a WDS WIM image that contains the right drivers to boot the clients from PXE and look to the MDT network share for machine builds which it can then deploy.

    The benifit of the whole windows core OS pxe boot is that it takes windows drivers which are in really short supply for quite a few new network cards and/or storage controllers.
    Last edited by SYNACK; 26th January 2009 at 11:37 AM.

  6. #6

    Join Date
    Jan 2006
    Location
    Surburbia
    Posts
    2,178
    Thank Post
    74
    Thanked 307 Times in 243 Posts
    Rep Power
    115
    I love MDT.

    Well apart from that PE network timeout bug which took a while to track down.

    PXE booting is the trivial bit. I never did get 2K8 WDS to work for me, but all you need are a couple of DHCP options and any old TFTP service.

  7. #7

    Join Date
    Mar 2012
    Location
    Ireland
    Posts
    2
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    WDS vs MDT

    Quote Originally Posted by browolf View Post
    Im confused, mdt & wds seem to do the same thing, apparently re: all my previous questions about wds, turns out we were using mdt (but had wds installed as well) :-S

    since it had broke I figured I'd start with wds by itself. followed instructions on here, captured an image, when it comes to deploy it back it doesnt work. think boot.wim needs drivers injecting cos there's driver failures in setupapi.log

    thing is injecting drivers in wds seems to be a massive pain in the ass, whereas mdt pretty much does it itself, put them in a folder, update files in workbench.

    wondering if I should uninstall wds and just use mdt, it seemed a whole lot easier to manage everything. what's the point of wds then?
    Hi

    Just running through some threads and seen your query BroWolf. It is a shame that it is now 2012 and your original post was 2009. However, I have experience with both technologies, and I would like to point to out that they may be similar in ways, but definitely one is much easier to use. I am a fan of WDS, mainly due to the fact of how it rolls out images. It is just a simple F12 keypress and pxe boot to the network, then choose if you want to capture and image or roll out an image, after this the answer files take care of the rest, right up to the CTRL ALT DELETE screen. Marvellous deployment tool, names the machines, joins them to the domain, activates windows etc....

    With my experiences with MDT however there is far more work having to be done on the ground and alot of wizards to go through ( which can be dubbed in the bootstrap.ini and config.ini). I have yet to find a way to boot to the deployment share other than USB or CD, which is a pain.

    The WDS has a driver pool as does MDT. Your original question about having to inject drivers into the boot.wim is easily rectified using WDS. I had similar problems with various models of machine and eventually figured out how to do this, rather quite easily. You do not need to use DISM or any of the WAIK tools to do this. There is a wizard in the WDS console. If you right click on your boot image there is an option to add driver package. All you have to do is get the drivers you need and extract them to folder, and open the wizard and point to the driver folder and voila the boot.wim has the drivers needed injected into it. No more network errors at boot time!!

    Hope this helps!! Even though it may be 3 years later )

  8. #8
    browolf's Avatar
    Join Date
    Jun 2005
    Location
    Mars
    Posts
    1,524
    Thank Post
    106
    Thanked 88 Times in 74 Posts
    Blog Entries
    46
    Rep Power
    40
    Quote Originally Posted by rocky View Post
    Hi

    Just running through some threads and seen your query BroWolf. It is a shame that it is now 2012 and your original post was 2009. However, I have experience with both technologies, and I would like to point to out that they may be similar in ways, but definitely one is much easier to use. I am a fan of WDS, mainly due to the fact of how it rolls out images. It is just a simple F12 keypress and pxe boot to the network, then choose if you want to capture and image or roll out an image, after this the answer files take care of the rest, right up to the CTRL ALT DELETE screen. Marvellous deployment tool, names the machines, joins them to the domain, activates windows etc....

    With my experiences with MDT however there is far more work having to be done on the ground and alot of wizards to go through ( which can be dubbed in the bootstrap.ini and config.ini). I have yet to find a way to boot to the deployment share other than USB or CD, which is a pain.

    The WDS has a driver pool as does MDT. Your original question about having to inject drivers into the boot.wim is easily rectified using WDS. I had similar problems with various models of machine and eventually figured out how to do this, rather quite easily. You do not need to use DISM or any of the WAIK tools to do this. There is a wizard in the WDS console. If you right click on your boot image there is an option to add driver package. All you have to do is get the drivers you need and extract them to folder, and open the wizard and point to the driver folder and voila the boot.wim has the drivers needed injected into it. No more network errors at boot time!!

    Hope this helps!! Even though it may be 3 years later )
    Thanks! Although we gave up with that and use fog server now { http://www.fogproject.org/ }

  9. #9
    chazzy2501's Avatar
    Join Date
    Jan 2008
    Location
    South West
    Posts
    1,781
    Thank Post
    213
    Thanked 263 Times in 213 Posts
    Rep Power
    67
    Quote Originally Posted by rocky View Post
    If you right click on your boot image there is an option to add driver package. All you have to do is get the drivers you need and extract them to folder, and open the wizard and point to the driver folder and voila the boot.wim has the drivers needed injected into it. No more network errors at boot time!!
    errr. I don't get this option.

  10. #10
    DMcCoy's Avatar
    Join Date
    Oct 2005
    Location
    Isle of Wight
    Posts
    3,432
    Thank Post
    10
    Thanked 488 Times in 428 Posts
    Rep Power
    111
    Quote Originally Posted by chazzy2501 View Post
    errr. I don't get this option.
    2008 R2?

  11. #11

    Join Date
    Jul 2009
    Posts
    541
    Thank Post
    43
    Thanked 101 Times in 86 Posts
    Rep Power
    67
    Quote Originally Posted by chazzy2501 View Post
    errr. I don't get this option.
    It's there in the 2008R2 version of WDS.

    Edit: was beaten by DMCcoy, but it was a new feature in 2008R2: http://technet.microsoft.com/en-us/l...=ws.10%29.aspx
    Last edited by computer_expert; 5th March 2012 at 01:34 PM.

  12. #12
    EvLPhenom's Avatar
    Join Date
    Apr 2006
    Location
    Sutton Colfield
    Posts
    430
    Thank Post
    21
    Thanked 39 Times in 34 Posts
    Rep Power
    23
    @browolf I did exactly the same here. Think fog is a great peice of software and just sits there until I need to do something, then just schedule the lot to image and job done, practically zero touch for computers. Laptops have to have some bits done but nothing major. I was very pleased with it compared to when we used Ghost.

  13. #13

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,076
    Thank Post
    853
    Thanked 2,676 Times in 2,270 Posts
    Blog Entries
    9
    Rep Power
    769
    Quote Originally Posted by rocky View Post
    I have yet to find a way to boot to the deployment share other than USB or CD, which is a pain.
    Just add the lightouch.wim from the MDT share, this boots it just like WDS with f12 but with all the additional functionlity afforded by MDT.

  14. #14

    Join Date
    Mar 2012
    Location
    Ireland
    Posts
    2
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    WDS + SCCM

    Sorry should have said that we are using R2 SP1 Systems which does have extra functionality. It still can be achieved by using WAIK system Image manager. Have just started a new project, purely on a test pilot basis. Have SCCM up and running but only at early stages, have managed to deploy the client agent and some software packages to clients. Trying to get OS deployment configured...it's pain staking and frustrating.... anyone know of any good articles on OSD using SCCM 2007??

    Cheers!

SHARE:
+ Post New Thread

Similar Threads

  1. WDS Unattended help
    By Ste_Harve in forum Windows
    Replies: 15
    Last Post: 20th June 2011, 12:22 PM
  2. (MDT), WDS and PXE TFTP not happening
    By PiqueABoo in forum Windows Server 2008
    Replies: 5
    Last Post: 14th November 2009, 03:17 PM
  3. RIS & WDS Show stopper :(
    By ssiruuk2 in forum Windows
    Replies: 3
    Last Post: 18th August 2008, 07:51 PM
  4. WDS Legacy Mode vs WDS
    By markwilliamson2001 in forum Windows
    Replies: 0
    Last Post: 15th July 2008, 12:50 PM
  5. WDS or RIS
    By netadmin in forum Windows
    Replies: 5
    Last Post: 12th July 2007, 07:03 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •