n00blar

That works for RC1, but not for RC2. MS has confirmed that there is a bug with RC2 and WDS service that never gets uninstalled even after removing DP role from RC2.

I had this same error message, but mine was due to WinPE not having the correct NIC drivers for my DELL testing machine. The way I found this out is when I pressed F8 and then I typed ipconfig in the command prompt. FYI, PXE seems to be buggy in RC2 as well. I've already left a couple of 'bug/feedback' messages here.

That wasn't the question of the OP. For serial number, I believe there are scripts for that as well, each computer vendor may have one or someone may have written one. I think if you do a search in this forum you may find a link.

If you've not found it yet, you can find info here.

Yup, I'm going to have to revert back to a previous snapshot just before I started working with DP and PXE.

So, I think I found it, but how do I fix it? I ran an Update Distribution Point on Boot Image (x64), and this came up: Error: Boot image to update: • Microsoft Windows PE (x64) Error: Actions to perform: • Add ConfigMgr binaries • Enable Windows PE command line support • Add drivers 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:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp"; • Line = 4318; • ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook"; • Operation = "ExecMethod"; • ParameterInfo = "SMS_BootImagePackage.PackageID=\"LAB00002\""; • ProviderName = "WinMgmt"; • StatusCode = 2147749889; }; Error: Boot image to update: • Microsoft Windows PE (x64) Error: Actions to perform: • Add ConfigMgr binaries • Enable Windows PE command line support • Add drivers 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:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp"; • Line = 4318; • ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook"; • Operation = "ExecMethod"; • ParameterInfo = "SMS_BootImagePackage.PackageID=\"LAB00002\""; • ProviderName = "WinMgmt"; • StatusCode = 2147749889; }; Error: Boot image to update: • Microsoft Windows PE (x64) Error: Actions to perform: • Add ConfigMgr binaries • Enable Windows PE command line support • Add drivers 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:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp"; • Line = 4318; • ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook"; • Operation = "ExecMethod"; • ParameterInfo = "SMS_BootImagePackage.PackageID=\"LAB00002\""; • ProviderName = "WinMgmt"; • StatusCode = 2147749889; }; Error: Boot image to update: • Microsoft Windows PE (x64) Error: Actions to perform: • Add ConfigMgr binaries • Enable Windows PE command line support • Add drivers 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:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp"; • Line = 4318; • ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook"; • Operation = "ExecMethod"; • ParameterInfo = "SMS_BootImagePackage.PackageID=\"LAB00002\""; • ProviderName = "WinMgmt"; • StatusCode = 2147749889; }; Error: Boot image to update: • Microsoft Windows PE (x64) Error: Actions to perform: • Add ConfigMgr binaries • Enable Windows PE command line support • Add drivers 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:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp"; • Line = 4318; • ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook"; • Operation = "ExecMethod"; • ParameterInfo = "SMS_BootImagePackage.PackageID=\"LAB00002\""; • ProviderName = "WinMgmt"; • StatusCode = 2147749889; };

So, finally I fixed PXE and I was able to get machines to go to the WinPE portion (where you get to select the image to install). I decided to inject some drivers to the Boot images (x86 and x64), so I added the drivers and created a driver package. Soon after I selected to inject those drivers to the boot images, an error came up towards the end of the wizard. I decided to remove all drivers and drive packages and I also went in the Drivers tab for the boot images and made sure nothing was showing there - which there wasn't any there. I tried to to image another computer, well...it goes to the WinPE portion (I get to see the desktop) and 5 seconds later..machine reboots! Any ideas on how to troubleshoot this? (I think I might have corrupted the boo.wim file; I could be wrong though) Thanks!

