Guidance on disabling system services on windows server 2019
I am looking for recommended system services that should be or ok to disable in windows server 2019. Earlier last week i saw that the following link has a note that it applies to windows server 2019 as well but today it is changed to only applies to windows server 2016 with desktop experience and some of the services recommendation is changed from ok to disable to no guidance. for example: CNG Key Isolation COM+ Event System COM+ System Application https://docs.microsoft.com/en-us/windows-server/security/windows-services/security-guidelines-for-disabling-system-services-in-windows-server Does someone know where can i find the final guidance for 2019 server?
After Windows 2019 CU KB5012647, enabling IIS automatic rebind of renewed certificates gets an error
Hello everyone, after installing the KB5012647 cumulative update on a Windows Server 2019 it seems no longer possible to enable the IIS function "automatic rebind of renewed certificates". I get this error: Error occurred when trying to register automatic rebinding of certificate. Details: The process creation has been blocked Any hint ? Thank you Riccardo
Issues with Remote Desktop Web Client (HTML5)
Hey all, I'm having a strange issue after implementing the Remote Desktop HTML 5 Client for one of our RDS instances. Everything is working up until the actual act of opening an application which we then receive the following error: We have performed all of the verification steps to ensure that the set up is configured correctly and haven't had any issues out of other RDS instances with the same set up. Below is a list of everything that we have verified: The RDS server (singular server, running all RDS roles) is Server 2019 and is entirely up to date with Windows Updates. The public trusted certificates are configured correctly. Licensing is set to per-user client access, not device level. Verified that the RDS server's NPS is registered with Active Directory. Reviewed all appropriate connection and authorization access policies, verified that these are looking great. We receive this error when attempting to access locally using the FQDN as well as externally over the internet as well. When performing a log capture we can see the following error: 2022-12-22T20:01:12.622Z WebSocketTransport(ERR): WebSocket error received for url=wss://removed.for.confidentiality:443/remoteDesktopGateway?CorId=%7B9ca382bc-96b8-444e-b22c-3e5cbc370000%7D&ConId=%7B299f9980-d47f-44e9-86e7-479750c95ab4%7D&ClGen=HTML%3D1&ClBld=Type%3DRdClient%3B%20Build%3Dprivate&AuthS=SSPI_NTLM websockettransport.cpp(304): OnErrorFromJS() Does anyone have any ideas or have ran into this issue before? The results online are very scarce and every recommendation that has worked for other doesn't appear to work in our case. Assistance would be greatly appreciated!
Outlook 2021 Phänomen in Verbindung mit Server 2019 und FSLogix
Guten Tag Liebe Community, ich habe hier aktuell einen Fall der mich Haare verlieren lässt. Zur Umgebung: RDS-Umgebung mit FSLogix (Funktioniert an sich Super!) FSLogix: Aktuelle Version (2.9.8171.14983) Windows Server 2019 komplett durchgepatcht (Komplette Umgebung ist WS2019) 3x Terminalserver Office LTSC 2021 aktueller Patch (16.0.14332.20279) 32bit (32bit wird benötigt wegen DATEV) Exchange Online User Arbeiten ausschließlich auf den RDS Hosts -> Client Computer sind Intel NUCs und ThinClients (Alles Win10) Zum Problem: Haben letztens ein Upgrade von Office 2016 auf 2021 bekommen. Ich also: Office 2016 mittels OffScrub Tool deinstalliert und Office 2021 installiert mithilfe des Office Bereitstellungstools. Office funktioniert, nur Outlook nicht zu 100%. Hier haben wir folgendes Problem: Viele User bekommen keine Verbindung zu ihrem Postfach -> Outlook versucht die Moderne Auth. zu öffnen und bekommt das nicht hin, das Fenster schließt sich direkt. Ich habe schon etliches Versucht: EnabelADAL 1/0 WAMOverride... etc., div. Tools seitens MS ausgeführt und und und. Bei der Basis Auth. kommt man sogar in einen Login-Loop. Wenn man ein neues Outlook Profil anlegt, schafft Outlook es nicht mal in die Cloud zu verbinden. "Es konnte keine Sichere Verbindung hergestellt werden" Witzig: wenn man die @x.onmicrosoft.com Adresse nimmt, geht das ganze -> man kann sich da einiges hintricksen -> Ist aber absolut nicht Sinn der Sache und führt letztendlich wieder in die selbe Problematik. Ich habe dann die Userprofile Neuangelegt -> Outlook läuft -> Aber nur auf einem der 3 Terminalservern, auf welchem Outlook aktuell Funktioniert ist reines Glück. Hat hier wer Erfahrung, eventuell sogar das selbe Problem gehabt oder hat mir einen Tipp welche Einstellungen ich noch Prüfen kann? Ich danke Vorab!!! Ich habe hier schon etliche Zeit verbracht und sehe vor lauter Bäumen den Wald nicht mehr.
VBox: Remote Management / Add Roles & Features: The WS-Management service cannot process the request
Hello, I have installed Windows Server 2019 in a VirtualBox 6.1 machine. In the Server Manager I want to activate remote management and install roles like AD DS, but these error messages appear: Local Server \ Remote Management: "The WS-Management service cannot process the request because the XML is invalid." Add Roles and Features: "The WS-Management service cannot process the request. The service in configured to not accept any remote shell requests." I have created the VirtualBox virtual machine as "Windows 2016" and tried several options like EFI, I/O APIC, PAE/NX, nested VT-x, nested paging, NAT, bridged adapter. In the Local Group Policy Editor (Windows Server virtual machine), I have manually enabled "Allow Remote Shell Access" in Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Shell and run gpupdate /force. I have also installed Windows Server in VirtualBox on two other computers, but the same problem appears. I hope anyone can help me solve this problem. What has to be configured to make the WS-Management service work correctly?Windows Server 2022 as Domain and DHCP Server
Hi, Windows Server 2022 announced. There are many IT Executives or Organizations who use Windows Server only for DNS Server, DHCP Server, managing network resources and implementing group policies. For this purpose, if we compare Windows Server 2012R2, Windows Server 2016, Windows Server 2019 and Windows Server 2022; can we find any differences? Moreover, for those executives or organizations, does it matter Windows Server 2022 announced? Please let us know differences in Windows Server from above perspectives. With Regards NndnG
FIle replication Refs file system
We have 2 windows server 2019 based file server We'd like to replicate folder between them with DFS Replication Groups but when trying to set up the replica for a folder we got the error that the path is not on NTFS, is actually REFS, and so it fails . Is refs still not supported for replica on windows 2019 ? Is there a way to overcome such limitation ? thanks
