Incorrect TPM driver deployed through MDT2010 using Dell CAB files

Question

I have a MDT2010 deployment server to image our Dell Latitute E4300, E4310, E6320, E6400, E6410, and E6420 with Windows 7 Enterprise (x86 and x64). With each release of a new CAB for the models listed previously, I create a new folder with the name of that CAB file. I build a LiteTouch boot media for x86 and x64, then re can begin imaging. We have begun to look at enabling TPM/Bitlocker . When encrypting the OS drive, Windows complains saying TPM is not enabled but it is in the BIOS. After looking through the system devices, I see a device titled Broadcom TPM. (Driver ver: 3.0.0.2; Date:11/19/2009). If I uninstall and tell Windows to remove the driver than rescan the hardware, the following driver appears: Working driver: Broadcom Trusted Platform Module (A2) v1.2 V 6.1.7600.16385 Driver provider: Microsoft Date:6/21/2006 This is a fresh Windows 7 Enterprise deploy from MDT2010 No additional drivers (except Dell CAB files listed in Out-of-Box drivers) , updates, nor applications. If I do a fresh Windows 7 Enterprise DVD install, the Microsoft driver is installed and TPM works. I see no errors in Device Manager regarding this device, it just seems like the newer Broadcom driver does not work. Somewhere the wrong driver is in these CAB files which is being copied over. Any ideas? Thanks. Steve

DELL-Warren B · Answer

Is this with a specific system in your list or all of them?

steve.poe · Answer

I also have the Dell WinPE A06 installed in the Out-of-Box drivers. Currently, I can duplicate this on an E4300, E6320, E6400, and E6420. I do not have access to the other models at this moment.

DELL-Warren B · Answer

Since it is happening on a number of systems, I would remove the Broadcom TPM driver from your driver packages to see if that clears it all up. If so, then I'll send that feedback to the dev team for review.

steve.poe · Answer

I think found the source inf file, I think, but I don't know what package this would be listed as. I am going to have to look in each package folder. I'll keep you posted.

steve.poe · Answer

It seems like the BTPMWIN.INF package is the culprit.. I will test a little more.

steve.poe · Answer

In Microsoft's MDT2010, I found the BTPMWIN package, compressed the folder, deleted it, then I was able to enable TPM. With either of the Dell Latitudes I mentioned, what TPM driver package (version and date) should be recognized coming from the Windows 7 CAB files?

side note: I keep the old packages enabled, Dell E4300 Win7 A00, even though Dell E4300 Win7 A01 is the latest CAB that I've added. I figure the latest driver will get recognized. Any thoughts?

Thanks.

Steve

steve.poe · Answer

Unfortunately, renaming the package isn't good enough, the system is still wants to use the newer Broadcom TPM driver which does not work.

DELL-Warren B · Answer

Yes, you will have to remove it completely. Also, be wary of leaving older drivers available. I've seen a few instanced where the newest driver was superseded by an older one for various reasons. So having only the latest available is a best practice.

steve.poe · Answer

I will give this a try.

nrfowle · Answer

Thanks to this post, I had the same problem with a Latitude E4300 whilst deploying the Dell CAB file via Configmgr/MDT2010 OSD. by removing the Broadcom TPM driver from the package and redeploying the E4300 build completed successfully enabling TPM and Bitlocker. Thank guys for this post. Also deploying to E4200,E4300,E4310,E6400,E6410,E6220,E6320,E6420,E6500,E6510, Optiplex 740,780,790,960,980,990. all succussful but each using its individual driver package (Dell CABS)

Clint11 · Answer

In my experience using the Microsoft included TPM driver in Windows Vista and later is always better than using Broadcom TPM drivers.

armeng · Answer

I am having the same issue.  I have checked my driver bits and there is no sign of the BTPMWIN.inf driver.  I went into my driver store and removed the Broadcom TPM drivers, updated the DPs and still everytime i image a laptop, the TPM Device installs as Broadcom TPM under System Devices in the Device manager rather than Security Devices.  This is a really frustrating problem.  Anyone have any ideas?

Reza Prawirasat · Answer

I also posted here

en.community.dell.com/.../2065.dell-driver-cab-files-for-enterprise-client-os-deployment.aspx

Is there a way for me to contact Dell Driver CAB support by phone! This is for latest Dell Driver CAB version 5.0. We started ordering Optiplex 7010 and it installed all the drivers via SCCM (no need to use TPM) but on the laptop site (it broke the TPM!!!) with the same message from posted by "teamfox201"

NOTE: There's no TPM problem with Dell Driver CAB version 3.0

I have the same issue with the poster below.

Posted by teamfox201 on 10-10-2012 7:56 PM

TPM does not work from the CAB file, I ran into the same issue. I removed all the TPM drivers and then it properly appeared under Security Devices. Microsoft does not recommend using NON Microsoft TPM drivers.

If you use the TPM driver from the CAB, expand System Devices. Right Click Broadcom TPM and uninstall, MAKE SURE YOU SELECT THE DELETE DRIVE CHECKBOX. Then do a Scan for hardware changes and it will show up in the correct place.

Can I use a non-Microsoft TPM driver?

Microsoft does not support non-Microsoft TPM drivers and strongly recommends against using them with BitLocker. Attempting to use a non-Microsoft TPM driver with BitLocker may cause BitLocker to report that a TPM is not present on the computer and not allow the TPM to be used with BitLocker.

DELL-Warren B · Answer

What driver CAB are you referring to?

Reza Prawirasat · Answer

Warren,

I'm using the latest Dell Driver CAB version 5.0 from: en.community.dell.com/.../2171.windows-7-notebook-combo-driver-cab.aspx

Apparently, Broadcom_TPM is messing Latitude model E6420 and below. It's working fine with E6430. What I did, remove completely security folder from that and let Windows installed Broadcom_TPM; it worked fine with E6420 and below and also works for E6430.

I'm really hoping Dell will fix this soon!

Enterprise Client

Was this post helpful?