XymonPSClient repository

list Stef Coene · Mon, 26 Jan 2026 09:39:44 +0100 ·

Hi,

I create a private github repository and tried to merge all the changes I made to the Windows Powershell client.

But I realised it is better to create a repo in https://github.com/xymon-monitoring/ with v2.42 from https://sourceforge.net/p/xymon/code/HEAD/tree/sandbox/WinPSClient/.
Then I can fork that repo and add my changes.


So is it ok if I create a XymonPSClient repository and add client v2.42 to it?


Stef

list Nicola Canepa · Mon, 26 Jan 2026 09:12:59 +0000 ·

I think it's a good idea: should we name it xymon-client-win-ps?

The idea is xymon-<type>-<os>-<language> so we can have some uniformity if more come

Nicola

Il giorno 26 gennaio 2026, alle ore 08:39, Stef Coene <xymon@xymon.com> ha scritto:

▸ quoted from Stef Coene

Hi,

I create a private github repository and tried to merge all the changes I made to the Windows Powershell client.

But I realised it is better to create a repo in https://github.com/xymon-monitoring/ with v2.42 from https://sourceforge.net/p/xymon/code/HEAD/tree/sandbox/WinPSClient/.
Then I can fork that repo and add my changes.

So is it ok if I create a XymonPSClient repository and add client v2.42 to it?

Stef
_______________________________________________

Xymon mailing list -- xymon@xymon.com

list Stef Coene · Mon, 26 Jan 2026 11:41:42 +0100 ·

Hi,

I don't know how many clients are not natively supported.
The Powershell Windows client is one, maybe Mac?

So for this one:
xymon-client-windows-powershell


Stef

▸ quoted from Nicola Canepa


On 2026-01-26 10:12, Nicola wrote:

I think it's a good idea: should we name it xymon-client-win-ps?
The idea is xymon-<type>-<os>-<language> so we can have some uniformity if more come

Nicola

Il giorno 26 gennaio 2026, alle ore 08:39, Stef Coene <xymon@xymon.com <mailto:xymon@xymon.com>> ha scritto:

Hi,

I create a private github repository and tried to merge all the changes I made to the Windows Powershell client.


But I realised it is better to create a repo in https://github.com/ xymon-monitoring/ with v2.42 from https://sourceforge.net/p/xymon/ code/HEAD/tree/sandbox/WinPSClient/.

▸ quoted from Nicola Canepa

Then I can fork that repo and add my changes.


So is it ok if I create a XymonPSClient repository and add client v2.42 to it?


Stef

list Bruno Manzoni · Tue, 27 Jan 2026 07:22:37 +0100 ·

Hi Nicola, hi Stef,

Following our chat, I created a repo named xymon-client-windows-powershell.

Looks OK to me.

Bruno

Le 26.01.2026 à 11:41, Stef Coene a écrit :

▸ quoted from Stef Coene

Hi,

I don't know how many clients are not natively supported.
The Powershell Windows client is one, maybe Mac?

So for this one:
xymon-client-windows-powershell

Stef

On 2026-01-26 10:12, Nicola wrote:

I think it's a good idea: should we name it xymon-client-win-ps?
The idea is xymon-<type>-<os>-<language> so we can have some uniformity if more come

Nicola

Il giorno 26 gennaio 2026, alle ore 08:39, Stef Coene <xymon@xymon.com <mailto:xymon@xymon.com>> ha scritto:

Hi,

I create a private github repository and tried to merge all the changes I made to the Windows Powershell client.

But I realised it is better to create a repo in https://github.com/ xymon-monitoring/ with v2.42 from https://sourceforge.net/p/xymon/ code/HEAD/tree/sandbox/WinPSClient/.
Then I can fork that repo and add my changes.

So is it ok if I create a XymonPSClient repository and add client v2.42 to it?

Stef

xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com

xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com

xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com

list Stef Coene · Tue, 27 Jan 2026 09:41:14 +0100 ·

Hi,

I think it's a good idea to keep the sourceforge version data 'as is' for archival purposes.
Can you also create a xymon-client-windows-powershell-sourceforge repository?
I will upload the sourceforge version and then this repository can be archived.


Stef

On 2026-01-27 07:22, Bruno Manzoni via Xymon wrote:

Hi Nicola, hi Stef,

Following our chat, I created a repo named *xymon-client-windows- powershell*.

