Boot image

I have made a disk image of my harddrive. I now would like to know how I can make a univeral boot image that I can use to them install my disk image.
Any sugestions on how to make a boot image?

If you are storing this image on an external drive, then I would suggest a different approach. Make a bootable clone of your hard drive onto the external drive. You can then boot from the external drive and use the clone to restore the system on the hard drive should you have a problem. With the right backup software you can also schedule regular incremental updates to the clone so the clone is always the same as the hard drive. See the following:
Basic Backup
Use an external Firewire drive at least equal in size to the internal hard drive and make (and maintain) a bootable clone/backup. You can make a bootable clone using the Restore option of Disk Utility. You can also make and maintain clones with good backup software. My personal recommendations are (order is not significant):
1. Retrospect Desktop (Commercial - not yet universal binary)
2. Synchronize! Pro X (Commercial)
3. Synk (Backup, Standard, or Pro)
4. Deja Vu (Shareware)
5. PsynchX 2.1.1 and RsyncX 2.1 (Freeware)
6. Carbon Copy Cloner (Freeware - 3.0 is a Universal Binary)
7. SuperDuper! (Commercial)
8. Intego Personal Backup (Commercial)
9. Data Backup (Commercial)
The following utilities can also be used for backup, but cannot create bootable clones:
1. Backup (requires a .Mac account with Apple both to get the software and to use it.)
2. Toast
3. Impression
4. arRSync
Apple's Backup is a full backup tool capable of also backing up across multiple media such as CD/DVD. However, it cannot create bootable backups. It is primarily an "archiving" utility as are the other two.
Impression and Toast are disk image based backups, only. Particularly useful if you need to backup to CD/DVD across multiple media.
Visit The XLab FAQs and read the FAQs on maintenance, optimization, virus protection, and backup and restore. Also read How to Back Up and Restore Your Files.
Although you can buy a complete FireWire drive system, you can also put one together if you are so inclined. It's relatively easy and only requires a Phillips head screwdriver (typically.) You can purchase hard drives separately. This gives you an opportunity to shop for the best prices on a hard drive of your choice. Reliable brands include Seagate, Hitachi, Western Digital, Toshiba, and Fujitsu. You can find reviews and benchmarks on many drives at Storage Review.
Enclosures for FireWire and USB are readily available. You can find only FireWire enclosures, only USB enclosures, and enclosures that feature multiple ports. I would stress getting enclosures that use the Oxford chipsets (911, 921, 922, for example.) You can find enclosures at places such as;
Cool Drives
OWC
WiebeTech
Firewire Direct
California Drives
NewEgg
All you need do is remove a case cover, mount the hard drive in the enclosure and connect the cables, then re-attach the case cover. Usually the only tool required is a small or medium Phillips screwdriver.

Similar Messages

Boot image does not exist and cannot read disk label errors.

