Nodes Added via Network Sonar are showing up as Hyper-V but they are not Hyper-V

I have 7 nodes that when they get added to Solarwinds they are added as Hyper-V nodes. But they are not Hyper-V nodes but regular Windows Servers.

Not sure why.

Network Discovery is not configured to check for VMWare or Hyper-V

If I go to one of the nodes, List Resources, uncheck Hyper-V the next morning the nodes are reporting as Hyper-V

These nodes are all different OS and located in different domains. I have setup Network Discovery per domain so each of them are in different Network Discovery jobs.

I disabled Hyper-V polling under the virtualization tab.

Anyone run into this before?

Thanks,

Dave

Find more posts tagged with

network discovery

Hyper-V

Accepted answers

All comments

martian_monster

I answered my own question lol. I checked the nodes and they have Hyper-V services enabled. Now to figure out who or why they did it.

marcrobinson

Yeah - i have run into that. There was a short conversation about who left the services enabled. Happy Hunting! (This turned out to be a good thing as everyone forgot to disable those services.) If no one admits - you can always play the cyber security/risk card and offer to call them to sort it out. That may get a panicked but useful response.

iltejadilla

I think you're correct because of the Hyper-V services but is it on-prem or via VM?