OSD Boot image 'Failed adding image'
Hi all,
I've recently upgraded to SCCM SP2 and am trying to implement PXE. I have been able to install WDS on the SCCM site server which is running Windows 2K8 SP2, as well as the PXE service point. the pxecontrol log file shows successful PXE test:
Successfully performed availability check against local computer.
SMS_PXE_SERVICE_POINT 18/05/2010 20:58:33
4988 (0x137C)
adding address to server list xxx.xxx.xxx.xxx
SMS_PXE_SERVICE_POINT 18/05/2010 21:03:33
4988 (0x137C)
adding address to server list 127.00.00.01
SMS_PXE_SERVICE_POINT
18/05/2010 21:03:33 4988 (0x137C)
Sending availiability packet to: xxx.xxx.xxx.xxx SMS_PXE_SERVICE_POINT
18/05/2010 21:03:33 4988 (0x137C)
Sent 274 bytes to xxx.xxx.xxx.xxx:4011
SMS_PXE_SERVICE_POINT
18/05/2010 21:03:33 4988 (0x137C)
PXE test request succeeded.
SMS_PXE_SERVICE_POINT
18/05/2010 21:03:33 4988 (0x137C)
However when I perform a pxe boot I get the pxe error 'no boot file name received'.
I have looked at the smspxe.log and found that there appears to be issues processing the boot image when it is distributed to the pxeDP
Opening image file E:\RemoteInstall\SMSImages\SMSPKG\100000E7\boot.100000E7.wim
smspxe 18/05/2010 21:01:08
6072 (0x17B8)
Failed to read PXE settings.
The system cannot find the file specified. (Error: 80070002; Source: Windows)
smspxe 18/05/2010 21:01:08
6072 (0x17B8)
Found Image file: E:\RemoteInstall\SMSImages\SMSPKG\100000E7\boot.100000E7.wim
PackageID: SMSPKG\100000E7
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
smspxe
18/05/2010 21:01:08 6072 (0x17B8)
Closing image file E:\RemoteInstall\SMSImages\SMSPKG\100000E7\boot.100000E7.wim
smspxe 18/05/2010 21:01:08
6072 (0x17B8)
Mutex was not owned. Now have ownership.
smspxe 18/05/2010 21:01:08
6072 (0x17B8)
Failed adding image E:\RemoteInstall\SMSImages\SMSPKG\100000E7\boot.100000E7.wim. Will Retry..
Not found (Error: 80041002; Source: WMI)
smspxe
18/05/2010 21:01:08
6072 (0x17B8)
I have already tried stopping WDS and recreating c:\windows\temp as well as deleting the image from the pxeDP and resending it as well as uninstalling and reinstalling both the PXE Service Point and WDS but get the same result.
Any help greatly received.
May 18th, 2010 11:19pm
in your confirmgrsetup.log do you see that your boot images were successfully installed ? have you tried to reinstall SP2 for SCCM 2007 ? (or WAIK for that matter)
My step by step
SCCM Guides
windows-noob on Twitter
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2010 11:31pm
configmgrsetup.log looks like this
"E:\sccm_sp2\ConfigMgr07SP2Upgrade_RTM_ENU\SMSSETUP\BIN\I386\setup.exe"
<05-13-2010 18:08:38> This is 32 bit.
<05-13-2010 18:08:39> Verifying the Reg for AssetIntelligence Installation
<05-13-2010 18:08:39> Found installation of AssetIntelligence Full version
<05-13-2010 18:08:39> Setup detected an existing SCCM installation. Currently installed version is 6487
<05-13-2010 18:08:39> Phase is 1C7
<05-13-2010 18:08:39> Setting the default CSV folder path
<05-13-2010 18:08:40> SMS Build Number = 6487
<05-13-2010 18:08:40> SMS Version = 4.0
<05-13-2010 18:08:40> SMS Minimum Build Number = 800
<05-13-2010 18:08:40> Verifying SMS Active Directory Schema Extensions.
<05-13-2010 18:08:41> DS Root:CN=Schema,CN=Configuration,DC=xxxx,DC=xxxx
<05-13-2010 18:08:41> Verifying SMS Active Directory Schema Extensions.
<05-13-2010 18:08:41> DS Root:CN=Schema,CN=Configuration,DC=xxxx,DC=xxxx
<05-13-2010 18:08:41> Registered type SQLSERVER MASTER for SQLSERVER INSTANCE6\master
<05-13-2010 18:08:41> Registered type SMS Master for SQLSERVER INSTANCE6\master
<05-13-2010 18:08:41> Registered type SQLSERVER INSTANCE6\SMS_201 for SQLSERVER INSTANCE6\SMS_201
<05-13-2010 18:08:41> Registered type SMS ACCESS for SQLSERVER INSTANCE6\SMS_201
<05-13-2010 18:08:48> Setup has detected an existing primary site on this computer.
<05-13-2010 18:08:48> Setup has detected an existing primary site on this computer.
I've looked at ComponentSetup.log and our SP2 upgrade shows the following
Back up customizable files: Completed
Create and initialize site database: Completed
Transfer files: Completed
Install SMS provider components: Completed
Register controls: Completed
Upgrade inboxes: Completed
Upgrade site control file: Completed
Initialize Configuration Manager site: Completed
Install site component manager: Completed
Update default boot image packages: Failed
Create program group: Completed
Install Configuration Manager services (site component manager): Completed
Install component monitor: Completed
Install SMS executive: Completed
Install database notification monitor: Completed
Install site control manager: Completed
Install hierarchy manager: Completed
Install inbox manager: Completed
Install policy provider: Completed
Install MP control manager: Unknown
Install management point: Unknown
This is the Child Primary in a heirarchy so I sent the boot images from the already upgraded primary site above it.
This is a fully functioning (except OSD) production site so I could do with being able to correct this without having to rebuild or reinstall the site.
May 19th, 2010 11:43am
have you definetly distributed your boot images to dp's ? (both x86 and x64)
My step by step
SCCM Guides
windows-noob on Twitter
Free Windows Admin Tool Kit Click here and download it now
May 19th, 2010 12:03pm
the boot images from the central primary show up has distributed in the console and I can find the wim files if I browse to
\\servername\smspxeimages$ it looks like something needs to happen when the boot images arrive, from the investigation i've done it looks like something uses c:\windows\temp\pxebootfiles and then folders in REMINST\SMSBoot
should get populated but none of this seems to happen. The pxebootfiles folder was missing from c:\windows\temp so I've created this but still get the same errors in smspxe.log
Opening image file E:\RemoteInstall\SMSImages\SMSPKG\10000001\boot.10000001.wim smspxe 19/05/2010 11:05:07 9980 (0x26FC)
Failed to read PXE settings.
The system cannot find the file specified. (Error: 80070002; Source: Windows) smspxe 19/05/2010 11:05:07 9980 (0x26FC)
Found Image file: E:\RemoteInstall\SMSImages\SMSPKG\10000001\boot.10000001.wim
PackageID: SMSPKG\10000001
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
smspxe 19/05/2010 11:05:07 9980 (0x26FC)
Closing image file E:\RemoteInstall\SMSImages\SMSPKG\10000001\boot.10000001.wim smspxe 19/05/2010 11:05:07 9980 (0x26FC)
Mutex was not owned. Now have ownership. smspxe 19/05/2010 11:05:07 9980 (0x26FC)
Failed adding image E:\RemoteInstall\SMSImages\SMSPKG\10000001\boot.10000001.wim. Will Retry..
Not found (Error: 80041002; Source: WMI) smspxe 19/05/2010 11:05:07 9980 (0x26FC)
May 19th, 2010 1:09pm
I know this has been open for a long time but I finally have a answer to share. Having spent ages with Premier support they have discovered some missing WMI tables on the site server for BCD and also reregistered the BCD dlls. One reboot later and we are
up and running, bring on Windows 7 deployments!
Free Windows Admin Tool Kit Click here and download it now
September 2nd, 2010 12:07pm
Same here. Please provide a detailed step by step Tech_SR .
I'm having this exact same issue.
March 13th, 2011 11:35am
Tech_SR....can you identify the exact steps that it took to fix this? We are having the exact same issue on a secondary SCCM site and we are unable to fix with anything else. We have tried the whole remove pxe and reinstall, refresh dp's....not
working.
I think we may have to apply the same fix as you have.
Free Windows Admin Tool Kit Click here and download it now
March 13th, 2011 12:11pm
We had the same problem on a secondary SCCM server and I was able to fix by doing the following:
On secondary server open cmd prompt at C:\Windows\System32 regsvr32 bcdprov.dll regsvr32 bcdsrv.dll cd wbem net stop /y winmgmt mofcomp bcd.mof net start winmgmt
I then stopped and started the following sms services
SMS Agent Host
SMS_EXECUTIVE
SMS_SITE_COMPONENT_MANAGER
and or probably would be good to reboot the server as well if possible.
Cheers
April 6th, 2011 9:07pm