A Remote Desktop Services deployment does not exist on Powershell

A Remote Desktop Services deployment does not exist

Archived Forums

Remote Desktop Services [Terminal Services]

• Question

• 0

  Sign in to vote

  Hi

  I am trying to run a PowerShell command to add an application from a network share onto my Remote Desktop Server 2016. When I run the command, it shows the following:

  New-RDRemoteApp : A Remote Desktop Services deployment does not exist on SR1RDS002.ad.collinsco.com. 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".
  At line:1 char:1
  + New-RDRemoteApp -CollectionName RD_APPS_1 -DisplayName BankLink -File ...
  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  + CategoryInfo : NotSpecified: [:] [Write-Error], WriteErrorException
  + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,New-RDRemoteApp

  The Remote Desktop Server is running and I have staff currently using the applications on it therefore do not understand why this is happening.

  This is very frustrating as I have two applications that run from a Network share that I need to have published.

  Can anyone please help me with this issue? Thanks

  Friday, January 19, 2018 4:50 AM

All replies

• 0

  Sign in to vote

  Hi,

  How are RDS roles distributed and from which system that the cmdlet was executed?

  Note that a RDS deployment requires 3 roles, RD Session Host, Connection Broker and Web Access.

  Pleaseensure that FQDN of Connection Broker is specified within PowerShell comdlet via -ConnectionBroker parameter and all servers belonging to the RDS deployment are added into server pool.

  You may run cmdlet below to get information about all RDS servers within deployment:

  Get-RDServer -ConnectionBroker rdcb.contoso.com
  

  Best Regards,

  Amy

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact .

  • Proposed as answer by Amy Wang_ Tuesday, January 23, 2018 2:34 AM
  • Marked as answer by trytobegeek Tuesday, January 30, 2018 9:27 AM

  Friday, January 19, 2018 9:38 AM

• 0

  Sign in to vote

  Hi,

  Kindly mark useful reply as answer, which would be much more efficient for other community members to find useful information.

  Let us know if further assistance is required.

  Best Regards,

  Amy

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact .

  Thursday, January 25, 2018 9:15 AM

• 1

  Sign in to vote

  Hi,

  Try disabling firewall temporarily, thenrun PowerShell as Administrator to see whether it works.

  Best Regards,

  Amy

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact .

  Tuesday, January 30, 2018 9:25 AM

• 0

  Sign in to vote

  I found that running the commands in an administrative PowerShell console did the trick, too. I was just hoping someone else made the same discovery...

  Thursday, February 22, 2018 10:12 PM

• 0

  Sign in to vote

  You have the answer right under your nose. In your first command you added ConnectionBroker:

  Get-RDSessionHost -CollectionName RDSFarm -ConnectionBroker broker.domain.local

  In your second command you left that out…

  Set-RDSessionHost -SessionHost rdssh02.domain.local -NewConnectionAllowed No

  Just add -ConnectionBroker broker.domain.local to your second command and it will work

  Set-RDSessionHost -SessionHost rdssh02.domain.local -NewConnectionAllowed No -ConnectionBroker broker.domain.local

  Wednesday, April 17, 2019 12:26 PM