@Wayne-Workman What about crowdfunding? I would give some dollars for this.

@Wayne-Workman that means current ipxe7156.efi is a signed one?

Don’t forget to disable “Secure Boot” else the Surface won’t boot the fog kernel because of the missing signature.
https://www.youtube.com/watch?v=E47f7n8N4PA

@george1421 @Wayne-Workman @tom-elliott Is there a way to sign the fog kernel to match what the devices would expect from a secure boot kernel?
http://kroah.com/log/blog/2013/09/02/booting-a-self-signed-linux-kernel/

Let’s say this work i think we have to place our own keys into each device, that would would be the same pain (more pain) as just turning secure boot off. Isn’t there a way to use the embedded keys to sign our kernels?

The more i read about that it sounds complicated…

FYI all Surfaces are UEFI Class 3 devices, so no legacy boot. It was never there.

I already imaged Surface 4 Pro, i’ve used the port replicator to boot them:

Afai remember i used them in legacy mode (don’t had uefi images at that point) but it’s possible that the current firmware does not support legacy anymore but ipxe7156.efi should boot them anyway in uefi mode.

But you can also use the usb nic adapter that was available with surface 3 pro’s:

It also supports pxe boot but could be hard to purchase one.

Do you already have a golden syspreped image? If not i would recommend to finish one of them then sysprep it, image it and deploy to all the others. Beware that you should remove the nic’s mac from all the imaged devices associated with fog’s hosts if you use the same dock or usb nic to image them.

Regards X23

If the connections are to thin for gigabytes i would suggest to work with local storage nodes without replication if not mandatory necessary.

@rowebil @george1421 Have you ever tried ipxe7156.efi for your Acer System? I have to use this for HP X2’s or MS Surface’s since ipxe.efi will not boot them propperly in UEFI mode.

https://forums.fogproject.org/topic/9005/uefi-pxe-boot-how-to-do-it (don’t wonder i have used ipxe.efi there but this has changed to ipxe7156.efi)

FYI: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

FYI, i don’t know if the random mac stuff is the issue, i could not reach the notebook today user was already gone for the weekend, i will report next week.

@Tom-Elliott @Wayne-Workman the system is currently not in house so i cannot proof this.
I found the option: https://superuser.com/questions/1212736/random-hardware-addresses-in-windows-10-creators-update/1212749

I will check this if the system is reachable.

Regards X23

@Tom-Elliott no since this notebook has been deployed with our image this can’t be enabled, the only option could be the user itself. I’ve never heared about this where can this be enabled/disabled?

@Tom-Elliott @george1421 @Wayne-Workman It looks like the pending macs have stopped accouring since i uninstalled the fog client from the machine it4314, can someone identify something crude in installed software, ipconfig and or network nics? My post before with the Screenshots.

@Tom-Elliott Information about IT4314

ipconfig /all

Windows-IP-Konfiguration

   Hostname  . . . . . . . . . . . . : it4314
   Prim„res DNS-Suffix . . . . . . . : haan.local
   Knotentyp . . . . . . . . . . . . : Hybrid
   IP-Routing aktiviert  . . . . . . : Nein
   WINS-Proxy aktiviert  . . . . . . : Nein
   DNS-Suffixsuchliste . . . . . . . : haan.local
                                       carbolite.local

Ethernet-Adapter Ethernet:

   Verbindungsspezifisches DNS-Suffix: haan.local
   Beschreibung. . . . . . . . . . . : Intel(R) Ethernet Connection I219-LM
   Physische Adresse . . . . . . . . : 40-B0-34-11-A6-D2
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja
   Verbindungslokale IPv6-Adresse  . : fe80::6844:9327:ec81:4731%11(Bevorzugt) 
   IPv4-Adresse  . . . . . . . . . . : 172.19.101.150(Bevorzugt) 
   Subnetzmaske  . . . . . . . . . . : 255.255.252.0
   Lease erhalten. . . . . . . . . . : Donnerstag, 8. Juni 2017 13:20:03
   Lease l„uft ab. . . . . . . . . . : Freitag, 9. Juni 2017 13:20:03
   Standardgateway . . . . . . . . . : 172.19.100.1
   DHCP-Server . . . . . . . . . . . : 172.19.100.9
   DHCPv6-IAID . . . . . . . . . . . : 54571060
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-20-3C-5E-9A-40-B0-34-11-A6-D2
   DNS-Server  . . . . . . . . . . . : 172.19.100.9
                                       172.19.100.10
   NetBIOS ber TCP/IP . . . . . . . : Aktiviert

