P3nnyw1se Posted March 31, 2014 Report post Posted March 31, 2014 As weird as it may sound this is what happens to me.I use Config Mgr 2012, SP1.I'm currently OSD'ing 6-7 different type of machines, one of those is the Lenovo T520.I went to Lenovos site and picked up their drivers for this model for Windows 7 x64.It aborted though during the task sequence, after downloading and applying windows, halfway through installing the driver packthat I assigned for the model.It said the file : ifm63x64.sys was missing or corrupt.a bit of googling told me that several other people have had issues with this driver.."Intel Ethernet FCoE Virtual Storport Miniport Driver Version 1.14.12.0"The sites I checked seemed to have 100% succes rate by simply removing this specific driver from the package.They also stated its not an essential driver.So I completely deleted the driver from config mgr, and of course updated my driver package to the distribution point.Then got the same error during task sequenceThought that was pretty weird, to get an error on a driver that was now supposedly non existent..So I googled some more and saw that some had issues with the driver pack did not actually update even though it said it did.they fixed this by completely removing it and making a new one.So I did the following:1: Deleted the driver Pack2: Went to the directory and made sure the driver pack had no files left on the server.3: I created a brand new Driver Pack, I added all the drivers, without the previously deleted 'FCoE Virtual Storport miniport Driver'4: I make sure the task sequence uses the correct new Driver PackAnd I still get the error. This is where I'm lost.. I attached a photo of the remaining drivers in the pack.I was hoping someone could take a look at these drivers and go 'ifm63x64.sys' could also be hiding in this onewhich doesn't make much sense.. I deleted the driver.. so whats going on? Quote Share this post Link to post Share on other sites More sharing options...
lweems Posted April 16, 2014 Report post Posted April 16, 2014 Did you ever come up with a solution to this? I'm having a very similar issue but I'm using MDT 2012. I have a Lenovo 20A8 and it goes all through the task sequence and reboots then I get the error ifm63x64.sys is missiing or corrupt. It's not in my driver package on MDT but it is in the drivers folder that I downloaded from Intel. Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted April 16, 2014 Report post Posted April 16, 2014 can you post your smsts.log file so we can see the failure ? Quote Share this post Link to post Share on other sites More sharing options...
P3nnyw1se Posted April 17, 2014 Report post Posted April 17, 2014 Did you ever come up with a solution to this? I'm having a very similar issue but I'm using MDT 2012. I have a Lenovo 20A8 and it goes all through the task sequence and reboots then I get the error ifm63x64.sys is missiing or corrupt. It's not in my driver package on MDT but it is in the drivers folder that I downloaded from Intel. Yes I DID in fact come up with a solution to this. I cleared out all drivers and deleted the package of course. related to this product. then instead of the network driver package that intially caused these troubles (both with and without the FCOE driver) I just dropped that one, and went online to find an older driver version I did that actually buy looking at an already installed similiar computer model. that was manually installed last summer... and read what version its netcard drivers had. once I applied the old package.. it somehow just got through... Conclusion: in my case it wasn't just enough to remove certain drivers from the faulty ETHERNET package.. I needed to completely replace it. Not the first time 2014, lenovo drivers cause me problems... Quote Share this post Link to post Share on other sites More sharing options...