locked
TCP Templates RRS feed

  • Question

  • Hello,
    We're migrating from Windows 2008 to Windows 2019. And previously we were using netsh commands to fine tune TCP performance, Windows 2019 seems to deprecate some of its features at least, thus TCP Templates should be used. But this brings a set of questions:

    The existing templates: "Datacenter", "Internet", "DatacenterCustom" and "InternetCustom", might be able to cover most ofthe cases, but the only way to explicitly control which template would be used for the particular destination is usage of New-NetTransportFilter PowerShell command, which works only in conjunction with Windows Firewall, which we don't use in our case, for the performance reasons.

    At the same time Windows seem to be able to apply those templates in some way(without Firewall enabled), but can't find any information on how it works and how to control/influence this process. There are cases where such automatic selection isn't optimal, yet no way to amend specific significant properties of a given template (MinRto(ms) or DelayedAckTimeout(ms) for instance).

    Is there a way to manage this feature?

    Thanks forward.

    Oleg
    Sunday, April 5, 2020 8:23 PM

All replies