SQL Probe and WID

[DuaneNMore]

When I run a discovery against a Windows 2012R2 server, the SQL Server probe finds the Windows Internal Database and thinks we have a sqlserver. This is because this thing runs as C:\Windows\WID\Binn\sqlserver.exe. I think I'd like to ignore this particular instance, but the way discovery is set up, if it sees sqlserver.exe it thinks you are running sqlserver. Being new to discovery (took the class last week) I know there is a way, but I am uncertain how.

I also have the additional problem of installing the SQL management library (SMO) for when I do discover real sql servers but that is well known.

[Ryan Zulli · Accepted solution]

Hi Duane,

The process classification is where you'd want to look...Discovery --> Discovery Definition --> CI Classification --> Processes.   Click on the Microsoft SQL Server record and you'll see that we look for a condition where Command contains sqlserver.exe.   Here you can add another condition, AND where Command IS NOT C:\Windows\WID\Binn\sqlserver.exe.

Of course the proper way would be to copy the OOB code and create a new record that way during the next update you can compare changes (if any).

Let me know if this helps.

Thanks,

-Ryan

[DuaneNMore]

Thank you. I went in made the change; dumped the CI so that the SQL Server would go away and rediscovered the Server and this fix worked.

We are going to go to production in January, and this work is being done on an on-premise "Proof Of Value" implementation. (a.k.a Test). I am executing the discovery on the MidServer using the loopback. It is never making it to Completed State and seems to get stuck in Active, however ECC Queue starts 12 and completes 12 and there is no indication of an error. Do you have any suggestions or insight on what I would do to troubleshoot. I have tried some of the rudimentary steps given in the Discovery class but have nothing yet.

[Ryan Zulli]

Try restarting the MID Server and running the scan again....Assuming this doesn't happen with the other servers you are scanning, try not using the Loopback as a test (however it should work).   If all else fails you may need to open a support ticket with HI.

[DuaneNMore]

I restarted and it behaves the same. Created a credential, and when I tried to test the credential the test would fail; however when I run the Discovery the Discovery executes successfully, although it still never completes. Looking at opening an incident/support ticket.