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 mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com

---

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

---

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

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 |

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 :

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 mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com

---

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

---

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

---

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

---

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

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

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 > _______________________________________________ > Xymon mailing list -- xymon@xymon.com > To unsubscribe send an email to xymon-leave@xymon.com

---

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

---

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

---

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

---

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

---

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

---

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

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

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 *stef.coene@docum.org * 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 mailing list -- xymon@xymon.com <mailto:xymon@xymon.com>
To unsubscribe send an email to xymon-leave@xymon.com <mailto:xymon-
leave@xymon.com>

---

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

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

On Wed, Jan 28, 2026 at 4:41 AM Stef Coene <stef.coene@docum.org> 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 mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com

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

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

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 mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com