Hi all, we have the following setup in our hosted environment:
Server 1 - RDG, Gateway and License
Server 2 - Session host
They are server 2019.
If I RDP into server 1 and do a file transfer, (copy and paste) the speed is decent. for ex 2MB/sec..
If I RDP into server 2, the transfer speed goes down the toilet, like 300-400KB / sec
Connectivity between server 1 and 2 is fine, they are in the same network.
Any idea?
Hello,
I can log into my RDS session on Windows 10 without issue, however using the exact credentials in the exact network on a Windows 8.1 PC, the RDS session will not connect.
Are there any other configurations or patches required for 8.1 to work?
Thank You,
Franjisk
I have found that when a RDP session that connects with Seamless SSO is interrupted, if the Network Location Awareness service decides to go into 'identifying' for even a half second, when the RDP connection goes to resume, SSO credentials do not work. However I have found that the times that the NlaSvc does not go into 'Identifying' then the connection will resume just fine. It appears that when its 'Identifying' even if I have the local policy set to 'Private' for Identifying connections, then SSO does not work. Is there a fix for this? Can RDP be made to wait or reattempt SSO credentials again automatically? The NlaSvc always goes back to DomainAuthenticated properly, even after half a second, but its still too late as RDP appears to have already tried reconnecting and fails to pass credentials at which point it prompts for a password.
I really need the reconnecting feature to work. Anyone have any ideas to solve this?
We utilize a Remote Desktop deployment to provide a unified browsing experience for our libraries. There are 115 clients involved hosted over 3 host servers.
While numbers per server are balanced workload is not. The presentation to the customer is via a browser which is in a kiosk mode. I am wanting to even out the distribution of workload by balancing the "users" who generate the greatest activity wore uniformly across the host servers. I can do this based upon the memory usage for the kiosk app process, which I can get a breakdown for but nothing I have found includes the "user" name.
Any help appreciated
Hi folks,
I have a Windows Server 2016 Remote Desktop Services environment. On one server collection there areno UPD's configured. Each user account has a roaming profile path configured on the profile tab in AD.
I want to migrate to User Profile Disks. There is some content in the roaming profiles directories that has to be in the User Profile Disks in order to start an application properly.
On the website below I red that the content is copied automatically after configuring the UPD path and logging on and off with a user account. I presume I can delete the roaming profile pathafterwards?
https://www.techslave.ch/2016/03/10/from-roaming-profiles-to-user-profile-disks-part-i-2/
The question is, is this information correct? Or is there another / better way to do this, or is this the way to go?
I've read a lot of documentation regarding VDI and RDS, yet I am still a little confused on some aspects.
Consider my company's scenario:
- We have a Windows Server 2019 Datacenter Edition running on a physical machine with 2 8-core processors (total of 16 cores)
- All employees have Software Assurance included with their Windows OS license on their laptops
We want:
- To host Client-based VMs (Win10 mainly) on our physical WS2019 and allow employees to remotely access their dedicated personal virtual machines
- Very rarely, we would occasionally like to host Server-based VMs (WS2012RS and WS2016 mainly) on our physical WS2019 and allow employees to access their personal server virtual machines. Our employees will not need to use this scenario often, only in unique circumstances.
- None of these VMs would be in use long-term. At max, each VM would be used for a month or two. More often, VMs will probably be needed on a week-long basis, then destroyed.
To my understanding:
- We need to apply a core-based license to our physical WS2019 Datacenter, covering all 16 cores, for the hardware to be in compliance.
- We can deploy as many Windows Server-based VMs as we would like, and can properly handle licensing VM OS's using AVMA
- Employees can connect to Server-based VMs only if they have a CAL
- We can deploy Client-based VMs, and employees can concurrently access up to 4 client virtual machines at any given time because they have SA
My questions:
- Do I have any of the information above wrong? Please correct me if I do
- Do we need to worry about licensing each individual Client-based VM? It seems ridiculous to need to provide a separate product key/activation for each VM instance when they're only needed for a short time.
- Can we deploy both Server-based and Client-based VMs like this in the same VDI environment?
- Do we need to still have the core-based license for our physical WS2019 if we only deploy Client-based VMs?
- How do we go about purchasing and applying a core-based license for our physical WS2019?
Please let me know if there is any other critical information I may need that I have missed.
Thank you in advanced for helpful insights.
dears,
I need your assistance with the below, i was deploying rds server.
Configured rds hosts and rds brokers and rds licenses servers. I issued from the license server licenses per cal and per devices.
In the collection, i added a group that contains the users who are able to connect to the host.
After testing, more than one user were able to connect to the rds host therefore the testing was successful.
however when i went to test the per device cal, i did the following i added the server from where i want to access the rds host to the collection group created earlier. then i logged in to this device using anonymous user and tried to rdp the rds host from that server, however it returned an error : the connection was denied because the user account is not authorized for remote login which is true, the anonymous user is not added to any rds group but the server from where he tries to access the host is added to the group.
I need to understand the per device scenario, can anyone help me with how it its tested?
best regards
I just configured RDWeb-access on the server by setting the PasswordChangeEnable as true (IIS -> Pages -> Application settings)
Page shows up, Users can login..all good.
The problem is, when they try to change their password, it says:
Your new password does not meet the length, complexity, or history requirements of your domain. Try choosing a different new password.
No matter what password you put it, it would not take the password. I even tried something like A19G8fczAe!!W
** I have disabled password complexity in Group policy. ** still no hope.
BUT - when i go to AD and set the user to : Must change password at next login.
Then I go to RDWeb and try. It successfully changes the password..
So it only works when i set the user up to MUST CHANGE PASSWORD NEXT LOGIN..
is it how it should work?
Users want to change their passwords whenever they want..but it doesnt work.
am I missing something?
We are seeing the following error during start up on more than one of our VMs running Windows Server 2016 Datacenter, this is prevent users from being able to RDP to the server. It seems this error resolves itself as the WID service does eventually start, but the dependent RDS services do not start thereafter, but will start with manual intervention. The following are the errors listed in the event log:
1. A timeout was reached (30000 milliseconds) while waiting for the MSSQL$MICROSOFT##WID service to connect.
2. The MSSQL$MICROSOFT##WID service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
3. The Tssdis service depends on the MSSQL$MICROSOFT##WID service which failed to start because of the following error:
The service did not respond to the start or control request in a timely fashion.
There is also the below message logged before the first error, but I'm not sure this is the actual cause, as said previously, it does eventually start, which makes me think its a timing issue.
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSIDAdditionally, this does not happen each time the server starts and is seemingly random, but we are seeing similar behavior on another server with RDS installed.
I've found the following post, but this is not a fix and merely extends the timeout value for all services.
Thanks
Hello.
Running a test RDS2019 server with UserProfile disks hosted on an RDSbroker share on 2016.
Everything was fine but since the weekend, logging new users onto this server caused a black screen. The system became completely unresponsive. Upon investigation, we're noticing the following errors..
1) Disk 4 has the same disk identifiers as one or more disks connected to the system. Go to Microsoft's support website (http://support.microsoft.com) and search for KB2983588 to resolve the issue.
2) An error was detected on device \Device\Harddisk4\DR24 during a paging operation.
4) The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \\?\Volume{7483659d-0000-0000-0000-100000000000}, DeviceName: \Device\HarddiskVolume27.
(A device which does not exist was specified.)
5) The IO operation at logical block address 0x24ea0 for Disk 4 (PDO name: \Device\00000131) was retried.
For issue 1 i've looked at the KB and checked several other posts, using diskpart to look at the uniqueid, they are all different.
2) Related? not sure
3, 4 and 5 I could do with some advice please.
Hi All,
I am trying to configure multifactor authentication with Azure MFA on my remote desktop gateway. I followed this article:
https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-nps-extension-rdg
All seems ok but it is not working as expected. When I try to access a remote desktop I get the notification on my phone. When I approve, the remote desktop keeps trying to connect and I get the notification on my phone 2 more times. Eventually the RDP just times out.
On my NPS server with the NPS extension I can see in the eventlog that access has been granted. On my remote desktop gateway in the NPS logs I can see this:
The RADIUS Proxy received a response from server X.X.X.X with an invalid authenticator.
Where X.X.X.X is my NPS server.
All servers are windows server 2019. My testuser has an Azure AD Premium P1 license (and an office365 business premium).
Any ideas on what could be wrong with my setup?
Hi,
I'm trying to open a virtual channel in my remote desktop-session. I'm calling the WTSVirtualChannelOpen-function of the WtsApi32.dll.
I already succeed to open and use the virtual channel, but since the windows-update 1903 the open-function failes with the error-code 50 (ERROR_NOT_SUPPORTED).
The client and terminal are both running windows 10 with the 1903-update.
I tried to check the Permission-Settings for Remote Desktop Services Connections, but I don't know how.
Other References said it moved to the Group-Policies, but I can't find it there.
I also tried to use the newer VirtualChannelOpenEx-function, but same result. The OpenServer- and EnumerateSessions-function are working fine.
So I'm searching for this Settings:
https://docs.microsoft.com/de-de/windows/win32/termserv/terminal-services-permissions
Thank you for your help,
Nils G.
I currently have the following setup:
This has been up and running with no issues for a couple years.
Now, when users login in they get to the login page, enter credentials, and once attempting to login they get a black screen. This black screen will last for roughly 5 minutes and eventually bring them to there desktop.
All of the above mentioned servers are running virtually on 2 Hyper-V hosts running Server 2012 r2 as well. This issue started 2 days ago.
Rebooting the servers and hosts does not help.
I also restored ALL servers from a backup except for the server running the user profile disks and that made no difference either.
Please help.
Brian Modlin
I have a application server that client computers remote into to access. At this point they can see the desktop of the server. The RDP file I have is suppose to let the user remote into the server but only see the application. When they use it though the error below pops open.
Windows Server 2016
cvh
Thanks for any feedback.