Trying to manage a Remote Desktop Services deployment using PowerShell, I recently stumbled across this annoying error. Symptom Set-RDSessionHost : A Remote Desktop Services deployment does not exist on <YourConnectionBrokersFQDN>. This operation can be performed after creating a deployment. For information about creating a deployment, run “Get-Help New-RDVirtualDesktopDeployment” or “Get-Help New-RDSessionDeployment”. The obvious solution according to many internet sources is simple: run PowerShell as administrator. But in this case, it didn’t help.As another test, I ran Get-RDServer -Connectionbroker <YourConnectionBrokersFQDN> and the result was this one: Get-RDServer : To configure the Remote Desktop management server for a high availability deployment, provide an active Remote Desktop management server name for the RD Connection Broker server. Huh. Interesting. Cause It seems to me that both the PowerShell commandlets and error messages are not entirely fitted to high availability deployments. While in a non-HA deployment you only have one connection broker, which makes commands like for example Get-RDServer -Connectionbroker <YourConnectionsBrokersFQDN> a no-brainer, in HA deployments there is an important differentiation: what the commandlet needs is not “a connectionbroker” but “the connectionbroker which currently is the active management server”. In other words: “A Remote Desktop Services deployment does not exist” is not really precise – it does exist, it’s just not active on the very server at the very moment. Solution Before you run any commands, make sure you target the currently active management server. So either you query the active server and target the result, for example like this … $ActiveCB = (Get-RDConnectionBrokerHighAvailability -ConnectionBroker ).ActiveManagementServer Get-RDServer -Connectionbroker $ActiveCB … or you set the server you target to be active: Set-RDActiveManagementServer -ManagementServer Hint: as changing the active server may lead to little hickups (for example open sessions of the Remote Deskop Services Overview in the Windows Server Manager will be reset), I recommend the first and less invasive approach. -
Is this RDS Server in use? The RDS Overview should look like image 3. Maybe you didn't add the Server into the view? You do that in Server Manager, RDS Overview, Servers - which is showing in your image. -edit - Correction - you add it in Server Manager, All Servers. Once added there it should show up in the RDS Overview, Servers list.
Spice (1) flagReport 1 found this helpful thumb_up thumb_down
-
DragonsRule wrote:
Is this RDS Server in use?
The RDS Overview should look like image 3. Maybe you didn't add the Server into the view? You do that in Server Manager, RDS Overview, Servers - which is showing in your image.
-edit - Correction - you add it in Server Manager, All Servers. Once added there it should show up in the RDS Overview, Servers list.
Yes, that server is in use, and is listed in the server pool.
-
If you go to Powershell as an admin on that server and run this, what do you get? Get-RDserver Also, just a reality check - when you are viewing server manager, do you have admin rights for the RDS server? If not, you won't see things correctly.
Spice (1) flagReport 1 found this helpful thumb_up thumb_down
-
DragonsRule wrote:
Also, just a reality check - when you are viewing server manager, do you have admin rights for the RDS server? If not, you won't see things correctly.
:-) Yes, I'm logged in with my Domain Admin account.
DragonsRule wrote:
If you go to Powershell as an admin on that server and run this, what do you get?
Get-RDserver
Nice idea. Not a good result:
Powershell
PS C:\Windows\system32> Get-RDserver
Get-RDserver : The RD Connection Broker server is not available. Verify that
you can connect to the RD Connection Broker server.
At line:1 char:1
+ Get-RDserver
+ ~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorExcep tion + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio n,Get-RDServer PS C:\Windows\system32>
Although even an error can help. I'll investigate it.
-
Basically the same thing as before. Something's not right with the Broker. Maybe something here will help: https://www.concurrency.com/blog/august-2019/diagnosing-failed-rds-broker-role
Spice (1) flagReport Was this post helpful? thumb_up thumb_down
-
DragonsRule wrote: Basically the same thing as before. Something's not right with the Broker. Maybe something here will help: https://www.concurrency.com/blog/august-2019/diagnosing-failed-rds-broker-role
That NEARLY worked. The article mentions error code 2150859180 but I was seeing error code 2150859027 in an otherwise identical Event Log entry. That translated to Hex 0x80338113, which then led me to this article: https://rcmtech.wordpress.com/2016/10/21/fix-powershell-winrm-remote-connection-errors/ ...at the end of which was the suggestion to disable IPv6 on the server's adapter. After which, it started working! Much fist pumping ensued. So, have a 'Best Answer', as you did all the real work here. Thank you, DragonsRule! Spice (1) flagReport Was this post helpful? thumb_up thumb_down
-
Great news! Glad I could help lead you in the right direction.
Spice (1) flagReport Was this post helpful? thumb_up thumb_down
|