– SOLVED (See Below)
Using the Auto-Apply Drivers, no issues occur, but the Install Windows step is failing regularly when using the “Apply Driver Package” step. I need this feature working as I have multiple customers using the SCCM Media Deployments.
setupact.log output:
2013-01-09 12:07:12, Info IBS AddDriverPackageIntoDriverStore:Driver package path is [E:\_SMSTaskSequence\drivers\2\iaAHCIC.inf]
2013-01-09 12:07:12, Info IBS AddDriverPackageIntoDriverStore:Image architecture is [0x9]
2013-01-09 12:07:12, Info IBS AddDriverPackageIntoDriverStore:System root is [E:\Windows]
2013-01-09 12:07:12, Info IBS AddDriverPackageIntoDriverStore:System drive is [C:\]
2013-01-09 12:07:33, Warning [0x0602b1] IBS AddDriverPackageIntoDriverStore:Failed to add the driver package [E:\_SMSTaskSequence\drivers\2\iaAHCIC.inf] into driver store. Error code is [0x80070032]
2013-01-09 12:07:33, Error [0x0602a9] IBS CallBack_AddDriverPackageIntoDriverStore:Failed to install the driver package [E:\_SMSTaskSequence\drivers\2\iaAHCIC.inf]. Driver package is [Critical]. Error code is [0x32][gle=0x00000032]
2013-01-09 12:07:33, Error [0x0602ab] IBS CallBack_AddDriverPackageIntoDriverStore:An error occurred while installing the driver package [] offline GLE is [0x32][gle=0x00000032]
2013-01-09 12:07:33, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows installation cannot continue because a required driver could not be installed.]
2013-01-09 12:07:34, Info [SETUP.EXE] Called script [X:\windows\Setup\Scripts\ErrorHandler.cmd] to handle fatal error
2013-01-09 12:07:34, Info IBS Callback_Rollback_ExecuteOnlineRollback: Executing [E:\_SMSTaskSequence\Packages\PS100008\SOURCES\rollback.exe /CleanInstallFromWinPE /noui /BTFolder:E:\$WINDOWS.~BT\Sources]…
I’m also seeing alot of these errors in the SMS..log:
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type
Any help is much appreciated.
.ZIP of Log Files: https://panaconsulting.box.com/s/yxhqadtx80zjrbcar4gt
Storage Drivers being injected: https://panaconsulting.box.com/s/mqjhgsblwvop3kh1nyl1
Issue was related to the Intel MSD driver package. This driver package was intended to be installed AFTER the OS is installed. SCCM was determining the driver as critical to the Install of the OS as its an MSD driver and exiting the TS.
Having the same issue did you find a resolution
It was related to the driver I was injecting and not sccm. Verify that your driver is meant to install during PNP and not inside the windows OS.
With SCCM 2012 R2, how are you making it install during PNP and not Inside the Windows OS?
I believe I had SCCM run the setup.exe on first bootup and didn’t use the INF installer.
/BG