none
Server 2016 Cannot install RDS RRS feed

  • Question

  • Hi,

    I have been trying to deploy a server 2016 RDS and its weirdly giving me this error at this stage. I cant say I have had this problem before either! 

    I cant get anything out of event viewer which seems to point me at what is faulting. 

    The server has been rebuilt twice but still now luck.

    We suspected a conflict with an older RDS in the live environment which we have also removed but still get to this point.

    Is this likely to be a fault in the domain somewhere?

    Any help would be greatly appreciated.

    many Thanks,

    Steven Parsons 

    Wednesday, August 21, 2019 2:31 PM

Answers

All replies

  • Refer this,

    https://fabrikam.wordpress.com/2013/07/15/connection-broker-installation-failedremote-desktop-deployment-issues/

    1. You try to install the Remote Desktop Connection Broker (RDCB) on a server that also has the Active Directory Domain Server (domain controller) role installed. This configuration is not supported by Microsoft. You need to install the RDCB on a server that does not have this role installed. See: Remote Desktop Services role cannot co-exist with AD DS role on Windows Server 2012 http://support.microsoft.com/kb/2799605
    2. If you don’t have the Active Directory Domain Service install, this issue might be caused by the Windows internal database (WID) that the connection broker installs and the Windows Update KB2821895. If you have KB2821895 installed, unfortunately you can not uninstall this KB. Try to install the Remote Desktop Connection Broker (RDBC) role on a server that does not have this Windows update. 
      There is currently no official communication from Microsoft that here is an issue with RDBC and KB2821895. However, try the RDBC installation without this KB and see what happens.

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/fd13f6a2-6f2b-482c-bd2b-14dc6c0894e0/windows-server-2016-rd-connection-broker-failed-to-install-because-one-or-more-parent-service?forum=winserverTS

    1. Open PowerShell, and type “get-windowsfeature” with enter.
    2. Check the cmdlet result and confirm that if Windows Internal Database has been installed. 

    If WID(Windows Internal Database) has been installed:
    1. Open Run, type “services.msc” and end with enter.
    2. Find service Windows Internal Database, open its Properties – Log On, make sure it has been configured with “Local system account”.
    3. Save the change and re-start the service, try to install RD CB again.

    If problem persists, please try:
    1. Uninstall the Windows Internal Database. 
    2. Rename the old WID (C:\Windows\) to WID_old.
    3. Try to install RDCB again to check the result.

    Thursday, August 22, 2019 12:42 AM
  • HI
    1 can you check if there more related log information in below location?
    %windir%\Logs
    RDMSDeploymentUI.txt
    C:\Users\<username>\AppData\Local\Temp
    RDMSUI-trace.log
    Introduction to log files that are useful for troubleshooting RDS issues in Windows Server 2012
    https://support.microsoft.com/en-my/help/2747656/introduction-to-log-files-that-are-useful-for-troubleshooting-rds-issu

    2 when the problem happen ,is there more related logs in below location ?
    event viewer\windows logs\
    application
    security
    system
    on other RDS related server
    Event Viewer – Applications and Services Logs – Microsoft – Windows – TerminalServices-****
    Event Viewer – Applications and Services Logs – Microsoft – Windows –remote desktop management service
    Event Viewer – Applications and Services Logs – Microsoft – Windows – RemoteDesktopServices-****
    Event Viewer – Applications and Services Logs – Microsoft – Windows-remoteapp and desktop connections
    Event Viewer – Applications and Services Logs – Microsoft – Windows-remoteapp and desktop connection management


    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, August 22, 2019 8:07 AM
    Moderator
  • Refer this,

    https://fabrikam.wordpress.com/2013/07/15/connection-broker-installation-failedremote-desktop-deployment-issues/

    1. You try to install the Remote Desktop Connection Broker (RDCB) on a server that also has the Active Directory Domain Server (domain controller) role installed. This configuration is not supported by Microsoft. You need to install the RDCB on a server that does not have this role installed. See: Remote Desktop Services role cannot co-exist with AD DS role on Windows Server 2012 http://support.microsoft.com/kb/2799605
    2. If you don’t have the Active Directory Domain Service install, this issue might be caused by the Windows internal database (WID) that the connection broker installs and the Windows Update KB2821895. If you have KB2821895 installed, unfortunately you can not uninstall this KB. Try to install the Remote Desktop Connection Broker (RDBC) role on a server that does not have this Windows update. 
      There is currently no official communication from Microsoft that here is an issue with RDBC and KB2821895. However, try the RDBC installation without this KB and see what happens.

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/fd13f6a2-6f2b-482c-bd2b-14dc6c0894e0/windows-server-2016-rd-connection-broker-failed-to-install-because-one-or-more-parent-service?forum=winserverTS

    1. Open PowerShell, and type “get-windowsfeature” with enter.
    2. Check the cmdlet result and confirm that if Windows Internal Database has been installed. 

    If WID(Windows Internal Database) has been installed:
    1. Open Run, type “services.msc” and end with enter.
    2. Find service Windows Internal Database, open its Properties – Log On, make sure it has been configured with “Local system account”.
    3. Save the change and re-start the service, try to install RD CB again.

    If problem persists, please try:
    1. Uninstall the Windows Internal Database. 
    2. Rename the old WID (C:\Windows\) to WID_old.
    3. Try to install RDCB again to check the result.

    Hi Udara,

    Looking from your instructions we found it was the Windows internal database service. It was struggling to start, once we renamed the WID to old. the service was able to start. No idea what broke it in the first place but greatly appreciated! 

    Also thank you ANDY You for your suggestion as well :)!

    Kind Regards,

    Steveo


    Friday, August 23, 2019 8:56 AM