1

I’ve tried everything I can find to get Spiceworks to scan our first Windows 10 PC and it won’t. I’ve tried the following things:

  1. Turn on File and Print Sharing.
  2. Ran the Spiceworks Unknown Assistant tool.
  3. Edited the registry using this command: netsh advfirewall firewall set rule group=“windows management instrumentation (WMI)” new enable=Yes
  4. I’ve adjusted the Firewall Settings to open the ports Spiceworks suggested.

This system is part of the domain. I’ve tried so many things that I’m sure I forgot to list some of them. It shouldn’t be this difficult to scan this PC. What needs to be done to scan it?

5 Spice ups
2

Windows 10 will scan fine, if UAC is enabled, run the reg file in the client machines

This WMI will also help

Run a Command Prompt as Administrator on the machine that is failing, and enter / paste the following (without quotes):

“netsh advfirewall firewall set rule group=“windows management instrumentation (WMI)” new enable=Yes”

Spiceworks_UAC_remote_allow.reg (167 Bytes)

3

I already found your post about this on a previous thread and they didn’t work.

4

Unless you have IDS/IPS or a third party firewall in the way this should be all that is needed.

What does SW see on a scan for a machine that has Windows 10?

If you add a single device to scan by itself and scan it, what happens?

5

I don’t have any IDS/IPS or third party firewalls. Spiceworks sees the Windows 10 PC as a Windows 10 device and picks up the name, IP address, and MAC address. It’s the only Windows 10 PC it’s scanning. I get the same results if I run a scheduled scan, scan just that IP address, or use the rescan option. It appears to get past the credentials part of the scan so I don’t think this is a credentials issue.

6

Scrap this thread! For some unknown reason the next scheduled scan picked up the PC. Don’t ask me how, because I have no clue.

7

Mark a best answer (even your own to mark the thread as complete)