▸ quoted from Bruno Manzoni


Looks OK to me.

Bruno


Le 26.01.2026 à 11:41, Stef Coene a écrit :

Hi,

I don't know how many clients are not natively supported.
The Powershell Windows client is one, maybe Mac?

So for this one:
xymon-client-windows-powershell


Stef

On 2026-01-26 10:12, Nicola wrote:

I think it's a good idea: should we name it xymon-client-win-ps?
The idea is xymon-<type>-<os>-<language> so we can have some uniformity if more come

Nicola

Il giorno 26 gennaio 2026, alle ore 08:39, Stef Coene <xymon@xymon.com <mailto:xymon@xymon.com>> ha scritto:

Hi,

I create a private github repository and tried to merge all the changes I made to the Windows Powershell client.

But I realised it is better to create a repo in https://github.com/ xymon-monitoring/ with v2.42 from https://sourceforge.net/p/xymon/ code/HEAD/tree/sandbox/WinPSClient/.
Then I can fork that repo and add my changes.


So is it ok if I create a XymonPSClient repository and add client v2.42 to it?


Stef

list Bruno Manzoni · Tue, 27 Jan 2026 10:20:35 +0100 ·

Hi Stef,
Seem to me that it is already archive at
https://github.com/xymon-monitoring/xymon-svn-mirror/tree/sandbox/
Do you think we need more ?

Below the process to import it (Chatgpt: check!)
Let me know if you want me to do it
Bruno
--------------------------------------------

Chatgpt: Here is the clean, standard way to do it, without rewriting history.

Goal: copy sandbox/WinPSClient from xymon-svn-mirror into
xymon-client-windows-powershell.

Steps

Clone the new repo

git clone https://github.com/xymon-monitoring/xymon-client-windows-powershell
cd xymon-client-windows-powershell

Add the svn mirror as a temporary remote

git remote add svn-mirror https://github.com/xymon-monitoring/xymon-svn-mirror
git fetch svn-mirror

Extract only the folder you want

git checkout svn-mirror/master -- sandbox/WinPSClient

Move contents to repo root (recommended)

