Thanks to some smart folks, some one pointed me in the right direction to get the 2.0 Agents from the bin folder from the source files... 
Having said that... I may have stumbled across a bug in the Agents and the net.if.discovery...
In several of my servers, we use built in NICs... In one particular server, I have those two NICs connected to separate vlans, et al.
the net.if.discovery picks up the nics in the system, but it returns the second nic to be the same as the first...
returns:
typeperf -qx returns these values as
Broadcom NetXtreme Gigabit Ethernet
and Broadcom NetXtreme Gigabit Ethernet#1
(OS is Windows Server 2003 SP2, 32 bit)
Is this a known issue or should I file a bug (and where do I file it) ?
See Yas!
Brant

Having said that... I may have stumbled across a bug in the Agents and the net.if.discovery...
In several of my servers, we use built in NICs... In one particular server, I have those two NICs connected to separate vlans, et al.
the net.if.discovery picks up the nics in the system, but it returns the second nic to be the same as the first...
Code:
#zabbix_get -s myserver -k net.if.in.discovery
Code:
{
"data":[
{
"{#IFNAME}":"Broadcom NetXtreme Gigabit Ethernet"},
{
"{#IFNAME}":"Broadcom NetXtreme Gigabit Ethernet"},
{
"{#IFNAME}":"MS TCP Loopback interface"}]}
Broadcom NetXtreme Gigabit Ethernet
and Broadcom NetXtreme Gigabit Ethernet#1
(OS is Windows Server 2003 SP2, 32 bit)
Is this a known issue or should I file a bug (and where do I file it) ?
See Yas!
Brant
Comment