SOLVED Unable to add WinPe.wim as a bootimage to SCCM

[Passiez]

Hi,

I'm having an issue with adding a bootimage WIM file to SCCM and I really hope someone could help me find out what to do.
After I selected the winpe.wim file which copied from the "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us" to a shared folder "\\mcm01\MCM$\BOOTWIMS\amd64" (because it won't work if I'm not using a shared path).
I went next, give it a name, next and install.

The the following happend:
Status: The SMS Provider reported an error.

ConfigMgr Error Object:
instance of SMS_ExtendedStatus
{
Description = "Error retrieving object PackageID=";
ErrorCode = 2151811598;
File = "D:\\dbs\\sh\\cmgm\\1213_044837_0\\cmd\\1b\\src\\SiteServer\\SDK_Provider\\SMSProv\\SspInterface.h";
Line = 1199;
Operation = "GetObject";
ParameterInfo = "SMS_BootImagePackage.PackageID=\"\"";
ProviderName = "ExtnProv";
StatusCode = 2147749890;
};

-------------------------------
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException
The SMS Provider reported an error.


Stack Trace:
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObjectBase.get_ObjectClass()
at Microsoft.ConfigurationManagement.AdminConsole.OsdCommon.OsdImageWizardForm.PostApply(BackgroundWorker worker, DoWorkEventArgs e)
at Microsoft.ConfigurationManagement.AdminConsole.ProgressPage.backgroundWorkerPostApply_DoWork(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

-------------------------------

System.Management.ManagementException
Not found


Stack Trace:
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObjectBase.get_ObjectClass()
at Microsoft.ConfigurationManagement.AdminConsole.OsdCommon.OsdImageWizardForm.PostApply(BackgroundWorker worker, DoWorkEventArgs e)
at Microsoft.ConfigurationManagement.AdminConsole.ProgressPage.backgroundWorkerPostApply_DoWork(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

-------------------------------

There is no single sollutions I could find on any forum. Hopefully anyone could help me. ;(

Thanks in advanced.

Regards,

Pascal

 

[kentmj]

Hi,

I'm having an issue with adding a bootimage WIM file to SCCM and I really hope someone could help me find out what to do.
After I selected the winpe.wim file which copied from the "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us" to a shared folder "\\mcm01\MCM$\BOOTWIMS\amd64" (because it won't work if I'm not using a shared path).
I went next, give it a name, next and install.

The the following happend:
Status: The SMS Provider reported an error.

ConfigMgr Error Object:
instance of SMS_ExtendedStatus
{
Description = "Error retrieving object PackageID=";
ErrorCode = 2151811598;
File = "D:\\dbs\\sh\\cmgm\\1213_044837_0\\cmd\\1b\\src\\SiteServer\\SDK_Provider\\SMSProv\\SspInterface.h";
Line = 1199;
Operation = "GetObject";
ParameterInfo = "SMS_BootImagePackage.PackageID=\"\"";
ProviderName = "ExtnProv";
StatusCode = 2147749890;
};

-------------------------------
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException
The SMS Provider reported an error.


Stack Trace:
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObjectBase.get_ObjectClass()
at Microsoft.ConfigurationManagement.AdminConsole.OsdCommon.OsdImageWizardForm.PostApply(BackgroundWorker worker, DoWorkEventArgs e)
at Microsoft.ConfigurationManagement.AdminConsole.ProgressPage.backgroundWorkerPostApply_DoWork(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

-------------------------------

System.Management.ManagementException
Not found


Stack Trace:
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObjectBase.get_ObjectClass()
at Microsoft.ConfigurationManagement.AdminConsole.OsdCommon.OsdImageWizardForm.PostApply(BackgroundWorker worker, DoWorkEventArgs e)
at Microsoft.ConfigurationManagement.AdminConsole.ProgressPage.backgroundWorkerPostApply_DoWork(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

-------------------------------

There is no single sollutions I could find on any forum. Hopefully anyone could help me. ;(

Thanks in advanced.

Regards,

Pascal

I'm having the exact same issue. I ran this suggestion but it does not seem to help: https://learn.microsoft.com/en-us/t...gmgr/os-deployment/error-managing-boot-images

 

[Passiez]

I'm having the exact same issue. I ran this suggestion but it does not seem to help: https://learn.microsoft.com/en-us/t...gmgr/os-deployment/error-managing-boot-images

You are right, this suggestion is was not the sollution for me either.
Today I'm having a call with MS. Maybe I will find something helpful...

 

[kentmj]

You are right, this suggestion is was not the sollution for me either.
Today I'm having a call with MS. Maybe I will find something helpful...

I've noticed that if i attempt to mount images outside of the OS (as mentioned in the article), it fails. This leads me to believe it's not necessarily an SCCM issue. But perhaps the latest ADK (or a more recent one) breaks DISM on some servers.

 

[kentmj]

So it looks like i got things working. I created a Server 2022 VM and compared that reg key. I adjusted it to what it should be. I rebooted my server and then confirmed that i could use DISM within the OS to mount an image, which i was able to do. I then removed the ADK and WinPE add on, then rebooted. When the OS came up, i once again tested to see if i could mount an image, and that was successful. I then installed the ADK and WinPE add-on, then rebooted once more. Again, back in the OS, I first verified the registry key. It was still set to what it was before the ADK. I then tested mounting a WIM using DIM as i had done before. This worked correctly. I then went into SCCM and added a boot image. I had no issues. I'm not sure if i had to do this all in order but it helped to verify things as I went along. I was able to boot and image a VM. I will test with physical hardware tomorrow.

 

[Passiez]

So it looks like i got things working. I created a Server 2022 VM and compared that reg key. I adjusted it to what it should be. I rebooted my server and then confirmed that i could use DISM within the OS to mount an image, which i was able to do. I then removed the ADK and WinPE add on, then rebooted. When the OS came up, i once again tested to see if i could mount an image, and that was successful. I then installed the ADK and WinPE add-on, then rebooted once more. Again, back in the OS, I first verified the registry key. It was still set to what it was before the ADK. I then tested mounting a WIM using DIM as i had done before. This worked correctly. I then went into SCCM and added a boot image. I had no issues. I'm not sure if i had to do this all in order but it helped to verify things as I went along. I was able to boot and image a VM. I will test with physical hardware tomorrow.

You are my hero.
I did the exact same steps like you described. It workt!!
I added the WinPe to SCCM.

Thanks alot!