BGinfo can save computer info into a file

[SimpleSi]

I've just discovered (after I wanted to log what memory I had installed in each computer in a school) that BGinfo (which I already run in each computer startup) will save all the info it can into an Excel file

 

Just had to alter the settings in my networked .bgi file and they'll all report in next time they re-boot

 

Some days you win

 

Simon

[TheScarfedOne]

Nice little gem of info there... might well use this one myself too!

[mossj]

or if you run spiceworks it pulls anything relevent from every machine/switch/printer/server on the network, and makes a handy gui & report interface for you.

[SimpleSi]

or if you run spiceworks it pulls anything relevent from every machine/switch/printer/server on the network

 

I'd put good money on it not doing unless you've configured your network to work with spiceworks

 

Tried it once in the past - it found the HP networked printer and that's all

 

regards

 

Simon

[SYNACK]

I have a VBS script that runs locally on each computer at machine startup and chucks vast amounts of hardware information up to a central database including serial numbers etc. It just uses WMI and gives you a good picture of the network. I can probably post it if people are interested.

[SimpleSi]

Yes please

(off to google WMI )

 

regards

 

Simon

[powdarrmonkey]

I also collect this during startup, but as part of a larger workstation manager project (that's taking far too long... damn users )

[amfony]

why would you go this route when you could go service agent install on OCS? To each their own but the service route doesnt require any one to be logged on - but then again how often is a computer not logged on in an education evironment ...

[SYNACK]

Yes please

(off to google WMI )

 

Have attached it, you can either point it at an access DB, which can be problomatic or a SQLExpress server. It should bea easily modifiable to connect to a different type of DB like mySQL but those would need the ADO drivers installed to each client pc.

 

It is rough and still in progress but has been running alright for six months or so. It will update based on the system serial number so it does not matter if you reinstall the box with a different name. Some machines don't have the serial number written propperly so there is a section where you specify bogus serial numbers so that it updates the pcs via system name instead.

 

Have a read of my blog posting http://www.edugeek.net/forums/blogs/synack/54-dmi-discontinuity-perils-brand-x-computing.html for more details on this and writing the values to the BIOS if nessisary.

 

You can get lots more information with WMI but this is just a subset that I found useful as it gives you a good indication of the screen. The SMBIOS data has lots of useful information in it which I do have some code somewhere to decode. It will tell you how many expantion slots and what type are on the MB along with the ram sockets, type and even RAM chip serial numbers in some cases.

 

I also collect this during startup, but as part of a larger workstation manager project (that's taking far too long... damn users )

 

Yea, this is aprt of a much larger datasystem that includes helpdesk reporting and asset tracking but it is no wear near done unfourtunatly. I can only code for a short period of time before I loose interest.

 

why would you go this route when you could go service agent install on OCS? To each their own but the service route doesnt require any one to be logged on - but then again how often is a computer not logged on in an education evironment ...

 

As this runs on startup it does not require anyone to logon and it is also all native which means that it is light and you don't need to install anything. It also means that they report in when they are avalible so you shouldn't miss any.

SQLInv.vbs

Edited February 27, 2009 by SYNACK