invisik wrote:I have a number of offices with their Windows XP desktop machines running DHCP on a Windows Active Directory domain setup. I believe I can use the "Domain\Administrator" naming to authenticate to any system on the network from HostMonitor, which is great.
Correct.
invisik wrote:I would like to check all of the XP systems event logs once a day for Errors. Can I specify an IP range for NT Log to check and have it return the IP (or ideally the hostname) of the machines it is checking? I would need some way to find out what machine had an error.
What's the best wayt to poll a large number of desktop systems without setting each one up individually?
"NT Event Log" test method does not support range of target IP's. You should create separate test for each certain XP box. In this case, I think, "Replicator utility" will be helpful.
Quote from he manual:
http://www.ks-soft.net/hostmon.eng/replicator/index.htm
===================================
Those who have large networks with hundreds of servers will appreciate the ability to replicate a test (i.e. reproduce and apply to...) for an array of systems in almost an instant. For example if you have a CPU Usage test that works on one machine, with the help of a Replicator you may reproduce the same test for every workstation without a hassle of setting the parameters of each of them separately.
===================================
So, in your case, you just should create one "NT Event Log" test to check one specific XP box and use Replicator to create the same tests for other XP boxes.
Probaly, for the DHCP network, it would be better to use HostNames instead of IP. However, if you specify IP-adresses it should work as well. It is up to you.
To resolve, what exact XP box has an error, you should assign to the tests action profile, that uses "NT Event Log" specific macro variables:
Quote from the manual:
http://www.ks-soft.net/hostmon.eng/mfra ... .htm#macro
================
the following variables have sense for "NT Event Log" test only, they represent parameters of the last "Bad" event detected:
%NTEventSource% Event source. Identifies the software that logged the event
%NTEventComp%
Name of the computer where the event occurred
%NTEventTime% Time of the event
%NTEventType% Type of the event
%NTEventID% Event identifier
%NTEventText% Event description
%NTEventUser% Represents the user name if an event is attributed to a specific user
================
invisik wrote:Thanks! Everytime I look at my HostMonitor it does something else new!
You are welcome!
Regards,
Max