Set a fullscreen Boot image

Hi,
I know that I can change the boot image by simply replacing the file BootLogo.png into another one with the image I want to appear at the startup screen.
But I want this image to be fullscreen size, and I cannot do that, as I don't know where or how to configure it.
So, how do I set a boot image as fullscreen?

Something funny is happening here!
Before testing something (I'll say later) I would say the things below:
>>
Maybe I haven't expressed myself properly.
I don't want to change the login background picture, I want to change the boot picture (the gray apple that appears at the startup, when you turn on your mac) and its size.
That gray apple file (BootLogo.png) is located at the same place as the DefaultDesktop.jpg file is. See image below.
The point is that I don't know how to change the boot picture size (to fullscreen, for example).
<<
But just after writing all that, I've thought that this file (BootLogo.png) could habe been created by BootXChanger. So then, I opened that program and set the boot image to the default (the gray apple), deleted that .png file and restarted the computer.
I noticed that the original gray apple appeared at the startup (boot) screen without troubles and that the BootLogo.png file hadn't been restored (as if the OS did not need that file).
After that, I opened the BootXChanger.app to change the boot image again and the BootLogo.png file reappeared.
So, now, I have 2 questions:
- the original one; how do I set a fullscreen boot image?
- and; if the BootLogo.png file doesn't exist, how do I change the boot image without having BootXChanger?

Similar Messages

  • Set PXE boot image

    I'm having a problem similar to what's described at https://social.technet.microsoft.com/Forums/en-US/1398dc34-1672-4336-92fc-5cb72de031d5/locking-selected-pxe-boot-image?forum=configmanagerosd
    We are running SCCM 2012 R2 (upgraded from SP1) We have a 64 bit and and a 32 bit boot image. The 64 bit has "Deploy this boot image from the PXE-enabled distribution point" unchecked. The 32 bit image is checked. Clients are still trying to boot
    64 bit. We had using the 32 bit image for months (before and after R2 upgrade) I was making changes to the 64 bit image and suddenly it decided it was the PXE boot image. How can I get SCCM to go back the the 32bit boot.wim?
    Here's what I've tried:
    1) Right click 32 bit boot wim and update distribution points
    2) Deploy a new TS that is set to use the 32 bit boot.wim.
    3) Reboot the SCCM server (we have a single server, single distribution point)
    What else can we do to get back to a working state with PXE boot?

    In addition to the other comments, 1 and 3 are effectively meaningless in this context.
    #2 will work per Jorgen's and Doug's comments -- this comes down to the fact that if there is any ambiguity as to which boot image should be used (usually because the system has multiple possible task sequences targeted to it that have different boot images),
    then the boot image associated with the task sequence having a deployment with the highest ID is used; i.e., the boot image for the most recently deployed TS (as Doug stated also).
    Because you've already seemingly addressed this, it sounds like you may have simply switched the boot image associated with the TS on accident and you should verify this first.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • Setting up an Image Server and Selecting boot Images

    I am setting up my first image server and when i perform a network boot I can see that i am reaching the DHCP server but i dont i am not getting a boot image.  I have configured the server with an install image and a boot image but still getting nothing. 
    Can someone please help a novice set up this server.

    If this is for ConfigMgr enter the following in your DHCP 
    Option 066 - the FQDN of your SCCM server.
    Option 067 - the path smsboot\x86\wdsnbp.com 
    Cheers
    Paul | sccmentor.wordpress.com

  • 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.

  • 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)>

  • 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.

  • MDT 2012 Update 1 Boot Image Creation Fails in SP1

    I have my site server (SCCM 2012 SP1) installed on Server 2012 with the Windows 8 ADK installed (I've also tried installing the Win7 WAIK with no change to the below problem). It is hosting the site server, FSP, AIS, and Endpoint protection roles. I
    installed MDT 2012 Update 1 (build 6.1.2373.0) and installed ConfigMgr integration. I have a share
    \\siteserver\bootimages that I'm creating the boot image to and the system account has full control on both the NTFS and Share permissions. When I create the boot image I get an error almost immediately and
    a popup that the Microsoft.BDD.ElevatedProxy has stopped working. Details from the pop-up:
    Description:
      Stopped working
    Problem signature:
      Problem Event Name: CLR20r3
      Problem Signature 01: microsoft.bdd.elevatedproxy.exe
      Problem Signature 02: 3.0.0.0
      Problem Signature 03: 50400c36
      Problem Signature 04: System.ServiceModel
      Problem Signature 05: 3.0.0.0
      Problem Signature 06: 4fee6b19
      Problem Signature 07: fb9
      Problem Signature 08: a7
      Problem Signature 09: G3DT0URDW53KGT4VJDEEQCRAUIFCNTLL
      OS Version: 6.2.9200.2.0.0.272.7
      Locale ID: 1033
    The error in the boot image creation wizard is:
    Started processing.
    Creating boot image.
    Error while importing Microsoft Deployment Toolkit Task Sequence.
    System.ServiceModel.FaultException: The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug>
    configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.
    Server stack trace:
       at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
       at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
    Exception rethrown at [0]:
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at INewBootImage.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
       at NewBootImageClient.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
       at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)
    I haven't found anything online on this particular error, I've seen all the ones about MDT 2012 and ConfigMgr 2012 CU 1. Any ideas? Any logs that may be revealing to the cause of this error? I've tried removing integration components, uninstalling MDT, reboot,
    re-installing, etc, but same problem occurs each time.

    I just tried to create a new boot image again, the DISM.log file does not show any evidence of the attempt to create the boot wim, in fact nothing since 0800 this morning. The most recent logs are as follows:
    2013-03-03 20:22:59, Info                  DISM   PID=2252 TID=4312 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-03-03 20:22:59, Info                  DISM   PID=2252 TID=4312 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=4312 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 Deleted g_internalDismSession - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 Shutdown SessionTable - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 Leave DismShutdownInternal - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Enter DismInitializeInternal - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Initialized GlobalConfig - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Initialized SessionTable - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
    2013-03-03 22:02:51, Info                  DISM   API: PID=3544 TID=3672 Waiting for m_pInternalThread to start - CCommandThread::Start
    2013-03-03 22:02:51, Info                  DISM   API: PID=3544 TID=4172 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=4172 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 m_pInternalThread started - CCommandThread::Start
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 Created g_internalDismSession - DismInitializeInternal
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 Leave DismInitializeInternal - DismInitializeInternal
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 Enter DismShutdownInternal - DismShutdownInternal
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=4172 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=4172 Successfully dequeued command object - CCommandThread::DequeueCommandObject
    2013-03-03 22:03:59, Info                  DISM   API: PID=3544 TID=4172 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
    2013-03-03 22:03:59, Info                  DISM   API: PID=3544 TID=4172 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-03 22:04:39, Info                  DISM   PID=3544 TID=4172 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
    2013-03-03 22:04:39, Info                  DISM   PID=3544 TID=4172 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-03-03 22:04:39, Info                  DISM   PID=3544 TID=4172 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=4172 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 Deleted g_internalDismSession - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 Shutdown SessionTable - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 Leave DismShutdownInternal - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Enter DismInitializeInternal - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Initialized GlobalConfig - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Initialized SessionTable - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
    2013-03-04 08:41:08, Info                  DISM   API: PID=1016 TID=1620 Waiting for m_pInternalThread to start - CCommandThread::Start
    2013-03-04 08:41:08, Info                  DISM   API: PID=1016 TID=4176 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=4176 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 m_pInternalThread started - CCommandThread::Start
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 Created g_internalDismSession - DismInitializeInternal
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 Leave DismInitializeInternal - DismInitializeInternal
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 Enter DismShutdownInternal - DismShutdownInternal
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 Successfully dequeued command object - CCommandThread::DequeueCommandObject
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-04 08:42:44, Info                  DISM   PID=1016 TID=4176 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
    2013-03-04 08:42:44, Info                  DISM   PID=1016 TID=4176 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-03-04 08:42:44, Info                  DISM   PID=1016 TID=4176 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=4176 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 Deleted g_internalDismSession - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 Shutdown SessionTable - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 Leave DismShutdownInternal - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-05 08:44:10, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 Enter DismInitializeInternal - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 Initialized GlobalConfig - DismInitializeInternal
    2013-03-05 08:44:13, Info                  DISM   API: PID=4140 TID=3140 Initialized SessionTable - DismInitializeInternal
    2013-03-05 08:44:13, Info                  DISM   API: PID=4140 TID=3140 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
    2013-03-05 08:44:14, Info                  DISM   API: PID=4140 TID=3140 Waiting for m_pInternalThread to start - CCommandThread::Start
    2013-03-05 08:44:14, Info                  DISM   API: PID=4140 TID=640 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 m_pInternalThread started - CCommandThread::Start
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 Created g_internalDismSession - DismInitializeInternal
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 Leave DismInitializeInternal - DismInitializeInternal
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=640 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 Enter DismShutdownInternal - DismShutdownInternal
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 Successfully dequeued command object - CCommandThread::DequeueCommandObject
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-05 08:46:18, Info                  DISM   PID=4140 TID=640 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
    2013-03-05 08:46:18, Info                  DISM   PID=4140 TID=640 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-03-05 08:46:18, Info                  DISM   PID=4140 TID=640 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=640 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 Deleted g_internalDismSession - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 Shutdown SessionTable - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 Leave DismShutdownInternal - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 DismApi.dll:                       

  • Netboot : boot image - default user settings

    Hello
    So far I have successfully created from installation DVDs a netboot boot image and customized/modified it so that I can use it for all users created on the MacOSX Server.
    Now for some details I was not able to resolve them. I can not persistently set some computer preferences/settings assigned to the administrator like timezone, ntp-server etc. on the client.
    Also I have noticed, that after booting from the netboot image, the client has for the login window an US keyboard layout but should have in our case a swiss-german layout, because otherwise our users can not enter correctly their login passwords, especially if they use some some special characters in their passwords. Is there any way to set this this on the netboot image or in the clients nvram ?
    Many thanks in advance, André Müller

    /System/Library/User Template is where all of these are stored. You will have enable the root login account and log in to it in order to make changes to that folder with the GUI.
    Changing anything in the System folder is always a bit unreliable, though. Apple might release a software update that will undo any of the changes.
    If you really are managing 850+ Macs, you should look into getting OS X Server. OS X Server has the tools you need to set up custom templates for new users, without having to muck in the System folder.

  • WDS - No boot image

    Good afternoon,
    Hoping that one of you gurus will be able to help save my sanity here. :)
    Background: We used RIS for quite a while, but after the SP2 update it failed so we decommisioned it. Now, WDS is on a Server 2008 R2 box and joined to the in the domain. While not an actual DHCP server, it is authorized in AD as a DHCP server. The DHCP
    server is on a different server (running Solaris) on the same subnet. I have created images and have been able to do captures and remote installations.
    Issue: The WDS server and the PXE clients work perfectly if they are both connected to a workgroup/soho type switch (5 port Linksys/DLink/etc). However if they are both plugged into the wall (the 'real' network) they do not work at all...the PXE client just
    spins waiting for an address before returning that it couldn't locate a boot image. This is true even if I put both the WDS server and the PXE client on the same subnet.
    I have ran packet captures on both working and non-working scenarios. In the non-working scenario with both machines on the same subnet the server's NIC can see the network traffic, but does not respond to it. When they are both on the workgroup switch it
    does respond to it. I have checked the routers for this subnet and there is an ip address helper configured to match the IP of the WDS server. However, if they are both on the same subnet then they are in the same broadcast domain and really that shouldn't
    matter...but it is there and configured because eventually the WDS server will move to a different subnet than the PXE clients.
    So I am curious, does anyone have any ideas as to why WDS would work flawlessly on a little workgroup switch, but not on the corporate network even when on the same subnet, in the same room, on the same wallplate, running to the same switch?
    I appreciate any and all advice, tips, tricks, insights that anyone could provide. :)
    -Joe

    Hi Joe,
    Can I ask if you've configured the DHCP options required on your Solaris DHCP Server?
    A snippet from the WDS deployment guide
    http://technet.microsoft.com/en-us/library/cc766320(WS.10).aspx
    "Add DHCP options 66 and 67. Option 66 should be set to the Windows Deployment Services server, and option 67 should be set to boot\x86\wdsnbp.com."

  • Update Boot Image Issues

    Environment:  SCCM 2012 SP1 CU3
    Issue:  errors when trying to update distribution points (Driver Additions)
    Error Message:
      Error: Boot image to update:
    • Microsoft Windows PE (x64)
      Error: Actions to perform:
    • Add ConfigMgr binaries
    • Disable Windows PE command line support
    • Add drivers
      Error: Failed to import the following drivers:
    • Intel(R) Ethernet Connection I217-LM
    • Broadcom NetLink (TM) Gigabit Ethernet
    • 3Com Dual Port 1000-SX PCI-X Server NIC
    • Realtek PCI GBE Family Controller
    • LAN7500 USB 2.0 to Ethernet 10/100/1000 Adapter
    • Intel(R) 82579LM Gigabit Network Connection
    • Intel(R) 82575EB Gigabit Network Connection
    • Intel(R) 82580 Gigabit Network Connection
    • Intel(R) 82599 Multi-Function Network Device
    • DELL PERC RAID Virtual Device
    • PERC H310 for Dell Precision
    • LSI MegaRAID Virtual Device
    • Intel(R) C600 series chipset SATA AHCI Controller
    • Intel(R) C600/C220 series chipset SATA RAID Controller
    • Intel(R) C600 Series Chipset SAS RAID Controller
    • Intel(R) 5 Series 4 Port SATA AHCI Controller
    • Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller
    • System Management Device
    • System Management Device
    • LSI SAS x28 Expander
    • LSI Adapter, SAS2 2116 Meteor ROC(E)
    • Intel(R) ICH9M-E/M SATA AHCI Controller
    • Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller
     Optional components:
    • Scripting (WinPE-Scripting)
    • Startup (WinPE-SecureStartup)
    • Network (WinPE-WDS-Tools)
    • Scripting (WinPE-WMI)
      Error: The wizard detected the following problems when updating the boot image.
    • Failed to inject a ConfigMgr driver into the mounted WIM file
    The SMS Provider reported an error.: ConfigMgr Error Object:
    instance of SMS_ExtendedStatus
    • Description = "Failed to insert OSD binaries into the WIM file";
    • ErrorCode = 2152205056;
    • File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
    • Line = 4630;
    • ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
    • Operation = "ExecMethod";
    • ParameterInfo = "SMS_BootImagePackage.PackageID=\"PS100081\"";
    • ProviderName = "WinMgmt";
    • StatusCode = 2147749889;
    Anyone have any idea's why the WIM file will not update?  I have been trying to get a Dell 7440 to boot properly so I can image it but the problem is:  PXE loads fine but when the system starts to load the SCCM deployment piece it just restarts. 
    I have not found any errors during this portion and did not see anything in the SCCM logs.  Assumed it had to do with the drivers but now I am unsure.
    Thanks,
    JAK
    EDIT:  on a side note, I have re-created the boot images and removed and re-added drivers still same issues.

    SMSPROV.log
    CExtUserContext::EnterThread : User=**** Sid=0x0105000000000005150000002EA925CE2D54C0A5946DF1F931320000 Caching IWbemContextPtr=00000000050CF1A0 in Process 0xe60 (3680) SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: SMSAppName=Configuration Manager Administrator console SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: MachineName=****.**** SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: UserName=**** SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: ObjectLockContext=501335b7-4817-4296-9032-30a05bb53be6 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: ApplicationName=Microsoft.ConfigurationManagement.exe SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: ApplicationVersion=5.0.7804.1400 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: LocaleID=MS\0x409 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: ReturnAll=1 (Bool) SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: FolderTypeName=SMS_BootImagePackage SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: QueryQualifiers=1 (Bool) SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: InstanceCount=1001 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: __ProviderArchitecture=32 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: __RequiredArchitecture=0 (Bool) SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: __ClientPreferredLanguages=en-US,en SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: __GroupOperationId=10280 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    CExtUserContext : Set ThreadLocaleID OK to: 1033 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    CSspClassManager::PreCallAction, dbname=CM_PS1 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    ExecQueryAsync: START SELECT * FROM SMS_BootImagePackage WHERE ActionInProgress!=3 ORDER BY Name SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Adding Handle 45277256 to async call map SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    CExtProviderClassObject::DoCreateInstanceEnumAsync (SMS_Query) SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    CSspQueryForObject :: Execute... SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Execute WQL  =SELECT * FROM SMS_BootImagePackage WHERE ActionInProgress!=3 ORDER BY Name SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Execute SQL =select  all SMS_BootImagePackage.PkgID,SMS_BootImagePackage.Action,SMS_BootImagePackage.Architecture,SMS_BootImagePackage.DefaultImage,SMS_BootImagePackage.Description,SMS_BootImagePackage.DisconnectDelay,SMS_BootImagePackage.UseForcedDisconnect,SMS_BootImagePackage.ForcedRetryDelay,SMS_BootImagePackage.Icon,SMS_BootImagePackage.IgnoreSchedule,SMS_BootImagePackage.ImagePath,SMS_BootImagePackage.IsVersionCompatible,SMS_BootImagePackage.Language,SMS_BootImagePackage.LastRefresh,SMS_BootImagePackage.Manufacturer,SMS_BootImagePackage.MIFFilename,SMS_BootImagePackage.MIFName,SMS_BootImagePackage.MIFPublisher,SMS_BootImagePackage.MIFVersion,SMS_BootImagePackage.Name,SMS_BootImagePackage.NumOfPrograms,SMS_BootImagePackage.PkgID,SMS_BootImagePackage.PackageType,SMS_BootImagePackage.PkgFlags,SMS_BootImagePackage.StorePkgFlag,SMS_BootImagePackage.Source,SMS_BootImagePackage.PreferredAddress,SMS_BootImagePackage.Priority,SMS_BootImagePackage.SedoObjectVersion,SMS_BootImagePackage.ShareName,SMS_BootImagePackage.ShareType,SMS_BootImagePackage.SourceDate,SMS_BootImagePackage.SourceSite,SMS_BootImagePackage.SourceVersion,SMS_BootImagePackage.StoredPkgPath,SMS_BootImagePackage.StoredPkgVersion,SMS_BootImagePackage.TransformAnalysisDate,SMS_BootImagePackage.TransformReadiness,SMS_BootImagePackage.Version
    from vSMS_BootImagePackage_List AS SMS_BootImagePackage  where (SMS_BootImagePackage.PkgID not  in (select  all Folder##Alias##810314.InstanceKey from vFolderMembers AS Folder##Alias##810314  where Folder##Alias##810314.ObjectTypeName =
    N'SMS_BootImagePackage') AND SMS_BootImagePackage.Action <> 3) order by SMS_BootImagePackage.Name SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Results returned : 0 of 0 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Removing Handle 45277256 from async call map SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    ExecQueryAsync: COMPLETE SELECT * FROM SMS_BootImagePackage WHERE ActionInProgress!=3 ORDER BY Name SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    CExtUserContext::LeaveThread : Releasing IWbemContextPtr=84734368 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CExtUserContext::EnterThread : User=**** Sid=0x0105000000000005150000002EA925CE2D54C0A5946DF1F931320000 Caching IWbemContextPtr=00000000050CF0C0 in Process 0xe60 (3680) SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: SMSAppName=Configuration Manager Administrator console SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: MachineName=****.**** SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: UserName=**** SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: ObjectLockContext=501335b7-4817-4296-9032-30a05bb53be6 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: ApplicationName=Microsoft.ConfigurationManagement.exe SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: ApplicationVersion=5.0.7804.1400 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: LocaleID=MS\0x409 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __ProviderArchitecture=32 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __RequiredArchitecture=0 (Bool) SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __ClientPreferredLanguages=en-US,en SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __GroupOperationId=10290 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __WBEM_CLIENT_AUTHENTICATION_LEVEL=6 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CExtUserContext : Set ThreadLocaleID OK to: 1033 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CSspClassManager::PreCallAction, dbname=CM_PS1 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    ExecMethodAsync : SMS_BootImagePackage::GetImageProperties SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Requested class =SMS_BootImagePackage SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Requested num keys =0 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CExtProviderClassObject::DoExecuteMethod GetImageProperties SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    *~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspimagepackage.cpp(586) : Failed to get the image property from the source WIM file due to error 80070002~*~* SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    *~*~Failed to get the image property from the source WIM file due to error 80070002 ~*~* SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CExtUserContext::LeaveThread : Releasing IWbemContextPtr=84734144 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CExtUserContext::EnterThread : User=**** Sid=0x0105000000000005150000002EA925CE2D54C0A5946DF1F931320000 Caching IWbemContextPtr=00000000050CF0C0 in Process 0xe60 (3680) SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: SMSAppName=Configuration Manager Administrator console SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: MachineName=****.**** SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: UserName=**** SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: ObjectLockContext=501335b7-4817-4296-9032-30a05bb53be6 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: ApplicationName=Microsoft.ConfigurationManagement.exe SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: ApplicationVersion=5.0.7804.1400 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: LocaleID=MS\0x409 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __ProviderArchitecture=32 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __RequiredArchitecture=0 (Bool) SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __ClientPreferredLanguages=en-US,en SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __GroupOperationId=10295 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __WBEM_CLIENT_AUTHENTICATION_LEVEL=6 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CExtUserContext : Set ThreadLocaleID OK to: 1033 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CSspClassManager::PreCallAction, dbname=CM_PS1 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    ExecMethodAsync : SMS_BootImagePackage::GetImageProperties SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Requested class =SMS_BootImagePackage SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Requested num keys =0 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CExtProviderClassObject::DoExecuteMethod GetImageProperties SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    *~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspimagepackage.cpp(586) : Failed to get the image property from the source WIM file due to error 80070002~*~* SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    *~*~Failed to get the image property from the source WIM file due to error 80070002 ~*~* SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CExtUserContext::LeaveThread : Releasing IWbemContextPtr=84734144 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    JAK

  • Failed to Create MDT Boot Image in SCCM 2007

    Hello Everyone,
    I am trying to create MDT Integrated Boot Image in SCCM to Enable DART Integration on it. But when i try to Create Boot Image it Fails with below Error Message.
    Started processing.
    Creating boot image.
    Copying WIM file.
    Mounting WIM file.
    WIM file mounted.
    Setting Windows PE system root.
    Set Windows PE system root.
    Set Windows PE scratch space.
    Adding standard components.
    Adding extra content from: C:\Users\ADMINI~1\AppData\Local\Temp\1\i5wqsynb.efm
    Unmounting WIM.
    Copying WIM to the package source directory.
    Creating boot image package.
    Error while importing Microsoft Deployment Toolkit Task Sequence.
    Failed to insert OSD binaries into the WIM file
    Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The ConfigMgr Provider reported an error.
    ---> System.Management.ManagementException: Generic failure
    at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
    at System.Management.ManagementObject.Put(PutOptions options)
    at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
    --- End of inner exception stack trace ---
    at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
    I have searched over Internet for the same Error and I guess it was a Permission Issue. But my Environment is as below.
    AD & SCCM Server on Same Machine
    Folder have Full Permissions to SYSTEM, SCCMComputerAccount, DomainAdministrators, and Even I gave to Everyone Full
    Control.
    This is a LAB Environment with No Antivirus, No UAC
    ANY HELP ON THIS Folks..... (:-()
    Ram

    Hi Ychinnari,
    As your question is related to SCCM report. it is not supported here.
    you could post it in SCCM forum for better supports, Thanks for your understanding.
    SCCM forum link:
    https://social.technet.microsoft.com/Forums/systemcenter/en-US/home?category=configurationmanager
    Best regards,
    Youjun Tang
    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.
    Click
    HERE to participate the survey.

  • SCCM 2012 R2 Boot Image won't load in Windows XP

    I'm using ADK 8.1, MDT 2013, x86 Boot image w/ PE 5. Deployed a TS to Windows XP SP3 computer with a single task: Reboot Computer to PE
    Getting this: Executing command line: "C:_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR TSManager 10/31/2013 9:49:27 AM 3000 (0x0BB8)
    Failed to install boot image. is not a valid Win32 application. (Error: 800700C1; Source: Windows)
    More detailed smsts.log below:
    <![LOG[Captured settings for adapter 1]LOG]!><time="09:33:52.197+420" date="10-31-2013" component="OSDNetSettings" context="" type="1" thread="5368" file="netsettings.cpp:99">
    <![LOG[OSDNetSettings finished: 0x00000000]LOG]!><time="09:33:52.197+420" date="10-31-2013" component="OSDNetSettings" context="" type="1" thread="5368" file="main.cpp:192">
    <![LOG[Process completed with exit code 0]LOG]!><time="09:33:52.307+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="commandline.cpp:1123">
    <![LOG[Installing boot image to hard drive]LOG]!><time="09:33:52.353+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootimage.cpp:621">
    <![LOG[Backing up existing boot system before trying to set up new boot system]LOG]!><time="09:33:52.353+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856"
    file="bootimage.cpp:644">
    <![LOG[BootLoader::backup: C:\, C:\_SMSTaskSequence\backup]LOG]!><time="09:33:53.213+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootloader.cpp:85">
    <![LOG[BootLoader::restore: C:\_SMSTaskSequence\WinPE, C:\]LOG]!><time="09:33:54.479+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootloader.cpp:382">
    <![LOG[Saving bcd store to C:\_SMSTaskSequence\WinPE\boot\BCD]LOG]!><time="09:33:57.057+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootconfigimplbcd.cpp:703">
    <![LOG[Executing command line: "C:\_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR]LOG]!><time="09:33:57.166+420" date="10-31-2013" component="TSManager" context="" type="1"
    thread="4856" file="commandline.cpp:827">
    <![LOG[CreateProcess failed. Code(0x800700C1)]LOG]!><time="09:33:57.182+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="commandline.cpp:1018">
    <![LOG[Command line execution failed (800700C1)]LOG]!><time="09:33:57.182+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="commandline.cpp:1245">
    <![LOG[Failed to install boot image. 
     is not a valid Win32 application. (Error: 800700C1; Source: Windows)]LOG]!><time="09:33:57.182+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="bootimage.cpp:681">
    <![LOG[Failed to install boot image UCI00073. 
     is not a valid Win32 application. (Error: 800700C1; Source: Windows)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:840">
    <![LOG[Failed to reboot the system. Error 0x(800700c1)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:953">
    <![LOG[Failed to initialize a system reboot. 
     is not a valid Win32 application. (Error: 800700C1; Source: Windows)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:577">
    <![LOG[Fatal error is returned in check for reboot request of the action (Restart in Windows PE). 
     is not a valid Win32 application. (Error: 800700C1; Source: Windows)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:273">
    <![LOG[An error (0x800700c1) is encountered in execution of the task sequence]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:348">
    <![LOG[Set authenticator in transport]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="0" thread="4856" file="libsmsmessaging.cpp:7734">
    <![LOG[Task Sequence Engine failed! Code: 800700C1]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="tsmanager.cpp:919">
    <![LOG[****************************************************************************]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856"
    file="tsmanager.cpp:953">
    <![LOG[Task sequence execution failed with error code 800700C1]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="tsmanager.cpp:954">
    <![LOG[Cleaning Up.]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="tsmanager.cpp:675">
    <![LOG[Removing Authenticator]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="tsmanager.cpp:686">

    See the "Workaround" section of this post for an example of downgrading bootsect.exe:
    http://social.technet.microsoft.com/Forums/en-US/6e934990-999a-4367-860a-3ce4e5eda956/sccm-2012-r2-error-0x800700c1?forum=configmanagerosd
    It is not the version of WinPE that is the problem here, but the version of bootsect.exe that gets injected into the boot media.
    Nash Pherson, Senior Systems Consultant
    Now Micro -
    My Blog Posts
    <-- If this post was helpful, please click "Vote as Helpful".
    This workaround worked in my environment.  Fixed my in-place upgrades from XP to Windows 7, and as a bonus, fixed imaging XP as well. yeah, I have to keep XP for awhile. :-(

  • Unable to find a volume that is suitable for staging the boot image.

    I have an SCCM 2012 OSD task sequence that is failing when it tries to stage the boot image to the drive before rebooting.  The log file shows:
    Staging boot image CET00028 TSManager 6/5/2014 3:57:58 PM 1492 (0x05D4)
    Mounting \Device\HarddiskVolume6 at Z: TSManager 6/5/2014 3:57:58 PM 1492 (0x05D4)
    Unmounting volume Z:\ TSManager 6/5/2014 3:57:58 PM 1492 (0x05D4)
    Checking to see if the data path is on a bootable volume TSManager 6/5/2014 3:57:59 PM 1492 (0x05D4)
    Volume C:\ because it is not suitable as the system partition TSManager 6/5/2014 3:57:59 PM 1492 (0x05D4)
    Searching for a volume to stage the boot image TSManager 6/5/2014 3:57:59 PM 1492 (0x05D4)
    Volume S:\ is not NTFS TSManager 6/5/2014 3:57:59 PM 1492 (0x05D4)
    Volume C:\ because it is not suitable as the system partition TSManager 6/5/2014 3:57:59 PM 1492 (0x05D4)
    Volume R:\ is not on a fixed disk TSManager 6/5/2014 3:57:59 PM 1492 (0x05D4)
    Volume X:\ is not on a fixed disk TSManager 6/5/2014 3:57:59 PM 1492 (0x05D4)
    BootImage::FindBootableVolume( NULL, sPath), HRESULT=80070490 (e:\qfe\nts\sms\framework\tscore\bootimage.cpp,1045) TSManager 6/5/2014 3:57:59 PM 1492 (0x05D4)
    Unable to find a volume that is suitable for staging the boot image.
    Element not found. (Error: 80070490; Source: Windows) TSManager 6/5/2014 3:57:59 PM 1492 (0x05D4)
    I've seen others get this error code and fix it by injecting the correct storage drivers.  In my case I believe I have the correct storage drivers.  In a separate MDT 2013/WDS environment I can deploy
    8.1 to the same machine using the same drivers with no problems so my drivers appear to allow proper access to the drive.  When I check the volumes with DiskPart they all appear to be fine.  The C:\ volume has the _SMSTaskSequence folder on it with
    files so it is certainly writable.  The system is set for UEFI mode.  Of course if I change it to Legacy mode this problem doesn't happen.  I have also integrated MDT 2013 into SCCM console and both an SCCM task sequend and an MDT task sequence
    do the same thing. Any ideas?
    Thanks,

    From the error, the C could not be the staging location because it is system partition. You need to format a fixed drive to NTFS partition and try again.
    Juke Chou
    TechNet Community Support

  • 64-bit Boot Image Drivers Are Not Working

    I've been deploying Windows 7 x86 and x64 for years. I've been using the same 32-bit boot image for both and it's been working great.
    We've decided to take the plunge and go all x64 moving forward.  I want to switch to a 64-bit boot image so I don't have to curate the drivers for two architectures.
    I've created a 64-bit boot image, and included all of the 64-bit versions of the drivers in my 32-bit boot image, but they don't seem to be working.  I've tried booting 3 different models, but I receive "Failed to find a valid network adapter."
    I've looked within the boot image, because I wanted to see the driver files.  Either I just don't know where I'm looking, or they're in the "Files" folder where each file is renamed to a number.
    What might I have done wrong?

    I've solved my problem by downloading and importing the Dell WinPE driver pack.  Now I've just got to add the USB 3.0 drivers (I support laptops that don't have optical drives), and I'll be set.

Maybe you are looking for

  • How can I tell what control the modulation wheel is assigned to?

    Hello, I understand how to reassign the Mod Wheel and other controls with Command-L. However, once I deleted my learned assignments I realized that the modulation wheel had not been working as it should with the thousands of other presets. Apparently

  • Error when using Movement type 561 both in MIGO and MB1C

    I am getting the following error when performing movement type 561 Check table 003M: entry DB   does not exist I am using IDES system and learning SAP MM my self... i googled ans searched for this error and couldnt find a solution so please help me..

  • FRM-92101 Blob in Record Type

    Hi! I have a package in db with a record type and a procedure: type timage is record ( name varchar2(255), format varchar2(4), dpi number, content blob procedure get_image(my_image_var out timage) is begin select tblob into my_image_var.content from

  • How do i turn off the feature that browses album art work in landscape view?

    How do I turn off the feature that browses album art work in landscape view?  My videos will not play full screen since I updated my phone to iOS 7.1.

  • Mac puts itself into Safe Boot.

    I don't touch the keyboard (I tried unplugging it) but suddenly my imac g4 17" boots in safe mode. Any suggestions? thank you alan