Fresh Install of Windows Server 2019, Unable to connect to Session Host Servers

January 3, 2020, 3:35 am

≫ Next: Unable to contact license server

≪ Previous: RD Gateway manager issue

$

0

0

Hi,

I've been facing this issue since Windows Server 2016 and now this problem has happened to me again on Server 2019, I am not sure what the issue is and how I can fix this, if someone can help me on this then it would be great.

Scenario:

DC01 - Active Directory Domain Controller, RD Licensing and File Server on Windows Server 2016
10.10.10.150/24

RDSH01 - RD Connection Broker, RD Session Host, RD Gateway, RD Web Access - Server 2019 (updated)
10.10.10.151/24

RDSH02 - RD Session Host, RD Gateway - Server 2019 (updated)
10.10.10.152/24

Windows Firewall is disabled on all 3 servers. Everything installs fine no errors or warning, certificates are installed as well.

The 3 servers are VM's running on seperate servers, I have done a fresh install of Operating system and not cloned them (as i heard there would be issues with cloning)

When connection with both Session hosts, I as the first user I am connected to RDSH01 without any problems let's call this user1, now when i try connecting as user2, since there is 50-50 load balancing by default, it tries to connect me to RDSH02 and it fails with the below error

 

And the Event logs have the following events

EVENT ID 1280:

Remote Desktop Services failed to join the Connection Broker on server RDSH01.domain.com.
Error: Current async message was dropped by async dispatcher, because there is a new message which will override the current one.

EVENT ID 1306:

Remote Desktop Connection Broker Client failed to redirect the user Domain\user2 . 
Error: NULL

EVENT ID 1296:

Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.
User : Domain\user2
Error: Remote Desktop Connection Broker is not ready for RPC communication.

EVENT ID 2056:

The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database.

Pooled virtual desktop collection name: NULL
Error: Logon to the database failed.

I installed SQL Management studio and am able to connect to the Windows Internal Database without any problems, All services related to Remote Desktop are also running.

Ping and DNS lookups are working fine as well each server can ping and reverse lookup the other 2 servers without any issues. The 3 servers are also added in the Server pool in Server Manager.

Can someone help me figure this out please? I am scratching my head over here for over 2 days. I mean this is a fresh install after all, shouldn't be creating such problems.

---

MCITP:Server Administration|MCTS: Server 2008| MCSE: Server 2003| MCSA + M: Exchange Server 2003| MCP: Windows XP|

---

Unable to contact license server

January 3, 2020, 6:04 am

≫ Next: Unable to connect to the server by using Windows Powershell Remoting

≪ Previous: Fresh Install of Windows Server 2019, Unable to connect to Session Host Servers

$

0

0

Hi,

I have installed Remote desktop session host on one of our server and created a registry key mentioned below with license server name

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters\LicenseServers

"SpecifiedLicenseServers" REG_MULTI_SZ "XXXXXX"

My license server is in different Vlan therefore i had opened below ports on network firewall end with port query success.

TCP 135

TCP 139

TCP 445

UDP 137-138

TCP 49152 - 65535 

TCP 5985

yet my session host is not able to communicate to license server and indicates "License server XXXXX is not available, this could be caused by network connectivity problems" in RD licensing diagnoser

AM i missing any port or is there anything additionally that i have configure to solve this problem?

Unable to connect to the server by using Windows Powershell Remoting

July 20, 2017, 12:14 am

≫ Next: Windows Server 2012 R2 stuck restarting on RDP but normal on vm console

≪ Previous: Unable to contact license server

$

0

0

HI,

We are trying to install RDS on one of the server OS 2016. But facing below error

Unable to connect to the server by using Windows Powershell Remoting

-- We are installing all RDS Role on the same server, there is no remote server involve in it.

Did below troubleshooting but still issue persist .

-- We ran below command but no luck.

Enable-PSRemoting -force
Set-Item WSMan:localhostShellMaxMemoryPerShellMB 1000

Refer : https://community.spiceworks.com/topic/1463758-unable-to-connect-to-the-server-by-using-windows-powershell-remoting-rds

-- Disable windows firewall

refer : https://rlevchenko.com/2015/05/22/rds-unable-to-connect-to-the-server-by-using-windows-powershell-remoting/

Ran "Set-ExecutionPolicy -ExecutionPolicy RemoteSigned"

Ran "Set-ExecutionPolicy -ExecutionPolicy UnRestricted"

Refer : https://social.technet.microsoft.com/Forums/sharepoint/en-US/68af42d6-7a12-49eb-941c-72ba0cc6d316/setexecutionpolicy-unrestricted-force?forum=winserverpowershell

-- Further we tried to install the RDS from DC but when we tried to add the server **3 in server manager group it shows below error.

