Scanning Errors for Windows 10

stevengiffin · 2015-09-27T06:56:30.000Z

Hi I am trying to scan my Windows 10 devices and it wont scan, I turned off the firewalls to see if that was an issue, any ideas??

thanks

steven

Rod-IT · 2015-09-27T08:46:44.000Z

A little more information than it wont scan would help.

Is it domain joined or in a workgroup?

Does SW find the device, but fail to scan it, or fail to find it too?

Rod-IT · 2015-09-27T08:48:52.000Z

3 things to check

Make sure file and printer sharing is enabled
Run the below

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”

3. Run the attached registry file

All to be done on the client not scanning

Spiceworks_UAC_remote_allow.reg (167 Bytes)

texkonc · 2015-09-27T11:11:15.000Z

I didn’t think they supported win10 yet

Rod-IT · 2015-09-27T11:20:33.000Z

They don’t support it as a Spiceworks host, but they do still scan (even if not supported), I have all my Windows 10 devices inventoried.

stevengiffin · 2015-09-27T20:32:08.000Z

So I am running a domain it finds the devices but gives no details [see photo]

Sorry, but on that command prompt, I enter

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

and all I get is “Group cannot be specified with other identification conditions”

stevengiffin · 2015-09-27T20:33:04.000Z

Pic

SW.PNG800×238 43.6 KB

Rod-IT · 2015-09-27T20:35:31.000Z

That error indicates you or someone has already run it, and it already exists.

Did you run the registry file?

stevengiffin · 2015-09-27T20:59:48.000Z

yeah I ran the registry file

texkonc · 2015-09-28T01:44:21.000Z

Did you reboot after the reg file? it’s touchy like that.

stevengiffin · 2015-10-05T04:45:44.000Z

yes I did reboot, has anyone heard of when Win10 will be supported?

Rod-IT · 2015-10-05T18:01:59.000Z

How are you scanning this, by IP/DNS Name or from a range?

Is there another firewall between you and the SW server, do you have any probe detection software on the client that may block port scans?

Any AV that might block scripts running?

Rod-IT · 2015-10-05T18:10:37.000Z

I have several W10 devices scanning fine here.

Make sure if they are in the domain, the domain profile is showing under network and sharing centre, make sure file and printer sharing is enabled, the WMI command seems to have already been run, as does the reg file so I don’t see what else other than something blocking your scans would prevent this.

Some people have found scanning the device with it’s IP entered by itself works, I’m not sure why a network scan does not but an individual scan has been known to work

stevengiffin · 2015-10-05T21:21:46.000Z

Everything scanned fine with the system when they were Win7/8/2008 R2, my Server 2012 systems scan fine, it finds my printers, my APs, switches, just not details about Win10 systems

stevengiffin · 2015-10-05T21:23:22.000Z

I run the ManageEngine and it detects my Win10 systems with no issues

stevengiffin · 2015-10-05T21:25:28.000Z

the only change to my network was upgrade my workstations to Win10 and my servers to 2012 R2

I run SCEP\defender, thats it

stevengiffin · 2015-12-28T05:28:05.000Z

looks like spiceworks fixed the issue, thanks everyone for the ideas!

georgemcfarlin · 2015-12-28T11:58:27.000Z

Guessing you were using win10 before spiceworks was ready to support it.

Rod-IT · 2015-12-28T15:02:35.000Z

Scanning Windows 10 is fine, I’ve been doing so since the beta - I’m guessing there was a client issue and not a Spiceworks one and something changed on the client so now Spiceworks can scan it