+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 20
O/S Deployment Thread, WDS vs WAIK vs MDT vs SCCM? in Technical; Quick Intro I see a lot of talk with all these different deployment tools but I'm finding it tricky to ...
  1. #1
    Sam_Brown's Avatar
    Join Date
    Sep 2009
    Location
    Northampton
    Posts
    436
    Thank Post
    73
    Thanked 24 Times in 22 Posts
    Rep Power
    14

    Cool WDS vs WAIK vs MDT vs SCCM?

    Quick Intro
    I see a lot of talk with all these different deployment tools but I'm finding it tricky to figure out how they relate to one another, which ones supercede others and just in general how they work and what they do.

    Now I've been in IT for about 18 months now so while I feel I've picked up a hell of a lot in that time I'm still relatively green so forgive me for any inaccuracies I make in this and subsequent posts. Also the more info you guys can give the better for me!

    WDS, WAIK, MDT and SCCM
    Could someone give me a brief run down on each of these and how they work together. What each one does and whether any of them supercede the others? For example do you still need WDS if you have SCCM set up?

    SPECIFICS I WANT TO DO!
    Anyway I'll tell you where we were and where we are now and perhaps you guys could give me an idea on where to move to next.


    GHOST
    So in ye olden days we had an old ghost cast server. You'd F12 and PXE boot into RIS (on the same server), select the relevant GHOST boot image with the correct DOS Drivers for the network card then the reset was just the standard connecting to the Ghost Cast Server and capturing \ deploying an image. This worked ok for a while but I decided we should move away from GHOST because it was getting harder to find DOS drivers that worked for newer machines and this led to alot of issues with clients dropping out mid imaging\ not being able to connect in the first place.

    WDS
    So I spend a week or so reading up on WDS. Installed it on a blank 2K8R2 server and configured it. All in all it was pretty easy and took about two hours to get it up and running and capturing images. It seems to me that WDS is pretty much the same as GHOST. Create a base image. PXE boot to the network and then capture it so you can deploy it later on. Immediately though I found it loads better than the previous GHOST server because we had no issues connecting to the WDS server (well apart from one set of laptops but injecting the drivers into the boot image was easy to fix). It was also a lot quicker to capture and deploy and we had no issues with clients dropping out half way through. Also learning to use Sysprep has enabled me to learn about automating certain things with the newly imaged machines such as auto joining the domain (we still put the computer name in manually using minisetup).

    Can you believe in the olden days we didn't use Sysprep and instead manually connected all imaged computers to the domain and run NEWSID? Madness! I still have nightmares from last summer when I had to image 60 laptops manually one by one and running NEWSID \ Joining The Domain Manually .

    WHERE DO I WANT TO GO NEXT?
    So this is all working out pretty awesome. A lot better than the old Ghost way we did things however it's become obvious that we now have about 8 or 9 different models of PC and Laptops with pretty much exactly the same image and the only difference being they have different hardware and therefore need differing drivers. But it seems stupid having so many images for such a minor change. I've heard about the ability to create hardware independent images. I was wondering how do I go about doing this and what tools do I need? Also something minor but was wondering how to configure naming the computers once they've been imaged. So far the only real intervention we have from starting to image a machine to it being ready is to put in the machine name. What are the best ways to automate naming the computers so the correct computer gets the correct name when it's imaged?

    AND WHERE I WANT TO BE AFTER THIS?
    The next big issue we have is regarding things like Flash and Patches for programs like Seriff and whatnot. At the moment end users have to bring there laptops to us and we log them off, log on as admin and update it for them. This is a pain in the arse . Believe there is a way to use some of the deployment tools to push out updates to client computers but I have no idea how to do it and again what technologies I need to use. Can anyone help? Also I'm interested in making things a bit more Zero Touch. Possibly pushing out deployments from the server instead of going round the rooms.

    FIN
    Whoa... that is one hell of TL;DR right there. Hope some of you guys will be kind enough to give me some help with this! I know I can probably find all this on my own however I really think asking on here is going to give me the direct answers to the questions I have and hopefully some of the more experienced on here can give me some pointers and examples of how they set things up. I find it easier to see how other people have done things and working out how that works opposed to reading through a 400 page book and trying to pick out the bits I need!

  2. #2

    Gatt's Avatar
    Join Date
    Jan 2006
    Posts
    6,543
    Thank Post
    831
    Thanked 610 Times in 413 Posts
    Rep Power
    432
    If you have the time and patience, I would thoroughly recommend looking into SCCM..
    Its a cracking system and will be a big timesaver once working

  3. #3
    TheScarfedOne's Avatar
    Join Date
    Apr 2007
    Location
    Plymouth, Devon
    Posts
    1,075
    Thank Post
    520
    Thanked 146 Times in 132 Posts
    Blog Entries
    78
    Rep Power
    78
    Likewise... another vote for SCCM here. Please see my blog post series for getting it set up. Also, feel free to PM me if you need any help/advice.

  4. Thanks to TheScarfedOne from:

    Sam_Brown (24th March 2011)

  5. #4

    Join Date
    Dec 2008
    Location
    Essex
    Posts
    2,137
    Thank Post
    1
    Thanked 326 Times in 316 Posts
    Rep Power
    76
    Hi

    It seems like that you need to use SCCM as Gatt suggested. This will allow you to create you independent hardware images/architecture images as well as deploy applications to machines without interruption to the user. There are major differences between WDS and SCCM. SCCM is more for the enterprise who want more than just deploying the OS to the desktops. If you;re looking for zero touch then this is a must.

    Creating hardware independent images, deploying applications etc... There are lots of posts within edugeek and sticks that you can read rather than a 400 page document which explains the technologies.

    I think the next step for you is to actually deploy SCCM and then maybe ask specific questions if you have issues or want to know "how to".

    Sukh

  6. #5
    Sam_Brown's Avatar
    Join Date
    Sep 2009
    Location
    Northampton
    Posts
    436
    Thank Post
    73
    Thanked 24 Times in 22 Posts
    Rep Power
    14
    So with SCCM I don't need WDS \ WAIK \ MDT and won't need to know about these three?

    If that is the case is it worth starting on a brand new server with no WDS set up on it?

    Also would there be any issues with having SCCM on the same server as WSUS?

    EDIT: As it stands we using Windows XP across our site. We probably won't be moving to 7 until 2012 (possibly a few test work stations this summer). Is this going to screw things up at all as all the guides I have read refer to Windows 7. I was wondering on whether SCCM would work with Windows 7?
    Last edited by Sam_Brown; 24th March 2011 at 09:52 PM.

  7. #6

    Join Date
    Dec 2008
    Location
    Essex
    Posts
    2,137
    Thank Post
    1
    Thanked 326 Times in 316 Posts
    Rep Power
    76
    Hi

    WAIK/MDT can and is used with SCCM. SCCM supports Windows 7 too. With SCCM you have OSD for OS Deployment. WSUS Integrates with SCCM, WSUS will become Winodws Update Services under SCCM.

    Sukh

  8. #7

    Gatt's Avatar
    Join Date
    Jan 2006
    Posts
    6,543
    Thank Post
    831
    Thanked 610 Times in 413 Posts
    Rep Power
    432
    SCCM R3 pretty much handles everthing on the network here now - OS Deployment of WIndows 7, Software Deployments, WSUS Integration, Reporting
    There is also Asset Intelligence and NAP integration though I haven't looked at these two areas in any detail..

    It took a lot of work to get it right, and I would recommend installing it in Native Mode if you are able to build the needed PKI and Certificates - it'll make life easer and wont cause dupliate clients..

    I pretty much found http://www.windows-noob.com to be the best source for guides and information for SCCM.

    As noted above SCCM does need the WAIK and WDS (you may need to reinstall WDS as it needs to be unconfigured - same with WSUS) for OSD..

    th e other good thing about SCCM is that you can monitor advertisements pretty much live with the System Status tree and usually it tells you where something has failed.

  9. Thanks to Gatt from:

    Village_Idiot (17th May 2011)

  10. #8

    Join Date
    Apr 2010
    Posts
    1,834
    Thank Post
    62
    Thanked 161 Times in 133 Posts
    Rep Power
    64
    SCCM is probably what you want but I just wanted to point out that all the others can do driver injection even a wim image with my sysprep running from a usb or network point can do this.

  11. #9
    Sam_Brown's Avatar
    Join Date
    Sep 2009
    Location
    Northampton
    Posts
    436
    Thank Post
    73
    Thanked 24 Times in 22 Posts
    Rep Power
    14
    Ah ok.

    I'll probably start with this then move on to SCCM later when I have the time. What is the best way to inject drivers into a Windows XP image?

    Oh and could someone tell me how WAIK \ MDT relate to WDS and what they both do?

    Thanks

  12. #10

    Gatt's Avatar
    Join Date
    Jan 2006
    Posts
    6,543
    Thank Post
    831
    Thanked 610 Times in 413 Posts
    Rep Power
    432
    MDT is probably your best place to start.. It'll do eveything you need to do via Task Sequences - install OS, inject the necessary drivers and then install any sofware you want via LTI and uses the WAIK behind the scenes for configuring Windows settings

    You create an MDT Boot image that you can then add to WDS, allowing you to PXE boot your PCs with the MDT Boot Image

    You can script MDT based on Make/Model of PCs - handy for Driver Integration
    I used to use MDT this way so that all I had to do at a PC was enter the name of the PC and what software I wanted on it - eveything else was handled by the Task Sequences

  13. #11

    Gatt's Avatar
    Join Date
    Jan 2006
    Posts
    6,543
    Thank Post
    831
    Thanked 610 Times in 413 Posts
    Rep Power
    432
    Just thought i'd give quick summary of what everything is/does


    • WAIK - Windows Automatied Installation Kit - needed for just about everything - has all the tools for WIM files (WinPE, imageX, etc) - Also contains System Image Manager (SIM or WSIM) which is used to edit unattend XML files for Vista / 7 / 2008 / R2
    • WDS - Windows Deployment Services - Replaces the old RIS service - 3 main points - Boot Images - for PXE booting the PC to either WDS itself or MDT or SCCM.. Clean Install Windows (Vista onwards) as if it was from the install DVD, or capture and deploy a sysprepp'd PC - XP onwards...
    • MDT - WDS with extras - alllows for custom "fresh" deployments of Windows XP onwards, and can be customised with drivers, OS Patches, Software via Task Sequences - Can be furhter customised by targetting TS's to Makes/Models of PC (eg drivers).. Ues Lite Touch Installations (LTI) - so you need to visit each PC - at least once (power it on and press F12) depening on the TS's
    • SCCM - the creme de la creme - does everything MDT does and a heck of a lot more - it supports Zero Touch Installations (ZTI) - meaning you dont even need to go near a PC to rebuild it (Force PXE Boot, Schedule Rebuilds at a certain time), can integrate with MDT (never done this but it is possible)
    Last edited by Gatt; 25th March 2011 at 09:01 AM.

  14. 2 Thanks to Gatt:

    camel (29th March 2012), Village_Idiot (17th May 2011)

  15. #12
    tarquel's Avatar
    Join Date
    Jun 2005
    Location
    Powys, Mid-Wales, UK
    Posts
    1,740
    Thank Post
    13
    Thanked 44 Times in 34 Posts
    Rep Power
    28
    Just my two pence here, and pretty much echo'ing the others many, while I fully love and recommend SCCM, I dare say that it could be overkill depending on what you actually need.

    If you do want or need to do normal application deployment (after the OS is on the machine), OSD (Operating System Deployment in SCCM Terms ), machine inventory and reporting / Software Metering, etc etc.... then, providing the licensing cost isnt too much for you, go for it.

    If you think it might be a case of doing too much in one hit, but eventually you will want it, then possibly just set it up, but only use it for Application Deployment and some light reporting, and set up a seperate WDS/MDT server for OSD'ing.

    We kind of did this approach, with the exception that we used (and still do currently use) RIS for deploying XP, next came the set up of SCCM for some inventory / package deployment / natural progressing of things, and then started deploying Win7 via SCCM OSD around Oct of last year

    At the very least, it would seem to me that you'll likely need WDS WITH MDT in it for your needs (may as well, they are both free and MDT with WDS gives you much more scope than either one alone IMO), and it'll help you get in to how the OSD works in SCCM, while keeping SCCM fresh for when you're confident in doing that.

    Quite happy to have a chat about it in the evening if you want a IM'ing session - I'm heavily into it myself, along with some not-so-easy customised things within it - so always happy to chat about it PM me later on if you do want to chat about it

  16. 2 Thanks to tarquel:

    OverWorked (29th June 2011), Village_Idiot (17th May 2011)

  17. #13

    Join Date
    Mar 2008
    Location
    S.E. Kent
    Posts
    8
    Thank Post
    0
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Hi All,
    We have just bought into EES agreement with MS, desktop and core std. I have given myself lots of work , updating windows XP to Windows 7 and office 2003 to Office 2010 on around 500 computers & laptops around the school.
    I have used Ghost 2.5 and sysprep in the past while booting from a USB stick into PXE. SCCM cal are included in the agreement while the SSCM server licence probably costs less than 200 inc SQL . so is reachable in cost. Although I haven't got hardware to put in on. What's the min spec ? I have got workstations I could use as servers e.g. DEll GX745 dual core machines 2Gb ram. I can use either 2003 or 2008 server. Good enough ?
    So where shall I start? SCCM or WDS or stay with Ghost? We also deploy packages (msi) via AD and MS updates via SWUS also AV via McAfee , I think Forefront may be included in EES.
    My current deployment XP pro with office etc image via ghost takes 40 mins ... boot to usb stick, load sysprepped image, when done just name machine and its joined to the domain.
    How quick is SCCM?
    Does it put the win 7 key in , allow naming and join to domain ?
    Any comments thanks.

  18. #14

    Gatt's Avatar
    Join Date
    Jan 2006
    Posts
    6,543
    Thank Post
    831
    Thanked 610 Times in 413 Posts
    Rep Power
    432
    It depends on the size of the deployment..
    SCCM can install from the network or from USB/DVD
    An average network install takes about an hour, it takes its names from AD and auto-joins the domain or to a workgroup and can store Windows 7 keys (OEM or MAK - none needed if KMS is in effect)
    I dont use image based installs favouring clean installs of windows and applications.

  19. #15

    Join Date
    Mar 2008
    Location
    S.E. Kent
    Posts
    8
    Thank Post
    0
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Hi Gatt,
    Ok bit slower than Ghost.
    we generally ghost 32 pc's at a time using around 12 different images (windows XP) I'm hoping we can reduce that with Win 7.
    "I dont use image based installs favouring clean installs of windows and applications" what does that mean ?.... clean image of Win 7 followed by packages sent via AD ( msi) ?
    Is this because more flexible in package changes ?
    Should I start small say with WDS or just jump straight in with SCCM (not used either before) ?

SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. mdt & wds
    By browolf in forum Windows
    Replies: 13
    Last Post: 10th March 2012, 12:33 AM
  2. Zero Touch MDT SCCM
    By oxide54 in forum O/S Deployment
    Replies: 3
    Last Post: 9th January 2011, 03:38 PM
  3. MDT/WDS is doing my head in...
    By Sirbendy in forum O/S Deployment
    Replies: 6
    Last Post: 15th October 2010, 03:36 PM
  4. [SCCM 2007] Setup SCCM 2007 with MDt 2010 and WDS
    By Gatt in forum O/S Deployment
    Replies: 2
    Last Post: 7th November 2009, 11:19 AM
  5. WAIK, WDS, WSS3 released
    By thom in forum Windows
    Replies: 2
    Last Post: 17th November 2006, 08:12 PM

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
  •