kelvin

Thanks for the reply... Windows XP, and whatever client ships with ConfigMgr 2007 R2 SP2. All clients are XP - 700 or so have installed successfully, with only a handful exhibiting the "Found New Hardware" symptoms. I've noted that on some machines, when I go into the driver properties for the ConfigMgr Remote Control driver it is listed as unsigned, and only one driver file is listed (C:\WINDOWS\system32\DRIVERS\smsmdm.sys) - as opposed to the two files as reported on some other clients which show the driver as signed. I'm confused to be honest - the vast majority of clients appear to have installed successfully (even those with the Remote Control Driver issue), but there is clearly something not quite right about this component. What is the function of the Remote Control Driver, and should it be reported as signed on all machines that have the client installed? Could a local conflict result in the driver not being installed fully, leading to the "unsigned" issue? Kelvin

As a brief follow up to this, it appears that once installed, "some" ConfigMgr Remote Control Drivers on clients show as signed within device manager (although viewing the driver via a remote device manager session always shows it as unsigned... bizarre...). That said, there have still been (and may be more out there) a number of machines that haven't successfully installed because they think the driver is unsigned. Anyone?!

Afternoon all, I have an issue I could do with some assistance on... We're mid-deployment of SCCM at a customer of ours, and I have a handful of clients that are presenting a "Found New Hardware" popup relating to the ConfigMgr Remote Control Driver. We are deploying the Client Agent via a GPO, and have around 700 reported "successful" installations. It appears from some preliminary investigation, that the driver installed is unsigned so fails to silently deploy - it's effectively waiting for an administrator to approve the unsigned driver before finalising the install of the Remote Control device. Our workaround is obviously to log on as an Administrator/provide administrative credentials which allows the installation to complete - this is far from ideal though. The ccmsetup.log reports a successful installation, and the client reports back to the MP as having the client regardless of whether the driver issue is present. At the moment we've only had reports of this on a few devices, but this could be on the majority for all we know - we have no way of telling. Has anyone else come across this issue? Surely the driver should be signed? Is there a way we can prevent this from happening? Thanks in advance, Kelvin