OK I give up,
I have tried unsuccessfully for months to get a few of my client machines to populate to my inventory in Spiceworks. These machines all have authentication issues, even though I am a domain admin and should have local admin rights to all the PCs. I am using my login as authentication.
I have set up the GPO for the client firewall, and have checked that is it being applied correctly.
I would love any kind of help I could get.
I know you will probably need more info. just let me know what you need to better asses.
5 Spice ups
jstear
(Jstear)
2
If you have worked on this for months and nothing has come about it, you may have a bigger issue than missing something. Send a ticket into support@spiceworks.com and reference this thread.
2 Spice ups
grey
(Grey)
4
2 Spice ups
I will try this tomorrow and update. thanks .
I ran This script I also Added a GPO to enable inbound WMI through firewall on clients. Still getting this message:
check account, password or WMI configuration
These are PCs I have recently re-installed Windows on for various reasons. I’m guessing I am missing some sort of setting or GPO rule here.
I do have PCs on my network that I am connecting to fine with these credentials.
peterb99
(Peter B (Spiceworks))
7
Adam,
I just saw the ticket you started with us @ support@spiceworks.com. I’ll send you a response to that in just a minute, but I wanted to show you this really awesome tool we made to help with these sorts of issues. Behold…the Spiceworks Unknowns Tool: http://community.spiceworks.com/help/Spiceworks_Unknowns_Tool
1 Spice up
peterb99
(Peter B (Spiceworks))
8
Run that bad boy on one of your workstations you are trying to scan in. It should fix 3 of the most usual suspects and/or let you know if any of those are to blame.
If that doesn’t shed any light on what is causing Spiceworks to not be able to scan your workstations, then it could be WMI or DNS. This article goes over both in great detail: http://community.spiceworks.com/help/Inventory_WMI
I shall bask in the glory that is your unknowns tool and instruct my clients to worship at the feet of its mighty fixing ability.
1 Spice up
I ran the tool but I’m still not getting through to WMI. Blocks 1 and 3 are green and 2 is yellow. I have Symantec endpoint running on my clients.
peterb99
(Peter B (Spiceworks))
11
Adam,
Can you temporarily disable SEP on one of your clients, try to scan just that IP address, and let me know if that fixes it? If it does, we likely need to add a policy on the Symantec Endpoint Protection Manager console. One of the very first parts of the Spiceworks scan is a port scan, to see which ports are open on the given device. Some overzealous intrusion detection and prevention software, like SEP has built into it, can flag this as an attack and block traffic from that IP (your Spiceworks server).
I’ll bet that’s what is going on here.
I’m checking this out now
1 Spice up
peterb99
(Peter B (Spiceworks))
13
Good morning Adam,
What’s the score? Were you able to identify what was causing traffic to be blocked?
So with SEP disabled I can authorize, but it still makes it to about 85% of a scan and has a WMI timout error.
peterb99
(Peter B (Spiceworks))
15
Good to know. So it seems like SEP was likely blocking traffic (you’ll need to set a policy in the management console to allow Spiceworks - or the Spiceworks server - to not be blocked or scanned by SEP) but there are also some deeper WMI-related issues.
Take a look at the steps on the following page: http://community.spiceworks.com/help/Troubleshooting_WMI
The first step, running the WMIC command, is a really good step while testing the policy you’ll need to put in place with SEP. Let me know when you get that one nailed down.
The other steps go more into fixing the errors or inconsistencies in WMI. Send me an email or update this thread if you get stuck on any of this.
