Well it just magically started working, tried it on another server that had issues and now it’s fine. I think I might have been trying different configurations too fast at first.
What worked:
- Downloaded the mk-sql.exe executable from the checkmk server, same place where the original windows agent is downloaded
- Upload the file to the Windows server at
C:\programdata\checkmk\agent\plugins - Create a new file called mk-sql.yml at
C:\programdata\checkmk\agent\configswith the following contents
---
mssql:
main:
authentication:
username: ''
type: integrated
- Do a service discovery in CheckMK
The services should appear.
Note that TCP/IP communication was enabled on all of the SQL servers, like the checkmk documentation suggests.
The only mandatory requirement for the use of
mk-sqlis that the TCP/IP protocol is activated in the SQL Server network configuration. If TCP/IP is not permitted or allowed in your MSSQL server environment, you will have to fall back on the legacy plug-inmssql.vbsuntil further notice.
Thanks to the people who helped get me on the right track, especially with the idea of creating that config file from the bakery.. A more complex example of a config file was also posted which could help others who don’t want to have to launch a new instance of CheckMK simply to get the file