OK, so here is the solution. When we migrated from SCCM 2007 to 2012 we also migrated drivers but it kept the driver source location from an old 2007 server for some reason. We de-commissioned that server about a week ago so the boot.wim couldn’t re-add the drivers it needed. I had to create a new server with the same name and the same share as the old one that was decommissioned. Luckily I had a copy of the drivers backed up with the original folder structure. Once I got everything in place I was able to update the WIM with the drivers I needed. Ron Knight Desktop Engineer II Innovative Technology Solutions Texas Health Resources (682) 236-6374 [email protected] [Texas Health Resources]<http://mytexashealth/SiteMaker/websitefiles/MyTHRCon8545866/homepage.cfm> [itil]
From: [email protected] [mailto:[email protected]] On Behalf Of Chris Nackers Sent: Wednesday, November 20, 2013 3:53 PM To: [email protected] Subject: [MDT-OSD] RE: Issues with boot.wim Is it erroring out during the load of winpe? (before you see the wallpaper) if so it’s not a driver issue at that point… You can always catch it with F8 and then open up winpeinit.log to see what is going on… I would never recommend downloading and attempting to inject ANY vendor’s WinPE cab, just a bad idea. There is guaranteed to be drivers you don’t need in there. What are you using for Anti-Virus? It’s very common for AV to mess with OSD wim creating/editing processes. Chris Nackers Microsoft MVP – Enterprise Client Management Email: [email protected]<mailto:[email protected]> Nackers Consulting Services, LLC From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Knight, Ron Sent: Tuesday, November 19, 2013 3:15 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] Issues with boot.wim SCCM 2012 sp1 boot.wim updating issue: I’m having some issues integrating the new HP EliteDesk 800 g1 computers into our OSD. When I PXE boot the machine it loads the boot.wim fine until it gets 90% of the way loaded. I am pretty sure that it is the network driver causing the machine to reboot although it could be a mass-storage device. The first step I’ve taken was to go to HP and download the PE driver package for this machine and try to inject the drivers into my x86 boot wim. When I do, I get this error: [cid:[email protected]]Error: Actions to perform: · Add ConfigMgr binaries · Set scratch space · Enable Windows PE command line support Optional components: · Scripting (WinPE-Scripting) · Startup (WinPE-SecureStartup) · Network (WinPE-WDS-Tools) · Scripting (WinPE-WMI) [cid:[email protected]] Error: The wizard detected the following problems when updating the boot image. · Failed to inject a ConfigMgr driver into the mounted WIM file The SMS Provider reported an error.: ConfigMgr Error Object: instance of SMS_ExtendedStatus { · Description = "Failed to insert OSD binaries into the WIM file"; · ErrorCode = 2152205056; · File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp"; · Line = 4630; · ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook"; · Operation = "ExecMethod"; · ParameterInfo = "SMS_BootImagePackage.PackageID=\"THR000E6\""; · ProviderName = "WinMgmt"; · StatusCode = 2147749889; }; So I tried removing the new drivers and updating the DP’s just to see if that would fix it and I get the same error. I’ve even tried creating a new boot.wim file but it doesn’t work. Any ideas would be greatly appreciated! BTW Ron Knight Desktop Engineer II Innovative Technology Solutions Texas Health Resources (682) 236-6374 [email protected]<mailto:[email protected]> [Texas Health Resources]<http://mytexashealth/SiteMaker/websitefiles/MyTHRCon8545866/homepage.cfm> ________________________________ The information contained in this message and any attachments is intended only for the use of the individual or entity to which it is addressed, and may contain information that is PRIVILEGED, CONFIDENTIAL, and exempt from disclosure under applicable law. If you are not the intended recipient, you are prohibited from copying, distributing, or using the information. Please contact the sender immediately by return e-mail and delete the original message from your system. The information contained in this message and any attachments is intended only for the use of the individual or entity to which it is addressed, and may contain information that is PRIVILEGED, CONFIDENTIAL, and exempt from disclosure under applicable law. If you are not the intended recipient, you are prohibited from copying, distributing, or using the information. Please contact the sender immediately by return e-mail and delete the original message from your system.
<<inline: image001.jpg>>
<<inline: image003.jpg>>
<<inline: image004.png>>
