RDS install gone bad
-
I have a RDS server that seems to have gone bad. The problem started when it stopped accepting RDP logins and stopped allowing Remote Apps to be launched. We would reboot the server and it would allow people to connect again, and then in as little as 5 minutes it stopped accepting connections. Some people that were connected could stay connected, but it dropped others.
After finding nothing in the event logs, we decided to restore the server from a day before the problem started showing up. It seemed ok, and then the same problem started again. The only errors I have in the event log are a couple of TLS errors that show up sometimes at the same time I have been denied, but not always. I was about to change the cert from a 3rd party back to a server generated self signed cert, but now I can't manage the server. It thinks the RDS role is gone.
If I try to add the role, it gives mean the error:
Could not retrieve the deployment information from the RD Connection Broker Server <server name>
Any ideas?
-
I should add that at the moment I can pull up the web page of the remote apps and also RDP to the server, so it's kind of working, I just can't modify anything to try to fix the blocking issue.
Also as part of my troubleshooting, I disabled the RDPguard service and firewall since it seemed like something like that was killing it. It made no difference, so I turned them back on.
-
Don't know anything about the RDP role, but can you retrieve and alter settings using PowerShell? Most major Microsoft services feature an PowerShell interface today.
-
@thwr said in RDS install gone bad:
Don't know anything about the RDP role, but can you retrieve and alter settings using PowerShell? Most major Microsoft services feature an PowerShell interface today.
You can. Almost all of the RDS services except session host can even run on a box without a GUI.
-
Pretty much every powershell command I do says there isn't a deployment on this server and goes like this:
PS C:\Windows\system32> Get-RDDeploymentGatewayConfiguration
Get-RDDeploymentGatewayConfiguration : A Remote Desktop Services deployment does not exist on
rds.myServer.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-RDSeserveronDeployment".
At line:1 char:1- Get-RDDeploymentGatewayConfiguration
-
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Get-RDDeploymentGatewayConfiguration
-
Make sure you are running the poweshell commands as admin.
Also, is the connection broker role also installed on this server as well?
You can also try to remove and then re-install the connection broker role .
-
@Mike-Davis said in RDS install gone bad:
Pretty much every powershell command I do says there isn't a deployment on this server and goes like this:
PS C:\Windows\system32> Get-RDDeploymentGatewayConfiguration
Get-RDDeploymentGatewayConfiguration : A Remote Desktop Services deployment does not exist on
rds.myServer.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-RDSeserveronDeployment".
At line:1 char:1- Get-RDDeploymentGatewayConfiguration
-
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Get-RDDeploymentGatewayConfiguration
Any recent Windows Updates?
-
running powershell as admin.
Even if I try to create a new session, it bombs: (this is after running Enable-PSRemoting)
PS C:\Windows\system32> New-SessionDeployment -ConnectionBroker rds2.mydomain.com
cmdlet New-SessionDeployment at command pipeline position 1
Supply values for the following parameters:
SessionHost[0]: rds2.mydomain.com
SessionHost[1]:
New-SessionDeployment : Validation failed for the "RD Connection Broker" parameter.
rds2.mydomain.com Unable to connect to the server by using Windows PowerShell remoting. Verify
that you can connect to the server.
At line:1 char:1- New-SessionDeployment -ConnectionBroker rds2.mydomain.com
-
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,New-SessionDeployment
-
I have a 2008 R2 RDS server being stupi lately. But nothing like this.
