drivers | Todd's Blog

Managing Drivers in Task Sequences with System Center Configuration Manager 2012

posted on February 19, 2014

When of the question I always get when deploying Windows whether it be Microsoft Deployment Toolkit or System Center Configuration Manager is how to I properly deploy drivers.

Now there is no right or wrong way, but I always steer people away from putting them in one big folder and letting the OS figure out which to use. Have you ever seen a Dell using an HP Driver? Been there so here is a flashback of a back post of how to manage drivers in MDT.

Let’s take a quick look at how to clean this up in System Center Configuration Manager. Basically add your drivers and put them into folders and then add them in as driver packages.

Then when setting up your task sequences, add a section where it evaluates the machine type and if it matches, apply the drivers.

Here is a screen shot of a task sequence in System Center Configuration Manager I did for a customer.

What happens here is as the task sequence continues along, it checks to see if the drivers need to be applied based on a WMI query. To get this information use WMIC to pull out the model information.

Further along we install applications that are drivers, but poor ones in that they need to be installed. Again we use a WMI query to only install the application if it matches the make and model of the device we specify.

Driver Management in MDT 2010

posted on August 9, 2010

If you manage drivers in Microsoft Deployment Toolkit, you know it can get unwieldy to manage all the drivers in one big folder. I had done it that way for quite a while as I only had 3 or 4 builds of computers that I managed from MDT. These days though I manage about 10 different kinds of computers covering netbooks, laptops, desktops and servers. I needed a way to be able to figure out which driver was for which computer. I had used folders to manage this and it seemed to work okay. Put all the Dell drivers in one folder, put HP into another folder. I never encountered any problems doing this. [Read more…]

Group Policy Preferences

posted on May 14, 2008

I have upgraded two of three domain controllers to Windows Server 2008 over the last couple months. The install went smooth and I will admit, Windows Server 2008 does seem like a rather nice OS. One of the new features of having a Windows Sever 2008 domain controller is the group policy preferences. Preferences will let you do things like create desktop shortcuts, printer mappings and map network drives along with many other things.

I decided to use it to do two things, the first being map network printers and the second create desktop shortcuts. Group Policy in 2003 R2 had the option to push printers based on linking policies to OUs. Group Policy preferences had the benefit that I could create on Policy, and have printer maps based on the computer’s subnet. For example, machines with 42 in the third octet would be given printers local to that site, computers in 40 subnet would be given a different set of printers, but I wouldn’t need to have multiple policies, nor would I have to worry about moving the computer between OU’s. I could also push desktop icons to users who say belong to a certain group , relatively quick and painless. Basically, the new features match things I have seen in the past with Scriptlogic which is a product I was very pleased with when I used it at the City of Kingston, back when I worked there.

Once you create your settings, you need to ensure the patch to use group policy preferences is applied to the computer. You can download the patch from Microsoft’s site and is available for XP, 2003 and Vista. I applied the patch to test the machines, rebooted and the machine came up, I logged in as the patron and the computer froze, would no longer log in. It would try but go nowhere. Remove the group policy from being applied, the machine logs in.

I don’t know what the problem is yet, but I narrowed it down to adding the printers and I am guessing it is driver related. The computers I tested on where Vista and needed the driver installed, so UAC could have also been hanging it up. The printer is applied as a user preference but it looks at the subnet of the computer to determine which printer to install. I plan to test later but for now I will use GPO to assign printers to computers.

I will have more to come on this, probably in June or July.