Hi anyweb, Thanks for the reply. Well, I can't even get to that point. I used my lab snapshot to prior enabling PXE on RC2...things seem to be working again. The issue came up as soon as I rebooted RC2. So far, I've not rebooted the server (and I won't as I want to test the other PXE related features), but I'll post if I find anything during my lab work. Thanks again.

I had the exact same issue as yours. I spent three hours troubleshooting, with no apparent solution. Since I installed CM2012 RC2 in a vmware lab environment, I just loaded my snapshot back to the point before I enabled PXE and I've not had that issue again. Now, in my case, I got PXE to work for several machines; however, once I rebooted CM2012 RC2, then PXE stopped working. I know there was a PXE bug in RC1, and there was a workaround for it, but I've not spend enough time trying to see if this is a bug in this release or something like that.

I don't have one on the sever; I looked everywhere in the LOGS folder and and the drive, and it doesn't exist. Here's the results of the new Task Sequence wizard: Success: The task sequence has been created successfully. Success: Create a new task sequence • Name: Build and capture Windows 7 x64 • Boot Image: Boot image (x64) 6.1.7600.16385 en-US Success: Install the Windows operating system • Package: Windows 7 x64 Enterprise SP1 en-US • Server licensing mode: Do not specify • Use random password: No Success: Configure the network • Join workgroup: workgroup Success: Install the Configuration Manager client • Package: Microsoft Configuration Manager Client Upgrade 5.0 ALL • Installation properties: SMSMP=SCCM2012RC2.GLLAB.COM Success: Include software updates • Install software updates: All software updates Success: Image Properties • Created by: smsadmin Success: Capture image settings • Save to: \\sccm2012rc2\Sources\OS\Captures\win7entsp1x64.wim (This file never gets created and the entire process takes like 5 seconds to complete; I recall from RC1 this taking much longer) • Account to access output folder: GLLAB\SMSadmin

Is anyone having issues building and capturing an OS with RC2? I was redoing lab 7 and RC2 will not create the .wim file for some reason. I recall doing lab 7 for RC1 and it worked fine. I recall from RC1, that the TS step in lab 7 took a couple of minutes to comlete, but in RC2 it takes just seconds and when I check the path specified for saving the .wim file...the folder's empty. Any suggestions?

Update Okay, I think I figured this one out. DELL's BIOS packages can be installed as a SCCM package and can be easily deployed that way.

Can anyone give me a few tips on how to achieve this? I have an .exe file that I downloaded from DELL; I can use the -NOPAUSE parameter to pass to this file, to force a shutdown and to disable notifications. I created a package and I deployed it to a collection (as required) that queries all my devices with a BIOS less than 'x'. The collection query process works fine as it shows the only DELL machine that has a BIOS version less than 'x'; however, the package is sent to the computer, but it doesn't actually run. Any ideas on how to get this to work? Thanks!

I have a slight different version from anyweb. This could help you. Anyweb's right though; it's a bug in RC1. If you restart the SCCM server, you'll have to disable PXE from SCCM to have the WDS server come up properly. I pulled my hairs for 2 wees before reporting it to MS and they found it to be a bug in RC1.

This is a known bug in RC1 and MS has closed the case, so I'm assuming it should be fixed in RC2 (if there is one). What I do, before restarting the server, is disable PXE from the Distribution Point role - yes, it's a pain, but it's the only way I've found to go around this problem. Once you disable PXE from the DP role then the service will start properly and you can then re-enable it.

Hello everyone, I'm testing Out of Band feature of SCCM 2012. I have installed the proper site roles (Enrollment Point and Out of band service point); I completed all the pre-requesites as well, so all that has been taken care of. I was able to discover a machine with AMT (DELL Optiplex); the problem is that prior to using the 'discover' option; I had already made changes to AMT through the BIOS. So, in SCCM the AMT status for this computer shows 'detected', and when I right click on the device object, the only options under Manage OOB are: Discover AMT Status and Remove AMT Provisioning Data - all other options are grayed out. I went ahead and clicked on Remove AMT Provisioning Data on this object, but this didn't do anything - at least from what I can tell. I also, manually, cleared all the AMT setting from the BIOS on this computer (I don't know if this action messed things up with SCCM). How do I "Enable Automatic AMT Provisioning" on this device?

www.mytechstuffSPAM! www(.) mytechstuff(.)info For some reason the link's marked as spam.

After opening and reading most of the logs, I found the correct file! smsts*.logs

I was working on this same project a few weeks back, so I heavily modified a VB script, you can find it here.

Still working on the SCCM 2012 test lab, and recently I added a driver package to the an OSD TS; I'd like to know if these drivers got properly installed and I don't know which logs to look into. Looks like during the OS deployment job the task sequence that is supposed to load the drivers (mainly DELL Optiplex drivers) runs properly, since I don't see any errors, but I just want to make sure since one set of drivers isn't getting installed. I'm assuming the client logs under windows\CCM\logs, but which file? Thanks!

Ohh, you're right! I forgot to do that...thanks!!

Yup, you're right. It takes a few minutes (10-20min) before SCCM starts to deploy the updates; I was not waiting long enough. Thanks!

I noticed something in my lab environment. 1. System Center 2012 Endpoint Protection shows as: real-time protection OFF and virus and spyware definitions Out of date How do I go about changing these settings? I can't find them on SCCM.

Hello everyone, I just realized that in my SCCM2012 RC1 lab, all the applications that I've created do not show up in the application catalog website (http://sccmServer/CMApplicationCatalog). These applications do show up in Software Center client though. Can someone point me on a direction to troubleshoot this?

Looks like you guys are hitting the PXE bug in RC1. Try these steps.