windows server 2019
38 TopicsNo way of running OneDrive on Windows Server 2019?
I'm running an instance of Windows Server 2019 on Amazon AWS, and need to sync some files. Apparently Windows Server 2019 comes with no traces of OneDrive (even though the OneDrive webpage recognizes my web client as Windows 10 and assures me that it should be installed), so I'm trying to install the app manually. I've downloaded OneDriveSetup.exe (from onedrive.live.com), but the system ignores it when I try to run it, ie. nothing happens... I'm close to tear out my hair, what is happening?Solved120KViews0likes15CommentsGuidance 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?9.5KViews1like0CommentsAfter 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 Riccardo9.2KViews0likes5CommentsNew management experiences for Windows Server 2019 - Storage Migration Service and System Insights
First published on on Jun 20, 2018 The Extension manager within Windows Admin Center is a vehicle for our 3rd party partners to release extensions for their products and services, but also for Microsoft to release new management capabilities for Windows Server features in preview, enabling us to get early feedback and iterate quickly.7.6KViews0likes1CommentIssues 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!6KViews0likes5CommentsGuidance 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://techcommunity.microsoft.com/t5/microsoft-security-baselines/guidance-on-disabling-system-services-on-windows-server-2016/ba-p/701058 Does someone know where can i find the final guidance for 2019 server?Solved5.1KViews0likes3CommentsCannot reach/ping second 2019 server via Site-to-Site VPN, all other computers can be reached
Hi! I REALLY need help on this issue! Main office has: 192.168.1.0/24 Branch office: 192.168.2.0/24 i.e. two different subnets. DHCP is configured in the routers on each side; main/branch (i.e. no DHCP configured in the server). Main office has two Windows Server 2019: 1. Main server with AD, DNS, DC 2. Application server that is joined to domain and there are also clients in the main office: 3. Normal domain connected clients (Win10 and Win8) I can ping forth and back between all computers but when I try to ping from Branch to Main office towards the "2. Application Server" I don't get through. I have no probem to ping from Branch to "1. Main server" or towards normal clients in the "main network". If I ping "2. Application server" from any local computer on the Main office side, the server responds. Basic fault tracing tells me it's a server configuration thing versus the Branch network, something in the "2. Application server" stops the calls, right? I have checked the server's firewall (incoming ping) and also temporarely turned off the firewall, but no success. So firewall seems to be out of the question. I also added the branch's subnet in "1. Main server" under AD Services and Sites, no success. I really can't understand this magic going on in the second server, why doesn't it respond to calls from the Branch side? Please help! br /MarcusSolved4.4KViews0likes3CommentsInstall on Windos server 2019 RDS - Problem - blank
Hey, hello, everybody. I have a problem with installing Teams on Windows server 2019 RDS. We are currently using the server as a terminal server for 10 users. We have installed MS365, where the whole office suite is installed, but Teams is not. So I was solving the installation manually via a procedure: https://learn.microsoft.com/en-us/MicrosoftTeams/teams-for-vdi#deploy-the-teams-desktop-app-to-the-vm --> After installing and running MS Teams (new version), I was given the option to log in. After logging in, there was only a blank white screen. So I was solving the installation via: https://learn.microsoft.com/en-us/microsoftteams/msi-deployment Here it was a bit better, but after logging in and a long loading time I got an error cad0009 So I was solving via: https://learn.microsoft.com/en-us/microsoftteams/new-teams-bulk-install-client This gave me a message that the version was incompatible with the system. The last one was through the command: Dism /Online /Add-ProvisionedAppxPackage /PackagePath:<MSIX package path> /SkipLicense But the same problem as the first variation... How to get MS Teams for Windows server 2019 RDS (license - business standard ) Thanks a lot for your help... Bing failed me, it was not able to help me. Unfortunately neither ChatGPT.3.8KViews0likes0Comments