Got another handy tool to help troubleshoot issues with SSH connection failures in your discoveries....

We use a version of J2ssh to make the connections to your 'nix machines and sometimes you just cant figure out why a connection to the box fails while other methods are successful...

Its really as simple as adding a SSH debug parameter to your Unix Classify probe. This will add to your midservers /agent/logs folder more debug data in the agent0.log0 file and also generate a ssh.log for your troubleshooting needs.

My friend in the BRK showed me this handy little way to help prove a WMI connection outside the midserver but using the same components asking the question. This can come in handy when you can't figure out why you are having problems connecting to a Windows OS and want to see the raw return before the "machine" starts processing it.

We are having few Computers in our organization. These computers can be assigned to a person based on the availability. If a person to whom a computer was assigned, leaves the organization,Computer tagged to him becomes free and is available for allocation to other person.However, We want to retain the record of retired Computer. In both the case Serial number of the computer will remain same.

Has anybody out there attempted to or have been able to discover an IBM Z/OS Mainframe environment? If so, please can you share your experience with us?

Thanks in advance

Dirk

Does anyone have details on how to configure security in SQL to allow Discovery to discover MSSQL catalogs?

http://wiki.service-now.com/index.php?title=Database_Catalogs

Thank you.

I was thinking tonight about how our load balanced behaviors work and though of some improvements that you might think about when setting up your schedules.

As it works currently, when defining the 'Mid Servers' of those that would execute a particular functionality when the schedule kicks off it will use the first (mid server)in the list to run the shazzam probe then of course Load balance across the other mid servers in the list.

What I have come across is that in many environments you could be using a single LB behavior to run multiple schedules at the same time...

I am having trouble with some computers running the "snc_discovery.js".

We use "wscript.exe /B snc_discovery.js" in the "Run" key in the registry. Some machines it works great, some machines wscript.exe runs forever and never returns results.

Has anyone seen this before?

Here's a simple and very useful feature of JavaScript that you may not be aware of: functions may be nested, one inside another. Here's a simple example, in a script you can run on your instance:

gs.log('Hex value of 11259375 is: ' + hex(11259375));

function hex(value) {
    var rem = value;
    var result = '';
    while (rem > 0) {
        var r = rem % 16;
        rem = Math.floor(rem/16);
        result = hexChar(r) + result;
    }
    return result;
    
    function hexChar(charValue) {
        return '0123456789ABCDEF'.charAt(charValue & 0xFF);
    }
}

We would love to have your thoughts about the Discovery Lab at Knowledge10!

Our Knowledge10 conference is coming up in just a couple of months! I'll be there, and I hope to see you there as well. But whether you're attending or not, we'd like to hear your thoughts on the best use of our two hour Discovery lab.

We've had several ideas ourselves – a troubleshooting primer, an implementation primer, advanced classifications, building custom probes and sensors, and so on. But these are products of our fevered and slightly loony imaginations. What we'd really like to know is this: what would you find most valuable? Please let us know your thoughts in the comments to this post!