Just wanted to inform you that I posted a feature request regarding this template here: https://support.zabbix.com/browse/ZBXNEXT-2765
The original discussion leading to the feature request is documented here: https://www.zabbix.com/forum/zabbix-...already-exists
In brief: The default template relies on Win32_NetworkAdapter, which under certain conditions fails to distinguish {#IFNAME} when the only difference is something like "ifName" vs. "ifName #2" vs. "ifName #3" (possibly in combination with Hyper-V Virtual Switch). Zabbix relies upon the fact, that {#IFNAME} is unique - which is not the case in my setup, when using Win32_NetworkAdapter.
The original discussion leading to the feature request is documented here: https://www.zabbix.com/forum/zabbix-...already-exists
In brief: The default template relies on Win32_NetworkAdapter, which under certain conditions fails to distinguish {#IFNAME} when the only difference is something like "ifName" vs. "ifName #2" vs. "ifName #3" (possibly in combination with Hyper-V Virtual Switch). Zabbix relies upon the fact, that {#IFNAME} is unique - which is not the case in my setup, when using Win32_NetworkAdapter.
Comment