Drahtlos-LAN-Adapter LAN-Verbindung* 2:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix: 
   Beschreibung. . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physische Adresse . . . . . . . . : F4-8C-50-49-D1-AE
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Ethernet-Adapter Bluetooth-Netzwerkverbindung:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix: 
   Beschreibung. . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Physische Adresse . . . . . . . . : F4-8C-50-49-D1-B1
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter WLAN:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix: haan.local
   Beschreibung. . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 8260
   Physische Adresse . . . . . . . . : 72-3F-F5-26-FF-6C
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Installed Software:

Network devices in device manager:

@Tom-Elliott after chatting with tom we decided to remove the fog client from it4314, i also removed all the pending macs again. Now lets wait what happens.

@Tom-Elliott

172.19.101.150 - - [08/Jun/2017:13:18:25 +0200] "GET /fog/management/index.php?sub=requestClientInfo&mac=40:B0:34:11:A6:D2%7CF4:8C:50:49:D1:AE%7CF4:8C:50:49:D1:B1%7CD2:B1:A5:D6:12:7C&newService&json HTTP/1.1" 200 1705 "-" "-"
172.19.101.150 - - [08/Jun/2017:13:18:27 +0200] "GET /fog/service/usertracking.report.php?action=login&user=it4314%5Ccca&mac=40:B0:34:11:A6:D2%7CF4:8C:50:49:D1:AE%7CF4:8C:50:49:D1:B1%7CD2:B1:A5:D6:12:7C&newService&json HTTP/1.1" 200 583 "-" "-"
172.19.101.150 - - [08/Jun/2017:13:20:37 +0200] "GET /fog/management/index.php?sub=requestClientInfo&mac=40:B0:34:11:A6:D2%7CF4:8C:50:49:D1:AE%7CF4:8C:50:49:D1:B1%7CD2:B1:A5:D6:12:7C&newService&json HTTP/1.1" 200 1705 "-" "-"
172.19.101.150 - - [08/Jun/2017:13:23:08 +0200] "GET /fog/management/index.php?sub=requestClientInfo&mac=40:B0:34:11:A6:D2%7CF4:8C:50:49:D1:AE%7CF4:8C:50:49:D1:B1%7CD2:B1:A5:D6:12:7C&newService&json HTTP/1.1" 200 1705 "-" "-"
172.19.101.150 - - [08/Jun/2017:13:24:19 +0200] "GET /fog/management/index.php?sub=requestClientInfo&mac=40:B0:34:11:A6:D2%7CF4:8C:50:49:D1:AE%7CF4:8C:50:49:D1:B1%7CD2:B1:A5:D6:12:7C&newService&json HTTP/1.1" 200 1705 "-" "-"
172.19.101.150 - - [08/Jun/2017:13:26:44 +0200] "GET /fog/management/index.php?sub=requestClientInfo&mac=40:B0:34:11:A6:D2%7CF4:8C:50:49:D1:AE%7CF4:8C:50:49:D1:B1%7CD2:B1:A5:D6:12:7C&newService&json HTTP/1.1" 200 1705 "-" "-"

172.19.101.150 belongs to IT4314 hrhr

@Tom-Elliott sorry i really would do this but i am a little bit lost with it what should i do next? any help is appreciated.

@Tom-Elliott @Wayne-Workman the first pending mac is back

argh oh nooo

I cannot find this MAC Adress (d2:b1:a5:d6:12:7c) on any MAC Vendor list, this sounds to me like a virtual adapter too.
Would it be a good idea to also filter d2:b1:a5 without any research?

@Tom-Elliott ok i’ve shortened it to the first 3 octetts like you recommended. I’ve read the hint for the setting but i thougth filtering until mac change would be better, but i did what you told me

@Wayne-Workman i’ve done the following:

I will now delete all pending macs to see if they come back or not.

Regards X23

@Tom-Elliott @george1421 @Wayne-Workman i could get the desired info from most of the system i found with duplicate macs:

it3210: https://pastebin.com/NLU4uZjM
it3256: https://pastebin.com/4ek2esnT
it3286: https://pastebin.com/KnQ8PWZK
it3905: https://pastebin.com/BKREi3Fu
it4004: https://pastebin.com/v3kxZrk2
it4027: https://pastebin.com/sC01izYN
it4092: https://pastebin.com/v7p1SbZv

What i found out so far:

00:50:56:C0:00:01 VMWare
00:50:56:C0:00:08 VMWare
02:80:37:EC:02:00 WWAN Device (H5321) Ericsson
00:11:6B:66:3C:89 still unclear (Systems are currently not connectable)

Edit:

I could Check it3394 for the 00:11:6B:66:3C:89 mac but the system does not have any device with that mac associated so what should i do know? Set the both vmware macs oon the filter list and also add the wwan device?

My pending mac list ist getting fuller and fuller actually there are more then 300 pending macs from it4314, i need to get rid of this.

Regards X23

@Tom-Elliott sorry my bad!

this painful ubuntu s***