Jump to content


Search the Community

Showing results for tags 'boot.wim'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 4 results

  1. Hi There, We recently upgraded from SP1CU3 -> R2CU1 and are now having issues building machines using our OSD task sequence. First we tried using our existing x64 boot.wim (version 6.2.9200) - however our task sequence fails at the diskpart stage. We then noticed that the driver tab is missing from the Boot Images properties page - probably because the WIM was created by an older version of ADK. So then we tried using the boot image automatically placed into SCCM by the ADK8.1 install (6.3.9600.16384) in our task sequence. However this results in a WIndows8 BSOD screen with the error message "BAD_SYSTEM_CONFIG_INFO" after it finishes downloading the WIM file and shows the windows logo briefly (but before getting to the familiar WinPE page). Finally we tried using a freshly baked boot.wim created with the "copype.cmd amd64" command. Using this boot.wim in our task sequences allows the build process to progress a little further - we see it initialise WinPE and go through a couple of status messages before hard rebooting. The last status message it shows before it reboots the machine is "Preparing network connections...". NB: we were able to progress much further into our task sequence using the x86 ADT8.1 boot image... Any ideas on what we can try next?
  2. At first I attempted to add drivers to a specific boot WIM and then updated the DP but got an error. Researched the error couldn't find anything, so I decided to update one of the other boot WIMs which we have and same thing (this time I didn't even try to add drivers, for one of them I even deleted the drivers and then update the DP) Here is the error I get. Error: Boot image to update: MDT Custom PE Error: Actions to perform: Add ConfigMgr binaries Disable Windows PE command line support Add drivers Error: Failed to import the following drivers: Error: The wizard detected the following problems when updating the boot image. Failed to install required packages into to the boot image Failed to install required packages into to the boot image Failed to install required packages into to the boot image Failed to install required packages into to the boot image Failed to install required packages into to 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 = "c:\\qfe\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp"; Line = 4262; ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook"; Operation = "ExecMethod"; ParameterInfo = "SMS_BootImagePackage.PackageID=\"LUW00022\""; ProviderName = "WinMgmt"; StatusCode = 2147749889; };
  3. I Set up SCCM 2012 RTM, and have been fighting with deploy and capture for a few days. I successfully imported an Operating System Installer I successfully created a task sequence I I was able to get the machine to PXE boot, and it almost loaded windows PE; however, I kept getting the following error message: Windows PE cannot start because the actual SYSTEM ROOT directory (x:\windows) is differrent from the configured one (x:\$windows.~bt\windows). This can be configured from dism.exe with the /set-target path command. please refer the documentation for more details I was able to trace this problem back to using a boot.wim file other than the one included with SCCM / WDS. I had deleted the original boot.wim files, and used one from a windows 7 install cd. To resolve the problem, i used dsim.exe to modify the boot image: C:\sources\os >mkdir wim C:\sources\os>dism /mount-wim /wimfile:boot86.AAA0001c.WIM /index:1 /mountdir:wim C:\sources\os>dism /image:wim /set-targetpath:X:\ Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7600.16385 Target Path : X:\ The operation completed successfully. C:\sources\os>dism /unmount-wim /mountdir:wim /commit Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image File : C:\sources\os\boot64.AAA0001b.WIM Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. C:\sources\os>copy boot86.AAA0001C.WIM c:\RemoteInstall\SMSImages\AAA0001C\ Overwrite c:\RemoteInstall\SMSImages\AAA0001C\boot86.AAA0001C.WIM? (Yes/No/All): y 1 file(s) copied. After these commands, I was able to boot into launching the Task Sequence to Build and Capture my windows 7 image (Don't mind the x86/x64 difference from the screenshot and the commands above, I had to do the procedure twice...once for each boot image) However, after the Build and Capture, I was again presented with the same error I rebooted into the PXE WinPE (F12 network boot), and launched command prompt (F8 if you have enabled it within the SCCM image): I repeated the same procedure as I did on the PXE boot image for the local image, but first i had to find out where the local image was: X:\sms\bin\i386 >bcdedit Windows Boot Manager -------------------- identifier {bootmgr} description Windows Boot Manager locale en-US inherit {globalsettings} default {default} displayorder {default} timeout 30 Windows Setup ------------- identifier {default} device ramdisk=[C:]\_SMSTaskSequence\WinPE\sources\boot.wim,{ra mdiskoptions} path \windows\system32\boot\winload.exe description Windows Setup locale en-US inherit {bootloadersettings} osdevice ramdisk=[C:]\_SMSTaskSequence\WinPE\sources\boot.wim,{ra mdiskoptions} systemroot \windows nx OptOut detecthal Yes winpe Yes My local (hard-disk) image is in =[C:]\_SMSTaskSequence\WinPE\sources\boot.wim, So I ran the same commands against that file: C:\_SMSTaskSequence\WinPE >mkdir wim C:\_SMSTaskSequence\WinPE\sources>dism /mount-wim /wimfile:boot.wim /index:1 /mountdir:wim Deployment Image Servicing and Management tool Version: 6.1.7601.17514 Mounting image [==========================100.0%==========================] The operation completed successfully. C:\_SMSTaskSequence\WinPE\sources>dism /image:wim /set-targetpath:X:\ Deployment Image Servicing and Management tool Version: 6.1.7601.17514 Image Version: 6.1.7601.17514 Target Path : X:\ The operation completed successfully. C:\_SMSTaskSequence\WinPE\sources>dism /unmount-wim /mountdir:wim /commit Deployment Image Servicing and Management tool Version: 6.1.7601.17514 Image File : C:\_SMSTaskSequence\WinPE\sources\boot.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. Then I rebooted and everything continued along happily
  4. Hi guys i recently had network driver problems with some new HP models (8200 elite and Z210) i was looking at having to slipstream the drivers into the win7 and server 2008 boot.wim. I was having some problems finding the right drivers to inject when i thought that the win8 pre-release iso would have a boot.wim in the sources folder with lots of new drivers already on. And it did... so no more using win7 and server 2008 boot.wim. Hopefully this will help anyone who has similar problems. Knowing my luck everyone has already been doing this and i've just been sleeping. :-) Regards Les
×
×
  • Create New...