In this article, I’m going to show you how to maintain a driver library within MDT and use one Task Sequence for all hardware models.
Separate your drivers out to avoid conflicts and reliability issues. This also makes it easier to update manufacturer drivers.
In this article, I’m going to demonstrate how to configure WSUS to work with MDT (or rather MDT to work with WSUS).
Now, updating the odd computer with the latest updates isn’t really an issue, even on the slowest of internet connections. But what if your trying to update tens, or hundreds of client computers during your image deployment? Every one of those clients is going to individually attempt to contact Microsoft and download necessary updates. You’ll find this quickly bottlenecks your internet feed, even on the fastest of connections.
What’s a WSUS?
No, cast that image that weedy person to one side!
Because we’re talking about Microsoft WSUS!!
Windows Deployment, Part 3: Installing and Configuring WADK
We now need to install WADK (We’re concentrating on Windows 8.1 deployments (if you want to deploy Windows 7, you would need WAIK http://www.microsoft.com/en-us/download/details.aspx?id=5753 – WAIK cannot coexist with WADK!)
Download WADK from: http://www.microsoft.com/en-us/download/details.aspx?id=30652 It is several GB in size (16-07-2015 – link updated to Windows 8.1 Update version of the WADK).
Get WADK for Windows 10 here
Run the adksetup installer (you’ll be given the option to download the full package for use on another computer – I recommend this).
Accept the default options.