Post Sysprep: TPM device on Laptop not Satisified
I have scratched my head long enough so here it goes:
Found New Hardware post sysprep for TPM.
Using updated baseline image and updated sysprep to accomodate laptop x60s (1702-3ju). OemPnPDriversPath within sysprep has the appropriate entry: c:\drivers\tpm
Confirmed firm is copying all appropriate drivers to c:\drivers, including the tpm folder...all contents are present.
This is the only device not being satisified by Windows.
Actually, I don't even care to have it recognized because we don't use the Lenovo security application and we don't plan on loading windows vista and using bitlocker.
If there was a way to keep it from being recognized, I'm all for that too. I have even gone into the BIOS to determine default setting in BIOS was listed as inactive, changed to active and still the same outcome.
With that said, I don't know what else I'm missing and I'm about to drop kick something....
NEED YOUR HELP!
Thanks.
Comments
Driver Folder
You might want to verify that all the files that are needed are in the top most level of the folder being referenced in Sysprep. For example, if you reference c:\drivers\tpm, make sure there isn't another folder called c:\drivers\tpm\win32 or something else. If there is, try copying the files from those directories to the "tpm" level and see if that works for you.
Brian Hawver
Systems Engineer
Yaskawa America, Inc.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.
Verified Driver Folder
Only a single entry: c:\drivers\tpm
Driver Folder
And in that driver folder, is there INF and driver files, or is it just an exe type file?
Brian Hawver
Systems Engineer
Yaskawa America, Inc.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.
all files: *.cat, *.dll,
all files: *.cat, *.dll, *.inf, *.sys
these files have been extraced from Lenovo's self extracting .exe
I even went as far to place change the order of when sysprep should look for the driver to the very front of the OemPnPDriversPath - same behavior...Found New Hardware.
I tried placing the *.inf file in c:\windows\inf as part of the baseline image, no go either.
If I do it manually to satisfy DM, its happy.
So when the device isn't
So when the device isn't recognized, then the new hardware wizard comes up, if you point to c:\drivers\tpm does it work?
If that works, then it is your oempnpdrivers path. That path is statically set in the registry of your original *pre* sysprep image. You can't bring down an image that was already sysprep'd and then change it and re-sysprep. You also can't inject a new tokenized sysprep over the one that was in the original image and expect it to work. Most of the entries in a tokenized sysprep can be changed and injected over top. The oempnpdriverspath is not one of these things.
Fix: Bring down your non-sysprep'd checkpoint image and fix path. Re-seal and capture new image.
Workaround: Paste your .cat and inf's for the tpm into one of the other c:\drivers folders that is working. If you have to overwrite readme.txt and what not it doesn't matter.
Would you like to reply?
Login or Register to post your comment.