Citrix plugin issues

CMK ver: 2.1.0p32
OS: Ubuntu 22.04

I am trying to setup the built-in check plugins for Citrix XenApp and XenDesktop products (version 7.1912 in this case). However there are no clear instructions provided on how to set it up. I had to contact support just to find out where they store the “citrix_farm.ps1” script plugin file so that I can copy to my delivery controllers plugin folder.

Current issue: I cannot get CheckMK to show any Citrix checks, even though I have copied the citrix_farm.ps1 file to the agent plugins folder. The agent detects the file but does not add any new checks.

I have read and followed the advice from the following forum threads:
[Check_mk (english)] Problems with citrix plugins Check MK 1.4.0p15 - Archive / checkmk-en - Checkmk Community
Citrix XenApp Monitoring - Global Community - Checkmk Community

I have set the checkmk service on our Citrix Delivery Controllers to run as a domain service account, which I have granted full administrator access to our Citrix farm. This service account also has local administrator access on the controllers. And as mentioned, I have already copied the citrix_farm.ps1 file to the correct agent plugin folder on the controller.

Despite all of this, no new checks appear on the host when doing a service discovery. I also tried forcing it using some of the Citrix rules, but nothing works.

Really stuck here on how to use. Due to the fact that this is a built-in plugin, developed by the Checkmk team, it seems this has meant a lack of anything on the Checkmk Exchange, so I either write my own plugin or try getting this to work.

I am having pretty much same issues getting the built-in Zerto plugin to also work, but I will tackle them one at a time!

Hi Greg,

the script is a simple powershell script that you can run manually without an parameters in the context of the service account you created.
Depending on the output we can then troubleshoot further.
The last topic with this kind of error was solved by configuring the Antivirus solution that was blocking the powershell script.

1 Like