Configuration Manager Client notification channel 1 Pc with multiple NICS

Question

HI,

What I am trying to achieve:
I am trying to achieve Wake-On-Lan via Configuration Manager using 'Client notification channel' from one Hyper-V machine which has multiple network interface cards.

My understanding:
I understand that for Client notifications to work a PC must be awake, have the client installed and be on the same VLAN.

Our setup:
We have 7 sites with around 8 VLANs per. Wake on Lan works providing I meet the criteria i outline above (1 pc online with the client and on the target VLAN)

Example:

Server (Primary site)
Virtual machine (Win 10, with Config manager client installed)
Target Machine (Win 10, physical on VLAN 2)

Test 1:
So, if I set the VM to have only 1 network interface card and specify it's VLAN as 2 this will wake the Target machine perfectly.

Test 2:
If I set the VM to have 2 network interface cards (VLAN 1 being the first card and VLAN 2 being the second card) and I attempt to wake the target PC this is unsuccessful. I had a trace running with Wireshark and I didn't see anything.

Config manager console is aware of a client having multiple subnets, as you can right click the properties of a client within the console and see all the different IPs and Subnets it's associated with. My assumption from the VM not finding any wake on LAN packets from the trace leads to the console not being intelligent enough to check what other interfaces are available on a client.

So is anyone aware of a change that can be made to Config manager so I could in theory use 1 Virtual machine per site with a network interface card per VLAN to wake all the required machines up.