Unsolved
This post is more than 5 years old
7 Posts
0
272476
September 28th, 2011 12:00
Incorrect TPM driver deployed through MDT2010 using Dell CAB files
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
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
No Events found!
Timothy77
3 Posts
0
July 29th, 2013 15:00
I had the exact same issue with a E6420 when I was deploying Windows 8 Pro through MDT 2012. So the problem still isn't fixed. I removed the driver and now everything works fine.
Dell Support couldn't even figure out what was going on. Thanks for posting this.
Reza Prawirasat
3 Posts
0
July 29th, 2013 15:00
Yep, Dell Support doesn't know what I'm talking about to begin with! Go figure.
Timothy77
3 Posts
0
July 29th, 2013 15:00
At first they told me that the 6420 does not support the TPM on Windows 8, which seemed like a truly bizarre comment to me. Usually Dell Pro Support is awesome. This was not such a case.
pyhoff
5 Posts
0
September 9th, 2013 08:00
Had same issue with XPS laptops posted in the CAB forum for XPS. My workaround was
Issue with TPM: When you have more than set of drivers injected to you image. TPM on XPS does not load correctly. After banging my head and looking all over the world for a driver thinking the TPM driver was missing, stopped to look at System devices, low and behold the TPM (Amtel TPM) was loaded as a System Device not a Security Device. So decide to force the drive to be native Windows TPM driver and this worked, TPM initialized and this one laptop now works. Now 65 to go. Hum......
How to script it? dpinst does not work, PNPUTIL could not figure out the command. So one last utility good ole DEVCON.EXE (64 bit version) part of the windows driver, and debug kit.
1) copy contents of "C:\Windows\System32\DriverStore\FileRepository\tpm.inf_amd64_neutral_d5bb6575cf91cd73." to temp folder.
2) Copied DEVCON.EXE (64 bit version) from Driver utility pack
3) Created a batch that contained the following command "devcon update tpm.inf *ATM1200" Fixed the issue in script. Other models please lookup the Hardware ID in device manager.
4) Call this batch in the SetupComplete.cmd that runs after sysprep
Voila, hope this works for some one.