Macbook & creating EFI bootable media

Hi,
I've got a quick clarification on something written on ArchWiki MacBook installation instructions concerning creating UEFI bootable media; it states "You will need to format the EFI partition with the hfsplus filesystem (hfsprogs) instead of vfat;" does this refer to the partition on the USB stick, or the EFI partition created on the macbook? If it is the former, I do not understand why it is referring to the USB partition as the "EFI partition;" if it is the latter, this seems to be in direct contradiction to the simple example of partitions created on the macbook thereafter.
I'm having a bit of trouble creating a bootable stick based on these instructions. I assume rEFIt is not required, since it is not mentioned on the macbook page. When I press alt on start up, my USB drive does not appear. (Though I wouldn't imagine this has any relevance on the USB drive appearing, currently this macbook only has Debian installed on it. I'm picking up some replacement install disks on Friday in order to create a clean install of Mac OS X to start from as suggested on the wiki's macbook page, but I wanted to see if my USB drive would actually boot first.)
Thank you very much for any help, apologies if I have overlooked any of the available literature which might clarify my issue.

Hi riemannia,
The instructions are actually referring to a second partition, which you make as part of the install, that is a EFI bootable partition. For example, on my rMBP-15, I have a 100MB /dev/sda4 which is hfs+ formatted and contains a grub.efi in System/Library/CoreServices on that partition. This is so that when you hold down option at boot, you'll have a choice between "Macintosh HD" and "Whatever you named your Linux EFI boot partition".
See once-through guide on vec.io (https://vec.io/posts/use-arch-linux-and … na-display) for a step by step. However, be aware that as things are right now, your newer Linux 3.11.6 kernel and the Nvidia 325 driver will result in a black screen and a computer that doesn't appear to respond. You can use the fbdev driver for X if you need to between now and (hopefully) Nvidia 331.
Hope that helps.

Similar Messages

Permission to create bootable media

what are the needed permissions needed for a user to create a bootable media? We are encountering the error "Error invoking WMI method SMS_Site.SubmitRegistrationRecord (0x80041001)" The user who is creating the bootable media was already part
of the local administrators group of the machine

Hi,
You need to take a look at the SMSPROV.log file to see why the registration failed.
For more information, please review the link below：
How to Deploy Operating Systems by Using Media in Configuration Manager
http://technet.microsoft.com/en-us/library/hh397285.aspx#BKMK_CreateBootableMedia
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.

Create Task Sequence Media Issue

I am 1 of 2 people that have full admin access to our config manager environment and when I create a bootable USB stick I get an error, "80004005", after I complete the HTA which indicate a certificate issue.
However if I have my colleague create it, who is the other full admin, using the same configuration I do not get the error and see the deployments. Any suggestions?

Sorry as i re-read my message I see that I was not clear. I do not get an error while creating the bootable media, I receive that error when I attempt to use the bootable media
to OSD a device.
I am getting the 0x80004005 error post boot after I complete the HTA's questions, in the boot image, and before it looks for the available task sequences deployed to that device.

No Available distribution points when i create task sequence media wizard

Hi All,
I need your support with the following issue
when I try to Create task sequence media and choose the location and boot image x64 or x86 I found this issues
FYI: I am using the administrator and i cheeked the permissions and i have the full permissions for all roles

For this issue, You can refer below link
http://blogs.technet.com/b/configurationmgr/archive/2012/08/28/troubleshooting-missing-management-points-when-creating-a-bootable-media-task-sequence-in-system-center-2012-configuration-manager.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Create Task Sequence Media Wizard Fails

When attempting to create a bootable media for a task sequence I get the error: Media creation failed with the error message: A required privilege is not held by the client. Refer to createTSMedia.log file to find more details. Upon looking in
this log file I see the following in red:
Unable to apply (0x80070522)
Closing image file C:\Users\sccmadmin\AppData\Local\Temp\_tsmedia_7156\Cache\LSA00022\WinPE.LSA00022.wim
Failed to create media generator (0x80070522)
CreateTsMedia failed with error 0x80070522, details=''
Media creation process that was started from Admin Console completed.
CreateMedia.exe finished with error code 80070522
I get this error with trying to create an iso as well as trying to create a bootable USB drive.
The SCCM Console was started with admin privileges. I get this same error trying it on the console installed on my workstation and the console installed on the sccm server. I am a local administrator on my workstation and sccm console. I
recall successfully creating media before but for some reason this doesn't work any longer and I am not sure what changed.
SCCM Server: OS and SCCM version are 2012 R2
Workstation: Windows 7 pro

OK, I would explain the symptoms you have as you have shown at the beginning of this post, explain the difference in policies between the Dev and Prod boxes. Ask that they create a temporary policy to add the default setting of Administrators back
in for you to do some testing.
I am guessing as this is applied to your servers and workstations, based on what you have said, that this setting resides in your Default Domain Policy GPO. Which is possibly the exact issue that Hai Deep had in the post Jórgen posted here
https://social.technet.microsoft.com/Forums/systemcenter/en-US/83b11a23-24ec-46b1-9a5f-52d335dc92b5/unable-to-create-task-sequence-media-privilege-not-held-by-client?forum=configmgrosd
The above post also says it was a user right which caused the issue, so there is a fair amount of justification to apply the test.
Is your Dev instance in the same Domain or is it a completely separate lab?
let me know if you have issues,
Thanks,

Can I create a bootable DVD for my Macbook running 10.5.8?

I'm trying to install a larger hdd in my 2007 MacBook 13" 2.16 Core Duo. I used SuperDuper to create a disk image on an external USB drive but when I reboot with the alt/option key depressed, it only finds my internal disk. I'm guessing I can't boot this old laptop from a USB disk, so now I'm wondering if I can create a bootable DVD or CD for it. Or do I need to upgrade my OS?

Hi, if tryly a PowerMac, (PPC instead of Intel), you may need a Firewire Drive to be bootable, most PPC Macs cannot boot OSX from a USB drive.
So we know more about it...
At the Apple Icon at top left>About this Mac, then click on More Info, then click on Hardware> and report this upto but not including the Serial#...
Hardware Overview:
Model Name: iMac
Model Identifier: iMac7,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.4 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 6 GB
Bus Speed: 800 MHz
Boot ROM Version: IM71.007A.B03
SMC Version (system): 1.21f4

How do I download Mountain Lion to create a bootable installer USB for an old macbook

I am trying to reformat an old macbook, and it says it is unable to unmount the drive when I attempt to erase the disc. I've been told I need to create a bootable installer and try using disc utility from the installer to erase it, but can't find out how to download any OS X installer other than Yosemite (which isn't suitable as the macbook is too old).

If it is too old to run Yosemite, Mountain Lion won't run either. The hardware requirements are the same for both versions of the OS. You might be able to use Lion, but from my experience with Lion, I'd stay with Snow Leopard.
Computer Compatibility - Lion Lion
Disk Unmount Using Terminal
Disk Unmount Using Terminal (2)

Creating a bootable Lion install disc/disk and using it

Hi all,
Below is a copy of a method ds store posted for creating a bootable Lion install disc. Some questions:
1. Is this a polished final version of the process, or are there other steps which could/should be added?
2. Are there any disadvantages to going this route instead of installing directly onto a Mac?
3. After creating a Lion install disc/disk via this method and using this saved dmg to install Lion on a Mac, will it set up the Mac exactly the same way it would by downloading/installing directly from the Apple Store (sounds like a "duh" question, but nothing would surprise me with Lion)?
4. Exact size of this dmg (in case I want to use a flash drive instead)?
I have been avoiding Lion, hoping it would shape up. I'm still not satisfied and will not run it on my main machines. (Of course ymmv; I'm not looking to be talked into or out of using Lion.) However, I am ******* (hmmm, I guess l-u-s-t-i-n-g is a bad word!) over a new Mac Mini, which will have Lion installed, with no chance of running SL on it due to the new hardware revision. Thus, I'm either going to have to make peace with Lion or forget about a new Mini. I guess I'll have to give Lion a try, but I still don't want to actually run it on any of my machines; thus, I want to run it from an external drive, playing with it as I have time/desire, leading to more questions.
5. Using the install disc/disk created above, will it set up Lion on a DVD, flash drive, or external HD exactly as it would on a Mac (Recovery Disk, etc.)?
6. How much space is needed on a destination disc/disk to install Lion?
7. Is it possible to boot from a different volume, mount this dmg, and install Lion from it?
8. Any advantages/disadvantages doing it this way (#7) as opposed to booting from the Lion install disc/disk created above?
9. Another method I'm thinking of using is to (after cloning my SL installation) actually install Lion on my MBP over my current SL installation (shudders violently ), clone it to an external HD, then erase/zero the MBP's HD and clone my SL install back to my MBP. Has anyone done this? Again, I'm concerned that Lion will do something goofy and leave some kind of footprint behind, like maybe messing with firmware; cloning my SL installation back to my internal HD would not reverse a firmware change.
10. Any constructive suggestions on anything related to any of these steps is welcome!
Yes, I've searched and read a number of responses, but I'm hoping much of the "discovery" phase is over, and there are some "solid"/refined answers by now. My bottom line is to be able to play with Lion without having to depend on it.
Thanks!
Backup Lion Bootable 10.7 Disk
Purchase and download Lion from the Mac App Store on any Lion compatible Mac running Snow Leopard.
Right click on “Mac OS X     Lion”     installer and choose the option to     “Show Package Contents.”
Inside the Contents folder     that     appears you will find a SharedSupport     folder and inside the     SharedSupport folder     you will find the “InstallESD.dmg.” This is         the Lion boot disc image we have all been waiting for.
Copy “InstallESD.dmg” to         another folder like the Desktop.
Launch Disk Utility and click     the     burn button.
Select the copied “InstallESD.dmg” as the image to     burn,     insert a standard sized 4.7 GB DVD,     and wait for your new Lion Boot     Disc to come     out toasty hot.
With this disc you can boot any Lion compatible Mac, andinstall10.7 just like you installed previous version of Mac OS X. Youcan even use Disk Utility's Restore function to image your Lion bootdisc image onto a external drive suitable for performing a cleaninstall on a optical-drive-less MacBook Air, or Mac mini server.

tjk wrote:
5. Using the install disc/disk created above, will it set up Lion on a DVD, flash drive, or external HD exactly as it would on a Mac (Recovery Disk, etc.)?
DVD: no, flash drive: if it's large enough, external hard drive: yes
6. How much space is needed on a destination disc/disk to install Lion?
Whatever Apple minimum requirements are.
7. Is it possible to boot from a different volume, mount this dmg, and install Lion from it?
possibly, never tried it, it is a dmg so it's a volume all to itself, except it can't install to the same media it's on and can only install to something formatted with GUID and a OS X extended format, like a flash drive or hard drive large enough.
DVD's can't be formatted with a GUID EFI partiton
8. Any advantages/disadvantages doing it this way (#7) as opposed to booting from the Lion install disc/disk created above?
Speed limitation of the media and bus your using, USB 1 is a slower than a hard drive with 7,200 RPM on a Firewire 800 port
9. Another method I'm thinking of using is to (after cloning my SL installation) actually install Lion on my MBP over my current SL installation (shudders violently ), clone it to an external HD, then erase/zero the MBP's HD and clone my SL install back to my MBP.
The problems come from installing Lion over a existing Snow Leopard setup that isn't quite pristine enough for Lions quirkyness, has tweaks or other software installed that breaks 10.7, requiring you to fix it.
You can try it, you've got the 10.6 clone to option boot off of and restore from.
Cloning back and forth is a performance enhancer, not a problem solver.
Ideally it's best to clone 10.6, disconnect, zero and install 10.6, same user name, then up to 10.6.8, then to 10.7, then install programs from fresh sources/copies and then files returned last from backup off the clone (no migration assistant or it brings trouble back)
This will ensure the best possible performance possible with the least trouble as everything is wiped and installed fresh. Only problem being your files it there is something wrong with them, which is easy to remedy to the cause as it's the only thing not pristine.
Once you've got a pristine system, then clone that twice, once for a immediate update other for falling back a week, two weeks or even a month back.
Has anyone done this? Again, I'm concerned that Lion will do something goofy and leave some kind of footprint behind, like maybe messing with firmware; cloning my SL installation back to my internal HD would not reverse a firmware change.
Firmware is hardware specific not OS specific, of course it's possible a old version of a OS won't work with newer firmware, like 10.5 for instance perhaps because Apple has dropped all work on PPC code.
10.6 and 10.7 are just fine with most all present firmware, however there will be a time where a new firmware update could disallow 10.6, likely when iOS X 10.8 Bobcat arrives.
10. Any constructive suggestions on anything related to any of these steps is welcome!
Yes, I've searched and read a number of responses, but I'm hoping much of the "discovery" phase is over, and there are some "solid"/refined answers by now. My bottom line is to be able to play with Lion without having to depend on it.
Cloning only clones the Lion OS X Partition, not the Lion Recovery Partition.
A comptuer that is Lion capable will boot off a media with no Lion Recovery Partition.
You need to create a Lion Disk Assistant USB which copies your Lion Recovery Partition.
It's in my post.
https://discussions.apple.com/message/16276201#16276201

Creating a bootable USB with diskutil and dd

I am trying to create a bootable usb drive using diskutil and dd. I have had some success but not exactly what I wanted or expected. I am creating a bootable usb for MemTest86. I have an img file provided by PassMark. I first partitioned the drive using:
diskutil partitionDisk /dev/disk4 1 GPT "HFS+" "MemTest86" 100%
output:
TYPE NAME
SIZE
IDENTIFIER
   0:
GUID_partition_scheme
*3.9 GB
disk3
   1:
EFI EFI
209.7 MB
disk3s1
   2:
Apple_HFS MemTest86
3.6 GB
disk3s2
This gives me what I would expect, the first partition is an EFI partition of size 209.7MB and the remaining 3.6GB, on a 4GB drive, being allocated to the second partition, /dev/disk3s2, MemTest86.
To copy the img to the disk i first unmount the partitions on disk3
diskutil unmountdisk /dev/disk3
I then run dd
sudo dd if='//Volumes/Mac Mini Backup/Archives/MemTest86 Pro/memtest86-pro-usb/memtest86-pro-usb.img' of=/dev/disk3 bs=1m
Now, the file does end up on the usb drive but..... The data is written to the first partition which used to be the EFI partition. It is now named Untitled and it is a FAT16 partition.
diskutil list /dev/disk3
output:
TYPE NAME
SIZE
IDENTIFIER
   0:
GUID_partition_scheme
*3.9 GB
disk3
   1:
Microsoft Basic Data
51.4 MB
disk3s1
   2:
EFI
103.8 MB
disk3s2
Now, although, this isn't what I expected it does sort of work. When I boot the system into the Startup Manager there are 2 extra drives to boot from, both named "efi boot", all lower case. Both boot into the MemTest86 utility which is my goal but I first didn't expect the partition layout that I got and I can't figure out why I get 2 boot icons to select from. I am guessing that the format of the img file is causing the partition to be a FAT16 partition but I am waiting to hear back from PassMark regarding that.
So if anyone cares to shed a little light on what is happening I would appreciate it.

The only known way to make it work on an external drive is by first installing Windows onto an internal drive, then cloning the install to an external Thunderbolt drive. Thunderbolt is seen as an extension of the internal bus, so Windows doesn't see it as an external device.

Cannot create your bootable usb stick

Hi all,
I'm new to bootcamp and I have the following problem:
When I'm creating a Windows 7 usb drive, it gives me an error "Cannot create your bootable usb stick there was a problem copying files".
I've tried searching google for the problem, but the only possible solutions I've got was to unmount the iso image and try again, but when I do that I still get the same error and when I check the disk utility I find the iso image is mounted again.
Does anyone haven an idea about what to do.
Specs:
OS X Yosemite 10.10.2
MacBook Pro Retina 13-inch Mid 2014
2,6Ghz Core i%
8 GB 1600 MHz ddr3
Thanks in advance!

Please see the Microsoft reference and the second link has an example.
https://support.microsoft.com/en-us/kb/841290?wa=wsignin1.0
Bootcamp Windows 8.1 "No Images Are Available"

When I restart my computer and hold the option key after creating a bootable usb with windows 7 and partitioning only the original partition shows up. Not the windows one or the bootable usb.

     Okay so first things first this isn't the newest macbook pro. When I open about my mac and go to system report it says it is a Macbook Pro 3,1 and the Boot Rom Version say MBP31.0070.B07. Originally when starting up Boot Camp Assistant there where only two options, the "create windows 7 bootable usb" was not there at all. So after some editing and helpful tutorials I was able to get the option show up and created a bootable usb with windows 7 and downloaded the support software onto a separate flash drive. Finally I did the last step and created a second partition for windows. Once the process is complete my computer automatically restarts.
     This is where the problem is. Once my computer makes the booting up sound it doesn't load up windows it gets stuck on a apple logo as if it's trying to reastart normally and can't. So I shut down and this time I hold down the option key during start up. It brings up the main partition and some recovery thing but no windows partiton and no bootable usb.
     I forgot to mention that I am running OS X 10.9.3. Okay any body want to help me out? Iv'e been at this for hours and can't get an inch closer to having windows. Please and thank you!
P.S. If I missed a discussion that answer my question just point me to it. Iv'e been looking for a while, but who knows i might have missed one.

The only known way to make it work on an external drive is by first installing Windows onto an internal drive, then cloning the install to an external Thunderbolt drive. Thunderbolt is seen as an extension of the internal bus, so Windows doesn't see it as an external device.

How do I create a bootable snapshot image of Lion?

How do I create a bootable snapshot image of Lion? In the past, I used disk utilities - restore to create a copy of current hard drive on an external drive. If there was a problem, kids could boot to external and work until internal drive was fixed. This proved to be a great solution. On a new Macbook Pro with Lion, I get an error when I try. It says to do a restore from the recovery disk, but the recovery disk says it is a limited function OSX. I would like a full OSX so they can continue to work and even copy files over if the internal disk is suffering intermittent failures enough not to boot but not enough to keep from copying files. A few years ago one of the kids had a disk/boot failure duing finals but was able to boot from the external hard drive, copy over what he needed and access the internet so that he could finish the exams. Time machine is great, but there are instances where you need a quick fix to keep going until the new hard drive arrives.

I do not run Windows, so I have no idea how to handle that type of situation.
But, just to be clear: disregarding Windows, the recovery option downloads the OS and installs it. Technically, that is not a clone unless you copy the installer and create a bootable OS with it. A clone is an exact copy of your system including all your apps, user settings, files, etc, etc and will exist on an external hard drive in addition to your system on your internal - that is done with CCC or SuperDuper.
And, a GUID partition is created in Disk Utility > click on the drive > choose Partition > choose a layout other than what you now have > there will be a clickable Options button below. Click on that and you can choose GUID. Note: partitioning your drive will erase everything on it.

How to install windows 7 using usb as the bootcamp doesnot have the option of creating a bootable usb. please help

I have an intel based mac with 10.6.8 mac os x. How to install windows 7 using usb as the bootcamp doesnot have the option of creating a bootable usb. please help

Welcome to Apple Support Communities
You can install Windows from a USB drive in one of these computers:
- MacBook Pro with Retina display.
- Mac mini (Mid 2010 and newer).
- MacBook Air.
- iMac (Late 2012).
If you don't have any of these Macs, you can't install Windows through a USB drive. Instead, buy Windows on a DVD. Follow Apple's steps > http://support.apple.com/MANUALS/1000/MA1519/en_US/Boot_Camp_Install-Setup_10.6. pdf

Can't Create a Bootable DVD of TechTool Deluxe

I am trying to create a bootable dvd of TechTool Deluxe (from AppleCare) and it just isn't working.
I have followed the instructions to the letter, but when I try to boot from the disk (either by holding down C or changing the startup disk before restarting) all I get is a gray screen that eventually shuts down to black and tries to start again.
I've tried the disk on my brand new 24" iMac as well and it isn't working there either. I previously made a TechTool Deluxe disk for my Mac Mini (now sold) and it did work, so I am confused as to why there is a problem now.
Thanks for any advice!

Bottom line here is that the TechTool Deluxe from my AppleCare for my MacBook is not bootable on my MacBook.
That's because that disc does not have the right bootROM on it.
Don't worry about it. That TechTool Deluxe disc that comes with AppleCare is a Mickey Mouse lite version of Tech Tool Pro. The idea is to get you to buy TTP.
Dave M.
MacOSG Founder/Ambassador  An Apple User Group  iTunes: MacOSG Podcast
Macsimum News Associate Editor  Creator of 'Mac611 - Mobile Mac Support'

Issue with Client Authenication Certificates within Bootable Media

Hi All,
I am in the process of deploying SCCM 2012 R2 in our environment parallel to our existing SCCM 2007 R3 environment. So far everything is working well. I have hit, however my first issue. This seems to be related to Client Authentication certificate validation.
The problem occurs when booting from SCCM 2012 Task Sequence Bootable media and attempting to contact a local Management Point. I am using a USB Boot key at this point as I do not want to overlap with our existing PXE environment.
The SMSTS.LOG shows the error 0x80072f8f. Specifically the error that I need to get past is:
[TSMESSAGING] AsyncCallback(): WINHTTP_CALLBACK_STATUS_SECURE_FAILURE Encountered TSMBootstrap 19/12/14 11:27:22 AM 1164 (0x048C)
[TSMESSAGING]                : dwStatusInformationLength is 4
TSMBootstrap 19/12/14 11:27:22 AM 1164 (0x048C)
[TSMESSAGING]                : *lpvStatusInformation is 0x10
TSMBootstrap 19/12/14 11:27:22 AM 1164 (0x048C)
[TSMESSAGING]            :
WINHTTP_CALLBACK_STATUS_FLAG_CERT_CN_INVALID is set
TSMBootstrap 19/12/14 11:27:22 AM 1164 (0x048C)
[TSMESSAGING] AsyncCallback(): ----------------------------------------------------------------- TSMBootstrap 19/12/14 11:27:22 AM 1164 (0x048C)
I have followed all of the recommended steps that I can think of so far. I have:
Ensured that the Server Authentication and client authentication certificate on all Site systems is correct (I.e. all certificates are based on Certificate Templates as per the TechNet documentation)
Ensured the Root and Issuing CA's are registered within the SCCM 2012 Site
The Distribution Point role and Bootable Media are using a dedicated Client Authentication certificate that has been imported via a .PFX
Ensured this certificate is in a "Not blocked" state
Ensured the Date and Time of each Site System and of WinPE during the boot process is in sync.
Checked the MPControl.LOG on each of our 2 Management Points looking for errors. These logs are all clear.
Checked the IIS Web Logs on the Management Points. These logs are also all clear.
The SMSTS.LOG is successfully importing the Root CA certificates ....
Root CA Public Certs=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX TSMBootstrap 19/12/14 11:27:22 AM 1164 (0x048C)Importing certificates to root store TSMBootstrap 19/12/14 11:27:22 AM 1164 (0x048C)
Added certificate to store or replaced matching certificate in store. TSMBootstrap 19/12/14 11:27:22 AM 1164 (0x048C)
Added certificate to store or replaced matching certificate in store. TSMBootstrap 19/12/14 11:27:22 AM 1164 (0x048C)
I have noticed that there are plenty of issues related to an invalid CA due to root CA import issues or CRL checking. We currently have CRL checking disabled and based on the "INVALID_CN" reference I don't believe CRL check is part of the equation.
With regards to the Common Name I can confirm the following:
The "ConfigMgr Client Certificate" Template used to auto enroll all domain joined systems is based upon the "Workstation Authentication" template. The Subject Field is set, as by default to "None". The SAN is set to DNS name.
The "ConfigMgr OSD Certificate" Template used to create the client authentication certificate used on the DPs and Bootable Media is set to "Supplied at Request". I set a CN of "Configmgr OSD Certificate" for this certificate.
I have tried using another client authentication certificate for the DPs and Bootable media that had no Subject Name defined.
Can offer any suggestions as to where I might be going wrong?
Thanks,
Nathan Sutton
NSutton

Hi Jason,
Here is the log as requested. I will post it up in separate messages.
<![LOG[LOGGING: Finalize process ID set to 724]LOG]!><time="13:36:01.388+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="728" file="tslogging.cpp:1495">
<![LOG[==============================[ TSBootShell.exe ]==============================]LOG]!><time="13:36:01.388+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="728"
file="bootshell.cpp:1055">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL']LOG]!><time="13:36:01.404+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="728" file="util.cpp:964">
<![LOG[Debug shell is enabled]LOG]!><time="13:36:01.404+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="728" file="bootshell.cpp:1066">
<![LOG[Waiting for PNP initialization...]LOG]!><time="13:36:01.419+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="732" file="bootshell.cpp:60">
<![LOG[RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM]LOG]!><time="13:36:01.419+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="732"
file="configpath.cpp:302">
<![LOG[WinPE boot path: D:\SOURCES\BOOT.WIM]LOG]!><time="13:36:01.435+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="732" file="configpath.cpp:327">
<![LOG[Booted from removable device]LOG]!><time="13:36:01.435+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="732" file="configpath.cpp:357">
<![LOG[Found config path D:\]LOG]!><time="13:36:01.435+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="732" file="bootshell.cpp:548">
<![LOG[Booting from removable media, not restoring bootloaders on hard drive]LOG]!><time="13:36:01.435+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="732" file="bootshell.cpp:582">
<![LOG[D:\WinPE does not exist.]LOG]!><time="13:36:01.497+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="732" file="bootshell.cpp:599">
<![LOG[D:\_SmsTsWinPE\WinPE does not exist.]LOG]!><time="13:36:01.497+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="732" file="bootshell.cpp:613">
<![LOG[Executing command line: wpeinit.exe -winpe]LOG]!><time="13:36:01.497+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="732" file="bootshell.cpp:860">
<![LOG[Executing command line: X:\windows\system32\cmd.exe /k]LOG]!><time="13:36:02.935+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="728" file="bootshell.cpp:860">
<![LOG[The command completed successfully.]LOG]!><time="13:36:02.951+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="728" file="bootshell.cpp:942">
<![LOG[Successfully launched command shell.]LOG]!><time="13:36:02.951+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="728" file="bootshell.cpp:432">
<![LOG[The command completed successfully.]LOG]!><time="13:36:15.371+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="732" file="bootshell.cpp:942">
<![LOG[Starting DNS client service.]LOG]!><time="13:36:15.371+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="732" file="bootshell.cpp:666">
<![LOG[Executing command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:D:\]LOG]!><time="13:36:15.890+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="732"
file="bootshell.cpp:860">
<![LOG[The command completed successfully.]LOG]!><time="13:36:15.890+480" date="12-19-2014" component="TSBootShell" context="" type="1" thread="732" file="bootshell.cpp:942">
<![LOG[==============================[ TSMBootStrap.exe ]==============================]LOG]!><time="13:36:16.062+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212"
file="tsmbootstrap.cpp:1165">
<![LOG[Command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:D:\]LOG]!><time="13:36:16.062+480" date="12-19-2014" component="TSMBootstrap" context="" type="0" thread="1212"
file="tsmbootstrap.cpp:1166">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL']LOG]!><time="13:36:16.078+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="util.cpp:964">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\TSRESNLC.DLL']LOG]!><time="13:36:16.078+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="resourceutils.cpp:169">
<![LOG[Current OS version is 6.2.9200.0]LOG]!><time="13:36:16.078+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="util.cpp:3094">
<![LOG[Adding SMS bin folder "X:\sms\bin\i386" to the system environment PATH]LOG]!><time="13:36:16.094+480" date="12-19-2014" component="TSMBootstrap" context="" type="0" thread="1212"
file="tsmbootstrap.cpp:963">
<![LOG[Failed to open PXE registry key. Not a PXE boot.]LOG]!><time="13:36:16.094+480" date="12-19-2014" component="TSMBootstrap" context="" type="0" thread="1212" file="tsmbootstrap.cpp:844">
<![LOG[Media Root = D:\]LOG]!><time="13:36:16.094+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmbootstrap.cpp:1000">
<![LOG[WinPE boot type: 'Ramdisk:SourceIdentified']LOG]!><time="13:36:16.094+480" date="12-19-2014" component="TSMBootstrap" context="" type="0" thread="1212" file="tsmbootstrap.cpp:779">
<![LOG[Failed to find the source drive where WinPE was booted from]LOG]!><time="13:36:16.094+480" date="12-19-2014" component="TSMBootstrap" context="" type="2" thread="1212" file="tsmbootstrap.cpp:1036">
<![LOG[Executing from Media in WinPE]LOG]!><time="13:36:16.094+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmbootstrap.cpp:1041">
<![LOG[Verifying Media Layout.]LOG]!><time="13:36:16.094+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:1623">
<![LOG[MediaType = BootMedia]LOG]!><time="13:36:16.094+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:2607">
<![LOG[PasswordRequired = false]LOG]!><time="13:36:16.094+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:2633">
<![LOG[Found network adapter "Realtek PCIe GBE Family Controller" with IP Address X.X161.12.]LOG]!><time="13:36:16.109+480" date="12-19-2014" component="TSMBootstrap" context="" type="0"
thread="1212" file="tsmbootstraputil.cpp:517">
<![LOG[Running Wizard in Unattended mode]LOG]!><time="13:36:16.109+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:2803">
<![LOG[Loading Media Variables from "D:\sms\data\variables.dat"]LOG]!><time="13:36:16.109+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsremovablemedia.cpp:322">
<![LOG[no password for vars file]LOG]!><time="13:36:16.156+480" date="12-19-2014" component="TSMBootstrap" context="" type="0" thread="1212" file="tsmediawizardcontrol.cpp:247">
<![LOG[Entering TSMediaWizardControl::GetPolicy.]LOG]!><time="13:36:16.156+480" date="12-19-2014" component="TSMBootstrap" context="" type="0" thread="1212" file="tsmediawizardcontrol.cpp:527">
<![LOG[Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00']LOG]!><time="13:36:16.172+480"
date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="environmentscope.cpp:263">
<![LOG[Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}]LOG]!><time="13:36:16.172+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212"
file="environmentscope.cpp:623">
<![LOG[Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00']LOG]!><time="13:36:16.172+480"
date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="environmentscope.cpp:263">
<![LOG[Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}]LOG]!><time="13:36:16.172+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212"
file="environmentscope.cpp:623">
<![LOG[Setting LogMaxSize to 1000000]LOG]!><time="13:36:16.172+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:555">
<![LOG[Setting LogMaxHistory to 1]LOG]!><time="13:36:16.172+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:556">
<![LOG[Setting LogLevel to 0]LOG]!><time="13:36:16.172+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:557">
<![LOG[Setting LogEnabled to 1]LOG]!><time="13:36:16.172+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:558">
<![LOG[Setting LogDebug to 1]LOG]!><time="13:36:16.172+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:559">
<![LOG[UEFI: false]LOG]!><time="13:36:16.172+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:569">
<![LOG[Loading variables from the Task Sequencing Removable Media.]LOG]!><time="13:36:16.172+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:584">
<![LOG[Loading Media Variables from "D:\sms\data\variables.dat"]LOG]!><time="13:36:16.172+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsremovablemedia.cpp:322">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL']LOG]!><time="13:36:16.172+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="util.cpp:964">
<![LOG[Setting SMSTSLocationMPs TS environment variable]LOG]!><time="13:36:16.172+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSMediaGuid TS environment variable]LOG]!><time="13:36:16.172+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSBootMediaPackageID TS environment variable]LOG]!><time="13:36:16.172+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSBootMediaSourceVersion TS environment variable]LOG]!><time="13:36:16.172+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSBrandingTitle TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSCertSelection TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSCertStoreName TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSDiskLabel1 TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSHTTPPort TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSHTTPSPort TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSIISSSLState TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSMediaCreatedOnCAS TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSMediaPFX TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSMediaSetID TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSMediaType TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSPublicRootKey TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSRootCACerts TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSSiteCode TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSSiteSigningCertificate TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSStandAloneMedia TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSSupportUnknownMachines TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSTimezone TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSUseFirstCert TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSx64UnknownMachineGUID TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSx86UnknownMachineGUID TS environment variable]LOG]!><time="13:36:16.187+480" date="12-19-2014" component="TSMBootstrap" context="" type="1" thread="1212" file="tsmediawizardcontrol.cpp:604">
NSutton

Macbook & creating EFI bootable media

Similar Messages

Maybe you are looking for