PC audit over network
mr2nut Member Posts: 269
I use a bit of Software called Belarc Adviser to do reports on machines to see the make and model number, along with many other useful information. I was just wondering if there is any Software available that can get these reports 'silently' over the Network? I don't want to disturb the clients, also they are quite far away from us so if we could do it remotely that would be great. In this case, my reason for doing this is i'd like to see what make/model number the PCs are for memory upgrades.
Unfortunately this client isn't set up this way but I do now remember what you mean, it's within the remote SUS Software for each computer. They have updates coming direct to each machine through the router
Another way to do this is to create a logon script that runs the systeminfo command.
maybe something like this....
systeminfo >> "Networklocation"\%computername%
SMS and Solarwinds would be overkill if all you want is some simple basic informtion. WMI would probably be better where you can connect to AD, look at all computers, perhaps determine if they're associated with an XP/Vista/Client OS, and then do some WMI queries against them.
It does but there's only a few PCs plus they have 8MB Broadband so it isn't an issue in this case. For my other clients that i've taken over the support for i've changed it to WSUS straight away.
That's a bit over my head to be honest but thanks all the same. I've heard of WMI queries before through AD to query certain aspects of computers on the Network but have never used it before (not had the need until now as I used to be in a small 20 user office so it would have been a bit lazy ) How exactly do you use the WMI then :
That lansweeper looks great, but I don't have SQL on the clients Server at all. Is there any other way of finding out the model/make of some PCs remotely with a nice easy to use GUI? (for free obviously )
Or you could just run %windir%\system32\dllcache\msinfo32.exe to bring up the GUI, then go to VIEW>REMOTE COMPUTER.
I don't think it's required for the client machines.... Just the server. For the Clients you run the LsClient.exe "servername" command
I put mine in the Sysvol with my logon scripts and just added to the logon to run the lsclient program.