Spiceworks can not scan Windows 10 computer

criostalprice · 2015-08-19T13:52:45.000Z

I just upgraded my first in-house computer to Windows 10. It is joined to the network and I have turned on al the sharing and allowed remote connections and everthing seems to be fine. But then Spiceworks can not scan the device, either by a full scan or by IP or Host Name. Is there something I can’t google that would explain why I can not inventory a windows 10 computer?

bryandoe · 2015-08-19T14:01:45.000Z

It’s working fine for me, except Spiceworks still says the 10 system is Windows 7 Pro at the top. Under Software it does list 10 Pro correctly.

criostalprice · 2015-08-19T14:18:03.000Z

The was a local firewall issue that was fixed with an older tool I had downloaded before. In the end it was only a matter of forcing open the WMI port.

criostalprice · 2015-08-21T14:09:22.000Z

I need to take that back. I was able to open the ports and it allows me to enter credentials but in the end it still fails the scan every time. When I open the /fix page from the machine it says there are no ports open but when I check my devices it says the WMI and RDP ports are open. I am against the wall on this one and cant’ figure out what is next. There are other issue I have found with Windows 10 that make it behave more like home addition then a pro addition, when joined to a domain. Overall this is a spare machine and I want to keep playing with it but as for upgrading users…I don’t think 10 is an option yet.

anon73201645 · 2015-08-26T06:11:40.000Z

Hmm… just followed the steps in the fix-URL and it worked.

Of course I did not forget to use a local account, member of local administrators group, to scan the new Windows 10 computer. Especially this was an issue in my case

criostalprice · 2015-08-26T12:28:31.000Z

I really don’t understand the problem but in the end I put a reverse lookup in my DNS and it worked and it is not inventoried. Thing is, none of the other computers have a pointer there and they all worked. Very weird indeed but now it is done and the scan and inventory worked.

thisisnotfacebook · 2015-09-22T02:24:47.000Z

I had this issue on Windows 10 machines (brand new, mostly settings coming from Group Policy) and once I followed the instructions ( http://community.spiceworks.com/help/Configuring_AV_Firewall ) with the group policy changes, Spiceworks was able to scan the machine without a problem.