It is possible that my answer is inappropriate. I simply ask you to take a deep look into the kernel model of Win 2025 and then do the same with a modern LINUX kernel. Keywords threading, garbage, and much more. Once you have really looked into it in depth, you will automatically decide to use Windows kernels for databases, eDir, GroupWise and others as long as it is not a native DB from MS, where ms sql now runs on LINUX. There may be reasons to rely on Win, but even with a plain core installation of Win there is still so much baggage that really costs resources.
As I said, this is just a technical statement about the two kernel models. Regarding the support of Win 2025 for GroupWise and eDir, please ask OT Support for an answer.

George

did you leave out a "not" somewhere in there, like ".... you will automatically decide NOT to use Windows kernels for databases..."?

it reads like you're advising against using Windows except for the missing word

my english sometimes plays tricks on me.

i mean

Databases, unless they are explicitly intended for Windows kernels, I would always use LINUX kernels. There are good comparisons between Win and LINUX kernels from very experienced developers. One thing that immediately comes to mind is what happens if a port cannot be reached on Win or Linux. LINUX gives an answer immediately, with Win it can take up to 2 seconds. This has a big impact on the behavior of the IP stack. with both oth IP protocol families. I don't want to go any deeper into the subject now,

I've just made a testinstallation on Win2025. From the running version 23.4 I copied the D-drive, where I keep all databases. Attached it to a new Win2025 server. Made an upgrade to GW 24.4. As far as I can tell, everything works fine.
As for the discussion Windows vs Linux, I've been running GW on Windows since Nt4.0 (GW 5.5). Never had a problem. It might be different on large installations though, We are under 100 users.

Good to hear. Thank you for your feedback!