1

Im having issues completing my network scan, we finally were able to do some housekeeping

on our devices however i’m having issues with a few. 10% of our windows computers (mixture of HP and lenovo) windows 7 64bit OS are not being inventoried. I have read quite a few articles we have here in the knowledge base and the forums. i don’t believe its a WMI issue as i can pull any and all info using power-shell from my computer as well as the server where spiceworks is installed on. the DNS is properly maintained and can pull the correct corresponding information with nslookup. its not an authentication error as it gets past the network scan with no issue. its not a firewall as i have used both the Spiceworks inventory helper which reports back no issues with the firewall, i went a step further as to open the ports needed as indicated in the spicework network scan requirements as well as deleted and rescanned the subnet as to which they are present. However im still having there is still items in the inventory that show the Host name/ the serial number/ the IP/ and device type: unknown.

(side note: going to tools and clicking on rescan, Edit>Scan using WMI/ Manually managed:False; network scan speed has been set to both fast, medium, and slow)

we also just upgraded to the latest version of spiceworks.

2 Spice ups
2

Have you ran my scripts?

On a troubled machine, make sure file and printer sharing are enabled.

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”

(Even if the firewall is disabled)

then run the registry file attached - it enabled elevation of UAC remotely.

Keep me posted, please share any screenshots or errors encoutnered

Spiceworks_UAC_remote_allow.reg (167 Bytes)

3

will try that today.

4

Keep me posted

5

unfortuneately it did not work. same instance. turned off our AV, turned on file and printer sharing, added your registry.

Also, i tried both the rescan and the deleting from the inventory and rescanning to see if it helped.

1.PNG
1.PNG800×412 56.6 KB
6

It does seem to make the connection though.

Do you have WMI disabled or any policies that prevent remote connections?

7

dont believe so if i pull up powershell in my workstation and use “Get-WmiObject -Class Win32_computersystem -ComputerName AUSTX098 –Credential domain/domainadmin”

im able to recieve this

Domain : domain.com

Manufacturer : LENOVO

Model : 10B00005US

Name : AUSTX098

PrimaryOwnerName : IT Admin

TotalPhysicalMemory : 8498761728

8

If you delete this machine from the inventory and rescan it, does it pick it up correctly?

There has been odd times I’ve seen it not get scanned when scanning a subnet, but if you add the manual IP of just this device, it gets it - try this as well please.

Once it has it you can remove the manual entry - it is only a validation check at the moment too

9

yes tried that both way from the subnet as well as the single IP. Same result.

10

SW team are going to need to peek at your logs to see what is going on then - bear with them as many are out partying at the event (I assume).

11

awesome.

12

if you get no help on here in a day or two, email support@spiceworks.com and ask if they can have a look at your DB, point them here for information.

13

ill be sure to do that as this has really stumped me.

14

UPDATE: running scans, then uploading to Spiceworks Support

15

Keep us posted with a fix

16

awaiting reply from spiceworks. Logs have been sent.

17

Final update, recieved from Spiceworks Support.

" Based on the logs you’re running into a known bug we’re currently working to

resolve. I don’t have a time frame at the moment, but if you’d like to keep an

eye out for updates you can subscribe to the release notes page linked below.

This page will list the internal bug ticket numbers resolved by each release.

Please also feel free to reach out to me in the meantime if

you’d like to check in.

Based on the logs you’re running into a known bug we’re currently working to

resolve. I don’t have a time frame at the moment, but if you’d like to keep an

eye out for updates you can subscribe to the release notes page linked below.

This page will list the internal bug ticket numbers resolved by each release.

Please also feel free to reach out to me in the meantime if

you’d like to check in. "

18

so progress has been made, i have been scratching my head on this for quiet awhile and the suggestions i got from spiceworks was to roll back my installation, then allow them to rebuild my database, then i could proceed further to update however i would potentially lose data.

As this wasn’t an option to my superiors, i decided to dig deeper using powershell i would go through every computer with the command “Get-wmiobject -class win32_Computersystem -computername “workstation”” and one by one resolved any and all WMI errors with the local Administrator credentials and my own domain admin credentials.

Once completed i would use the command you suggested and on each computer run “netsh advfirewall firewall set rule group=“windows management instrumentation (WMI)” new enable=Yes”"

after that i would go into each affected computer and input the owner name and the computer name, once completed i would initiate the rescan and every computer would start populating the data needed in our austin office, in chicago i would have to wait till the next day after the nightly scans run to see thier updated data.

Note: i also tried just rescanning without manually populating the computer info data and no changes would occur. so im not sure what would have resulted in a fix. any input?

19

A small loss of some data vs it not working at all is an option in my opinion - what data was they worried about losing?

Are you still having issues, if so are they the same or different?

20

we would have lost all data from when the last backup of the previous version till now.

and so far 99% of everything is working a couple here and there due to VPN users but all good now.