Hi - I'm having a problem with installing Solaris 9 4/04 on a Netra T1. The Netra already has Solaris 7. I need to get this set up as a jumpstart server but it can't find the boot image. I'm using a brand new bonafide installation disk - not a copy. The system won't let me install/upgrade to Solaris 9 either. I get an error stating that disk label can't be read. I've tried swapping out the CDROM but I still get the same errors. Does anyone know what or why this may be happening? (Oh - and another strange thing - like I said the CDs are the original but there doesn't appear to be a cdrom/cdrom0/s0 directory. The directory I see is cdrom/cdrom0/sol_9_404_sparc/Solaris_9/Tools)
ERROR: Install boot image /cdrom/sol_9_404_sparc/Solaris_9/Tools/Boot does not exist
Check that boot image exists, or use [-t] to
specify a valid boot image elsewhere.
and
Excuting last command: boot cdrom [- nowin]
Boot device: /pci@1f,0/pc1@1/ide/cdrom@2:f file and args: [- nowin]
Can't read disk label.
Can't open disk label package
Evaulating: boot cdrom [- nowin]@1/ide@e/cdrom@2:f File and args: [- nowin]
Can't open boot device
I appreciate any help at all - is there anyone out there who can tell me what I may be doing wrong?
Thanks

Hi check that you are booting of the right cd. Make sure it is soalris 9 software 1/2 if that fails then it may well be that your cd is buggered. most likely it is buggered it it cant find the boot image.

How to use two different boot images in the same task sequence

I have a need to use Two boot images in the same task sequence. The reason is I'm deploying ZTI to McAfee encrypted devices which I have already done with McAfee v6 Encryption successfully.
Here's where my problem comes in. We are about to deploy McAfee v7 which means we will have a mix of v6 and v7 in our environment. I must have two special Boot images one with v6 drivers and one with v7 drivers in order for my process to work. I don't see
a way right now to assign more than one boot image to a task sequence. Is there any way to do this?
If I can't do that then I will have to create two task sequences and target collections based on the Endpoint Encryption version to deploy to.
If anyone has suggestions it would be much appreciated. Thank you

Have you tested copying those files to %windir%\system32\drivers during the WinPE session (just enable commandline support to your boot image) to see if they need to be in there before the OS start? Test that and if they don't need to be there during the
boot up of WinPE then:
Create two packages (v6 and v7)
"Run command line", use the package created earlier and just use "copy /Y .\*.* %windir%\system32\drivers" ...again, this should be run according to your needs, variable or some other check like I said

How to load a boot image to cisco aironet 1140 series after missing boot image

Hi all,
I need a solution for this. When i switch my cisco aironet 1140 , it s blinking with red light .and gives a message "no boot image to load".
When i tried next time, by pressing escape it shows this message that i have mentioned below.
ap:
ap:
using eeprom values
WRDTR,CLKTR: 0x83000800 0x40000000
RQDC ,RFDC : 0x80000035 0x00000208
using ÿÿÿÿ ddr static values from serial eeprom
ddr init done
Running Normal Memtest...
Passed.
IOS Bootloader - Starting system.
FLASH CHIP: Numonyx P33
Checking for Over Erased blocks
Xmodem file system is available.
DDR values used from system serial eeprom.
WRDTR,CLKTR: 0x83000800, 0x40000000
RQDC, RFDC : 0x80000035, 0x00000208
PCIE0: link is up.
PCIE0: VC0 is active
PCIE1: link is NOT up.
PCIE1 port 1 not initialized
PCIEx: initialization done
flashfs[0]: 1 files, 1 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 32385024
flashfs[0]: Bytes used: 1536
flashfs[0]: Bytes available: 32383488
flashfs[0]: flashfs fsck took 16 seconds.
Reading cookie from system serial eeprom...Done
Base Ethernet MAC address: 28:94:0f:d6:c8:62
Ethernet speed is 100 Mb - FULL duplex
The system is unable to boot automatically because there
are no bootable files.
C1140 Boot Loader (C1140-BOOT-M) Version 12.4(23c)JA3, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Compiled Tue 18-Oct-11 14:51 by prod_rel_team
ap:
So , now my question is how to load the boot image ? From where will we get this ? OR
I m also having another Cisco aironet 1140 , Can i get bootimage from that . Kindly let me know the solution from genius ?

Take a look at this link as it should have the info you need
https://supportforums.cisco.com/docs/DOC-14636
Sent from Cisco Technical Support iPhone App

System Image Utility fails to create boot image

I am not able to successfully build a boot image with the System Image Utility. The build starts and runs for about 1 minute and then I get 100's of ditto messages saying "No space left on device". There's plenty of space left on the device. Eventually I get a GUI message stating the there was an error creating the image. The image is of course unusable. This only happens on a Boot image. I have no problem making an install image from the same source. Is it just me??
Xserve G5 Dual Mac OS X (10.4.5)

I had simililar problems with much headscratching as the result.
I found that whenever I tried to create a boot image with System Image Utility (SIU) using an image file of my existing system as the source SIU would fail with the annoying "No space left on device" message everytime. I did a little investigating and found that SIU always created a 400 MB disk image file to copy to. So the error message was correct as my source was way over 4 GB.
I checked the manual and found the embarrasingly simple solution. It's not mentioned directly, rather it is stated that when you want to create an boot image from an existing system you should boot the machine containing the desired system on disk from an alternate source and the run SIU on that machine. The "trick" is that you're running SIU with the existing system mounted as a disk.
So I went back to my Xserve, mounted the image so it appeared on the desktop. Ran SIU and chose the mounted volume as the source instead of the image file, and hey presto!
MacBook Pro, Xserve, eMac, iMac... any Mac I can get my hands on Mac OS X (10.4.6)

Having issues with Surface Pro 3 downloading boot image over PXE

Hi,
We've recently started to buy the new Surface Pro 3 with the new USB 3.0 Gigabit Ethernet adapter and we have some issues deploying them through SCCM. Basically, with the Pro 2 and Fast Ethernet adapter we have no issue at all, of course the deployment is
a bit longer than on any other computer, but it is still quite faster than the latest Surface.
We have the new 8.13.414.2014 driver injected in the Win 8.1 boot image for the USB 3.0 Gigabit adapter and all the drivers assigned to the new Surface in SCCM.
The problem occurs when we try to load the boot image after choosing PXE, it takes more than an hour to load it when it shouldn't take more than 5 minutes.
I tried rolling back to the old driver (8.6.128.2013) and use the Fast Ethernet adapter, use the Fast Ethernet adapter with the new driver and use the new adapter with the old driver, but it's still slow in any case, so
I'm pretty sure it has something to do with the new Surface and not the Ethernet adapter.
Anyone have an idea what could be the problem here? Anyone having issues with Surface Pro 3 and SCCM 2012?

I would imagine you have upgraded to R2, have you also applied KB2905002.
This hasn't got anything to do with the TFTP loading phase of the boot image.
Similar thread to this can be found here:
http://social.technet.microsoft.com/Forums/en-US/a6d80714-dc26-43db-a071-93eaee267122/surface-pro-2-surface-ethernet-adapter-super-slow-pxe?forum=configmanagergeneral
I already asked in that thread the same question, but how about normal PCs that are connected to the same network segment as the Surface devices, do they boot slow also?

Cannot backup Windows 7 (dual-boot) image to external HD (formated as Mac OS Extended)

I cannot backup my Windows 7 (dual-boot) image to my external HD (formated as Mac OS Extended). I installed MacDrive 8.0 hoping to solve the problem but Windows 7 gives me an error when I try to create a backup: "...drive is not formatted as NTFS, cannot use as backup...".
I also tried making an Image of the Windows 7 partition through Disk Utility but was not allowed to do so.
I am not sure where else to go from here. I need to keep my external hard drive formatted as Mac OS Extended but I also need to backup my Windows 7 partition. I only have the single external at the moment. Is there a way to backup my Windows 7 partition?
Thanks

Winclone will backup your Windows partition to a Mac formatted drive.
Just search for Winclone on this forum and on Goggle.

Do I need to use a boot image? 6509 / Sup2T Quad / VSS

I'm curious about boot loader images and if or why I should use one.
I've got a 6509 VSS setup running right now with no bootloader variable and no boot image.
SHEC-VSS#sh boot
BOOT variable =
CONFIG_FILE variable =
BOOTLDR variable =
Configuration register is 0x2102
Standby BOOT variable =
Standby CONFIG_FILE variable =
Standby BOOTLDR variable =
Standby Configuration register is 0x2102
SWITCH-VSS#sh ver
Cisco IOS Software, s2t54 Software (s2t54-ADVIPSERVICESK9-M), Version 15.1(2)SY2, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Wed 26-Feb-14 16:03 by prod_rel_team
ROM: System Bootstrap, Version 12.2(50r)SYS3, RELEASE SOFTWARE (fc1)
SHEC-VSS uptime is 16 weeks, 3 days, 21 hours, 10 minutes
Uptime for this control processor is 16 weeks, 3 days, 21 hours, 10 minutes
System returned to ROM by power on
System restarted at 13:56:56 CDT Fri May 16 2014
System image file is "bootdisk:s2t54-advipservicesk9-mz.SPA.151-2.SY2.bin"
Last reload reason: power-on
I'm about to set up a nearly identical VSS pair for another facility.
I just downloaded the latest SY3 version of IOS for the new pair, and there is a boot image available:
s2t54-boot-mz.SPA.151-2.SY3.bin
I just don't know why I would want or need that. Can anyone explain? I'm not a newbie by any means, but I just don't know why I'd need it. Right now, in the bootdisk: volume, I just have my IOS image: s2t54-advipservicesk9-mz.SPA.151-2.SY2.bin That was all that was in there before, but now that I'm building this new pair, I copied s2t54-advipservicesk9-mz.SPA.151-2.SY3.bin onto the same volume.
I understand that if I set a boot variable I can tell it to boot from one image or the other, but what does the BOOTLDR variable do for me. If I were to set the BOOTLDR variable to bootdisk:/s2t54-boot-mz.SPA.151-2.SY3.bin then what does that do for me? Right now, if I reboot, (until I added that 2nd image) it will just boot the only image in that directory with no issue.
What am I missing? Do I need to upgrade or use this boot image for anything?
Thanks for any tips you can provide!
Tim

Tim,
In simple terms, the bootldr file is the helper file to load the IOS.
The BOOTLDR environment variable specifies the Flash file system and filename that contains the boot loader image required to load system software.
The variable defines the primary Cisco IOS image that will load the final image from another source.
we need to set the BOOTLDR environment variable to specify the Flash device and filename of the boot loader image.
For Old version of IOS, there is a requirement of boot loader image to boot up the IOS image.
But for the latest version of IOS, no need for boot loader image.
Below are few things happen when the device boots:-
1. The router initially boots into ROMMON (this is your bootstrap code, which you can see in the show version command).
2. Then the router loads into the bootloader code (this is the bootloadr code, which you see in show version). This bootloader code is just an intermediate step between the ROMMON mode and the IOS mode.
3. The router then boots into the IOS mode from the bootloadr mode.
So if you do not mention the bootloadr specifically by giving the "boot bootloadr" command, the router will assume the bootloadr to be in bootflash of the device and try to boot it from there. If you mention the "boot bootloadr flash:...." command, then the router will look for the bootloadr in the flash (instead of the bootflash). Thats the only difference.
However, in both cases, if you have a valid IOS to boot into, then the router will come up without a problem, irrespective of the fact whether bootloadr image is in bootflash or flash.
HTH
REgards
Inayath
*Plz dont forget to rate if this info is helpfull.

Unable to import Windows 7 boot images

When we installed our SCCM 2012 server, no boot images appear to have been created. I have since upgraded to R2, and added CU3, and there are still no boot images available. I would like to add boot images for Windows 7 x64 but so far have been
completely unsuccessful. I have tried creating images with MDT on the server, and they will not import. I have also created them with WAIK 3.0 with the WAIK 3.1 Supplement from a Windows 7 machine, and those will also not import. In every situation I
receive the following error: The specified UNS path does not contain a valid WIM file or you do not have permission to access it. Specify a valid path. This occurs if I try to import from a share on the sccm server, or from a share on
another computer. The permissions on the share are set at Everyone--full control share permission, and NTFS permissions are set to give the system account, the computer account and domain admins full control. The SMSProv.log file shows the
following error on each failed attempt: Failed to get the image property from the source WIM file due to error 80070002. I have read everything I can find and tried everything that people are mentioning that has fixed the problem for them, and so far
no success. I feel like I must be missing something, but I'm not sure where else to look. Any suggestions will be most appreciated!

Uninstalled and reinstalled ADK--no improvement.
Every time I try to import a boot image, the SMSProv log shows this:
~ $$<SMS Provider><01-21-2015 15:30:43.623+300><thread=7084 (0x1BAC)>
CExtUserContext::EnterThread : User=COP\reistg Sid=0x01050000000000051500000010DFF9978E4D14F2AFDA7FC15A0C0000 Caching IWbemContextPtr=000000385D804E50 in Process 0xd80 (3456)~ $$<SMS Provider><01-21-2015 15:30:43.623+300><thread=7084
(0x1BAC)>
Context: SMSAppName=Configuration Manager Administrator console~ $$<SMS Provider><01-21-2015 15:30:43.623+300><thread=7084 (0x1BAC)>
Context: MachineName=xxx.xxxx.xxx~ $$<SMS Provider><01-21-2015 15:30:43.624+300><thread=7084 (0x1BAC)>
Context: UserName=COP\reistg~ $$<SMS Provider><01-21-2015 15:30:43.624+300><thread=7084 (0x1BAC)>
Context: ObjectLockContext=1316ccc7-f4be-40c3-9b9e-c34dd1028080~ $$<SMS Provider><01-21-2015 15:30:43.624+300><thread=7084 (0x1BAC)>
Context: ApplicationName=Microsoft.ConfigurationManagement.exe~ $$<SMS Provider><01-21-2015 15:30:43.624+300><thread=7084 (0x1BAC)>
Context: ApplicationVersion=5.0.7804.1400~ $$<SMS Provider><01-21-2015 15:30:43.625+300><thread=7084 (0x1BAC)>
Context: LocaleID=MS\0x409~ $$<SMS Provider><01-21-2015 15:30:43.625+300><thread=7084 (0x1BAC)>
Context: __ProviderArchitecture=32 ~ $$<SMS Provider><01-21-2015 15:30:43.625+300><thread=7084 (0x1BAC)>
Context: __RequiredArchitecture=0 (Bool)~ $$<SMS Provider><01-21-2015 15:30:43.625+300><thread=7084 (0x1BAC)>
Context: __ClientPreferredLanguages=en-US,en~ $$<SMS Provider><01-21-2015 15:30:43.626+300><thread=7084 (0x1BAC)>
Context: __CorrelationId={2F91BBB1-35A9-0008-97BC-912FA935D001}~ $$<SMS Provider><01-21-2015 15:30:43.626+300><thread=7084 (0x1BAC)>
Context: __GroupOperationId=13101 ~ $$<SMS Provider><01-21-2015 15:30:43.626+300><thread=7084 (0x1BAC)>
CExtUserContext : Set ThreadLocaleID OK to: 1033~ $$<SMS Provider><01-21-2015 15:30:43.626+300><thread=7084 (0x1BAC)>
CSspClassManager::PreCallAction, dbname=CM_COP~ $$<SMS Provider><01-21-2015 15:30:43.626+300><thread=7084 (0x1BAC)>
PutInstanceAsync SMS_BootImagePackage~ $$<SMS Provider><01-21-2015 15:30:43.627+300><thread=7084 (0x1BAC)>
CExtProviderClassObject::DoPutInstanceInstance~ $$<SMS Provider><01-21-2015 15:30:43.627+300><thread=7084 (0x1BAC)>
GetStorage : doing Loggin due to aged out context~ $$<SMS Provider><01-21-2015 15:30:43.627+300><thread=7084 (0x1BAC)>
************ WBEM Missing property TransformAnalysisDate~ $$<SMS Provider><01-21-2015 15:30:43.645+300><thread=7084 (0x1BAC)>
************ WBEM Missing property TransformReadiness~ $$<SMS Provider><01-21-2015 15:30:43.645+300><thread=7084 (0x1BAC)>
~*~*~e:\qfe\nts\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp(3634) : Failed to read image property from the source WIM file due to error 80070002~*~*~ $$<SMS Provider><01-21-2015 15:30:43.669+300><thread=7084 (0x1BAC)>
~*~*~Failed to read image property from the source WIM file due to error 80070002 ~*~*~ $$<SMS Provider><01-21-2015 15:30:43.669+300><thread=7084 (0x1BAC)>
Auditing: User COP\reistg called an audited method of an instance of class SMS_BootImagePackage.~ $$<SMS Provider><01-21-2015 15:30:43.669+300><thread=7084 (0x1BAC)>
CExtUserContext::LeaveThread : Releasing IWbemContextPtr=1568689744~ $$<SMS Provider><01-21-2015 15:30:43.678+300><thread=7084 (0x1BAC)>

Can't add drivers to Server 2012 R2 boot image in WDS

Hi all.
I want to use my "old" Windows Server 2012 (not R2), WDS to deploy new R2 servers but i can't add driver package to the R2 boot image, it comes out with error code: 0xc0000135 no matter what drivers i use.
Without network drivers i can't boot the image on my physical servers, i've tried on a virtual machine where it works just fine.
I can't use the old boot image to install R2, then it comes with error: "Windows could not apply unattend settings during pass [offlineServicing]." when it tries to install it on both virtual and physical servers.
My initial thought is that the WDS server has to be on a R2 server but i can't find anything that proofs that.
Can someone confirm that non R2 WDS is not supported to R2 or does anyone have an idea to a solution?
Thank you in advance.

Okay maybe not a solution but i installed a new WDS server on R2 and then there was no problem adding driver package to to boot image.
So i was able to confirm my theory that it's not supported to deploy R2 from a non-R2 WDS server. If anyone can make it work please let me know but until then i think this is the only way.
If I understand your description of the issue, the problem is that you are trying to update a WinPE 5.0 WIM with a version of the ADK that services WinPE 4.0 images. Installing the new Windows Server 2012 R2 server caused SCCM to use the version of the
ADK that services WinPE 5.0 images. You should be able to deploy them fine from the other server, but you can only service them from the new one. You will not be able to service the older WinPE 4.0 images from the new server either.

Where to see the boot image package path installed on my DP server

I have distribute the boot image content to one of my DP server. Where can I see the package is installed at which location at that particular DP in SCCM 2012 console?

Hi,
The blog below could answer your question.
Configuration Manager 2012: Content Monitoring and Validation
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Selected boot image did not authenticate. Press enter to continue

I just removed the stock HDD that came with my M4-1015x and now I'm trying to install windows 7 to the SSD that I replaced it with. However, upon boot up I get the message "Selected boot image did not authenticate. Press <enter> to continue" when the laptop attempts to read the OS from the disc. I've never seen this before... any help? (It's a legitimate DVD copy of Windows 7)
Thanks.
This question was solved.
View Solution.

I fixed it. Had to disable secureboot and enable legacy boot mode to get it to run.

Driver in boot image

Hi all,
I add some drivers for Wi-Fi and video, in boot image. I update distribution point. I see how the new drivers was injected in the image. I recreate the task with involved image. I create a new .iso file for offline deployment. But after installation
computer don't have installed drivers. Manually I update the drivers with some drivers used to add to the image and works.
Were I mistake ?
Thanks.

Parsing step node: Apply Driver Package TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Description: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
ContinueOnError: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
SuccessCodeList: 0 TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582) TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
No condition is associated with the step. TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Disable: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Run in attribute: WinPE TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Timeout: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
DefaultVarlist found TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Variable name: OSDAllowUnsignedDriver TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Action command line: osddriverclient.exe /install:NTM0003C /unsigned:%OSDAllowUnsignedDriver% TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Adding instruction at 7 TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Processed all elements TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Adding end group instruction at 8 TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
The next instruction after group will be at 9 TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Processing group TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Parsing group node: Setup Operating System TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Description: Setup Operating System TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
ContinueOnError: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Disable: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582) TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
No condition is associated with the step. TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Adding begin group instruction at 9 TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
There are 1 first level steps or groups TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Parsing step node: Setup Windows and Configuration Manager TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Description: Actions to setup Windows and Configuration Manager client TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
ContinueOnError: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
SuccessCodeList: 0 TSManager 3/10/2014 3:20:05 PM 864 (0x0360)

