Just put in a brand new Windows Server 2019 Standard Terminal Server at a client. Some of the partners in the firm are of an advanced age and their eyesight is no good. However other's are in their 20's and can see very well.
I tried searching for and and it seems microsoft had a solution for 2008 R2 and then nothing after.
Any way to get that on Windows Server 2019?
Hi,
I have got the following scenario and would like to change the domain controller on the Remote Desktop Session host server.
1.
Domain Name - xyz.local
SVR01 ( It is remote desktop session host and license server )
2.
Domain Name - abc.local
Requirement
I would like to move users, groups, GPO from xyl.local to abc.local domain without losing the user profiles settings and apps configuration in SVRRDSH01.
I will be decommissioning the domain xyl.local.
What would be the best method to complete the migration?
Windows Server 2019 1809 Build 17763,832 Win Defender Firewall disabled
I have a working publicly configured RDS-environment with RD GW and a trusted root certificate.
I have the NPS-extension installed ok.
I have configured
On the RD Gateway server:
RD CAP Store to 'use central server running NPS'
Remote Radius Server Group with ip of the central NPS Server, shared secret, recommended timeouts.
Radius Client with ip of the central NPS Server
Conn Request Policies
Network Policy
On the Central server running NPS:
Remote Radius Server Group with ip of the RD GW Server, shared secret, recommended timeouts.
Radius Client with ip of the RD GW Server, shared secret, recommended timeouts.
Conn Request Policies
The Network Policy on the central NPS Server was not created by me:
I have setup a RDS 2019 environment with the following roles.
- RDS Gateway and Web Access on one server
- Connection Broker
- 2 Remote Desktop session host servers
- RD licensing server on DC
- Application proxy on ADConnect
- Outbound ports are open to Azure AD
I followed this document.
When i log in internally to office 365 and open the On-premise application for remote desktop everything works fine
When i log in externally to office 365 and open the on-premise application for remote desktop i get the error "The computer can't connect with the external computer because authentication with the firewall is failed. Because the references from the firewall are missing".
There seems something is wrong in the firewall, but i configured the outbound ports. Do i configure more in the firewall for this ? Am i missing something else ?
HI there.
I am trying to redirect my Android Device (Nexus 5) via RDP, but cant find enough infos.
I can see my device in RDP client - option - local resource - Plug and Play device, but its still not working.
Can u guys give me some tips and solutions? I am waiting for your help.
Thanks.
Dear All,
I'm Receiving above error in Event Logs in every 1-2 Hrs,
I have tried all like below settings.
1. Offload Receive IP Checksum
2. Offload Receive TCP Checksum
3. Offload TCP Segmentation
4. Offload Transmit IP Checksum
5. Offload Transmit TCP Checksum
6. IPV4 Checksum Offload
7. Large Send Offload v2 (IPV4)
8. Large Send Offload v2 (IPV6)
9. Receive-Side Scaling
10. TCP Checksum Offload (IPV4)
11. TCP Checksum Offload (IPV6)
12. UDP Checksum Offload (IPV4)
13. UDP Checksum Offload (IPV6)
Disabling Chimney / RSS
Netdma Disabled through registry,.. but still im receiving Event : 50 errors.
If any one having solution, please let me know. Thanks in Advance.
Regards
Ashfak
I am currently testing RDS in our environment on 2019 servers. I followed this guide to set this up.
I applied a wildcard certificate for all the services.
When the user logs on to https://rds.mycompany.com/rdweb with domain credentials he is prompted for another login to the RD Gateway.
Image may be NSFW.
Clik here to view.
The RDweb service is running on the same host as the RD Gateway. I have come across applying group policy, trusted sites etc. But my issue here is the users will be logging from a non-domain joined home PCs. Please help.
Hi guys,
i have 2 connection broker server with 2012 R2 configured on ha mode. So i need to upgrade this server to 2019 because i will need to use 2019 as host server.
i have saw this document
but it's not clear, i need remove the server from HA group, upgrade OS, after upgrade the second server without remove the HA group and finally add the first server to HA group again? it's the correct procedure?
thanks
Andrea
Hello,
I am trying to install the RD License manager on a member of computer in AD. The AD Schema is Windows Server 2016 and this member computer is Windows Server 2019.
I have successfully installed the role and activated the server, added the member computer in the BUILTIN "Terminal Services License Server" group but in the configuration page I get the message "the system cannot determine if the license server is member of tsls group".
All the required ports are also open as specified by : https://support.microsoft.com/en-us/help/832017/service-overview-and-network-port-requirements-for-windows#method53
Does anyone have a similar issue or know how to solve this? I dont want to install any CaLs if the service has any errors.
Regards,
antonis michael
Hello everybody,
At a customer's site there is a PowerShell logon script set for users via GPO. The users log on to Terminal (RDP) Servers. PowerShell seems to be in restricted language mode at least for normal users. However, the logon script must use features not available in PowerShell restricted language mode.
How can we have the logon scripts in full language mode please?
Best Regards, Stefan Falk
TB
Hi all,
I have configured RDS on windows server 2019. I was able to configure SSO for both MSTSC and RDWEB. Including sign in to the RDWEB web page and starting RemoteApp from the web page.
My problem is with adding RemoteApp from control panel. When I add a new connection it always request credentials saying the used credentials are incorrect. I don't understand why because all other ways are working correctly...
Any help would be appreciated.
Rahamim.
Hi All
A bit of a strange one. This function has worked in the past, but seems to have stopped. Server 2016 Datacenter. RDS servers set up in a farm, RDS1, RDS2, RDS3 and RDS4. I am able to log on to RDS1, and run the following command:
Query User /Server:RDS2
And I can get a list of all users logged on to the remote server. However, when I try to run the command asking about RDS4, I get the following result:
Error 0x000006BA enumerating sessionnames
Error [1722]:The RPC server is unavailable
I am able to log in to RDS4 and run query user, and it shows me the list of logged in users just fine. I am able to query the other servers from RDS4 successfully. The error seems to happen only when querying RDS4 from 1, 2 or 3. I have tried running the command with the NETBIOS name, as well as the IP and the FQDN. Still get the same result. I have disabled the firewall and AV (Symantec) and still fails. Tried disabling all the third party services and rebooting, but still fails. Tried running sfc /scannow and dism /online /cleanup-image /restorehealth. Both ran through fine and didn't say they fixed anything, but rebooted anyway and still failing. Looking online, there are a lot of references to a certain registry key that needs to be enabled:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\AllowRemoteRPC
This key is set to 1, and has been rebooted. I am logged in as domain admin on all endpoints. The servers will have been created from a single image that was sysprepped, so is it possible that there is a old NETBIOS name somewhere in the registry? Starting to run low on things that I can try to find out what is happening, so Im hoping that someone here has seen this before or has an idea on something we can try.
Thank you for looking, and for your help.
James
Hi, I've this issue after migration of RDS server from 2012 R2 to 2016 and client have Windows 10 1709 but with Windows 10 1703 no issue.
Any suggestions?
Hello,
We are planning to deploy OneIdentity SPS for session monitoring. We want to deploy it as a Remote Desktop Gateway in front of a windows server (Session Host).
I want to know how will the license be managed in this case. Note: We have RDS Device CAL license model.
Knowing that all traffic will go through the SPS, is this considered as one device?
For more on SPS as RD gateway: https://support.oneidentity.com/technical-documents/doc1300463
Hello RDS experts,
I have few confusions here regarding configuring RDS in Azure AD. I'm aware of complete configuration w.r.t on premise. How different is it configuring RDS in complete Azure AD environment?
Also regarding RDS CALs,
1. How different is it configuring and making RDS Per user CALs work in Azure AD set up?
2. How different is it tracking Per User CALs in Azure AD?
3. For Azure AD joined machines, 'Domain' specification is defined as 'Workgroup' when checked in system properties! Does this create any issues in configuration, usage or tracking of Per User CALs here?
Apologies and correct me if I have got into a lot of confusion.
Thanks in advance!
Thanks & Regards,
CSR.
Best Regards, Srujan C.
Hello everybody,
A customer runs Windows Server 2019 terminal server farms. From the local network, everything is fine. Users get perfectly connected and load-balanced to the RD servers. However, if the log on to the domain through a VPN (TMG 2010) which does not block any traffic, they can only only sometimes connect to the farm. When they fail, their Windows 10 RDP client just yields an "internal error" without being more specific.
We checked already:
* TMG does not block anything coming from the VPN to the inner servers or vice-versa. We also tried temporary firewall rules allowing any traffic in both directions.
* DNS resolution and contact to the domain controllers is fine from the LAN and through the VPN. There are DNS A records for each RD server, and for each RD server there is a DNS A record with the farm name, pointing to each of the RD servers, for DNS round-robin.
* The RD broker (a separate server) load-balances the users just fine.
* The clients get a DHCP address for their VPN connection from VPN, also just fine.
* The clients CAN connect every time to the old 2008 R2 server farm which did not load balance. When they try to connect to a 2019 farm (with each farm consisting of 4 RD servers and its own broker and licensing server), the only connect sometimes, the other time failing with the "internal error".
* The clients connect (locally and through VPN) using the same .rdp file pointing to the farm name. The do not use RDWeb currently, nor a RD gateway.
We have the suspicion (although not proved 100% yet) that the users can connect when a RD redirection is not needed/requested by the RD server that they initially contact via DNS round-robin.
Is such a symptom known? Does anyone have a clue what is happening here?
Best Regards, Stefan Falk