Drivers not installing on TS

[Scott]

Hi

We have a single TS which will image both Intel and AMD devices, however the only AMD device that we have to test on, the drivers are not installing correctly. They are being copied to the C drive of the device, but are not installed, even by applying a driver package or automatically apply drivers.

 

Currently, the workaround is to install the software that was downloaded with the software, but this also installs the rubbish software with it! (ATI Graphics and HD Audio)

 

Has anyone ever had this? How did you get around it?

 

Cheers!

Scott

[Peter van der Woude]

Some drivers, often mentioned as BAD Drivers, just don't have the ability to be (good) installed without the executable...

[Paul H]

If the driver is present and you tell the machine to search for new hardware, does it find and use the proper drivers then?

 

In that case you might try an extra PnP run on the machine

a command line step with rundll32.exe Syssetup.dll,UpdatePnpDeviceDrivers

sometimes works

[Scott]

Some drivers, often mentioned as BAD Drivers, just don't have the ability to be (good) installed without the executable...

Is this because of the hardware, or is it worth trialling older/newer/oem versions of the drivers?

 

If the driver is present and you tell the machine to search for new hardware, does it find and use the proper drivers then?

 

In that case you might try an extra PnP run on the machine

a command line step with rundll32.exe Syssetup.dll,UpdatePnpDeviceDrivers

sometimes works

 

They will install using the inf, but not if i automatically search, I have to point to the inf file and install it that way. Is it possible to identify the correct path, like we used to using the sysprep driver path?

 

Cheers

Scott

[Scott]

This is now resolved!

 

I believe the issue is that when SCCM installs the Mass Storage driver, it creates around 150 folders in the C:\Drivers folder, it then reference this in HKLM>Software>Microsoft>Windows>Current Version > DevicePath. However, there is a character limit to this and therefore it wont reference the folders that contain the required inf files. My workaround for this has been to create a seperate software package with the correct drivers, a reg fix and a batch file to reinstall the drivers later in the task sequence. For anyone having this issue, the batch file contains the following:

 

xcopy "%~dp0\3DG\*.*" "C:\HP6555b\3DG\" /Y /V /R
xcopy "%~dp0\3DG\amd64\*.*" "C:\HP6555b\3DG\amd64\" /Y /V /R
xcopy "%~dp0\3DG\x86\*.*" "C:\HP6555b\3DG\x86\" /Y /V /R
xcopy "%~dp0\AUD\*.*" "C:\HP6555b\AUD\" /Y /V /R
xcopy "%~dp0\GFX\*.*" "C:\HP6555b\GFX\" /Y /V /R
xcopy "%~dp0\GFX\B_99351\*.*" "C:\HP6555b\GFX\B_99351\" /Y /V /R
xcopy "%~dp0\VID\*.*" "C:\HP6555b\VID\" /Y /V /R
xcopy "%~dp0\NIC\*.*" "C:\HP6555b\NIC\" /Y /V /R
regedit.exe /s "%~dp0\devicepath.reg"
START /WAIT RunDll32.exe Syssetup.dll,UpdatePnpDeviceDrivers

 

The xcopy lines are copying the inf files from the sourcefiles folder to the C: drive path

The regedit line imports the registry with the new DevicePath

%SystemRoot%\inf;%SystemDrive%\HP6555b\3DG;%SystemDrive%\HP6555b\3DG\amd64;%SystemDrive%\HP6555b\Aud;%SystemDrive%\HP6555b\GFX;%SystemDrive%\HP6555b\GFX\B_99351;%SystemDrive%\HP6555b\VID;%SystemDrive%\HP6555b\NIC

And the RunDLL line updates the drivers, searching through the folders specified in the paths above.

 

Cheers and hope this helps anyone else!

Scott