Image Capture Boot Image Fails with 0xc000000f

I am trying to capture a Windows 8.1 Enterprise (with Update) x64 installation using WDS, but the Capture Image fails to load. I used the boot.wim from the Windows Server 2012 R2 (with Update) ISO to create a boot image in WDS and then a capture image from
it. After I press F12 and the progress bar finishes the following message appears:
This only happens when I boot the capture image - the original boot image that I imported in WDS boots normally. I also tried with the Windows 8.1 (with Update) boot.wim, but the issue reoccurs. This is a Hyper-V VM on Windows Server
2012. Is this a problem with the recent update?

Hi,
We’re currently experiencing exactly the same issue. Also a fully-updated Server 2012R2 (with the recent KB2919355 update) machine.
So far, I found two other posts with exactly the same issue:
1) http://wp.secretnest.info/?p=1474
2)
http://community.spiceworks.com/topic/472581-wds-capture-image-winload-exe-corrupt-or-missing
According to these posts it seems like the issue occurs after the first time a capture image based upon a Windows 8.1 or Server2012R2 boot.wim is created.
What I’ve tried so far is removing the server role, deleting the WDS store, rebooting the server and start over with a Windows 7 boot.wim. The normal boot.wim starts ok, but the created capture image doesn’t.
So the process of creating the capture boot image did ‘something’ in a way the new boot.wim differences from the old boot.wim. To find out what, I first mounted the new .wim file to see if winload.exe is actually there – it is both in
system32 as well as systen32\boot. So my second guess was that the Windows Boot Manager cannot find the windows loader, because of an incorrect declaration of disks in the BCD store.
I used BCDEDIT to show the differences between the working and non-working boot images:
Windows Boot Loader
identifier {1d214c07-6892-401c-a762-04647ad38560}
device ramdisk=[boot]\Boot\x64\Images\boot.wim,{b321afc0-8a23-4
961-85dd-a10f3c46473f}
description Windows 7 Boot Image
osdevice ramdisk=[boot]\Boot\x64\Images\boot.wim,{68d9e51c-a129-4
ee1-9725-2ab00a957daf}
systemroot \WINDOWS
detecthal Yes
winpe Yes
Device options
identifier {b321afc0-8a23-4961-85dd-a10f3c46473f}
inherit {68d9e51c-a129-4ee1-9725-2ab00a957daf}
ramdiskmcenabled No
ramdiskmctftpfallback Yes
-- Second - Non Working disk --
Windows Boot Loader
identifier {872352a0-0ad9-46f6-8612-1aed71ea8534}
device ramdisk=[boot]\Boot\x64\Images\boot-win7-capture.wim,{7a
b86a3a-3651-4f50-a748-34f3e784158c}
description Windows 7 Capture
osdevice ramdisk=[boot]\Boot\x64\Images\boot-win7-capture.wim,{68
d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot \WINDOWS
detecthal Yes
winpe Yes
Device options
identifier {7ab86a3a-3651-4f50-a748-34f3e784158c}
inherit {68d9e51c-a129-4ee1-9725-2ab00a957daf}
ramdiskmcenabled No
ramdiskmctftpfallback Yes
So the ID for the osdevice is the same, and only the device is different, but mentioned correctly under Device options (as far as my knowledge goes in this subject). I hope there will be a solution anytime soon.

G41M-E43 and BIOS BOOT IMAGE

Does anyone know if this board can have it's BIOS BOOT image replced with a custom one?
What tool is used to do this?
I would like to change the image to something for my HTPC I am building....I know I can disable it. I want to put my own image on the BOOT screen.
Thanks,
*BH*

ThinkWiki says you have to work with them. I haven't come across a method to suppress them.
http://www.thinkwiki.org/wiki/How_to_change_the_BIOS_bootsplash_screen
I don't work for Lenovo. I'm a crazy volunteer!

Client getting an IP lease on the 64-bit LiteTouch boot image, but not the 32-bit version.

MDT 2012 U1. No problem with PXE booting so WDS is not the issue.
The NIC in question is the Intel I217-LM, which resides on both the new Dell Optiplex 9020 and the Latitude E7440. I downloaded the Dell drivers and then the Intel drivers and imported them into the WindowsPE drivers folder in the workbench. Updated
the boot images to make sure the new drivers were injected. Both yielded the same result. I can do everything I need to do when booting to the 64-bit LiteTouchPE_x64.wim boot image, but not the 32-bit version. When booting to the 32-bit
version, I get no IP configuration info at all.
When looking at the drivers in MDT, I see only one difference: the supported OS versions. The 64-bit driver supports 6.1, 6.1.1, and 6.2. The 32-bit driver supports only 6.1.1 and 6.2. Not sure if that's the issue.
Tried using drvload within 32-bit WinPE to manually inject the NIC driver. Still no luck. Ipconfig yields no configuration at all.
If I can't get these machines to boot to the 32-bit boot images, I can't deploy 32-bit images, unless there's a way of which I'm unaware.
EDIT: A little extra background. My WindowsPE folder has two subfolders called x86 and x64. Obviously, 32-bit drivers go into the x86 folder and 64-bit drivers go into the x64 folder. Then in the properties of the deployment share a
selection profile is selected which points to the architecture-specific folders.

Specifically what do you see when you are in WinPE, press the F8 button, and run ipconfig.
1. ipconfig shows no network adapters (see:
http://myitforum.com/cs2/blogs/rpedersen/clip_image002_53DA17D4.jpg ). This means you still have not loaded the correct device drivers, check the c:\windows\system32\wpeinit.log file.
2. ipconfig shows an "autoconfiguration IPv4 Address" with a netmastk of 255.255.0.0. This means that the client did not get an IP address from the DHCP server. Double check the connection between the client and the DHCP server.
3. ipconfig shows a correct address. There is no problem. :^)
Keith Garner - keithga.wordpress.com
I get the first result. Absolutely no network adapters, which I assumed indicated no appropriate device driver.
This is the result of the wpeinit.log from the machine booting to the 32-bit boot image:
Info WPEINIT is processing the unattend file [X:\unattend.xml]
Info Spent 1747ms initializing removable media before unattend search
Info ==== Initializing Display Settings ====
Info Setting display resolution 1024x768x32@60: 0x00000000
Info STATUS: SUCCESS (0x00000000)
Info ==== Initializing Computer Name ====
Info Generating a random computer name
Info No computer name specified, generating a random name.
Info Renaming computer to MININT-TFRU2BT.
Info Acquired profiling mutex
Info Service winmgmt disable: 0x00000000
Info Service winmgmt stop: 0x00000000
Info Service winmgmt enable: 0x00000000
Info Released profiling mutex
Info STATUS: SUCCESS (0x00000000)
Info ==== Initializing Virtual Memory Paging File ====
Info No WinPE page file setting specified
Info STATUS: SUCCESS (0x00000001)
Info ==== Initializing Optional Components ====
Info WinPE optional component 'Microsoft-WinPE-HTA' is present
Info WinPE optional component 'Microsoft-WinPE-MDAC' is present
Info WinPE optional component 'Microsoft-WinPE-WMI' is present
Info WinPE optional component 'Microsoft-WinPE-WSH' is present
Info STATUS: SUCCESS (0x00000000)
Info ==== Initializing Network Access and Applying Configuration ====
Info No EnableNetwork unattend setting was specified; the default action for this context is to enable networking support.
Info Acquired profiling mutex
Info Install MS_MSCLIENT: 0x0004a020
Info Install MS_NETBIOS: 0x0004a020
Info Install MS_SMB: 0x0004a020
Info Install MS_TCPIP6: 0x0004a020
Info Install MS_TCPIP: 0x0004a020
Info Service dhcp start: 0x00000000
Info Service lmhosts start: 0x00000000
Info Service ikeext start: 0x00000000
Info Service mpssvc start: 0x00000000
Info Released profiling mutex
Info Spent 749ms installing network components
Info Spent 1669ms installing network drivers
Error QueryAdapterStatus: no adapters found.
Info Spent 0ms confirming network initialization; status 0x80004005
Info WaitForNetworkToInitialize failed; ignoring error
Info STATUS: SUCCESS (0x003d0001)
Info ==== Applying Firewall Settings ====
Info STATUS: SUCCESS (0x00000001)
Info ==== Executing Synchronous User-Provided Commands ====
Info Parsing RunSynchronousCommand: 1 entries
Info Command 0: 0x00000000
Info Successfully executed command 'wscript.exe X:\Deploy\Scripts\LiteTouch.wsf' (exit code 0x00000000)
Info STATUS: SUCCESS (0x00000000)
Info ==== Executing Asynchronous User-Provided Commands ====
Info STATUS: SUCCESS (0x00000001)
Info ==== Applying Shutdown Settings ====
Info No shutdown setting was specified
Info STATUS: SUCCESS (0x00000001)
At first I thought the first bolded section might be relevant, but when I booted to the x64 boot image, which works fine, I get the same message in its wpeinit.log file. The only difference between the two log files is that the x64 boot image actually
shows successful installation of a driver where the second bolded section is.

Boot image

Similar Messages

Maybe you are looking for