Error **3 : Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig".  7/19/2017 5:03:36 AM

-- We provide local admin rights to user "helpdesk" but no result.

-- Disabled IP v6 but still no result.

Refer : https://rlevchenko.com/2015/05/22/rds-unable-to-connect-to-the-server-by-using-windows-powershell-remoting/

---------------------------------------------------------------------------------------------------------------------------------------

---

Thanks, Sajjan T

Windows Server 2012 R2 stuck restarting on RDP but normal on vm console

January 3, 2020, 6:02 pm

≫ Next: Remote desktop licenses not being issued, cannot connect using remote desktop.

≪ Previous: Unable to connect to the server by using Windows Powershell Remoting

$

0

0

I have windows server 2012 R2 installed on vmware. previously i restarted this server via RDP and stuck on restarting screen. but when i open this server via console vm, there is no problem and all service is ok. but until now in rdp is still stuck restarting and this is very annoying.

anyone can help me?

Remote desktop licenses not being issued, cannot connect using remote desktop.

January 3, 2020, 9:42 am

≫ Next: UPD Windows 7 reliplcate to new created pooled win10

≪ Previous: Windows Server 2012 R2 stuck restarting on RDP but normal on vm console

$

0

0

We are/have upgraded from a terminal server using Server 2008 R2 to a new server with Server 2019

I have loaded the 15 RDS user licenses and everything was working fine until this morning. I briefly lost the VPN tunnel from the remote office, and after it reconnected, none of the workstations are connecting. earlier connection said it was in grace period.

I have checked the new server and it shows 15 total licenses, 15 availalbe, 0 issued.

The remote stations connected fine yesterday, and were connecting to the old 2008 server last week. Is there something I need to do to get the remote computers to get a license from the new server?

---

John Mason

UPD Windows 7 reliplcate to new created pooled win10

January 4, 2020, 11:59 pm

≫ Next: USB Redirection for Publish apps in VDI using RDS

≪ Previous: Remote desktop licenses not being issued, cannot connect using remote desktop.

$

0

0

Hi Experts!

Can someone help me on how to replicate the old user profile disk of windows7 pooled to newly created win10 pooled in VDI ? We have some difficulties on we can use the old UPD of the user. i have some research telling that A user profile disk are for single collection only it means you will not able to use the old one but the best practices is to create a new folder for UPD which is seperate from win7 pooled collection. 

Considerations when implementing User Profile Disks

• User profile disks are for a single collection only.
   + A user connecting to two different collections will have two separate profiles.
• Properties of User Profile Disks are set automatically upon creation and contain all profile data and registry settings by default.
   + These properties can be defined prior to creation or after the fact in the Session Collection properties from Server Manager.
• Some form of central file share is required prior to UPD creation as the UNC path of this share will need to be provided in the wizard during initial configuration.
   + One major benefit of these file shares is that when more RDS hosts are added to support the collection, those hosts are automatically added to the ACL of the share, not requiring an administrator to take any action in modifying security permissions.
• User Profile Disks are restricted a single session, which means if a user is logged into one RDS host, they cannot connect to another and they cannot have more than one session active on a single host.
• User Profile Disks are created using a naming scheme that corresponds to a user's GUID and makes identifying the UPD associated with a user into a very complicated task.
   + To make this process a simple one, there is a standalone utility published in Microsoft's Technet Gallery that addresses this issue - Sidder

Thanks

Homer 

---

Homer Sibayan

USB Redirection for Publish apps in VDI using RDS

January 5, 2020, 12:08 am

≫ Next: Windows 10 Wyse Thin client USB redirection

≪ Previous: UPD Windows 7 reliplcate to new created pooled win10

$

0

0

Hi Experts!

Very question, Is it possible to have a USB redirection in VDI Publish Apps ? In pooled we have simply access the usb but on our publish apps  we're not able too.  As you can see on the RD web page the drive L2 folder is created for USB redirection for publish user who they have access. And on the RWMVDPOOL desktop icon this is for pooled user which we're able to see the USB removable devices. Is there a step how to resolve on usb redirection for publish user in VDI.? 

---

Homer Sibayan

Windows 10 Wyse Thin client USB redirection

December 16, 2019, 7:01 pm

≫ Next: HTML5 Client zoom

≪ Previous: USB Redirection for Publish apps in VDI using RDS

$

0

0

Hi Experts!

Can someone help us on how to enabled the USB redirection for Windows 10 Wyse thin Client in VDI in Group Policy ? Appreciate if you can give us the step by step procedure on how to do that. We're upgrading the windows 7 thin client image to win10 however we cant copy the USB restriction policy from win 7 to win10..

