SQL Probe and WID

DuaneNMore · ‎11-21-2016

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 · ‎11-21-2016

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

View solution in original post

Dave Smith1 · ‎11-30-2016

Good to hear the root cause has now been identified. Hope it all gets fixed!