@bobbyk18 We have not defined the dates when Transport throttling /
blocking would start taking those actions on Exchange 2016 / 2019. We
will define this, but it has not been done yet. Remember, this
(transport throttling / blocking) is not really a way to "enforce
installation of every update" rat...
@Nino_Bilic I guess that makes me wonder why it would take almost a year
for SE RTM to come out after 2019 CU15 (H2 CY 2024 for 2019 CU15 vs
Early H2 CY 2025 for SE RTM), if they're mostly identical. Like I said,
I think the plan is well-documented, but there's not much room for
something to go wron...
As I understand it, Exchange SE RTM bits will be identical to Exchange
2019 CU15 (plus post CU15 release SU's if applicable) bits with these
exceptions: "The License agreement, an RTF file shown only in the GUI
version of Setup, will be updated.The name will change from Microsoft
Exchange Server 201...
@bobbyk18 I hear what you are saying if you consider Exchange SE RTM >
October 14, 2025 (when E2016/E2019 go out of support) - however, does
the fact that we have zero features in RTM when compared to Exchange
2019 CU15 not give organizations "time"? This is exactly why Exchange SE
RTM has zero feat...
@Nino_BilicThanks for your reply. I wasn't able to find any issues with
procmon. The app writes all the performance monitor and event log files
to the Jetstress directory but fails to create the report, so I don't
think it's a permission error. I reinstalled the system with the English
ISO file and ...
Latest Comments