For Example : Using Windows 10 Thin client machine, I accessed RD Web access portal going to the interface of Remoteapp and Desktop connection where we can see the Publish app and pooled. What we are asking is how we can show the USB drive folder and set up usb redirection on Publish .? 

Thanks

---

Homer Sibayan

---

HTML5 Client zoom

January 5, 2020, 9:55 am

≫ Next: Substandard Performance overall

≪ Previous: Windows 10 Wyse Thin client USB redirection

$

0

0

Hi,

I have recently started rolling out the HTML5 client and have had an issue raised, in that using Control + in PhotoShop zooms in on the application but Control - will zoom the Browser window out and crash the session.

Has anyone found a fix for this or know a way to stop this happening? It seems like the key combination isn't being directed to the webpage.

Many thanks

Conor

Substandard Performance overall

December 22, 2019, 8:01 pm

≫ Next: RDS idle session limit error

≪ Previous: HTML5 Client zoom

$

0

0

I recently deployed a Windows Server 2019 with Hyper-V and with two VM's. One DC/File and Print server and a RDS.
Hardware - Dell 740 PowerEdge with RAID 10 and 8GB of Cache on the RAID controller and a Tesla GPU M10. 
RDS VM - Widnows Server 2019, 16 vCPU and 40GB of memory with the 1 GPU in DDA. On Avg 30 users. (Increased the memory from 24GB in an attempt to resolve some issues but didn't help).

Originally I created a NIC team but since removed it, as many forums had mentioned possible issues with NIC teaming, I have disabled RSC and VQM, I couldn't not disable Disk Write Caching, keep getting an error. I went over all the possible settings and can't seem to find anything that leads to a possible cause of performance degradation.

There is only a few application installed, Office 2019, ERP / Inventory package, AutoCad Viewers, Adobe 

The overall performance is that poor that I have advised the customer we redo this whole project with Server 2016. It takes ages for Outlook to open, the menus take a long time to load, at times the user sessions lock up or the display lags. It is random and not all users have the same issue at the same time, which is weird. For most of the time, users are putting up with it, the whole reason for this deployment was better performance and user experience hence the latest hardware, GPU and Windows 2019 platform. 
Since researching, I have found multiple end users with the similar issues, none pin pointing or finding a resolution and really hope there is an update or resolution to this soon, pretty poor from MS to release something this substandard. 

The CPU, MEM, GPU utilization is really good and not maxing out at anytime, Disk queue's are really good. The server is minimal network dependent, although I have realized when I transfer data on the HV host it had some impact on the server, the HV and VM's don't share a NIC, each have a dedicated.

Has anyone got similar issues with Server 2019 in a RDS environment that has had some success to a degree? From the Technet cases I read, their seems to be several complaints but yet a solid resolutions and I don't particular want to change this back to 2016.

Any advice, feedback or possible cause would be greatly appreciated.

Regards

RDS idle session limit error

January 1, 2020, 11:39 pm

≫ Next: Temporary profile folder

≪ Previous: Substandard Performance overall

$

0

0

Hi all,

We are setting up an RDS environment on Windows server 2019. The only collection we have has a third-party application.

The problem is that we have the Idle session limit set to 8 hours, but it seems that it is not working because we see users with 1 day and one hour in idle time.

Is there any way to check why it may be happening? I don't see logs or events.

Thanks and regards,

---

Gerardo,

Temporary profile folder

December 29, 2019, 4:28 am

≫ Next: Bypass approval for Remote Control Request

≪ Previous: RDS idle session limit error

$

0

0

Hi,

We have windows server 2012 R2 server. We see many temp.domain.xxx folders getting created. Basically, this is a SFTP server (tecia sftp application is installed). Users connect to this server using WinSCP but users profile folder are being created. However, recently we observed under c:\users\ , there are lot of temp.domain.xxx profile folders. Few users had a issue connecting via WinSCP. We deleted these temp profile folders and related .bak files from profilelist in registry. Rebooted the server but the issue still exists. Can someone please help fixing this issue as it is impacting multiple users. Is there any hotfix to install? Server is updated to the latest.

Thanks,

Umesh.S.K

Bypass approval for Remote Control Request

December 31, 2019, 12:55 am

≫ Next: Windows Server 2019 RDS Cal issue

≪ Previous: Temporary profile folder

$

0

0

Hi,

We have a Server 2016 server with only the following roles installed

- RDS Session Host
- RDS Web access

It is a single RDSH server hosting an application that has to be used by more then 2 people at the same time. The application will not be published, so a collection is not needed. Users will get a RDP file that let them connect to the application server on RDP poort 3390.

What i want to achieve is that non administrator accounts can take control of sessions. Server Manager is not the way to go because i dont have a broker role installed. Server Manager will just give me a message the broker role is not found.
Even when i would install the broker role, i guess i still need published apps / collections in order to see sessions and manage those sessions (kill them, take control, etc).

So i try to use one of the following tools:

- LazyTS
- tsadmin.exe (the old Terminal Server Manager from older server versions)

When i run the tool as Administrator i can do everything, but when i take control of a session on the RDSH server the logged on user has to give approval. For several reasons i dont want the approval to be given.

So i opened up the local Policy MMC on the RDSH and changed the "Set rules for remote control....." to "Full control without users permission".
Also on the AD account of the user logged on to the RDSH i made sure the "Require users permission" is unchecked. 
But it still asks me for approval!

When i use mstsc /V:<servername> /shadow:<nr> /noConsentPrompt /control i get in without approval.
So it is possible, but why would one of the tools behave differently? I guess the tool is not using a parameter like /noConsentPrompt, but i still disabled it in local GPO?

Did i miss something?

Windows Server 2019 RDS Cal issue

December 30, 2019, 8:32 am

≫ Next: Window 10 Pro with Window 7 Pro.

≪ Previous: Bypass approval for Remote Control Request

$

0

0

I have a domain setup with a domain controller, Remote desktop server and Web server, all server 2019. I also have a gateway, license manager, cals installed and per device settings. When I attempt to use the remote desktop service I receive an error stating that the licenses are incorrect the server is expecting Server 2016 licenses. Why would I receive this type of message with a server 2019 domain? 

Window 10 Pro with Window 7 Pro.

December 31, 2019, 1:24 am

≫ Next: signing into windows without RDP session

≪ Previous: Windows Server 2019 RDS Cal issue

$

0

0

Hi Everyone,

I have 20 Qty Window10 Pro FPP license.

And installed  Window10 Pro in 10 Pcs and rest 10 PCs installed with Window 7 Pro.

Can I install window 7 Pro in newly purchased computer and can get adjust/entitlement with existing window 10 Pro that purchase previously.

Do we need to buy extra Window 7 Pro for the license entitlement.

Many thanks....

---

signing into windows without RDP session

December 28, 2019, 11:30 am

≫ Next: RDS cal for 2019

≪ Previous: Window 10 Pro with Window 7 Pro.

$

0

0

Having a bit of a problem that needs to be resolved.

I hit the ctrl alt del, then click on change password.  It askes for the current password, but problem is I don't remember what it was.  My question is, is there a way of signing in without RDP session?

RDS cal for 2019

December 26, 2019, 8:30 am

≫ Next: Windows Search broken in Server 2019

≪ Previous: signing into windows without RDP session

$

0

0

Hello All,

If I buy 1 Device RDS cal for Windows server 2019 then How many users can connect to this server simultaneously .

4-5 Members from staff needs to connect this server at a time (simultaneously). Do I need buy 5 User cal or 1 device cal sufficient for 5 users. Please help me with information .

Thanks in advance !!

Mahesh Karale.

Windows Search broken in Server 2019

December 13, 2019, 12:36 am

≫ Next: Windows 2012 and RDS 2016

≪ Previous: RDS cal for 2019

$

0

0

Starting a new thread on that bug. (the thread named "Windows Search changes in Server 2019" doesn't reflect the exact catastrophy of that bug for RDSH users.

This is not a change this a broken feature.

Any fix ?

Windows 2012 and RDS 2016

December 26, 2019, 7:51 am

≫ Next: RDS Default Printers / Admin Rights

≪ Previous: Windows Search broken in Server 2019

$

0

0

Hi

We are looking to do a in-place upgrade on our Windows 2008 server to 2012, to hold us over until our new Windows 2016 servers are in place.

Currently we have the RDS roles on a Windows 2008 server which we are planning to retire as well.

My question is can we build a new Windows 2016 server and put the RDS roles on it and have the upgraded Windows 2012 servers use it for it licencing info and connection broker, until the Windows 2016 servers are ready, then have the new Windows 2016 server use the same server?

Thanks

Rich

RDS Default Printers / Admin Rights

January 6, 2020, 1:43 am

≫ Next: Certificate Warnings/Errors on RDS farm / RemoteApp

≪ Previous: Windows 2012 and RDS 2016

$

0

0

Hello

We've successfully deployed RDS on a 2019 Windows Server but just have a couple of questions that I can't seem to work out. 

1. When users connect through Remote Desktop Connection the default printer is being set as Microsoft OneNote, even though the default printer on the server and on the user's machine is an HP networked laser printer.  When you set the HP laser printer as default through RDC it is reset back the next time the user is logged in. 

Is there a default to set somewhere that we're missing?

2. Some users through RDC would like more admin rights (like going into Task Manager and adjusting settings).  I am reluctant to do this for obvious reasons but the customer is insistent.  Where do I give certain users more of an admin role?

Thank you in advance, Chris.