mv sandbox/WinPSClient/* .
rm -rf sandbox

Commit

git add .
git commit -m "Import WinPSClient from xymon svn mirror"

Push

git push origin main

Result

Clean new repo
Correct history point-in-time
No svn noise
Easy to evolve independently

This is the right approach for a client split.

Le 27.01.2026 à 09:41, Stef Coene a écrit :

▸ quoted from Stef Coene

Hi,

I think it's a good idea to keep the sourceforge version data 'as is' for archival purposes.
Can you also create a xymon-client-windows-powershell-sourceforge repository?
I will upload the sourceforge version and then this repository can be archived.

Stef

On 2026-01-27 07:22, Bruno Manzoni via Xymon wrote:

Hi Nicola, hi Stef,

Following our chat, I created a repo named *xymon-client-windows- powershell*.

Looks OK to me.

Bruno

Le 26.01.2026 à 11:41, Stef Coene a écrit :

Hi,

I don't know how many clients are not natively supported.
The Powershell Windows client is one, maybe Mac?

So for this one:
xymon-client-windows-powershell

Stef

On 2026-01-26 10:12, Nicola wrote:

I think it's a good idea: should we name it xymon-client-win-ps?
The idea is xymon-<type>-<os>-<language> so we can have some uniformity if more come

Nicola

Il giorno 26 gennaio 2026, alle ore 08:39, Stef Coene <xymon@xymon.com <mailto:xymon@xymon.com>> ha scritto:

Hi,

I create a private github repository and tried to merge all the changes I made to the Windows Powershell client.

But I realised it is better to create a repo in https://github.com/ xymon-monitoring/ with v2.42 from https://sourceforge.net/p/xymon/ code/HEAD/tree/sandbox/WinPSClient/.
Then I can fork that repo and add my changes.

So is it ok if I create a XymonPSClient repository and add client v2.42 to it?

Stef
xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com

xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com

xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com

xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com

xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com

list Stef Coene · Tue, 27 Jan 2026 12:00:10 +0100 ·

Hi,

Thanks, can you also create a xymon-client-windows-powershell-sourceforge repository?

I think it's a good idee to keep the sourceforge version data 'as is' for archival purpose.

▸ quoted from Bruno Manzoni



Stef

On 2026-01-27 07:22, Bruno Manzoni via Xymon wrote:

Hi Nicola, hi Stef,

Following our chat, I created a repo named *xymon-client-windows- powershell*.

Looks OK to me.

Bruno


Le 26.01.2026 à 11:41, Stef Coene a écrit :

Hi,

I don't know how many clients are not natively supported.
The Powershell Windows client is one, maybe Mac?

So for this one:
xymon-client-windows-powershell


Stef

On 2026-01-26 10:12, Nicola wrote:

I think it's a good idea: should we name it xymon-client-win-ps?
The idea is xymon-<type>-<os>-<language> so we can have some uniformity if more come

Nicola

Il giorno 26 gennaio 2026, alle ore 08:39, Stef Coene <xymon@xymon.com <mailto:xymon@xymon.com>> ha scritto:

Hi,

I create a private github repository and tried to merge all the changes I made to the Windows Powershell client.

But I realised it is better to create a repo in https://github.com/ xymon-monitoring/ with v2.42 from https://sourceforge.net/p/xymon/ code/HEAD/tree/sandbox/WinPSClient/.
Then I can fork that repo and add my changes.


So is it ok if I create a XymonPSClient repository and add client v2.42 to it?


Stef

list Stef Coene · Tue, 27 Jan 2026 12:03:40 +0100 ·

Hi,

I didn't realised that the sandbox directory was also copied.
So no, an other repo is not needed.

And thanks for the chatgpt commands :)


Stef

▸ quoted from Bruno Manzoni


On 2026-01-27 10:20, Bruno Manzoni via Xymon wrote:

Hi Stef,
Seem to me that it is already archive at
https://github.com/xymon-monitoring/xymon-svn-mirror/tree/sandbox/
Do you think we need more ?

Below the process to import it (Chatgpt: check!)
Let me know if you want me to do it
Bruno

Chatgpt: Here is the clean, standard way to do it, without rewriting history.

*Goal*: copy |sandbox/WinPSClient| from |xymon-svn-mirror| into
|xymon-client-windows-powershell|.


      Steps


 1.

    Clone the new repo

|git clone https://github.com/xymon-monitoring/xymon-client-windows- powershell cd xymon-client-windows-powershell |

 2.

    Add the svn mirror as a temporary remote

|git remote add svn-mirror https://github.com/xymon-monitoring/xymon- svn-mirror git fetch svn-mirror |

 3.

    Extract only the folder you want

|git checkout svn-mirror/master -- sandbox/WinPSClient |

 4.

    Move contents to repo root (recommended)

|mv sandbox/WinPSClient/* . rm -rf sandbox |

 5.

▸ quoted from Bruno Manzoni


    Commit

|git add . git commit -m "Import WinPSClient from xymon svn mirror" |

6.

▸ quoted from Stef Coene


    Push

|git push origin main |


      Result

  • Clean new repo

  • Correct history point-in-time

  • No svn noise

  • Easy to evolve independently

This is the right approach for a client split.


Le 27.01.2026 à 09:41, Stef Coene a écrit :

Hi,

I think it's a good idea to keep the sourceforge version data 'as is' for archival purposes.
Can you also create a xymon-client-windows-powershell-sourceforge repository?
I will upload the sourceforge version and then this repository can be archived.


Stef

On 2026-01-27 07:22, Bruno Manzoni via Xymon wrote:

Hi Nicola, hi Stef,

Following our chat, I created a repo named *xymon-client-windows- powershell*.

Looks OK to me.

Bruno


Le 26.01.2026 à 11:41, Stef Coene a écrit :

Hi,

I don't know how many clients are not natively supported.
The Powershell Windows client is one, maybe Mac?

So for this one:
xymon-client-windows-powershell


Stef

On 2026-01-26 10:12, Nicola wrote:

I think it's a good idea: should we name it xymon-client-win-ps?
The idea is xymon-<type>-<os>-<language> so we can have some uniformity if more come

Nicola

Il giorno 26 gennaio 2026, alle ore 08:39, Stef Coene <xymon@xymon.com <mailto:xymon@xymon.com>> ha scritto:

Hi,

I create a private github repository and tried to merge all the changes I made to the Windows Powershell client.


But I realised it is better to create a repo in https:// github.com/ xymon-monitoring/ with v2.42 from https:// sourceforge.net/p/xymon/ code/HEAD/tree/sandbox/WinPSClient/.

▸ quoted from Stef Coene

Then I can fork that repo and add my changes.


So is it ok if I create a XymonPSClient repository and add client v2.42 to it?


Stef

list Bruno Manzoni · Tue, 27 Jan 2026 12:29:29 +0100 ·

Hi Stef,

I have also started a short tutorial on setting up Git and GitHub:
https://github.com/xymon-monitoring/xymon/pull/13

It was initially written for my own use, as I mainly work with basic Git workflows, and writing it helped me consolidate my understanding.

The content is intentionally concise, practical, and easy to follow.
If it can help you or others, that is a plus; in any case, it was already useful for me.

Please note that it may contain some errors...

Bruno

▸ quoted from Stef Coene


Le 27.01.2026 à 12:03, Stef Coene a écrit :

Hi,

I didn't realised that the sandbox directory was also copied.
So no, an other repo is not needed.

And thanks for the chatgpt commands :)


Stef

On 2026-01-27 10:20, Bruno Manzoni via Xymon wrote:

Hi Stef,
Seem to me that it is already archive at
https://github.com/xymon-monitoring/xymon-svn-mirror/tree/sandbox/
Do you think we need more ?

Below the process to import it (Chatgpt: check!)
Let me know if you want me to do it
Bruno

Chatgpt: Here is the clean, standard way to do it, without rewriting history.

*Goal*: copy |sandbox/WinPSClient| from |xymon-svn-mirror| into
|xymon-client-windows-powershell|.


      Steps

 1.

    Clone the new repo

|git clone https://github.com/xymon-monitoring/xymon-client-windows- powershell cd xymon-client-windows-powershell |

 2.

    Add the svn mirror as a temporary remote

|git remote add svn-mirror https://github.com/xymon-monitoring/xymon- svn-mirror git fetch svn-mirror |

 3.

    Extract only the folder you want

|git checkout svn-mirror/master -- sandbox/WinPSClient |

 4.

    Move contents to repo root (recommended)

|mv sandbox/WinPSClient/* . rm -rf sandbox |

 5.

    Commit

|git add . git commit -m "Import WinPSClient from xymon svn mirror" |

 6.

    Push

|git push origin main |


      Result

  • Clean new repo

  • Correct history point-in-time

  • No svn noise

  • Easy to evolve independently

This is the right approach for a client split.


Le 27.01.2026 à 09:41, Stef Coene a écrit :

Hi,

I think it's a good idea to keep the sourceforge version data 'as is' for archival purposes.
Can you also create a xymon-client-windows-powershell-sourceforge repository?
I will upload the sourceforge version and then this repository can be archived.


Stef

On 2026-01-27 07:22, Bruno Manzoni via Xymon wrote:

Hi Nicola, hi Stef,

Following our chat, I created a repo named *xymon-client-windows- powershell*.

Looks OK to me.

Bruno


Le 26.01.2026 à 11:41, Stef Coene a écrit :

Hi,

I don't know how many clients are not natively supported.
The Powershell Windows client is one, maybe Mac?

So for this one:
xymon-client-windows-powershell


Stef

On 2026-01-26 10:12, Nicola wrote:

I think it's a good idea: should we name it xymon-client-win-ps?
The idea is xymon-<type>-<os>-<language> so we can have some uniformity if more come

Nicola

Il giorno 26 gennaio 2026, alle ore 08:39, Stef Coene <xymon@xymon.com <mailto:xymon@xymon.com>> ha scritto:

Hi,

I create a private github repository and tried to merge all the changes I made to the Windows Powershell client.

But I realised it is better to create a repo in https:// github.com/ xymon-monitoring/ with v2.42 from https:// sourceforge.net/p/xymon/ code/HEAD/tree/sandbox/WinPSClient/.
Then I can fork that repo and add my changes.


So is it ok if I create a XymonPSClient repository and add client v2.42 to it?


Stef

list Stef Coene · Wed, 28 Jan 2026 10:41:33 +0100 ·

Hi,

Just a small poll.

- Is anyone using xymon.ps1 to send data to the Xymon server?

- Who is using the Powershell client and in what kind of setup?
What are the issues and special stuff?


I monitor 800 Windows servers and have around 60 Xymon instances.

2 of the Windows servers are still running bbwin since they don't have the required Powershell installed.

The communication is mostly via https (xymoncgimsg.cgi) so it's encrypted. This is directly to the Xymon server or via internet (reverse proxy that forwards the data internally to the correct Xymon server).
All the communication is protected with username & password.

We manage everything from the Xymon server.
We wrote a script that generates the xml configuration file based on ini-files downloaded from the xymon server. This enables centralised management of the client configuration.

We also wrote a script that checks if a MSSQL server is running and if yes, it will download a MSSQL check script and runs it.
We are expanding this to Veeam.


Stef

list Neil Simmonds · Wed, 28 Jan 2026 09:57:13 +0000 ·

I've used the powershell client and found it a significant improvement on the bbwin client.

I'm down to 26 windows servers now but I also use central configuration on these and can't say I've had any problems. We've used quite a lot of custom tests and rolling those out using the central config is so easy. Unfortunately, due to a takeover of the Company Xymon is in decline and will disappear this year.

Real shame as I've really enjoyed using it over the years. I may yet install it on my homelab but that will be all Linux.

Neil Simmonds

Senior Platform & Middleware Engineer (Unix)

PHONE

0344 245 9200

ADDRESS

Unit A Brook Park East, NG20 8RY

Credit is provided by Frasers Group Financial Services Limited (Registered Company no. 00718151), which is authorised and regulated by the Financial Conduct Authority (FRN 311908) for consumer credit and general insurance and a member of the Finance and Leasing Association. Frasers Group Financial Services Limited is registered in England and its registered office is: Express House, Petre Road, Clayton Business Park, Accrington, Lancashire, BB5 5JB. For regulated payment services, Frasers Group Financial Services Limited is a payment agent of Transact Payments Limited, a company authorised and regulated by the Gibraltar Financial Services Commission as an electronic money institution. Transact Payments Limited, a company incorporated in Gibraltar (No 108217). Registered address 6.20 World Trade Center, 6 Bayside Road, Gibraltar, GX11 1AA.

Disclaimer | Frasers Group

▸ quoted from Stef Coene

-----Original Message-----
From: Stef Coene <user-dbffe946c0f4@xymon.invalid>
Sent: 28 January 2026 09:42
To: Xymon mailinglist <xymon@xymon.com>
Subject: [Xymon] Re: XymonPSClient repository

Hi,

Just a small poll.

- Is anyone using xymon.ps1 to send data to the Xymon server?

- Who is using the Powershell client and in what kind of setup?
What are the issues and special stuff?

I monitor 800 Windows servers and have around 60 Xymon instances.

2 of the Windows servers are still running bbwin since they don't have the required Powershell installed.

The communication is mostly via https (xymoncgimsg.cgi) so it's encrypted. This is directly to the Xymon server or via internet (reverse proxy that forwards the data internally to the correct Xymon server).
All the communication is protected with username & password.

We manage everything from the Xymon server.
We wrote a script that generates the xml configuration file based on ini-files downloaded from the xymon server. This enables centralised management of the client configuration.

We also wrote a script that checks if a MSSQL server is running and if yes, it will download a MSSQL check script and runs it.
We are expanding this to Veeam.

Stef

To unsubscribe send an email to xymon-leave@xymon.com

Attachments (1)

fgfs_e04c0205-c635-4f54-817e-d1a70ae03721.jpg image/jpeg · 13.3 KB

list Scot Kreienkamp · Wed, 28 Jan 2026 14:04:34 +0000 ·

I've used it previously in a number of Windows servers. Right now I only have a few in use, but I expect that to expand in the future.

▸ quoted from Stef Coene

-----Original Message-----
From: Stef Coene <user-dbffe946c0f4@xymon.invalid>
Sent: Wednesday, January 28, 2026 4:42 AM
To: Xymon mailinglist <xymon@xymon.com>
Subject: [Xymon] Re: XymonPSClient repository

Hi,

Just a small poll.

- Is anyone using xymon.ps1 to send data to the Xymon server?

- Who is using the Powershell client and in what kind of setup?
What are the issues and special stuff?

I monitor 800 Windows servers and have around 60 Xymon instances.

2 of the Windows servers are still running bbwin since they don't have
the required Powershell installed.

The communication is mostly via https (xymoncgimsg.cgi) so it's
encrypted. This is directly to the Xymon server or via internet (reverse
proxy that forwards the data internally to the correct Xymon server).
All the communication is protected with username & password.

We manage everything from the Xymon server.
We wrote a script that generates the xml configuration file based on
ini-files downloaded from the xymon server. This enables centralised
management of the client configuration.

We also wrote a script that checks if a MSSQL server is running and if
yes, it will download a MSSQL check script and runs it.
We are expanding this to Veeam.

Stef

To unsubscribe send an email to xymon-leave@xymon.com

This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.

Attachments (1)

lazboy_2024_inc_navy_4a4d68ec-613a-4141-a2aa-d73a2ae749f6.png image/png · 4.3 KB

list Kris Springer · Wed, 28 Jan 2026 07:46:17 -0700 ·

Yes, I use the Windows ps1 client a lot, also for many client networks. We use the SSL version when possible, but it would be great if that was the default and was baked into Xymon as the official Windows client.

https://krisspringer.com/posts/xymon-ps-client-over-ssl.php

Thank You,

Kris Springer

Systems Admin

I/O Network Administration

---- On Wed, 28 Jan 2026 02:41:33 -0700 user-dbffe946c0f4@xymon.invalid wrote ----

list Stef Coene · Wed, 28 Jan 2026 19:54:24 +0100 ·

Hi,

It's rather high on my TODO list to make xymoncgimsg.cgi a part of the default installation for xymon.
I already have made most of the changes on my local xymon branch for this.
Including wget and curl version for the *nix clients to enable https for communication.


Stef

▸ quoted from Scot Kreienkamp


On 2026-01-28 15:46, I/O Network Administration wrote:

Yes, I use the Windows ps1 client a lot, also for many client networks. We use the SSL version when possible, but it would be great if that was the default and was baked into Xymon as the official Windows client.
https://krisspringer.com/posts/xymon-ps-client-over-ssl.php

Thank You,
Kris Springer
Systems Admin
I/O Network Administration

---- On Wed, 28 Jan 2026 02:41:33 -0700 *user-dbffe946c0f4@xymon.invalid * wrote ----

Hi,

Just a small poll.

- Is anyone using xymon.ps1 to send data to the Xymon server?

- Who is using the Powershell client and in what kind of setup?
What are the issues and special stuff?

I monitor 800 Windows servers and have around 60 Xymon instances.

2 of the Windows servers are still running bbwin since they don't have
the required Powershell installed.

The communication is mostly via https (xymoncgimsg.cgi) so it's
encrypted. This is directly to the Xymon server or via internet
(reverse
proxy that forwards the data internally to the correct Xymon server).
All the communication is protected with username & password.

We manage everything from the Xymon server.
We wrote a script that generates the xml configuration file based on
ini-files downloaded from the xymon server. This enables centralised
management of the client configuration.

We also wrote a script that checks if a MSSQL server is running and if
yes, it will download a MSSQL check script and runs it.
We are expanding this to Veeam.

Stef

list Stef Coene · Thu, 29 Jan 2026 12:22:18 +0100 ·

Hi,

I just pushed a commit to my repo to integrate xymoncgimsg.cgi:
https://github.com/StefCoene/xymon/commit/33894b55979c2e738e42a7f5ccf546fc4686122b

Some documentation:
https://github.com/StefCoene/xymon/wiki/xymoncgimsg

The concept of this is running without issues in production for years (Linux/AIX/Windows).
I rewrote the scripts and integrated it in configure and the Makefiles.
In principle, it should work fine, but I don't have the time to test it in detail on a new deploy because I'm going offline for a few days to enjoy some free time this weekend.


Stef

▸ quoted from Stef Coene


On 2026-01-28 19:54, Stef Coene wrote:

Hi,

It's rather high on my TODO list to make xymoncgimsg.cgi a part of the default installation for xymon.
I already have made most of the changes on my local xymon branch for this.
Including wget and curl version for the *nix clients to enable https for communication.


Stef

list Jaime Kikpole · Thu, 29 Jan 2026 13:30:51 -0500 ·

I use the PowerShell client on all our Windows VMs and bare iron installs, excluding end user workstations. I believe that is 17 devices. I've used it for years and across two jobs.

Jaime Kikpole

Director of Technology
Ichabod Crane Central School District
(XXX) XXX-XXXX, x5425

▸ quoted from Stef Coene

On Wed, Jan 28, 2026 at 4:41 AM Stef Coene <user-dbffe946c0f4@xymon.invalid> wrote:

Hi,

Just a small poll.

- Is anyone using xymon.ps1 to send data to the Xymon server?

- Who is using the Powershell client and in what kind of setup?
What are the issues and special stuff?

I monitor 800 Windows servers and have around 60 Xymon instances.

2 of the Windows servers are still running bbwin since they don't have
the required Powershell installed.

The communication is mostly via https (xymoncgimsg.cgi) so it's
encrypted. This is directly to the Xymon server or via internet (reverse
proxy that forwards the data internally to the correct Xymon server).
All the communication is protected with username & password.

We manage everything from the Xymon server.
We wrote a script that generates the xml configuration file based on
ini-files downloaded from the xymon server. This enables centralised
management of the client configuration.

We also wrote a script that checks if a MSSQL server is running and if
yes, it will download a MSSQL check script and runs it.
We are expanding this to Veeam.

Stef
xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com

list Bruno Manzoni · Fri, 30 Jan 2026 07:01:42 +0100 ·

I also use it on server and worstation
- See my setup at: https://github.com/bonomani/Xymon-powershell-client-with-Windows-updates-centrally-managed
Bruno

▸ quoted from Jaime Kikpole

Le 29.01.2026 à 19:30, Jaime Kikpole via Xymon a écrit :

I use the PowerShell client on all our Windows VMs and bare iron installs, excluding end user workstations. I believe that is 17 devices. I've used it for years and across two jobs.

Jaime Kikpole

Director of Technology
Ichabod Crane Central School District

(518) 758-7575, x5425

▸ quoted from Stef Coene

On Wed, Jan 28, 2026 at 4:41 AM Stef Coene <user-dbffe946c0f4@xymon.invalid> wrote:

Hi,

Just a small poll.

- Is anyone using xymon.ps1 to send data to the Xymon server?

- Who is using the Powershell client and in what kind of setup?
What are the issues and special stuff?

I monitor 800 Windows servers and have around 60 Xymon instances.

2 of the Windows servers are still running bbwin since they don't have
the required Powershell installed.

The communication is mostly via https (xymoncgimsg.cgi) so it's
encrypted. This is directly to the Xymon server or via internet (reverse
proxy that forwards the data internally to the correct Xymon server).
All the communication is protected with username & password.

We manage everything from the Xymon server.
We wrote a script that generates the xml configuration file based on
ini-files downloaded from the xymon server. This enables centralised
management of the client configuration.

We also wrote a script that checks if a MSSQL server is running and if
yes, it will download a MSSQL check script and runs it.
We are expanding this to Veeam.

Stef
xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com
xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com

list Becker Christian · Fri, 30 Jan 2026 11:54:08 +0000 ·

Hi to the list,

in our prod environment we're using XymonPSClients, running different windows server and client systems (actually ~150), talking to Xymon 4.3.30.
The amount of windows systems is going to grow, since we have some older installations running BBWin and we want to replace them.
On most of the windows systems running with XymonPSClient we are using additional (self-made) scripts for additional use.

Running xymon and working with it since 2008, containing ~1000 systems reporting to it (xymon clients, windows clients, snmp devices).

Looking forward to use XymonPSClient in the future!

Regards
Christian

▸ quoted from Bruno Manzoni



===================================================================


Hi,

Just a small poll.

- Is anyone using xymon.ps1 to send data to the Xymon server?

- Who is using the Powershell client and in what kind of setup?
What are the issues and special stuff?


I monitor 800 Windows servers and have around 60 Xymon instances.

2 of the Windows servers are still running bbwin since they don't have the required Powershell installed.

The communication is mostly via https (xymoncgimsg.cgi) so it's encrypted. This is directly to the Xymon server or via internet (reverse proxy that forwards the data internally to the correct Xymon server).
All the communication is protected with username & password.

We manage everything from the Xymon server.
We wrote a script that generates the xml configuration file based on ini-files downloaded from the xymon server. This enables centralised management of the client configuration.

We also wrote a script that checks if a MSSQL server is running and if yes, it will download a MSSQL check script and runs it.
We are expanding this to Veeam.


Stef

XymonPSClient repository 🔗 link

Steps

Result

XymonPSClient repository