1

So the network i am trying to scan has a bunch of standalone Windows 10 PCs. Spiceworks is saying it cant scan them. It asks for a WMI username and password. Are these the local account username and password? I tried one but it still couldnt scan. Can Spiceworks handle this scenario or do these PCs need to be added to a domain? Not my network, just monitoring so not sure to what extent i can change.

1 Spice up
2

It’s probably that dreaded Windows 10 firewall.

3

Spiceworks can handle them fine, assuming the right ports are open on the clients.

File and printer sharing needs to be enabled on them for a start.

1 Spice up
4

Use a Local Admin accounts credentials to scan them. To make it easier make the account name and password the same on each computer then you can use .\scanadmin and the password to scan them all, instead of COMPUTERNAME\scanadmin for each computer.

Also take a look at the Unknown Assistant, it will update the settings that you need to scan them for you. https://community.spiceworks.com/help/Spiceworks_Unknowns_Tool

1 Spice up
5

Thanks for the replies. I know I am using the correct username and password for the local account (I tried it on the machine and it worked). When I try to scan it using the WMI service on port 135 from Spiceworks desktop, it fails to scan. Is there another service i should be using? Windows 10 Pro; local account; no domain; DHCP client. Firewall is off; Further thoughts? Again not the way i would have setup the network, but it is what they got.

6

UAC or WMI are getting in the way - firewall off is a bad idea

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”
Import the attached, reboot, re-scan it

Spiceworks_UAC_remote_allow.reg (167 Bytes)

1 Spice up
7

Yep that worked! Thanks Rod!

8

Please be kind and mark the post as best answer if you are solved.