1

Good morning,

I am running Spiceworks 7.4.00075. I use a Windows service account to scan for each workstation that has correct permissions to access the workstations. 29 of 78 workstations are reporting that they have login issues, while the other portion is still scanning correctly. For what it is worth these 29 workstations have been automatically scanned by Spiceworks for some time.

After following http://community.spiceworks.com/help/Resolving_Unknown_Devices#Windows and then getting an accessed denied message , I followed instructions on http://community.spiceworks.com/help/Authentication . My service account used for scans has local PC admin rights (as it has since it was set up and allowed for correct scanning of workstations) and UAC is not turned on at our workstations. This is in a domain environment. Could it be something in the string of password characters that is throwing this off? Or is there something else I can try for these workstations that continue to have errors?

1 Spice up
2

I also forgot to add that when I try the troubleshoot function in Spiceworks for the individual workstation, it responds to all tests correctly, and I can also ping and reverse DNS from the Spiceworks server to the workstation. WMI, Microsoft DS, and RDP are all showing as open ports.

3

Hey Ross,

I’ve also seen “access denied” messages pop up when there are problems in DNS. Have you checked out the article below to see if there might be any DNS-related issues?

https://community.spiceworks.com/help/Resolve_Your_DNS_Issues

4

I checked before but didn’t mention it, DNS is working in both directions… the workstation can resolve the server with the correct IP and the server can resolve the workstation with the correct IP.

I have also tried rebuilding WMI with the batch file that one of the other Spiceworks users had suggested, but WMI had responded to commands prior to even trying the batch file.

5

Hey Ross,

Hmm, okay. Let’s go ahead and get some logs over this way. Hang tight and I’ll shoot over an email!

6

Thanks Jon, I just sent over my zip file to you.

While I think of it, do you have any best practices for keeping the files in the logs folder trimmed down?

7

Hey Ross,

There aren’t any “official” best practices, but it’s safe to delete any of the logs within the log folder (don’t delete the actual folder, though!).

Generally, I like to keep a few of the latest production and scan (finder) logs available. That helps if you have to submit a support ticket.

Also, you can check to ensure debug logging is disabled over at Settings > Advanced & International Options > Show Additional Settings.

8

I ended up deleting out the user account that Spiceworks uses to scan workstations from the scan settings, and adding it back in. As soon as I scanned with the credentials added back in, Spiceworks was able to pick up the workstations having trouble. Thanks for the help!