Hi,
Running a Windows Server 2003. is it possible to install a dude server which can report CPU usage, RAM usage, read/write cycles etc.
Thanks
What I mean by this is:
Is it possible to run the server agent as like a service or hidden. I don’t want the client on the server, we have a machine set up to permanently monitor each server, but if the actual software could be set as a service that would be epic.
Any help would be cracking. Thanks 
I am sure I don’t understand your question but here are some thoughts…
The Dude Server can collect from a remote machine with out being installed on it. It uses SNMP.
You should be able to SNMPwalk any device if that works you can track CPU, Memory and Disk remotely client-less.
The client is only ran on your workstation to connect to the dude server.
All probes are added to devices on the server through the client.
Have you got SNMP setup and working?
Yes another server can be setup as an Agent to the main server but that is most useful for installations that cross firewalls. That way you only need to allow both Agent to Server and Server to Agent traffic through the firewall. The Agent can collect another network and report to the Server…
HTH,
Lebowski
Never done this myself to be honest. I installed The Dude (As it is) on a machine. I’ve used it to map the network. Now what I need is for certain servers to respond with CPU usage and RAM usage etc. I have SNMP set up 
Go to the settings for one device and add the probes(Services) you want to track… Don’t auto discover until you understand how probes get installed by the auto discover process.
On the services tab, click +, examine the list of possible probes, add the probe you want.
Do your self a huge favor and read the Dude wiki in the user manual link at the top…
I’ll do that. I noticed you wrote Cisco CPU. It is not a Switch/Router I am looking to monitor. I have 8 dedicated servers that I am looking to keep a real time check up on
So if I add a manual service like you said, how could I guarantee my server responds with the details? Surely I need to open some kind of port.
oh it is much to late at night for support… having fun though…
SNMP is how the dude asks other computers about things like disks and cpu.
So you have SNMP working, add your dude server to your top map page.
Click the discover button. The probes(services) on your dude server will get added automatically.
Many services that your Dude server does not support will be tested as well.
OH sorry that graphic above in my previous post should have you click on the drop down not the single square.
The single square directly edits the listed probe.
You will find the CPU and Disk probes in that list. The Cisco Cpu is just used that for example…
Here is a screen shot of the probes running against my dude server.
lebowski, if you read the wiki, can you suggest anything to be added to it, or something that needs to be explained in more detail? I think you as an expert could have an opinion
I agree. He clearly knows what he is talking about. I have set up SNMP on the server. I am trying it on one for the moment. However it is not responding even though i have added CPU as a service. Any idea? I have set the SNMP profile to both v1 and v2 and still had no luck.
I’m getting there, slowly 
select SNMPwalk from the device tools and run it. See if there is SNMP access at all, and if yes, manually copy the required OID from the SNMPwalk results.
Okay. Run the SNMP Walker. Timeout at the bottom. I haven’t set up an agent, i just chose default. But on Services under Windows Server, it doesn’t allow me to choose a port, agent username and password etc
Yeah, I need to contribute more to the Wiki for sure.
Skezza, stop, go back and read up on SNMP… but here is the short version.
On your dude server(assuming it is windows) manage the services and add an SNMP community.
That is the common word they will use to allow communication using SNMP.
Inside the dude configure a new snmp community the same as the service.
Configure the General tab of your test device (your dude server) to use your new SNMP Profile.
Leave Agent default (that is for specifying a different dude install to do the polling)
Ignore user name and password, that is for “ROUTER OS”
Leave secure mode, router OS and dude server unchecked.
You don’t need to specify a port or anything.
Adding Windows Server as a service on your dude server will report down until you get SNMP working.
Now SNMPWALK your dude server and you should not get a timeout.
HTH,
Lebowski
Thanks Leb,
Did some reading on it. Networking as such isn’t my topic of expertise. I’m a software developer to be honest, but just had to get this one going.
Sorted now.
Thanks