dani
Goto Top

Introducing Windows Server 2025

Content-ID: 7351382034

Url: https://rootdb.com/en/introducing-windows-server-2025-7351382034.html

Printed on: February 22, 2025 at 16:02 o'clock

mossox
mossox Jan 27, 2024 at 10:52:34 (UTC)
Goto Top
I can't even begin to understand the euphoria.
Has Ms. reinvented the wheel or what?
Lochkartenstanzer
Lochkartenstanzer Jan 27, 2024 updated at 10:57:48 (UTC)
Goto Top
Zitat von @mossox:

I can't even begin to understand the euphoria.
Has Ms. reinvented the wheel or what?

Another unfinished product on the market that only matures with the customer and when it becomes suitable, it is replaced by a new Dasch that washes even whiter than white new unfinished product.

lks
MysticFoxDE
MysticFoxDE Jan 27, 2024 updated at 11:42:31 (UTC)
Goto Top
ad und smb

So as for the new AD level, it was more than overdue and so much for the topic of the local AD supposedly being dead. 😁
However, I find it rather less funny that these Microsoftians have been fiddling with the SMB again, which will certainly cause a lot of trouble, especially at the beginning. 😬
Lochkartenstanzer
Lochkartenstanzer Jan 27, 2024 at 11:44:36 (UTC)
Goto Top
Zitat von @MysticFoxDE:

ad und smb

So as for the new AD level, it was more than overdue and so much for the topic of the local AD supposedly being dead. 😁
However, I find it rather less funny that these Microsoftians have been fiddling with the SMB again, which will certainly cause a lot of trouble, especially at the beginning. 😬

Somehow you have to seal yourself off from the functioning alternatives. face-smile
StefanKittel
StefanKittel Jan 27, 2024 updated at 13:28:41 (UTC)
Goto Top
Hi,

for me, the last really cool features at MS were:

  • FAT32 - Finally more than 2GB per partition and no more questions about whether certain data is on G or J.
  • IPv6
  • End of SBS2011
  • 64Bit

Stefan
Dani
Dani Jan 27, 2024 updated at 16:30:21 (UTC)
Goto Top
Moin,
I can't even begin to understand the euphoria.

I think the changes to AD are very sensible. Much of it makes sense for any environment: https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/whats-ne ...

In the Hyper-V area, thin provisioning, cluster-aware updating and ReFS are a very good start to gradually catch up with VMware.

Regards,
Dani
MysticFoxDE
MysticFoxDE Jan 27, 2024 at 18:11:43 (UTC)
Goto Top
Moin @Dani,

ReFS

The servers have been able to do this for a while, but I would be more careful with CSVs.

Warum ihr keine ReFS Formatierung für CSVs verwenden solltet, die von einem SAN bereitgestellt werden

Regards Alex
Dani
Dani Jan 27, 2024 at 19:11:11 (UTC)
Goto Top
Hi,
The servers have been able to do this for a while, but I would be more careful with CSVs.

My mistake. I always forget that often only half of my links are read in full. Even though this time there are videos in them. face-wink ReFS has got a native deduplication feature.

Regards
Dani
rickstinson
rickstinson Jan 27, 2024 at 20:50:06 (UTC)
Goto Top
Hot patching sounds nice, so without reboots, did I understand that right? When SRV2025 is out, I'll slowly make the 2019 to 2022. Being a major version behind has always made sense with MS.
em-pie
em-pie Jan 28, 2024 at 08:41:15 (UTC)
Goto Top
Hi,

I'm curious.

Here is a first Heise article:
Name steht fest: Microsoft plant Windows Server 2025
MysticFoxDE
MysticFoxDE Jan 28, 2024 updated at 09:20:24 (UTC)
Goto Top
Hi @Dani,

The servers have been able to do this for a while, but I would be more careful with CSVs.
My mistake. I always forget that often only half of my links are read in full. Even though this time there are videos in them. face-wink ReFS has got a native deduplication feature.

Yes, and "native deduplication and compression" doesn't really solve the problem I described.
So you should be careful with CVS running against a SAN with ReFS even with Server 2025, unless they also run in “direct mode” with it, which I can't imagine at the moment.

Regards Alex
Th0mKa
Th0mKa Jan 28, 2024 at 11:00:02 (UTC)
Goto Top
Quote from @rickstinson:

Hot patching sounds nice, so without reboots, have I understood that correctly?

Yes and no. Currently (with Server 2022 Azure Edition), there are four patches per year that require a reboot, and the other eight can be applied without. It cannot be ruled out that the number of baseline patches will be reduced, but that will only become apparent with the release.

This is how it works.
/Thomas
Lochkartenstanzer
Lochkartenstanzer Jan 28, 2024 at 11:35:03 (UTC)
Goto Top
Quote from @Th0mKa:

Quote from @rickstinson:

Hot patching sounds nice, so without reboots, have I understood that correctly?

Yes and no. Currently (with Server 2022 Azure Edition), there are four patches per year that require a reboot, and the other eight can be applied without. It cannot be ruled out that the number of baseline patches will be reduced, but that will only become apparent with the release.

This is how it works.

/Thomas


Hi,

But you should still keep the old support motto “A reboot will do you good!” in the back of your mind. face-smile

lks
rzlbrnft
rzlbrnft Jan 30, 2024 updated at 08:47:23 (UTC)
Goto Top
Well, I waited until 2019.

Quote from @rickstinson:
Hot patching sounds nice, so without reboots, did I understand that right? When SRV2025 is out, I'll slowly make the 2019 to 2022. Being a major version behind has always made sense with MS.

This is actually a feature that would make me switch to 2025 right away. An update without a reboot would be really nice, but it's questionable whether it would do what it's supposed to.