Re: How can get all the terminal names/IP addresses connected to network

I did something similar to this in a previous job. My solution was to approach the result fetching from the other direction.

Instead of :

Script 1 collects information on local host and stores results locally.
Script 2 polls all "alive" hosts and fetches their most current results.

Modify script #1 to save results locally and write them to \\server\temp.

Then script #2 can copy them from the local share (I'm assuming script runs upon "server") into the final destination - after preforming sanity checks to make sure you don't have a malicious local user uploading garbage to that location.

(The reason for the temporary share is because presumably you don't want random clients to a) see, or b) potentially modify other PC's results - so you have to have a staging area where the files can be tested for sanity before they are moved into the "real" location)

Steve
--

Comment on Re: How can get all the terminal names/IP addresses connected to network

Replies are listed 'Best First'.
Re^2: How can get all the terminal names/IP addresses connected to network by nimdokk (Vicar) on Oct 18, 2005 at 15:40 UTC
I'd go with this suggestion - except make it a permanent share that only the account running the job has access to (and perhaps a backup person or two). The nice advantage to this is you have all your raw data in one location plus it is being backed up on the network (you are doing backups aren't you? ;-)	[reply]