• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Coexistence of UEFI and Legacy - Troubleshooting help

Scheduled Pinned Locked Moved Solved
Windows Problems
4
24
7.1k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T
    Taspharel
    last edited by Oct 13, 2017, 10:40 AM

    Okay, thanks.

    So, We have two DHCP Servers, one gets its settings from the other per replication. So both should have the identical settings.

    I’m refering to: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

    Our new DCs are Windows Server 2016.

    Screenshots from my dhcp server settings are in the same folder as before, the details for the other vendor classes are the same.

    I added Policies with a * in front of the vendor class because i hoped that would change something, it didnt work without those either though.

    1 Reply Last reply Reply Quote 0
    • T
      Taspharel
      last edited by Oct 17, 2017, 10:04 AM

      I am so so so sorry.

      Just came out of a call with our external IT partner and casually he said: Oh btw.: I deactivated your Policies on the DHCP server.

      And I didn’t notice of course … so sorry for wasting time, it works now. 😞

      G 1 Reply Last reply Oct 17, 2017, 10:22 AM Reply Quote 1
      • G
        george1421 Moderator @Taspharel
        last edited by Oct 17, 2017, 10:22 AM

        @taspharel No worries, its always good to know that neither of us are insane where you know what should be and we found what is according to wireshark.

        I assume they will reenable your policies? You kind of need them to support dynamic booting. Well that’s not totally true, if you can’t have the policies in your MS dhcp server you can run an external proxy dhcp to supply the missing pxe boot information. The point is there are other ways to achieve what you need.

        Can we close this issue?

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        1 Reply Last reply Reply Quote 0
        • T
          Taspharel
          last edited by Oct 17, 2017, 10:33 AM

          Already enabled and works like a charm. 🙂

          Can be closed, thx for helping out.

          1 Reply Last reply Reply Quote 1
          • 1
          • 2
          • 2 / 2
          2 / 2
          • First post
            21/24
            Last post

          193

          Online

          12.0k

          Users

          17.3k

          Topics

          155.2k

          Posts
          Copyright © 2012-2024 FOG Project