locked
looking for boot image issue - not seeing the new image. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Before I start.. YES, I did set "deploy this boot image from the pxe distribution point..." .

    What I am seeing is... If I change from an old boot image to a new one my clients keep looking for my previous boot image.

    I went to my old boot image and remove the "deploy this boot image...." 

    I went to my new boot image and ticked the "deploy this boot image..."

    In "Data Access" I set copy the contents of this package..."

    I did not create a custom package name..

    In "Distribution settings" I set "Distribute the contents for this package to preferred..."

    I then restarted WDS service..

    I checked the RemoteInstall folder : D:\RemoteInstall\SMSImages\HEF00235\ and the WIM file is present: boot.HEF00235.wim

    If I check the smspxe.log file I see:

    00:15:5D:02:69:4A, 4F62BAB0-EFDA-4B44-BAB9-1D499A800697: could not find boot image HEF001C8	SMSPXE	11-05-2015 09:07:50	8228 (0x2024)00:15:5D:02:69:4A, 4F62BAB0-EFDA-4B44-BAB9-1D499A800697: Not serviced.	SMSPXE	11-05-2015 09:07:50	8228 (0x2024)


    Kindest regards, Martin

    Monday, May 11, 2015 7:08 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    ahhh so its defaulting to your old x86 boot image because its on the DP alongside your newer x64 boot image and probably tied to the original time that you first deployed the TS. Try deleting the Task Sequence deployment and then re-deploy it. This should tell it to boot up using your x64 boot image by default instead of the x86 boot image (as its the last Task Sequence that has been advertised/deployed that determines the default boot image)

    http://www.windows-noob.com/forums/index.php?/topic/8570-change-default-pxe-boot-image/

    hopefully this is the problem.

    Cheers

    Damon





    • Edited by Damon. Johns Monday, May 11, 2015 10:56 AM
    • Proposed as answer by Joyce L Wednesday, May 20, 2015 6:58 AM
    • Marked as answer by Joyce L Friday, May 22, 2015 3:12 AM
    Monday, May 11, 2015 10:53 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    ok, so far I tried many things.. but right before I left for the day, I created a copy of my TS and deployed it to a collection and booted a machine that was a member af that collection..

    now it's using the new boot image.... so yay.

    I will definetely be testing more tomorrow.. I only tried this on a Virtual machine and the real test will of course be in our production environment. 

    The reason I am even looking at bootimages is that I want to consolidate our driver/boot image system into only having to consider x64bit drivers etc. 

    I'll definetely look into the links you guys posted to see if I can find more information.. 

    will report back here tomorrow.

    Kindest regards, Martin

    • Proposed as answer by Joyce L Wednesday, May 20, 2015 6:57 AM
    • Marked as answer by Joyce L Friday, May 22, 2015 3:12 AM
    Monday, May 11, 2015 5:08 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    ack.. here's the log stuff in readable.. cannot find a code tag that looks better..:

    00:15:5D:02:69:4A, 4F62BAB0-EFDA-4B44-BAB9-1D499A800697: could not find boot image HEF001C8 SMSPXE 11-05-2015 09:07:50 8228 (0x2024)
    00:15:5D:02:69:4A, 4F62BAB0-EFDA-4B44-BAB9-1D499A800697: Not serviced. SMSPXE 11-05-2015 09:07:50 8228 (0x2024)


    Any ideas what I am missing?

    Kindest regards, Martin

    Monday, May 11, 2015 7:10 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    oh, and when I switch back to HEF001C8, then it boots fine again..

    So somewhere something isn't being updated..

    Kindest regards, Martin

    Monday, May 11, 2015 7:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Did you change the boot image that the Task Sequence is using? Right click on your TS and choose properties (from memory) and then select the boot image that you want that TS to use.

    Cheers

    Damon


    Monday, May 11, 2015 7:50 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    yes I did.. 

    I have checked everything I can think of :-)

    Kindest regards, Martin

    Monday, May 11, 2015 8:49 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Is there still at least one x86 and one x64 boot image available on the pxe-enabled DP?

    Torsten Meringer | http://www.mssccmfaq.de

    Monday, May 11, 2015 9:12 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    hi torsten.

    No Only a 64 bit.. 

    The old bootimage was x86 and the new one is x64..

    I'llt try (while awaiting further wisdom) adding the old x86 alongside the new x86..

    but I suspect that it'll just select the x86 boot image... 

    Since we're only deploying x64 OS I'd like to use an x64 boot image.. it's easy to forget that any driver I want to add to the boot image must be x86 even though I'm deploying x64 machines... 

    Kindest regards, Martin

    Monday, May 11, 2015 9:21 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    as I suspected... having both x86 & x64 boot image set to "deploy this boot image from the PXE-enabled...." and having selected the x64 boot image in my TS.. it still selects the old x86 boot image...

    Kindest regards, Martin

    Monday, May 11, 2015 9:25 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Regardless of what OS architecture your deploying - you should still have both an x86 and an x64 boot image distributed to your PXE enabled DP (Just one of each). Then set your Task Sequence to use your x64 boot image.

    Have you done this, it sounds like you have but I was a bit confused when you said that you were going to add your old x86 boot image alongside your new x86 boot image?

    Cheers

    Damon





    Monday, May 11, 2015 9:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    ok.. just to clarify..

    I have a working x86 boot image.. 

    I wish to change that to a working x64.

    I created a x64 boot image.

    They're now both deployed to the DP and both are set to "deploy this boot image from the PXE.." etc.

    In my TS I've selected the new boot image. 

    Both boot images have identical settings.

    When I pxe I see pxe boot downloads smsboot/x64/pxeboot.com

    Then it startes loading files : SMSimages/hef001c8/winpe.hef001c8.wim

    This is the old bootimage.

    I see im SMSimages a folder for the new boot image and inside I find 1 file: boot.HEF00235.wim

    which is the new x64 boot image that I want to use.  

    Kindest regards, Martin

    Monday, May 11, 2015 9:48 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    That's really odd - its almost like your hitting a different PXE enabled DP with your old boot image still sitting on it - the fact that its actually transferring your old boot image via PXE would indicate that its still sitting on a DP somewhere...

    Have you verified that you don't have your old boot image on any DP's and that your new boot images are distributed to all of your DP's? Is it possible that your workstation is talking to a different DP? Are you using IP Helpers or DHCP Scope options to tell your workstation where your WDS server is? Maybe verify were those are pointing to and again verify that you don't have your old boot image present.

    Maybe others can suggest some more ideas here?



    Monday, May 11, 2015 10:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    before I answer Damon's questions I just want to add a little extra..

    So.. I thought I'd let the tasksequence actually run even though it's still using the old boot image..

    here's what happened..


    I select my TS and click continue.. 

    it resolves selected TS dependencies

    ==

    and the following part I've never seen before:

    It downloads the Windows preinstallation environments and in the process downloads the x64 boot image..

    it then tells me that I can now remove the CD and not boot from CD afterwards.

    When I click "Finish" it boots up on my new x64 boot image and then fails with errorcode: 0x0000000D

    ==

    perhaps this is just showing because I've specified a different boot image than the one it is using in PXE.. but it's curious..

    Kindest regards, Martin

    Monday, May 11, 2015 10:24 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Do you see both boot images in \RemoteInstall\SMSImages?

    Torsten Meringer | http://www.mssccmfaq.de

    Monday, May 11, 2015 10:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    Just to verify; you do not have any other Deployment targeting the computer object which you attempt to PXE boot?

    I am not 100% sure, since I do not have a PXE server available, but I believe that you should be able to see the Deployment ID in the log file.

    If a computer object has more than one Deployments targeted, it will automatically attempt to boot using boot image with the most recent time stamp (date modified).

    As previously pointed out; even if you have changed the boot image to a x64 image, both the x64 and x86 boot image needs to be available on the Distribution Point.

    David Gustafsson

    Monday, May 11, 2015 10:37 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Some info relating to David's post.

    http://gerryhampsoncm.blogspot.co.uk/2013/03/sccm-pxe-boot-which-boot-image.html

    Monday, May 11, 2015 10:44 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    ahhh so its defaulting to your old x86 boot image because its on the DP alongside your newer x64 boot image and probably tied to the original time that you first deployed the TS. Try deleting the Task Sequence deployment and then re-deploy it. This should tell it to boot up using your x64 boot image by default instead of the x86 boot image (as its the last Task Sequence that has been advertised/deployed that determines the default boot image)

    http://www.windows-noob.com/forums/index.php?/topic/8570-change-default-pxe-boot-image/

    hopefully this is the problem.

    Cheers

    Damon





    • Edited by Damon. Johns Monday, May 11, 2015 10:56 AM
    • Proposed as answer by Joyce L Wednesday, May 20, 2015 6:58 AM
    • Marked as answer by Joyce L Friday, May 22, 2015 3:12 AM
    Monday, May 11, 2015 10:53 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    ok, so far I tried many things.. but right before I left for the day, I created a copy of my TS and deployed it to a collection and booted a machine that was a member af that collection..

    now it's using the new boot image.... so yay.

    I will definetely be testing more tomorrow.. I only tried this on a Virtual machine and the real test will of course be in our production environment. 

    The reason I am even looking at bootimages is that I want to consolidate our driver/boot image system into only having to consider x64bit drivers etc. 

    I'll definetely look into the links you guys posted to see if I can find more information.. 

    will report back here tomorrow.

    Kindest regards, Martin

    • Proposed as answer by Joyce L Wednesday, May 20, 2015 6:57 AM
    • Marked as answer by Joyce L Friday, May 22, 2015 3:12 AM
    Monday, May 11, 2015 5:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yeah, sounds like you have/had a more recent deployment of a task sequence that still references the x86 boot image.  Creating the new deployment like you stated above would now use the x64 boot image.  As Damon stated, if you have 2 TS's with different boot images, the client will use the boot image assigned to the most recently deployed TS.  This is likely the reason you were being instructed to reboot after the x64 image was staged.

    This is all of course assuming you have more than 1 task sequence at play here..

    Monday, May 11, 2015 9:47 PM