Problems - Updating boot images on distribution points
Hei!
I have added some extra drivers and enabled command support to my x86 boot image, but I am not able to update my distribution points with the changes. When I try the same operation on my x64 boot image evrything works fine.
The error message is shown below. Does anybody know how to fix this?
regards
Geir Almaas
Error: Boot image to update:
Microsoft Windows Vista PE (X86)
Error: Actions to perform:
Add ConfigMgr binaries
Enable Windows PE command line support
Add drivers
Success: Drivers that will be included:
3Com 10/100/1000 PCI
Intel(R) 82801FBM SATA AHCI Controller
Intel(R) 631xESB/632xESB SATA RAID Controller
Intel(R) PRO/1000 PT Dual Port Network Connection
Error: Failed to import the following drivers:
3Com 10/100/1000 PCI - Failed to inject a ConfigMgr driver into the mounted WIM file
Error: The wizard detected the following problems when updating the boot image.
The ConfigMgr 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:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
Line = 3822;
ObjectInfo = "CSspBootImagePackage:reRefreshPkgSrcHook";
Operation = "ExecMethod";
ParameterInfo = "SMS_BootImagePackage.PackageID=\"PHK00001\"";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
};
January 16th, 2008 5:44pm
Hi Geir,
When the boot image is updated on the distribution point Windows Package Manager is used to inject drivers into the boot image. It looks like it is having an issue installing your 3COM driver (this could be because it is missing some files, it incompatible with Vista x86, etc.). Please try removing the 3Com driver from the boot image package (this is an option on the boot images Windows PE tab) and update the boot image package again.
-- Brett
Free Windows Admin Tool Kit Click here and download it now
January 17th, 2008 8:54pm
Thanks Brett, that solved the problem.
Geir
January 18th, 2008 11:00am
Check the C:\Windows\Logs\DISM\dism.log file and view with SMS Trace. In my case the log showed a failure with a VMWare NIC driver. I had to delete it and reimport the driver again.
Free Windows Admin Tool Kit Click here and download it now
January 19th, 2011 12:11am


