We're starting to enable Intel's vPro / AMT through BIOS on our computers using SMB mode and hitting port 16992 using the host name as URL. Our problem is that we have to use the same host name and it's running over the same NIC. Therefore, Spiceworks detects the machine as a second entity and has trouble authenticating. I have no way of distinguishing between the two "machines" therefore I can't categorize this as AMT. Is there anything I can do? Ideally I'd like Spiceworks to merge the two entries; maybe I need to create a new user account through vPro that matches the account used in scans for the Windows system on top?

That makes perfect sense. We have been scanning entire network ranges using all three choices (Windows, SSH, and SNMP) because we figured it was better to try to detect what is on each IP, whether it's a Mac or PC or router.

I guess I can split the scopes up and pull SNMP off the segment that is issued through DHCP, as these will likely be PCs and Macs. Then that range can just use Windows and SSH. Hopefully any future AMT support in Spiceworks does not conflict with this strategy.

Thanks Scott, another great idea! Long story short, the DHCP range includes a diverse mixture of devices and since I want to grab as much as possible, I'm forced to cast a wide net until / unless they change topology.

But, you prompted me to rethink the solution: I was able to go to http://<PC host name>:16992 - which is the AMT management page - and under "Network Settings" I was able to change the "Computer Host Name" to something OTHER than the PC host name. I decided to use its asset tag.

So now I still pick it up as a separate device, but it doesn't have the same host name, and therefore does not confuse Spiceworks when looking for my computer's name in reports.

Thanks so much-- I truly appreciate the prompt responses and ideas.

0

This discussion has been inactive for over a year.

You may get a better answer to your question by starting a new discussion.