locked
Updating x64 boot image after CM2012 SP1 failure... RRS feed

  • Question


  • I have upgraded our SCCM 2012 site to SP1. Almos everything went Ok, except this boot image issue.

    After searching for ansver to update original default x64 boot image, I found one sollution, wich worked for x86 boot image. The sollution ( http://blogs.technet.com/b/systemcenterpfe/archive/2013/01/11/updated-system-center-2012-configuration-manager-antivirus-exclusions-with-more-details.aspx?CommentPosted=true#commentmessage ) was to run following powershell command:

    Get-CimInstance -Namespace root/SMS/site_xyz -ClassName SMS_BootImagePackage -Filter PackageId='xyz00004'" | Invoke-CimMethod -MethodName UpdateDefaultImage

     Which lead to an error: 

    Invoke-CimMethod : Generic failure

    At line:1 char:111 + ... ='xyz00004'" | Invoke-CimMethod -MethodName UpdateDefaultImage

                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        + CategoryInfo          : NotSpecified: (SMS_BootImagePa...D = "xyz00004")

       :CimInstance) [Invoke-CimMethod], CimException + FullyQualifiedErrorId : HRESULT 0x80041001,Microsoft.Management.Infrastructure.CimCmdlets.InvokeCimMethodCommand

    I tried to copy again winpe.wim from ADK amd64 folder to desired sccm osd folder, but still won't work.

    As I mentioned, x86 worked fine. On SCCM console, version is 6.1.xxx but when I open image properties, version seems to be 6.2, even I click reload. Image security and folder permissions were identical beetween x86 and x64 images.

    Thanks for the help!

    Cheers, Tuomas.


    Thursday, March 14, 2013 3:16 PM

Answers

  • Hi,

    Unfortunatetly as I said ealier, I copied boot images from ADK folder, it did not work.

    However, after I removed all drivers from ConfigManager and  re-runned powershell command, it succeeded. Now I'm importing drivers back to CM...

    Thanks

    ~Tuomas.

    • Proposed as answer by Garth JonesMVP Thursday, February 5, 2015 11:44 PM
    • Marked as answer by Garth JonesMVP Tuesday, October 27, 2015 5:04 PM
    Wednesday, March 20, 2013 8:10 AM

All replies

  • Hi Tuomas,

    You're missing a double quote in your command. You need an opening double quote just before PackageId. Give this a try:

    Get-CimInstance -Namespace root/SMS/site_xyz -ClassName SMS_BootImagePackage -Filter "PackageId='xyz00004'" | Invoke-CimMethod -MethodName UpdateDefaultImage

    Thursday, March 14, 2013 4:12 PM
  • Hi, thanks for hint but issue remains. For some reason I missed double quotation mark you mentioned. 

    WAIK was removed and server rebooted. ADK was installed after that and rebooted before installing SP1.

    Tuomas.

    Thursday, March 14, 2013 4:54 PM
  • I ran into the same issue when I did the SP1 upgrade. I ended up having to delete all traces of existing 6.1 boot images from SCCM and do a fresh import of the 6.2 boot images from the ADK.
    Thursday, March 14, 2013 5:16 PM
  • I found some clues while running ps command (smsprov.log) CM site server was not able to read device drivers. After I fixed some driver source paths, I'm now stuck where it attemps to inject a driver which is deleted from CM console. Should I remove the corresponding file also?

    ----8<-----
    Driver injection command line: "D:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /image:"C:\Windows\TEMP\BootImages\{BC25BB74-D300-4091-AC16-77F0F312ACB1}\mount" /Add-Driver /Driver:"\\corpvf\Install\SCCM_drivers\E5510-Win7-A04-4TPNW\E5510\Win7\x64\chipset\R302424\WIN7\NehalMEX.inf"    SMS Provider    3/15/2013 1:57:49 PM    4444 (0x115C)
    ERROR> Error 50 returned to execute the command line: "D:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /image:"C:\Windows\TEMP\BootImages\{BC25BB74-D300-4091-AC16-77F0F312ACB1}\mount" /Add-Driver /Driver:"\\corpvf\Install\SCCM_drivers\E5510-Win7-A04-4TPNW\E5510\Win7\x64\chipset\R302424\WIN7\NehalMEX.inf"    SMS Provider    3/15/2013 1:57:52 PM    4444 (0x115C)
    ERROR> Failed to inject driver from the driver path \\corpvf\Install\SCCM_drivers\E5510-Win7-A04-4TPNW\E5510\Win7\x64\chipset\R302424\WIN7\NehalMEX.inf    SMS Provider    3/15/2013 1:57:52 PM    4444 (0x115C)
    ERROR> Failed to inject SMS drivers.    SMS Provider    3/15/2013 1:57:52 PM    4444 (0x115C)
    *~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp(4418) : Failed to upgrade wim file with OSD binaries.~*~*    SMS Provider    3/15/2013 1:58:20 PM    4444 (0x115C)
    *~*~Failed to upgrade wim file with OSD binaries. ~*~*    SMS Provider    3/15/2013 1:58:20 PM    4444 (0x115C)


    ----8<----


    I also attempted to import WinPE.img from ADK amd64\sources folder, but CM wizard stopped immediately complaining about" The specified file can not be imported. Make sure you have read and write access to the specified file and its folder".  and smsprov.log shows following error:

    Failed to copy \ to \\CM1s\shared\{5DE1E4BA-5015-4618-9D2F-E7F5185E96B3}.wim. Error code = 5    SMS Provider    3/15/2013 1:48:00 PM    2312 (0x0908)
    *~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp(3642) : Failed to make a copy of the source WIM file due to error 5~*~*    SMS Provider    3/15/2013 1:48:00 PM    2312 (0x0908)
    *~*~Failed to make a copy of the source WIM file due to error 5 ~*~*    SMS Provider    3/15/2013 1:48:00 PM    2312 (0x0908)


    Site server computer account is member of local administrators group and I granted full permissions to shares and NTFS folders (drivers, source wim,...)  I also rebooted server, but none helps.

    Tuomas.

    Friday, March 15, 2013 12:17 PM
  • Hi

    There is a known issue in boot images in SCCM 2012 SP1 i.e. you would be unable to update/distribute boot images after installing SP1.

    Please check below link for more info

    http://blog.coretech.dk/rja/post-sccm-2012-sp1-failure-to-update-boot-images/

    After following this link, I'm able to update/distribute boot image successfully. Hope the same thing applies to you as well.


    Cheers | Navdeep Sidhu

    Friday, March 15, 2013 12:24 PM
  • Hi,

    Unfortunatetly as I said ealier, I copied boot images from ADK folder, it did not work.

    However, after I removed all drivers from ConfigManager and  re-runned powershell command, it succeeded. Now I'm importing drivers back to CM...

    Thanks

    ~Tuomas.

    • Proposed as answer by Garth JonesMVP Thursday, February 5, 2015 11:44 PM
    • Marked as answer by Garth JonesMVP Tuesday, October 27, 2015 5:04 PM
    Wednesday, March 20, 2013 8:10 AM