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 ...
24th March 2011, 09:03 PM #1
IDG Tech News
24th March 2011, 09:16 PM #2
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
24th March 2011, 09:20 PM #3
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.
Thanks to TheScarfedOne from:
Sam_Brown (24th March 2011)
24th March 2011, 09:34 PM #4
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".
24th March 2011, 10:47 PM #5
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 10:52 PM.
24th March 2011, 11:40 PM #6
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.
25th March 2011, 08:13 AM #7
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.
Thanks to Gatt from:
Village_Idiot (17th May 2011)
25th March 2011, 09:24 AM #8
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.
25th March 2011, 09:38 AM #9
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?
25th March 2011, 09:42 AM #10
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
25th March 2011, 09:57 AM #11
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 10:01 AM.
2 Thanks to Gatt:
camel (29th March 2012), Village_Idiot (17th May 2011)
6th April 2011, 04:01 PM #12
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
2 Thanks to tarquel:
OverWorked (29th June 2011), Village_Idiot (17th May 2011)
15th May 2011, 09:56 PM #13
- Rep Power
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.
15th May 2011, 10:24 PM #14
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.
15th May 2011, 10:57 PM #15
- Rep Power
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) ?
By browolf in forum Windows
Last Post: 10th March 2012, 01:33 AM
By oxide54 in forum O/S Deployment
Last Post: 9th January 2011, 04:38 PM
By Sirbendy in forum O/S Deployment
Last Post: 15th October 2010, 04:36 PM
By Gatt in forum O/S Deployment
Last Post: 7th November 2009, 12:19 PM
Last Post: 17th November 2006, 09:12 PM
Users Browsing this Thread
There are currently 2 users browsing this thread. (0 members and 2 guests)