How can I force ADDM to use the Windows credential on a Windows server that has SSH port 22 open? It looks like ADDM instead of treating it like Windows, runs the Linux script on the server. Is there any way to stop this?

I have attached a screenshot of the detect “host”. this happens on more than one host. Port 22 must remain open as it is part of the application that resides on that host.

Thank you in advance.

you should exclude the ip address from the ssh credential so if your ssh is set for 10.100.100.* and your 1p address is 10.100.100.124 use 10.100.100.1-123, 10.100.100.125-255 for your range

Makes sense, but that is a bad practice when running a discovery. The point of a discovery is to find out things that are not known or that could change. If someone were to change IPs between a Linux server and this Windows server, then I would have the same problem, but now I would not discover that Linux server. I was looking for something from the BMC staff on the forum before I open a issue ticket. I think I will just open a issue ticket. Thank you for responding.

that’s what the discovery reports are for so that you can see when something is no longer responding to addm and adjust accordingly.

I understand, but to have to filter out 35 or more Winodws hosts on the same subnet that have port 22 open would be too time consuming (they do not have consecutive IPs). I know the HP DDM product has this capability so I would expect that BMC would have thought of something like this or at least has a workaround.

good luck

Thank you. Sorry to sound so defensive. We have been finding out (and dealing with) a lot of the short comings of ADDM.

In Discovery Configuration there is a setting called “Use Open Ports to Identify OS:” try changing this to “no”. I would then also recommend making sure you have your credentials in the order they are used most due to the fact that if this setting being turned off means ADDM cannot identify the OS it will try all the creds in order from top to bottom.

Attempted that, but got the same problem. Probably since it was discovered once using the SSH cred. I might have to remove and re-enter it, but I’ll try after lunch. Thanks for the idea.