last scan time = old

ovestarckjohann7821 · 2016-01-21T11:16:41.000Z

Hello!

It looks to me live SW is not updating device-details on a regular basis. We’re daily scanning our devices, but “last scan time” on some (online) computers is month(s) old

Looks like SW is not working properly. Just installed the lastest version yesterday - but even the 11:00h scan today did not work properly.

What to do?

Ove

loesch · 2016-01-21T11:34:33.000Z

check if the IP (according to spiceworks) is beeing used on a device with spiceworks agent, if yes → do this

either do a scan with the device with the agent (not allways possible) or
give the not scanned device a new IP in a different range and scan the new range.
Afterwards change the new IP back to default ip range and do a rescan on the device (not the range)

ovestarckjohann7821 · 2016-01-21T12:03:50.000Z

we do use dhcp within our network with a 8 days lease-time. A pc being offline for 2 weeks will get another ip on the next start.

And we’re not using spicework-agents on the windows machines…

In general we do have two ip-ranges from our two dhcp-servers (10.10.3.x and 10.10.5.x).

If the ip of a device is outdated in SW shouldn’t SW fix the ip when scanning the ranges the next time?

Ove

ovestarckjohann7821 · 2016-01-25T12:45:19.000Z

any hints by support ?

Still no luck with scan-updates

Ove

loesch · 2016-01-25T13:32:20.000Z

you can install the agent, but once installed it needs always the agent, no way back (unless you delet the device in SW and loose all information about this device)

if have 2 PCs here where I found no other solution.

ovestarckjohann7821 · 2016-01-26T14:49:02.000Z

we’re talking about approx. 50-100 pc’s which do not update correctly

I’m not really planning to install an agent on all of them…

Isn’t there any solution available to “refresh” the finder-task and let it do it’s job without problems as it did before ???

Ove

jaimedelapaz · 2016-01-28T17:34:44.000Z

Let’s grab a copy of your logs. We can see if the scans are running properly or if there is something wrong when scanning the devices. I’ll email you with instructions.

ovestarckjohann7821 · 2016-02-02T06:43:08.000Z

just a short feed-back for the dudes stumbling across this thread.

After contacting sw-support they figured out the problem.

Deleting or renaming c:\Program Files (x86)\Spiceworks\Data\kuids.yaml and restarting the sw-service did do the job.

That file caches some info about the machines and it looks like that fu**ed up the scan-process of sw.

Ove

pathayzlett9568 · 2016-06-23T16:30:29.000Z

Was there a trouble ticket for this problem? Did the latest version (7.5.00088) fix it?

ovestarckjohann7821 · 2016-06-24T09:13:09.000Z

hmm…with 7.5.00087 problem was NOT solved - upgraded to 7.5.00088 now - will see progress the next days…

Ove

ovestarckjohann7821 · 2016-06-28T07:35:46.000Z

7.5.00088 did not solve the problem either…

Ove

davidbehr · 2016-12-21T16:31:15.000Z

Just tried this. Let’s see if this works for me.

acatic · 2018-10-30T17:26:09.000Z

For what it’s worth, on my present install on a 64-bit OS, the path is c:\Program Files\Spiceworks\Data\kuids.yaml. I do have the folder c:\Program Files (X86)\Spiceworks\Data, but kuids.yaml is not there.