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

    BIOS and UEFI Coexistence HP 850 G3 i219v nic

    Scheduled Pinned Locked Moved
    Hardware Compatibility
    3
    13
    4.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.
    • george1421G
      george1421 Moderator
      last edited by

      OK so now what I would do is see if you can identify the hardware by the uuid value? For example a surface pro 3 has a uuid of xxxx, pro 4 yyyy, hp (whatever) zzz. Once you have that, looking at the fog wiki page you should be able to create additional test conditions like with the arch 7, 9, whatever. And then combine them into a new policy like in step 6. That new policy may be arch7 and uuid xxxx == file name aaa (sorry about all of the abstractions but I don’t have a solid answer just yet). It seems logically like it should work.

      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!

      PsycholiquidP 1 Reply Last reply Reply Quote 0
      • PsycholiquidP
        Psycholiquid Testers @george1421
        last edited by

        @george1421 said in BIOS and UEFI Coexistence HP 850 G3 i219v nic:

        OK so now what I would do is see if you can identify the hardware by the uuid value? For example a surface pro 3 has a uuid of xxxx, pro 4 yyyy, hp (whatever) zzz. Once you have that, looking at the fog wiki page you should be able to create additional test conditions like with the arch 7, 9, whatever. And then combine them into a new policy like in step 6. That new policy may be arch7 and uuid xxxx == file name aaa (sorry about all of the abstractions but I don’t have a solid answer just yet). It seems logically like it should work.

        Sounds like a plan I will work it out and post back with what I find out, with pictures!!! I love pictures. LOL

        Wayne WorkmanW 1 Reply Last reply Reply Quote 1
        • Wayne WorkmanW
          Wayne Workman @Psycholiquid
          last edited by

          @psycholiquid My goal when I wrote that article was just to show people how create DHCP vendor classes and policies using Windows and Linux because at the time of writing there was about zero good documentation anywhere on the Internet for this stuff. The article was more of an educational one giving the tools & knowledge needed to create whatever vendor classes and policies needed.

          Ofcourse we can change it to be better, or add notes, or additional sections, or whatever needs done.

          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!
          Daily Clean Installation Results:
          https://fogtesting.fogproject.us/
          FOG Reporting:
          https://fog-external-reporting-results.fogproject.us/

          1 Reply Last reply Reply Quote 1
          • PsycholiquidP
            Psycholiquid Testers
            last edited by

            WEll snooping two different Surfaces I was able to get the following information"

            Surface one UUID = 598FDD98-C837-7A56-48E6-130AE625101C

            Surface two UUID = C3D3C87F-5BAB-FB24-5F25-D0FB46014244

            So it doesn’t look like we can use that as a Condition. Not real sure what they are doing there but it looks totally different and could just be built off of a few factors of the hardware to generate that UUID.

            @Wayne-Workman I didnt mean to convey it was wrong. I learned alot from the article. Just wanted to get it updated with more info. I think you did a great job when you wrote that as there was zero information I could find when I was working on the first UEFI stuff. You are the man!!!

            1 Reply Last reply Reply Quote 1
            • PsycholiquidP
              Psycholiquid Testers
              last edited by Wayne Workman

              So here is the whole snoop to see if we can glean some info out of it.

              Surface:
              
              Frame 1510: 401 bytes on wire (3208 bits), 401 bytes captured (3208 bits) on interface 0
              Ethernet II, Src: Cisco_5e:53:17 (00:a3:8e:5e:53:17), Dst: Vmware_bb:44:5b (00:50:56:bb:44:5b)
              Internet Protocol Version 4, Src: 10.20.42.3, Dst: 10.20.60.8
              User Datagram Protocol, Src Port: 67, Dst Port: 67
              Bootstrap Protocol (Request)
                  Message type: Boot Request (1)
                  Hardware type: Ethernet (0x01)
                  Hardware address length: 6
                  Hops: 1
                  Transaction ID: 0x3697a7aa
                  Seconds elapsed: 0
                  Bootp flags: 0x8000, Broadcast flag (Broadcast)
                  Client IP address: 0.0.0.0
                  Your (client) IP address: 0.0.0.0
                  Next server IP address: 0.0.0.0
                  Relay agent IP address: 10.20.42.3
                  Client MAC address: Microsof_f5:44:71 (bc:83:85:f5:44:71)
                  Client hardware address padding: 00000000000000000000
                  Server host name not given
                  Boot file name not given
                  Magic cookie: DHCP
                  Option: (53) DHCP Message Type (Request)
                      Length: 1
                      DHCP: Request (3)
                  Option: (54) DHCP Server Identifier
                      Length: 4
                      DHCP Server Identifier: 10.20.60.22
                  Option: (50) Requested IP Address
                      Length: 4
                      Requested IP Address: 10.20.42.134
                  Option: (57) Maximum DHCP Message Size
                      Length: 2
                      Maximum DHCP Message Size: 65280
                  Option: (55) Parameter Request List
                      Length: 35
                      Parameter Request List Item: (1) Subnet Mask
                      Parameter Request List Item: (2) Time Offset
                      Parameter Request List Item: (3) Router
                      Parameter Request List Item: (4) Time Server
                      Parameter Request List Item: (5) Name Server
                      Parameter Request List Item: (6) Domain Name Server
                      Parameter Request List Item: (12) Host Name
                      Parameter Request List Item: (13) Boot File Size
                      Parameter Request List Item: (15) Domain Name
                      Parameter Request List Item: (17) Root Path
                      Parameter Request List Item: (18) Extensions Path
                      Parameter Request List Item: (22) Maximum Datagram Reassembly Size
                      Parameter Request List Item: (23) Default IP Time-to-Live
                      Parameter Request List Item: (28) Broadcast Address
                      Parameter Request List Item: (40) Network Information Service Domain
                      Parameter Request List Item: (41) Network Information Service Servers
                      Parameter Request List Item: (42) Network Time Protocol Servers
                      Parameter Request List Item: (43) Vendor-Specific Information
                      Parameter Request List Item: (50) Requested IP Address
                      Parameter Request List Item: (51) IP Address Lease Time
                      Parameter Request List Item: (54) DHCP Server Identifier
                      Parameter Request List Item: (58) Renewal Time Value
                      Parameter Request List Item: (59) Rebinding Time Value
                      Parameter Request List Item: (60) Vendor class identifier
                      Parameter Request List Item: (66) TFTP Server Name
                      Parameter Request List Item: (67) Bootfile name
                      Parameter Request List Item: (97) UUID/GUID-based Client Identifier
                      Parameter Request List Item: (128) DOCSIS full security server IP [TODO]
                      Parameter Request List Item: (129) PXE - undefined (vendor specific)
                      Parameter Request List Item: (130) PXE - undefined (vendor specific)
                      Parameter Request List Item: (131) PXE - undefined (vendor specific)
                      Parameter Request List Item: (132) PXE - undefined (vendor specific)
                      Parameter Request List Item: (133) PXE - undefined (vendor specific)
                      Parameter Request List Item: (134) PXE - undefined (vendor specific)
                      Parameter Request List Item: (135) PXE - undefined (vendor specific)
                  Option: (97) UUID/GUID-based Client Identifier
                      Length: 17
                      Client Identifier (UUID): c3d3c87f-5bab-fb24-5f25-d0fb46014244
                  Option: (94) Client Network Device Interface
                      Length: 3
                      Major Version: 3
                      Minor Version: 16
                  Option: (93) Client System Architecture
                      Length: 2
                      Client System Architecture: EFI BC (7)
                  Option: (60) Vendor class identifier
                      Length: 32
                      Vendor class identifier: PXEClient:Arch:00007:UNDI:003016
                  Option: (255) End
                      Option End: 255
              
              1 Reply Last reply Reply Quote 0
              • PsycholiquidP
                Psycholiquid Testers
                last edited by

                OK ok ok , I am an idiot… (go ahead take the stab)

                So i forgot I have load balanced / failover DHCP in my environment. SO even if the fog server is set to one DHCP server it will still be pushed to the other in case of high utilization… (damn it me!!!)

                So I was able to get it working more granular down to the UNDI. With what @george1421 said this could be a problem later but I am thinking it will be fine for now as the versions will probably only go up from here for change dramatically. So here is the setup for clairity.

                DHCP (Windows Server 2012 R2) 'Failover is on your to configure"

                Set Vendor Class for hardware. (You can get this from Wireshark easily if you run it on the DHCP server and set ip.src == IP of client PC)

                0_1505318117679_7305fbf0-ae76-4da1-8848-d8f36aac2e67-image.png

                0_1505318135541_5df67178-312e-446d-8876-365dec696ecd-image.png

                Cant really copy and paste but here you go anyway: PXEClient:Arch:00007:UNDI:003016

                Then goto Policies for either your whole server or for your scope depending on how your network is setup:

                0_1505318223359_6ec6bee1-4a87-4ba9-9ff3-8e4395d15943-image.png

                Make a new Policy, name it and description.

                0_1505318268209_38d4eeaa-c33f-47eb-a73f-cd3a14e46828-image.png

                Add Condition:

                0_1505318294038_1dc1da12-9f99-40f6-9ea3-e248139451de-image.png

                Set Options:

                0_1505318315735_34d229ac-2354-4264-baae-7c60ae97519b-image.png

                Now if you refresh your Scope Options you will see the new options:

                0_1505318379964_4bedc421-ecf5-4d45-b897-17f9d78841fc-image.png

                I have tested and this works specifically for the Surface Pro 4s with the dock. I am not sure about the dongle yet because I don’t have one.But I will see about getting one.

                1 Reply Last reply Reply Quote 2
                • george1421G
                  george1421 Moderator
                  last edited by

                  First of all, great job on the documentation. The more we know and share the more we ALL will know.

                  Second I looked into the MS dhcp server and it doesn’t look like (on the surface) we can use uuid to set a policy event.

                  I did think of 2 alternates that might work.

                  1. Use the mac address to help identify the client. The first 6 bytes of a mac address is the nic vendor manufacturer number. We can key in on that element when creating a dhcp policy.
                  2. Give up on MS Dhcp server delivering pxe boot information to your network and use dnsmasq on the FOG server. DNSMasq will be configured to only provide pxe booting information only. IF the fog server goes off line for some reason, there is no harm since the clients will just bypassing pxe booting. A current version of dnsmasq (2.76) supports the advanced stuff you are wanting to try.

                  These are only 2 alternate ways I can think of to give you the answer you seek. You DO have a functional solution right now so just keep these ideas in the back of your mind.

                  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!

                  PsycholiquidP 1 Reply Last reply Reply Quote 0
                  • PsycholiquidP
                    Psycholiquid Testers @george1421
                    last edited by

                    @george1421 Yeah I am not versed in DNSmasq but it sounds like I need to be I will start looking at that also

                    george1421G 1 Reply Last reply Reply Quote 0
                    • george1421G
                      george1421 Moderator @Psycholiquid
                      last edited by

                      @psycholiquid Just search the tutorials forum I have a few posts out there about dnsmasq.

                      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
                      • Wayne WorkmanW
                        Wayne Workman
                        last edited by

                        #wiki worthy

                        @Psycholiquid thank you for the pictures and steps! I will get them included into the wiki when I can. @moderators and @testers if you have wiki access, you can help too!

                        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!
                        Daily Clean Installation Results:
                        https://fogtesting.fogproject.us/
                        FOG Reporting:
                        https://fog-external-reporting-results.fogproject.us/

                        1 Reply Last reply Reply Quote 1
                        • 1 / 1
                        • First post
                          Last post

                        197

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright © 2012-2024 FOG Project