locked
PXE boot and install Linux option RRS feed

  • Question

  • Greetings,

      We have the standard IP Helper pointing to WDS on DPs for F12 OSD deployment.

       Someone wants to use F12 to boot  and install Linux as an option.

      1. Can a linux boot option be added in SCCM?

      2. If so, how?

    Thanks

    David Z

    Tuesday, July 7, 2020 1:08 AM

Answers

  • In an environment where there are multiple PXE servers, each PXE server will only reply to the clients that it cares about. In the case of SCCM, the SCCM PXE server only cares about its own clients and will only respond to those clients that have task sequence deployed to them.

    Each PXE server should have an entry in the IP helper tables. That way, all the PXE servers will get the client boot discovery and request, and only the PXE that needs to respond will respond.

    • Marked as answer by David Zemdegs Wednesday, July 8, 2020 1:23 AM
    Wednesday, July 8, 2020 12:52 AM

All replies

  • Hi,

    Thanks for posting in TechNet.

    Based on my experience, there is no built-in capability to deploy Linux to bare metal in SCCM. However, here are some workaround for your reference:

    SCCM 2012: Two ways to deploy Linux with SCCM :-)
    Deploy Linux OS with Microsoft System Center Configuration Manager 2012 SP1 White Paper
    OSD for Linux Imaging? Yes, really.

    Thanks for your time.

    Best regards,
    Simon

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, July 7, 2020 10:01 AM
  • I dont want to deploy Linux using Config Manager. I want to know if there is a way to redirect the PXE to another server that does the deployment. So when doing F12 you get a windows or Linux option. The windows options will continue with presenting the CM task sequences and the Linux option will redirect to another server.
    Tuesday, July 7, 2020 9:23 PM
  • In an environment where there are multiple PXE servers, each PXE server will only reply to the clients that it cares about. In the case of SCCM, the SCCM PXE server only cares about its own clients and will only respond to those clients that have task sequence deployed to them.

    Each PXE server should have an entry in the IP helper tables. That way, all the PXE servers will get the client boot discovery and request, and only the PXE that needs to respond will respond.

    • Marked as answer by David Zemdegs Wednesday, July 8, 2020 1:23 AM
    Wednesday, July 8, 2020 12:52 AM
  • Hi,

    Thanks Kerwin for the answer providing.It may help others who have similar issue. Here's a short summary for the problem.

    Problem/Symptom:
    ===================
    Is there a way to redirect the PXE to another server that does the deployment?

    Solution/Reason:
    ===================
    Each PXE server should have an entry in the IP helper tables. That way, all the PXE servers will get the client boot discovery and request, and only the PXE that needs to respond will respond.

    Thanks again for your time!

    Best regards,
    Simon

    "MECM" forum will be migrating to a new home on Microsoft Q&A!
    We invite you to post new questions in the "MECM" forum's new home on Microsoft Q&A!
    For more information, please refer to the sticky post. Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, August 18, 2020 9:35 AM