Deployment | Todd's Blog

Drivers Showing as Unsigned in Configuration Manager 2012 R2

posted on January 5, 2016

A customer has a problem with importing drivers for their Surface Pro 3 devices in System Center Configuration Manager 2012 R2.

We keep noticing some of the drivers are unsigned. I immediately realized something is up as Microsoft releasing unsigned drivers isn’t going to happen. So I started digging and immediately came to KB3025419 which seems to cover my situation. My customer uses Windows 2008 R2 as the Host operating system for the Configuration Manager server and so this KB is relevant. Basically, Microsoft changed the way they signed drivers and now use a different method. This new method is different than what Server 2008 R2 recognizes and thus the change.

It affect Configuration Manager 2007, 2012 and 2012 R2 so you might see this as well down the road once hardware vendors use the new method.

Install the patches and don’t forget to reboot. A reboot is required even if it doesn’t prompt for a reboot. How do I know this, experience. Our server was patched by a different team but they didn’t reboot. The problem still persisted until the reboot.

Another thing you have to do is remove the “unsigned drivers”. This means delete the drivers that are showing unsigned before re-importing the drivers again. Once these two steps were performed we were back in business.

If you are running Windows Server 2008 R2 for your System Center Configuration Manager install you might just want to install this patch during your next maintenance schedule. As more vendors sign their drivers in the new method, you might start to see issues even if you don’t deploy Surface Pro. Of course, if you are running Windows Server 2012 R2 you probably have never saw this issue and the patches are not required.

Problems Deploying Apps with System Center 2012 R2 in an OSD Task Sequence

posted on August 26, 2015

Onsite at one of my customer’s sites we are deploying operating systems with a Config Manager 2012 R2 task sequence (TS). The issue I was having was the applications were not installing. They were set to deploy in a task sequence without deployment so that wasn’t the issue. Looking at the log, (logs are your friend, use them) and I discovered this:

Unknown operating system build number 9600 found, setting OSVersion to 'Other'.

Ouch, what does this mean. It means my CM12 deployment has something not right with it. I don’t what the issue is but I will bring it up with Garth of Enhansoft who is an Enterprise Client Management MVP. He might have an idea on how to fix this.

In the meantime, I just changed the settings so that the software doesn’t have an OS requirement to install it. Basically I can set the package so it only installs on Windows 7 or Windows 8.1. In this case we can’t use that as we don’t know the OS.

Just change the package or app and allow it to be installed on all operating systems and it will deploy fine. Not a great solution for those trying to lock down apps to specific operating systems but it works.

Once I figure out why 9600 is not being recognized, I’ll update the post and we can all fix.

Upgrading a Windows Server 2003 Domain Controller

posted on May 29, 2015

Customers seem to be finally getting the message about end of support for Windows Server 2003. Support ends in July. (July 14,2015 actually) So I have been assisting customers in preparing for their upgrade.

In most cases, the Server 2003 box is a 32-bit box so the an in-place upgrade path is non-existent. So I have designed steps for a side by each upgrade. The idea here is to bring up a new box on Server 2012, promote it to a domain controller and then demote the old 2003 Server DC.

*Update – One note before you start, you need to be at the Windows 2003 Domain and Forest level.

After installing the domain services role, click in the upper right, then click on Promote this server to a domain controller.

Next fill in the Deployment Configuration options. As you can see , I have selected Add a domain controller to an existing domain, selected a domain and entered my credentials.