Archived Forums
>Remote Desktop Services [Terminal Services]
Question
-
0
Sign in to vote
Hi All,
I've been trying for the past couple of days to deploy Remote Desktop Services to newly built 2016 Server [member server not DC]. It just fails repeatedly when trying to install the connection broker role.
I've completed the windows updates [although that was dramatic in itself!] and then turned my attention to installing RDS services, tried Role based and remote desktop services type deployments, but on both it just fails and gives a useless and generic error message:
----------------------------------------------------------------
GetAlterationState method returned Failed. Error: The request to add or remove features on the specified server failed.
Installation of one or more roles, role services, or features failed.
One or several parent features are disabled so current feature can not be enabled. Error: 0xc004000d
----------------------------------------------------------------I've tried the following:
Change the Windows Internal Database service to administrator, or network service, or local system. [didn't work]
Moved server to separate container and disabled GPO inheritance incase it's a group policy setting issue.
Tried installing connection broker role via powershell.
Changed local security policy to make sure log on as service right is set for NT Service\All services, domain admins and network service.
SFC scan and DSIM repair image.
I can't figure out which service is possibly required to install this role which I haven't already enabled.
CBS logs don't provide much insight into why this has failed unfortunately.
Any advice or help would be greatly appreciated.
Cheers,
BillyThursday, March 7, 2019 10:12 PM
All replies
-
0
Sign in to vote
Hi,
Based on your description, my understanding is that Connection Broker is failed to be installed on Windows Server 2016.
Please log on the server directly with domain admin credential. Then, please open Server Manager – Add roles and features – Role based or feature based installation – expand Remote desktop services and select RD CB.
If problem persists, please post the detail error message or relate screenshot about the failure.
Besides, please reference “Introduction to log files that are useful for troubleshooting RDS issues in Windows Server 2012” to enable the RDS log, then, try to reproduce the problem and collect relate log files:
//support.microsoft.com/en-my/help/2747656/introduction-to-log-files-that-are-useful-for-troubleshooting-rds-issu
Best Regards,
Eve WangPlease remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact .Friday, March 8, 2019 2:26 AM
-
0
Sign in to vote
Hi,
Please feel free to let us know if there is any update.
Best Regards,
Eve WangPlease remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact .Monday, March 11, 2019 1:15 AM
-
0
Sign in to vote
Hi Eva,
Also found the following in Event viewer logs under ServerManager-DeploymentProvider.
First Error:
Unable to install updates SBMgr-UI;SessionDirectory;. hResult: Unknown HResult Error code: 0xc004000d
Second Error:
Exception Detected: Installation of one or more roles, role services, or features failed.
One or several parent features are disabled so current feature can not be enabled. Error: 0xc004000d ErrorID: DISMAPI_Error__Failed_To_Enable_UpdatesThird Error:
GetAlterationState method returned Failed. Error: The request to add or remove features on the specified server failed.
Installation of one or more roles, role services, or features failed.
One or several parent features are disabled so current feature can not be enabled. Error: 0xc004000dHopefully this helps to track down the issue, because I'm at a loss now.
Many thanks,
Billy
Monday, March 11, 2019 9:05 PM
-
0
Sign in to vote
Hi Eva,
Thanks for this I'll attempt this now, FYI the error log on trying to install the RD CB role in the WID\logs directory states the following:
Starting up database 'tempdb'.
2019-03-12 11:34:54.62 spid20s Error: 3605, Severity: 16, State: 1.
2019-03-12 11:34:54.62 spid20s Schema verification failed for database 'RDCms'.
2019-03-12 11:34:54.63 spid20s The Service Broker endpoint is in disabled or stopped state.
2019-03-12 11:34:54.63 spid20s The Database Mirroring endpoint is in disabled or stopped state.
2019-03-12 11:34:54.63 spid20s Service Broker manager has started.
2019-03-12 11:34:54.95 spid7s SQL Server is now ready for client connections. This is an informationalI'll uninstall the internal database and try the steps you mentioned above and report back.
Many thanks,
Billy
Tuesday, March 12, 2019 11:42 AM
-
0
Sign in to vote
Hi Eva,
Just to confirm that RDS services are now configured including the RD CB role and I'm receiving no errors, following uninstall and reinstall of Windows Internal Database feature.
Thanks again for the help.
Cheers,
Billy
Tuesday, March 12, 2019 12:53 PM
Remove-RDServer
- Reference
Is this page helpful?
Yes No
Any additional feedback?
Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.
Submit
Thank you.
Module: RemoteDesktop
Removes a server from a Remote Desktop deployment.
In this article
16 Replies
· · ·
Thai Pepper
OP
Aug 26, 2016 at 13:28 UTC
Close PS, then "Run as Administrator" and it will work this time.
The problem occurs when you are running that command on the connection broker machine itself.
Edited Aug 26, 2016 at 13:39 UTC0
· · ·
Jalapeno
OP
Aug 26, 2016 at 13:46 UTC
Thank you! That got me to the next step where I am stuck yet again :/
0
· · ·
Jalapeno
OP
Aug 26, 2016 at 13:56 UTC
Ok. I had to run a Remove-RDSessionHost first and that got rid of the RDS-RD-SERVER role but now I'm having trouble removing the other two roles. See image below.
0
· · ·
Thai Pepper
OP
Aug 26, 2016 at 14:37 UTC
Can you remove them using the Server Manager?
0
· · ·
Thai Pepper
OP
Aug 26, 2016 at 14:40 UTC
Is your goal just to remove a server from your RDS farm? Or are you removing the only RDS server from your network?
RDS isn't like Exchange where you have to uninstall everything from your domain or forest, you can simply "turn it off" and create a new server/gateway/connection broker from scratch.
0
· · ·
Jalapeno
OP
Aug 26, 2016 at 14:49 UTC
I can't remove them through server manager because this is the screen I get:
The server listed in the message [CBN-TRMSRV01.AD.CIRCLEBOLT.COM] no longer exists. In fact, the ad.circlebolt.com domain no longer exists, now it's simply circlebolt.com.
My goal is to remove this and point this terminal server to our other terminal server for RDP licencing.
0
· · ·
Thai Pepper
OP
Aug 26, 2016 at 15:55 UTC
Try this. To add it to the pool of managed servers in Server Manager:
0
· · ·
Jalapeno
OP
Aug 26, 2016 at 16:30 UTC
That doesn't change anything :/
0
· · ·
Thai Pepper
OP
Best Answer
Aug 26, 2016 at 16:37 UTC
Ok, from PS try this:
Remove-WindowsFeature –Name RDS-Connection-Broker
then reboot, then reinstall it the same way on the same server:
Add-WindowsFeature –Name RDS-Connection-Broker
Apparentlythis is caused because of the old domain name getting hard-coded to the RDS-Connection-Broker service. This should reset the name to the correct domain and allow you to continue.
0
· · ·
Jalapeno
OP
Aug 26, 2016 at 17:06 UTC
Ok, thanks. I'll give that a try and report back afterwords.
This is a production server so I have to wait till after hours to reboot.
0
· · ·
Thai Pepper
OP
Aug 26, 2016 at 18:51 UTC
10-4, I'll try to keep an eye on the thread so that I can respond timely, since nobody else has any ideas they're willing to share.
1
· · ·
Jalapeno
OP
Aug 27, 2016 at 20:23 UTC
OMG... I think that did it!!!!!
0
· · ·
Thai Pepper
OP
Aug 29, 2016 at 12:22 UTC
Congratulations, I'm glad it's resolved!
1
· · ·
Jalapeno
OP
Aug 29, 2016 at 12:28 UTC
Thank you for all of your help!!!Jim Schuuz wrote:
Congratulations, I'm glad it's resolved!
0
· · ·
Anaheim
OP
Oct 11, 2018 at 07:19 UTC
I found this because i had the same error. my main problem was that specific users couldnt connect to the rds because of a broken connection broker service. Like i read here, its an server in production use and a reboot is necessary. Thats completly false, after uninstall it recommends to reboot. Just install the connection broker services right after you uninstalled it. Setup will give you a hint that the server has a pending restart [yellow box on top] but you can continue to install. After that installation was finished all users could connect withouth reboot.
So maybe for admins having the same issue, you can get ur live server working again withouth reboot and already connected users can continue their work.
kind regards Marcel
0
· · ·
Pimiento
OP
Nov 14, 2018 at 20:00 UTC
1st Post
Hi I tried these steps from my gateway machine in the RDS web farm. But I am still getting this error "there are no available computers in the pool". I get this error when I try to launch my remote app from the RDS web portal.
Remove-WindowsFeature %u2013Name RDS-Connection-Broker
then reboot, then reinstall it the same way on the same server:
Add-WindowsFeature %u2013Name RDS-Connection-Broker
Please help, I am stuck
0
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.
Virtualization and Windows 7
Jorge Orchilles, in Microsoft Windows 7 Administrator's Reference, 2010
Remote Desktop Services
RDS [formerly Terminal Services] is the most commonly used method of application virtualization. This method presents applications to connected users. The application actually runs in a session on the server in the data center while it appears to be running on the local desktop. This is a cost effective and reliable method of deploying applications to an enterprise. Figure 9.39 shows a simplified diagram of how RDS works.
FIGURE 9.39. Remote Desktop Services
Users, whether local or remote, all connect to the RDS server. The application is displayed to the end user while being executed on the RDS server. This gives equal performance to both local and remote users running the application. When the applications need to be upgraded or patched, they are patched only on the RDS servers. When the users next connect and run the application, they receive the updated version. The RDS server is capable of supporting multiple users on a single server, and there are many new enhancements in RDS with Windows Server 7 that allow for a variety of connection methods. Web Services, Session Broker, and Network Load Balancing all work together to provide a seamless application virtualization environment for most users.
If your users do not want to connect to a server or a Web page to run their applications, there is a new feature in Windows Server 2008 RDS called RemoteApp. A published application can be converted to a RemoteApp and generate a Windows Installer File [MSI] that can be deployed through Active Directory, file download, e-mail, or your SCCM environment to all the targeted users. When installed on your Windows 7 desktop, double-clicking on it will launch the application just like it is installed on the end-user desktop. The connection to the RDS server is automatically established and the application is started. The RemoteApp can add items to the desktop Start menu or desktop icon just like a locally installed application.
Using the advanced features of the Remote Desktop Client in Windows 7 allows for mapping of resources to the RDS server, so files and printers can be shared when a user connects. The advanced features also can authenticate a user before a user session is created to relieve the extra burden on the RDS server and allow for more connections and better performance. The drawback to this solution is the fact that a user must be able to connect to the RDS server in some fashion to be able to run an application.
View chapterPurchase book
Read full chapter
URL://www.sciencedirect.com/science/article/pii/B9781597495615000097
Deploying virtual servers for RDS
If you’re using Azure, keep in mind that each subscription has a maximum number of networks, VMs, and Cloud Services that can be provisioned. If you’re rolling out a new service for many clients at once, you may need multiple subscriptions to have enough RDS connections available.
A minimal RDS installation requires an RD Session Host and a Connection Broker. On top of that, each client will need either a Gateway server with SSL authentication or a secure tunnel.
Since Remote Desktop servers are valuable targets for attackers, make especially sure that all Administrator passwords meet the necessary complexity requirements, or ideally, randomly generate them for increased security. Set a change schedule for these passwords and make sure they’re only documented in a secure central location that can be accessed only by your trusted administrators.
Lastly, since many Partners are deploying multiple new RDS platforms for different clients right now, don’t forget to change administrator passwords if you’re replicating new tenant environments. It’s an easy thing to overlook when working quickly.
How to Set up Remote Desktop Services in Windows Server 2016
Author:
sengstar2005
Updated date:
Dec 25, 2020
Accomplished systems and network administrator with 10+ years of experience managing server infrastructures and data-center operations.
There was quite a change from installing Remote Desktop Services [aka Terminal Services] with the introduction of Windows 2012. It was confusing, and when you install the Remote Desktop Services host server, there was no longer the familiar Remote Desktop Manager, and you could either work through the settings in the registry directly or bring over the remote desktop manager snap-in from Windows 2008R2.
However, that wasn't quite the right way to install Remote Desktop Services on Windows 2012 and later. This tutorial will show how to install Remote Desktop Services in Windows Server 2016, but it can be applied to Windows 2012 or Windows 2012R2. This tutorial assumes that there are no Windows 2012 or later versions of Remote Desktop Services installation in the Windows domain.