Windows Server 2019 and .NET 4.8?
Hello, On a fully updated Windows Server 2019, roles and features allow me to install only .NET 4.7. One of the solution we are using require .NET 4.8 (Adaxes). When I install .NET 4.8 using the installer available here https://support.microsoft.com/en-us/topic/microsoft-net-framework-4-8-offline-installer-for-windows-9d23f658-3b97-68ab-d013-aa3c3e7495e0 It works, I can install Adaxes, but it break ServerManager as well as Azure AD Connect. What's the correct procedure to install .NET 4.8 on Server 2019 without breaking anything else? Thanks a lot
Is there a way to set different TLS cipher suites as server and as client separately?
Hi, I have an ASP .Net app hosted on IIS, Windows Server. The app needs to call external web APIs. For the app, I would like to set only a few secure TLS cipher suites as a server, but the app needs to use other (not so secure) cipher suites as a client for the external APIs. https://docs.microsoft.com/en-us/windows-server/security/tls/manage-tls configuration works for both of server and client. Is there a way to set different TLS cipher suites as server and as client separately?Windows Server vNext - TLS improvements, make TLS 1.2 the minimum standard for different areas.
Hi Server Team, it is great to see that Server vNext has enabled only TLS 1.2 and TLS 1.3 left experimental state in Internet Options (Windows System / IE) However the remark from AriaUpdated Changes to improve security for Windows devices scanning WSUS - Microsoft Tech Community does not yet match completely / consistently in Server vNext (not even speaking about productive release as 1607 and later) I would like to plea for following changes: 1. Server vNext should enable TLS 1.2 for PowerShell 5.1. Currently it is not enabled by default an so blocking access to repositories as github, PSget, nuGet etc 2. Upgrading WSUS to Server 2022 should enable TLS for WSUS by default (I know there are no GUI or wizard changes) 3. Server vNext should enable TLS 1.2 for SQL and .net by default 4. Server vNext should use TLS 1.2 for SChannel. Every supported OS (including domain controllers) support this. You should consider to disable TLS 1.0 / 1.1 for each of these Mary Hoffman Currently I am deploying actively these changes in mixed custmer enviroments using script / GPOs ranging from Server 2008-2019, SQL 2012-2019, Exchange 2013-2019, and do not face issues that cannot mitigated. However I would expect the standards to be higher with Server 2022 in compliance with what Aria stated. Thanks for your feedback
How to enable ASP.NET 4.8 on Windows Server 2016
Hello All, I have installed on my server as bellow: + Windows Server 2016 Standard Evaluation 64 bit + IIS 10 version 1607 - OS build 14393.693 + .NET Framework 4.8 - Release DWORD: 528049 Everything will be simple when I may enable ASP.NET 4.8; but I didn't see this option here. (There is only ASP.NET 4.6) May I enable ASP.NET 4.8 on above Windows Server 2016? Thanks in advance, Nguyen Duc Hoa
