SCCMTSPSI
SCCMTSPSI

I start my virtual machine but it does not find any boot image!!!

  • Topaz George

    Organizer
    31 July 2020 at 11:32 am

    Are you using boot USB medium or pxe?Is you virtual machine a Legacy BIOS or advanced UEFI system?
    Did you download the winpe from https://sccmtspsi.com/sccmtspsi-downloads/?section=winpe-boot-images
    have you checked boot device priority?
    What hypervisor are you using?

    • This reply was modified 4 years, 7 months ago by  Topaz George.
    • This reply was modified 4 years, 7 months ago by  Topaz George.

    sccmtspsi-downloads

    • Roddy Gelberty

      Member
      31 July 2020 at 10:06 pm

      Hi George,

      No, I am not using a USB, I am using pxe and a UEFI vm.

      Yes, I downloaded the winpe from that link. But I am using a sccm 2002 version and I have tried both versions in the end I have updated the one I downloaded but did not work.

      Yes I did check the boot device priority and it is ok, network first.

      I am using Microsoft Hyper-V.

      About the TS I just followed the steps of one in doc configuration setup.

  • Roddy Gelberty

    Member
    31 July 2020 at 11:31 pm

    I’d like to get some clarity on your current situation. Is the below statement true?
    “You cannot PXE boot” on your Hyper-V virtual machine
    If the above statement is true proceed with the following questions.

    • Have you been able to PXE boot into another boot image on the virtual machine or is it the first time you are trying PXE boot.
    • Have you tried PXE booting into a normal physical desktop or a laptop.

    Reason for the above questions : Setting up PXE boot on hyper-v is a bit complex. You have to create a virtual switch and use a Legacy network adapter. You can find some instructions here https://www.danielengberg.com/start-pxe-over-ipv4-hyper-v-machine/
    Also, please confirm the ADK version installed on your SCCM server.

    • Roddy Gelberty

      Member
      31 July 2020 at 11:41 pm

      Hi Stella,
      This is true. But I can boot from other boot image and my pxe is working fine! Only if I use the TS like the one from your document configuration or the winpe 1903 that it does not work.
      Just for your information I am using a UEFI vm.

  • Roddy Gelberty

    Member
    31 July 2020 at 11:52 pm

    How far do you get up to because I’ve just tried it on a vmware workstation and I do not seem to have any issues.
    When you PXE boot what exactly is the error message? Please upload a screenshot of your pxe screen.
    PS : I can get someone to ZOOM or TEAMS you if need be next week to get you through the initial steps. But lets see if we can get this going for your folks via text first.

    • Roddy Gelberty

      Member
      4 August 2020 at 7:33 am

      Hi Stella,
      After follow all your recommendation this is what is in my screen!

  • Topaz George

    Organizer
    1 August 2020 at 12:15 am

    Hermenegildo, Can you also please check the following?
    Check if both x86 and amd64 version of the PXEboot image is available on your PXE enabled distribution points. Remove other unnecessary boot images from the DP’s
    Check if at the least one of your task sequences has the ‘sccmtspi PXE image’ attached to it and it is deployed as ‘available‘ to the UNKNOWN SYSTEMS collection in addition to the Realm deployment collection (as described in the documentation). See the attached image.

    sccmtspsi-boot-image-setup-for-pxe

  • Roddy Gelberty

    Member
    1 August 2020 at 9:32 pm

    Sorry Boss, I’ve got a better way of doing this :-).
    Its always better to assign an empty Task Sequence to the “All UNKNOWN COMPUTERS” collection for security reasons. But again, this is only required for PXE booting; USB and other boot methods do not require this deployment to the “All UNKNOWN COMPUTERS” collection.
    New devices that are not known to SCCM via PXE are made aware of what Boot image to download by using this boot image assigned to the empty Task Sequence.
    See attached image.

  • Topaz George

    Organizer
    3 August 2020 at 9:12 pm

    Thank you, Rajesh. Hermenegildo, can you please check if the above-mentioned deployment of an “empty” task sequence with the sccmtspsi boot image helps you resolve the ‘boot image not found’ issue.

    • Roddy Gelberty

      Member
      4 August 2020 at 8:04 am

      My wimpe image version is 2002. I think this the problem because your image version is 1903.

  • Roddy Gelberty

    Member
    4 August 2020 at 2:01 pm

    @MikeGimi, We’ve now uploaded the 2004 WinPE version to our website. https://sccmtspsi.com/sccmtspsi-downloads/?section=winpe-boot-images

    Please give that a go and verify if your issue gets resolved. There is no public release for WinPE 2002 of ADK.

    But the screenshot that you affixed to your previous message, leads me to believe that the error is related to clearing the required PXE deployment flag.

    Right-click on the machine in SCCM, and then choose “Clear Required PXE Deployments“. [See image]

    Few things to verify (If you have not done so already).

    The version of Windows 10 Assessment and Deployment Kit installed on your SCCM server should be 10.1.19041.1.

    DO NOT tick the box to “Reload the boot image with the current Windows PE version from the Windows ADK” (Image attached).

    For PXE boot of new devices (as discussed before), deploy an empty task sequence with the sccmtspsi boot image to the “ALL UNKNOWN COMPUTERS” collection.

    sccmtspsi-downloads

    • Roddy Gelberty

      Member
      4 August 2020 at 8:08 pm

      Hi Rajesh,
      Thank you very much for your help. I will try as you recommended and reply to you as soon as possible.
      Regards

    • Roddy Gelberty

      Member
      11 August 2020 at 7:08 am

    • Roddy Gelberty

      Member
      11 August 2020 at 7:19 am

      Hi Rajesh,
      Finally a solve the problems thank you very much.
      But now I am finding problems to log in to my sccmtspsi machine because it is giving me an error ERR106.5 regarding to email account!!!

Log in to reply.

Start of Discussion
0 of 0 replies June 2018
Now