Searching further, I found this technet forum post in which the cause and solution are discussed.īasically, every time a user logs into the RDS server, a new set of firewall rules is created and are not removed when the users log off, but new ones are re-created when they login again. The system had only 6GB out of 128GB ram used and CPU (8 Cores) were at 2%
Windows terminal services 2016 install#
Trying to run the suggested PowerShell command failed and upon reviewing the AppPackage Log as suggested by the failure error I noticed that the package did not install because of insufficient resources. This led me to think there was an issue with Appx and came across some material that suggested repairing Cortana. When checking the event logs I noticed system events with ID 10001 like the one below The customer restarted the RDS host but the issue was not resolved. The question at hand that I am having trouble answering, is what are the mechanisms preventing the applications from accessing the memory, and how do you determine and configure what the limits are? I have read a great deal of Microsoft documentation about remote desktop, to no avail, so I am hoping someone in the community has more information than I do.A customer informed us that some users were getting a black screen after logon and others could not open the start menu after they got past the black screen. So the issue appears to be a graphics rendering issue, possible due to memory constraints. Doing some internet searches to see if I could find any documentation about this problem, I found several threads about similar issues running database and other memory intensive operations in remote desktop sessions, but no one seemed to have any resolutions.Īs far as the first issue, the freezing window while printing, we had considerable difficulty replicating the issue, because when doing admin on the server, I am logging in from a Debian Linux box, and it appears the issue only occurs when logged in locally.
Windows terminal services 2016 windows 10#
However, the same database application used on a standalone Windows 10 machine is running up to a gigabyte of memory, and performs much better. The server is running 12 cores with 32GB of RAM, but applications are showing maxed out and excessive paging with only a couple of hundred megabytes of memory usage. The second issue, discovered when troubleshooting the problem, and possibly related, is that once we configured the server to be a remote desktop server, it appears the server is limiting the amount of memory the applications can access.
The problem seems similar to that in the following: After considerable time wasted troubleshooting printers, it was determined that in fact the printing was actually successful, and the remote desktop would actually unfreeze if the window was minimized and then maximized. The first issue is that when the users try to print from the database, it appears that the remote desktop freezes up. The second issue was discovered while attempting to troubleshoot and diagnose the cause of the first issue. We are running into two problems, which may or may not be related. The application is a specialized database application from a third party vendor, and has no native network support, their only supported method of sharing the database to multiple workstation is via the terminal server. Initial configuration went smoothly, everyone can log in and access the required application.
Running a fresh install of Windows Server 2016 Remote Desktop server.
0 kommentar(er)
