Db Connection Broker issues

hi all,
i am using dbconnectionbroker from the site http://www.javaexchange.com/
it works very fine but i have one issue i want to connect db with 2 different users.
how in this class i can keep 2 different users connection or connection with 2 different DB.
can any one guide me???
thx lot
thx

if some did above mention solution with different method or different connection can also share his idea.
i need this help very much.
thx

Similar Messages

  • RDS 2012 R2 Connection broker in HA mode SQL mirroring issue

    Hi,
    I have an issue where our two brokers will not connect to the failover database when the database fails over.
    Our setup:
    Database - 2 x SQL 2012 Standard with the RDCB database mirrored in high safety with automatic failover mode. 
    Brokers/Web gateways - 2 x server duel role servers in different subnets. They're configured in HA mode
    I won't include the session hosts as it's out of scope for this issue.
    So the RD database connection string has been set to:
    DatabaseConnectionString : DRIVER=SQL Server Native Client 11.0;SERVER=server2\instance2,5555;Failover_Partner=server1\instance1,5555;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;Database=RDCB
    So when this was first set, the DB was failed over and it worked. It was then failed back to the correct principal but now when failed over to the Failover_Partner it will not connect.
    I've confirmed the SQL permissions and custom port aren't an issue.
    Has anyone else experienced this issue?
    Stephen Turner

    Hi Stephen,
    Thank you for posting in Windows Server Forum.
    Did you receive any specific error\Event ID for your issue?
    Apart it seems there is some misconfiguration issue for failover cluster. If connections are empty, that means broker servers are not connecting to the mirror server database, most common problem is database security in mirror server. So check all brokers have
    full access to the mirror database and mirror database saved folder.
    For more information to recheck the steps you can go through following articles.
    Window server 2012 | Remote Desktop Connection Broker high available with SQL Server Mirror
    https://asithadesilva.wordpress.com/tag/remote-desktop-connection-broker-high-availability-with-sql-mirror/
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • RD Session broker issue; Cannot connect to one of the host servers through RDC

    Hello,
    I am testing a RD session broker role.
    So I have 4 VMs: lest call them VM1, VM2 VM3 and VM4
    VM1 is the DC and all other 3 VMs are under VM1.
    VM2 is the Session broker server.
    VM3 and VM4 are the host servers which are in a farm called Farm1.
    Now I have done everything pretty much right. VM2, VM3 and VM4 all are listed in the Session broker computer local group (which is on VM2 since it is the session broker server)
    Then I also have VM3 and VM4 setup in regards to their Remote desktop session host configuration.
    RD Connection broker is VM2 and Farm name is Farm1.
    everything sounds good right?
    Okay.. So then I also have added those "New host (A or AAAA)" for VM3 and VM4 in the DNS on VM1 (which is DC).
    Both VM3 and VM4 are set to 100 in "Relative weight of this server in the farm".
    Now I am trying to do MSTSC from VM2 to farm1.domain.net. First user goes to VM3 just fine. But when I try to do MSTSC again with the second user, it tells me this:
    The remote computer hat you are trying to connect is redirecting you to the remote computer.
    Remote Desktop Connection cannot verify that the two remote computers belong to the same farm.
    This can occur if there is another computer on your network with the same name as the computer your are trying to connect to.
    I have read 10 pages of google search about this and still have no clue what to do. I have tried flushing DNS cache on VM1. Time and date is exactly the same on all 4 VMs. 
    I also read the following thread but could not understand the answer that he has given there.
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/40be1eda-f752-4b64-bb47-dbe2156218f9/remoteapp-cannot-verify-computers-belong-to-the-same-server-farm?forum=winserverTS
    Please help me on this.
    Thanks,

    Okay, so I found the issue and was able to solve the problem.
    Here is how to do this and I wonder why most of the online guides to do this whole thing don't talk about it!
    Go to Start --> Administrative tools --> Remote desktop services --> RemoteApp Manager
    Now a new window will open and in the window there's a box which says "Overview".
    The first option will say " RD Session Host Server Setting; Clients will be redirected to: computer.domain.com"
    That's where you need to make a change. If you'd open that, it will tell you that "If the RD session Host Server is in a farm, enter the DNS name of the farm".
    So now make that "Server name" look like this: farm.domain.com or whatever your farm's DNS name is.
    Do this on all the host servers and yeah then you might need to refresh the DNS settings on the DC. 
    It should start working then :)

  • RD Connection Broker Fails to install on Windows 2012 R2, fresh install

    I have been fighting this for a week
    Trying to install RD connection broker service on a Server 2012 R2.  I've had multiple errors, ranging from the "Server pending reboot" issue, to the install just hanging for 15-20 minutes and then failing.  This is NOT on a DC, and I've
    tried it on a fresh 2012 R2 server, and a fully updated Server 2012 R2.  It has to be something on the domain I'm joined too, as I can install it with no problem on test servers/domains at my office.

    Hi CitadelTCS,
    Some folk meet this issue because the server is DC, in your case could you try to run SFC /SCANNOW then monitor this issue again.
    The related KB:
    Use the System File Checker tool to repair missing or corrupted system files
    https://support.microsoft.com/en-us/kb/929833?wa=wsignin1.0
    I’m glad to be of help to you!
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Server 2012 R2 RDS- Only want the Session Host, Connection Broker and Licensing Server!

    Hi all,
    Wondering if anyone has experience with implementing Remote Desktop Services (RDS) on Windows Server 2012 R2.
    I am doing an RDS design for a platform where we only need an RDS Session Host, Licensing Server and Connection Broker. We do not need web access as these servers will simply be jump boxes internally!
    However, implementing this correctly in our test environment has proved to be tricky. The options are:
    Use the Server Manager and do a traditional install via Roles and Features ( specifically add the Session Host, Licensing Server and Connection Broker). The installation process seems to go through ok in this scenario but when I head over to the Remote
    Desktop Services section of the Server Manager I simply get the message 'An RDS Deployment does not exist in the server pool. To create a deployment head to Roles and Features'.
    Use the specific ‘Remote Desktop Services installation’ option on the Server Manager and do a Session Based Desktop deployment and Quick Start. This installation process seems to go through correctly and the Remote Desktop Section seems to be working
    correctly via the Server Manager. However this process is ‘hard locked’ i.e. it installs the session host, web access and connection broker. I can then remove the web access component later from Roles/ Features.
    Is there a best practice (if any) for installation? i.e. Will there be any issues down the line if I remove RDS Web Access from my server while following method 2?
    There is a complete lack of documentation from Microsoft here so not sure what to do! Just need a basic RDS session based deployment.

    Hi,
    As I know from server 2012\R2 the best deployment skill is to perform via “Remote Desktop Services” installation mode with Standard deployment and don’t let single role to install. Because when we install through RDS mode, there are specific extra tools and
    services activated along with that deployment which you can’t find with single role installation. And that is for sure, when we install RDS role as of this, by default we will get install RDCB, RDSH and RDWA role installed.
    Sorry don’t have any option to try to remove that role as that role basically needed for RemoteApp and Desktop purpose. But if you want then you can try it with help of “Remove-RDServer”Powershell command.
    https://technet.microsoft.com/en-us/library/jj215506.aspx
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Server 2012 RTM Remote Desktop Connection Broker Role Won't Install

    Hey guys,
    I have been searching for and trying fixes for this for 3 days, and I've gotten no where.  Thanks in advance for trying to help me out.
    Here's the situation:
    I have a brand new installation of the Windows Server 2012 Datacenter 64-Bit RTM from MSDN.  This is my one and only server (just my personal one for home), so I'm using this single server to run all of the services that I need.  After a fresh
    installation, I added the AD and DNS roles and promoted the server to the PDC.  Then I go to add the Remote Desktop Virtualization Services (the VM virtualization role).  The installation fails, but I can't find any explanation as to why.
    I've wiped out the OS and reinstalled from scratch at leat 15 times, trying various combinations, fixes, approaches, etc.  including powershell, Remote Desktop Services Deployment, standard role-based deployment, etc.
    Using the role-based deployment, I can get every 'Remote Desktop Services' component to install except the Remote Desktop Connection Broker.  I've tried enabling RDMSUI_TRACING, but didn't get any information at all as to why it's failing.  I also
    cannot find RDMSDeploymentUI.txt log.
    I've also tried to deploy this using Powershell using this command:
    New-SessionDeployment [-ConnectionBroker] <string> [-WebAccessServer] <string> [-SessionHost] <string>
    That particular item does provide some error messages, but they seem to complain about the Session Host not being able to install due to not being able to find the connection string key in the registry for the Windows Internal Database.  However, I can
    get the session host and every other component to install using role-based deployment, except the Connection Broker.
    I've run an SFC scan, which found no issues.   I've also tried applying the one update available in Microsoft Update, and tried it without applying that update (reinstalling between attempts of course).
    I'm completely at a loss.  Has anyone encountered this before?  Any suggestions would be greatly appreciated.  Is there a powershell command for just installing the Connection Broker that might provide some additional error information, or any
    information at all?
    I would greatly appreciate any help anyone could offer.  I'm willing to try anything.  Thanks for taking the time to read this.
    Sincerely,
    Dominick

    Also Found this:
    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.
    Note: 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.
    For more information, Refer below link...
    http://fabrikam.wordpress.com/2013/07/15/connection-broker-installation-failedremote-desktop-deployment-issues/

  • Remote Desktop Connection Broker role fails to install

    Hi,
    I am having a situation where I cannot install the RDS Connection Broker on a Windows 2012 R2 that also has AD DS installed.  I understand with Windows 2012 R2, you should be able to do this.
    I suspect that the Default Domain Controller Policy might be a factor in this, but I have modified the "Log on as a Service" right to include the "NT SERVICE\ALL SERVICES" user as directed in article
    2832204. The issue persists.
    I have reviewed the event logs and the Windows Internal Database logs, and it appears the hang up is with the installation of the Windows Internal Database.  The C:\windows\wid\log\error.log file shows the following line just before the installation
    fails:
    2014-12-12 11:05:32.54 Logon       Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Could not find a login matching the name provided. [CLIENT: <named pipe>]
    I am unsure where to go from here, but I tried renaming the C:\Windows\WID folder after a reboot to see if a clean install of the Windows Internal Database would fix it, but it still has the same issue.
    Some more information on the environment:
    Recently added this Windows 2012 R2 DC to a domain that previously only had a Windows 2003 domain controller. There were no errors with the DC promotion.  Windows 2003 domain controller still resides on the network as a DC (for now).
    Planning to install RD Connection Broker and RD Web Access role services to the new Windows 2012 R2 AD DS server. 
    Thank you for any assistance you can provide to resolve this issue.
    Tim

    Hi Tim,
    Thank you for posting in Windows Server Forum.
    Initially would like to say that it’s not best practice to have RDS and AD DS role on same server (Not recommended). There are various safety reason for this case.  Instead you can do one thing, install Hyper-v on physical server and then create 2 VM (one
    for AD DS and other for RDS) in this way you can achieve your goal. Please try to install as the mentioned way and verify whether you resolved you issue. For more information you can refer following article.
    Step by Step Windows 2012 R2 Remote Desktop Services – Part 1
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Connect RD Connection Broker to SQL

    Hello I'm not being able to install RD Connection Broker with High Availability.
    The RDS deployment consists on two servers running win2012
    server1 - RDWA and RDG
    server2 - RDSH and RDCB
    The SQL server 2012 that I'm using is installed on server2 itself and had to be installed after the RDS otherwise the SQL installation failed and had to be done using the RD-install. It's working fine , I've applications that run on it.
    As when configuring RDCB HA "both" RDCB hosts access directly to the SQL DB to create a new database, their accounts need to be authenticated as a SQL login with dbcreator role.
    1 step: I checked a straight forward installation_
    Installing and Configuring RD Connection Broker High Availability in Windows Server 2012
    Failed
    2 step: I checked an installation where my problem happened.
    I checked RD Connection Broker HA – SQL Permissions
    Added the host to a domain group and added the group as an SQL login, SQL authentication failed.
    4 step: Google for how to create SQL login for a computer account and  I added it by executing:
    “CREATE LOGIN [MyDomain\MyComputer$]
    FROM WINDOWS”
    Also tried to use Add-ADcomputerServiceAccount without success.
    3 step: I ended here
    Taking a closer look at RD Connection Broker High Availability in Windows
    Server 2012
    Where I verified that none of the following explanations were correct:
    The SQL Server Native client is not installed
    A firewall is blocking SQL Access from the RD Connection Broker (port 1433)
    The incorrect SQL Server Native Client version is specified
    An incorrect SQL Server name is specified
    I tried several variations of the string to use but this is the one I think it's correct:
    DRIVER=SQL Server Native Client 11.0;SERVER=WIN2012-1;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;Database=RDCB
    The error registered on SQL is:
    "Message
    Login failed for user 'RDS\WIN2012-1$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]"
    I tried to connect via ODBC with an existing username an it succeeded.
    The problem seems to be with the computer account not existing as an SQL login...the thing is that it exists.
    I need to set this up in order to be able to change the RDCB FQDN to a public FQDN.
    How were you guys able to overcome this? Did you faced this at all?
    Thanks,
    David

    Guys,
    I suffered with a very similar problem when setting up an RDS 2012 environment using SQL Server 2014 sitting on a server core VM, and two connection brokers sitting on server core OS as well. 
    My SQL logs were filling with with login failed for the connection brokers computer account even though I had configured the SQL permissions correctly. 
    In the end it was Arjan's post above that got me fixed, rebooting the connection broker VMs. Really annoying, as I let AD propagate over night, just in case that was the issue. After simply rebooting the connection brokers, this worked. For anyone who needs
    it, my SQL databases are stored on a separate D: drive and I used the string below:
    DRIVER=SQL Server Native Client 11.0;SERVER=<SQL Server Name>;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;DATABASE=<DB Name>.
    Hope this helps someone else.

  • Windows 2008 R2 connection broker

    I have a problem related to the fact that remote desktop client are not redirected to the disconnected sessionr when they try to reconnect.
    I'm using a netscaler load balancer that uses redirection toker with the connection broker server.
    I have made a small configuration test environment that reflect my origina configuration and the problem will exist event there.
    All the servers are windows 2008 R2 with sp1 and all latest fix available using microsoft update.
    The connection broker server is a domain controller server, and the terminal server are computer member of the domain.All the information are correctl registered by the connection broker database, but is seems that it works only with administative users.
    The error that is reported
    RD Connection Broker failed to process the connection request for user DOMAIN\USER.
    Load Balancing failed OR Specified endpoint could not be found.HRESULT = 0x80070515.  
    I have found no information about the error
    0x80070515.
    Here follow the connection broker information after
    ClusterName = MYCLUSTER
    NumberOfServers = 4
    SingleSessionMode = 1
        SERVER :
        ServerName = TS018.mydomain.local ServerSingleSessionMode = 1 LoadIndicator = 655350000
        ServerIP = 10.10.4.18
        ServerWeight = 0
        ClusterName = MYCLUSTER
        NumPendRedir = 0
        No sessions on server TS018.mydomain.local
        SERVER :
        ServerName = TS020.mydomain.local ServerSingleSessionMode = 1 LoadIndicator = 655350000
        ServerIP = 10.10.4.20
        ServerWeight = 0
        ClusterName = MYCLUSTER
        NumPendRedir = 0
        NumberOfSessions = 1
            SESSION :
            UserName= mydomain\administrator    ApplicationType=     SessionState= 0
            CreateTime= 20150303101848.856647+060    DisconnectTime=
            ServerName= TS020.mydomain.local
            SessionID= 1
            ServerIP= 10.10.4.20
            TSProtocol= 2
            ResolutionWidth= 1920
            ResolutionHeight= 1080
            ColorDepth= 4
        SERVER :
        ServerName = TS019.mydomain.local ServerSingleSessionMode = 1 LoadIndicator = 655350000
        ServerIP = 10.10.4.19
        ServerWeight = 0
        ClusterName = MYCLUSTER
        NumPendRedir = 0
        NumberOfSessions = 2
            SESSION :
            UserName= mydomain\administrator    ApplicationType=     SessionState= 1
            CreateTime= 20150303101224.366219+060    DisconnectTime= 16010101000000.000000-000
            ServerName= TS019.mydomain.local
            SessionID= 1
            ServerIP= 10.10.4.19
            TSProtocol= 2
            ResolutionWidth= 1920
            ResolutionHeight= 1080
            ColorDepth= 4
            SESSION :
            UserName= mydomain\Flavio    ApplicationType= D:\Programmi\Seac\SeacCruscotto.exe    SessionState= 0
            CreateTime= 20150303121903.740379+060    DisconnectTime=
            ServerName= TS019.mydomain.local
            SessionID= 2
            ServerIP= 10.10.4.19
            TSProtocol= 2
            ResolutionWidth= 1920
            ResolutionHeight= 1080
            ColorDepth= 4
        SERVER :
        ServerName = TS017.mydomain.local ServerSingleSessionMode = 1 LoadIndicator = 655350000
        ServerIP = 10.10.4.17
        ServerWeight = 0
        ClusterName = MYCLUSTER
        NumPendRedir = 0
        No sessions on server TS017.mydomain.local
    Second dump with the disconnected user and the same user that ties to reconnect and was redirected to a new session  instead to the disconnected session. You will find two user Flavio one in disconnected state (1) and one in connected state(0)
    ClusterName = MYCLUSTER
    NumberOfServers = 4
    SingleSessionMode = 1
        SERVER :
        ServerName = TS018.mydomain.local ServerSingleSessionMode = 1 LoadIndicator = 655350000
        ServerIP = 10.10.4.18
        ServerWeight = 0
        ClusterName = MYCLUSTER
        NumPendRedir = 0
        No sessions on server TS018.mydomain.local
        SERVER :
        ServerName = TS020.mydomain.local ServerSingleSessionMode = 1 LoadIndicator = 655350000
        ServerIP = 10.10.4.20
        ServerWeight = 0
        ClusterName = MYCLUSTER
        NumPendRedir = 0
        NumberOfSessions = 1
            SESSION :
            UserName= mydomain\administrator    ApplicationType=     SessionState= 0
            CreateTime= 20150303101848.856647+060    DisconnectTime=
            ServerName= TS020.mydomain.local
            SessionID= 1
            ServerIP= 10.10.4.20
            TSProtocol= 2
            ResolutionWidth= 1920
            ResolutionHeight= 1080
            ColorDepth= 4
        SERVER :
        ServerName = TS019.mydomain.local ServerSingleSessionMode = 1 LoadIndicator = 655350000
        ServerIP = 10.10.4.19
        ServerWeight = 0
        ClusterName = MYCLUSTER
        NumPendRedir = 0
        NumberOfSessions = 2
           SESSION :
            UserName= mydomain\administrator    ApplicationType=     SessionState= 1
            CreateTime= 20150303101224.366219+060    DisconnectTime= 16010101000000.000000-000
            ServerName= TS019.mydomain.local
            SessionID= 1
            ServerIP= 10.10.4.19
            TSProtocol= 2
            ResolutionWidth= 1920
            ResolutionHeight= 1080
            ColorDepth= 4
            SESSION :
            UserName= mydomain\Flavio    ApplicationType= D:\Programmi\Seac\SeacCruscotto.exe    SessionState= 1
            CreateTime= 20150303121903.740379+060    DisconnectTime= 16010101000000.000000-000
            ServerName= TS019.mydomain.local
            SessionID= 2
            ServerIP= 10.10.4.19
            TSProtocol= 2
            ResolutionWidth= 1920
            ResolutionHeight= 1080
            ColorDepth= 4
        SERVER :
        ServerName = TS017.mydomain.local ServerSingleSessionMode = 1 LoadIndicator = 655350000
        ServerIP = 10.10.4.17
        ServerWeight = 0
        ClusterName = MYCLUSTER
        NumPendRedir = 0
        NumberOfSessions = 1
            SESSION :
            UserName= mydomain\Flavio    ApplicationType= D:\Programmi\Seac\SeacCruscotto.exe    SessionState= 0
            CreateTime= 20150303122059.706850+060    DisconnectTime=
            ServerName= TS017.mydomain.local
            SessionID= 2
            ServerIP= 10.10.4.17
            TSProtocol= 2
            ResolutionWidth= 1920
            ResolutionHeight= 1080
            ColorDepth= 4
    Any idea ?
    Thanks
    Flavio

    Hi Flavio,
    It seems that you are facing issue with the RDCB load balancing between servers. Might possible that there is some wrong configuration happens which cause this issue. Still I like you to recheck all the configuration for your environment. Also as you said it
    works with admin users, have you provide access to user to connect to the server?
    From the error description it appears to be error 802 with specific code. To troubleshoot this issue, you can apply below steps and try.
    1. Please try to limit single RDS session for TS user. 
    2. Install RDS broker to separate server
    3. Run NLB diagnose to check if any issue related to NLB
    4. Use IP address redirection instead of token redirection
    Also try to apply this policy settings.
    Computer Configuration / Administrative Templates / Windows Components / Remote Desktop Services / Remote Desktop Session Host / RD Connection Broker / 
    Use RD Connection Broker load balancing: Enabled
    Configure RD Connection Broker server name: Enabled
    And then apply gpupdate /force on every server and check the result.
    Here is the article for related error only for reference.
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • SQL EXpress Server 2012 Installed in VM for RD Connection Broker

    All,
    I have big trouble now...
    I have 2 cluster machine and created one Virtual Machine in the cluster and installed SQL Server Express 2012 in VM.
    In both cluster machine installed SQL Client 11.0.  and RD Connection Broker installed one of the Cluster machine, while configure RD HA it throws error Please refer screen shot.
    Is it right to install SQL server on Virtual Machine ?
    Is it possible SQL Server 2014 Standard installed one of the cluster machine and RD Connection Broker enable both cluster machine and make HA of RD Connection Broker HA ?
    What is the best way to achieve to enable RD Connection broker with in Cluster machine(2 Node) ?
    Please any one guide to us.
    Regards
    Venki

    Hi Venki,
    Thank you for posting in Windows Server Forum.
    Generally the error which you are facing occurs due to permission and security issue on SQL server. we need to specify the permission during RDCB setting.  Here suggest to create the database manually and check the result.
    CREATE DATABASE 'rds_db'
    Where rds_db is the database specified in your connection string
    DRIVER=SQL Server Native Client 11.0;SERVER=<SQL Server Name>;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;DATABASE=<DB Name>
    Grant DBO permissions to the service account on the RDS server and try to run your wizard again.
    Also when configuring RDCB HA, we need to create a local folder to store database which is “Remote SQL file systems”. And if local path is used create a folder on the root directory of the SQL Server (C:\RDCB).
    Please check below article for more information.
    Deploying RD Connection Broker High Availability in Windows Server 2012
    http://ryanmangansitblog.com/2013/03/30/deploying-rd-connection-broker-high-availability-in-windows-server-2012/
    RD Connection Broker HA – SQL Permissions
    http://microsoftplatform.blogspot.com/2012/04/rd-connection-broker-ha-sql-permissions.html
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • Certificate error when using connection broker on Mac client

    We're using RD Connection Broker using IP address redirection for a couple of years now. Previously Mac client were using iTap RDP without any problems. Clients are connecting using a RD Gateway server.
    When trying to connect using the latest Microsoft remote desktop client (version 8.0.24255) a certificate warning is shown saying the IP-address doesn't match the name in the certificate. The client shoudn't match the IP address with the certificate but
    should match the farm name. The error occurs when the connection broker redirects the client to a server.
    Any help is appreciated
    <style type="text/css">p, li { Version 8.0.24255</style>

    Hi MatthijsO,
    Have you updated it to 8.0.3? Does the issue persist?
    Thanks.
    Jeremy Wu
    TechNet Community Support

  • 2008R2 Connection Broker internal vs external name and UCC Certificates

    I have a RD Farm, all in 2008R2.  Consisting of Gateway, Connection Broker, multiple Session Hosts.  They belong to an AD Domain, xyz.local.  The machines have AD names, CB.xyx.local, GW.xyz.local, SH1.xyz.local, SH2.xyz.local.
    The internal DNS system has a Zone for the External Domain, MyDomain.com.  There are host records for the farm, rdpfarm.mydomain.com pointing to the Internal IP of the farm.
    The farm is accessible on the Internet at rdpfarm.mydomain.com via Public DNS.
    We have a VeriSign Public UCC Certificate, that has the public MyDomain.com SAN's for the hostnames for all the machines,  CB.MyDomain.com, GW.MyDomain.com, SH1.MyDomain.com, SH2.MyDomain.com, and the farm name is the Common Name rdpfarm.MyDomain.com. 
    (Note, as of soon, internal Domain names are no longer allowed on UCC Certificates)
    I have tried everything I can find to get the Gateway and/or the Connection Broker to answer using the rdpfarm.MyDomain.com name and match the Certificate, without success.
    As I recall in Exchange Server we face a similar problem, but there is a method in Exchange to cover this.  If there is one for an RD farm, I cannot find it.
    Any help here would be greatly appreciated.

    Hi,
    Thank you for posting in Windows Server Forum.
    Did you receive any particular error during\event id this issue?
    For certificate, here is requirement for RDS server which need to have for successful configuration.
    Basic requirements for Remote Desktop certificates:
    1. The certificate is installed into computer’s “Personal” certificate store. 
    2. The certificate has a corresponding private key. 
    3. The "Enhanced Key Usage" extension has a value of either "Server Authentication" or "Remote Desktop Authentication" (1.3.6.1.4.1.311.54.1.2). Certificates with no "Enhanced Key Usage" extension can be used as well. 
    In Windows 2008/2008 R2, you connect to the farm name, which as per DNS round robin, gets first directed to the redirector, next to the connection broker and finally to the server that will host your session.
    Please check below article for information.
    a. Certificate Requirements for Windows 2008 R2 and Windows 2012 Remote Desktop Services
    b. Configuring Remote Desktop certificates
    c. Dealing to the annoying certificate errors and multiple credential
    requests in Remote Desktop Services 2008 R2
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • RD Connection Broker randomly fails to process connection requests

    The RD Connection Broker is a Windows 2008 R2 server. It's been running without issues for 3 years. It handles three RD servers also Windows 2008 R2.
    Starting yesterday some users - not all - no longer can log on using the farm name. If the RDP file is set up to point to the server they were disconnected from then they get their session back.
    There is only one error in the TerminalServices-SessionBroker log:
    Log Name:      Microsoft-Windows-TerminalServices-SessionBroker/Operational
    Source:        Microsoft-Windows-TerminalServices-SessionBroker
    Date:          8/19/2014 15:04:18
    Event ID:      802
    Task Category: RD Connection Broker processes connection request
    Level:         Error
    Keywords:     
    User:          NETWORK SERVICE
    Computer:      NJDC1.nj.kearfott.com
    Description:
    RD Connection Broker failed to process the connection request for user NJ\a.davis.
    Load Balancing failed OR Specified endpoint could not be found.
    HRESULT = 0xfffffc0a.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-TerminalServices-SessionBroker" Guid="{D1737620-6A25-4BEF-B07B-AAC3DF44EFC9}" />
        <EventID>802</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>101</Task>
        <Opcode>11</Opcode>
        <Keywords>0x2000000000000000</Keywords>
        <TimeCreated SystemTime="2014-08-19T19:04:18.882662400Z" />
        <EventRecordID>1971452</EventRecordID>
        <Correlation />
        <Execution ProcessID="2388" ThreadID="1308" />
        <Channel>Microsoft-Windows-TerminalServices-SessionBroker/Operational</Channel>
        <Computer>NJDC1.nj.kearfott.com</Computer>
        <Security UserID="S-1-5-20" />
      </System>
      <UserData>
        <EventXML xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="Event_NS">
          <param1>NJ\a.davis</param1>
          <param2>0xfffffc0a</param2>
          <param3>8</param3>
        </EventXML>
      </UserData>
    </Event>
    The MS updates were installed last week so this issue did not happen immediately after the install.
    Any help, pointers, ideas would be greatly appreciated

    Thanks for replying, Dharmesh but I forgot to mention a couple of things:
    1. There was only one 802 event and quite a few users who could not log on using the farm name for the RDP connection. This is still happening though the majority of the users have no problem logging on to the RD servers using the farm name.
    2. Those who could not log on using the farm name could log on using a specific server name. I have not tried all the names because on the first day I had noticed that one server had no users on while the other two had lots. So when the first call came in
    I pointed the user to the one server with the smallest load.
    3. This is the first time this happens since I set up the farm.
    4. This shouldn't matter but I had uninstalled IE 11 about a week before and reinstalled IE 9. 
    5. Some users who logged on using the farm name have to be logged off as they can't log back on after a disconnect.
    I had seen the first article before I posted. Looked ant the second. I'll have to study it because at the first glance it doesn't appear to have much to do with my issue.

  • RD WebAccess doesn't show RemoteApps while using RD Connection Broker

    Environment:
    All servers have Windows Server 2008 R2 installed
    Remote Desktop Session Hosts:
    RDSH01
    RDSH02
    RDSH03
    # Installed roles:
    Remote Desktop Session Host
     Remote Desktop Web Access
    # Local Users and Groups:
    TS Web Access Computers --> Member: RDSH01, RDSH02, RDSH03
    Remote Desktop 
    Session Broker:
    DC01
    # Installed roles:
    Active Directory Domain Services
    Remote Desktop Licensing
    Remote Desktop Connection Broker
    # AD groups:
    Session Directory Computers --> Member: RDSH01, RDSH02, RDSH03
    TS Web Access Computers --> Member: DC01, RDSH01, RDSH02, RDSH03
    ## Problem ###
    For some users the RemoteApps will not be displayed on RD Web Access Web site when the
    RD connection broker DC01 is used as source! If one of the three servers is selected as RemoteApp source it works without any error.
    On DC01 I find the message “Error in the WMI interface to rdfarm.domain.local. Check that the machine is running and connected to the network. If the
    problem persists, reboot the machine. Error Code: 0x800706BA“. All connections, pings, nslookup including FQDN request works fine.
    WMI and DCOM are also checked, security permission and group membership is correct. Firewalls are all disabled!
    Any idea what to check next?

    Hi,
    Thank you for posting in Windows Server Forum.
    The error which you are facing seems to occur because the communication between the RD web access and RD connection Broker is not communicating. Please verify the below two things.
    1.  Verify that the RemoteApp and Desktop Connection Management service is started.
    2.  Log on to the RD Web Access server that is configured to use the RD Connection Broker server.
    The RD Web Access server that is configured to use the RD Connection Broker server must be available to communicate with the RD Connection Broker server.
    a.  To open Remote Desktop Web Access Configuration, click Start, point to
    Administrative Tools, point to Remote Desktop Services, and then click
    Remote Desktop Web Access Configuration.
    b.  In the Domain\user name box, type a valid domain and user account name.
    c.  In the Password box, type the password for the user account.
    d.  Verify that you can successfully log on to the RD Web Access server by using Remote Desktop Web Access Configuration.
    More information:
    Event ID 1000 — RemoteApp and Desktop Connection Management Communication
    If still not resolved then please check the below Q&A regarding RD Connection Broker.
    Q. I’m using RD Connection Broker as the RemoteApp source in RD Web Access, but RD Web Access isn’t showing any icons. Why?
    A. There are several reason for this, at last it found a bug. “There’s a
    known bug where Windows Management Instrumentation (WMI) permissions for the Terminal Services namespace disappear, leaving RD Web Access unable to query RD Connection Broker as a RemoteApp source. Re-adding the
    RD Web Access server to the TS Web Access Computers group on RD Connection Broker resolves this issue for a while (but will most likely happen again over time). See
    this TechNet Forum thread for more details and possible work-arounds.”
    More information.
    Microsoft Windows Server 2008 R2: Understand the RD Connection Broker
    Hope it helps!
    Thanks,
    Dharmesh

  • Unable to start remote desktop connection broker

    somehow I could no longer start remote desktop connection broker service. I noticed that Windows image acquisition (WIA) service could be started manually and then it stopped by itself. I am not sure if they are related or not. From event viewer, I see some
    errors as follows (may be related):
    event 485 ESENT
    tssdis (2916) An attempt to delete the file "C:\windows\system32\edbtmp.log" filed with system error 5 (0x00000005):"Access is denied." The delete file operation will fail with error- 1032 (0xfffffbf8).
    Any clue or suggestion where I can look into?
    Thank you very much!!!!!

    Hi,
    Thank you for your posting in Windows Server Forum.
    register the below files using regsvr32
    regsvr32 %systemroot%\system32\wuapi.dll 
    regsvr32 %systemroot%\system32\wuaueng.dll 
    regsvr32 %systemroot%\system32\wuaueng1.dll 
    regsvr32 %systemroot%\system32\wucltui.dll 
    regsvr32 %systemroot%\system32\wups.dll 
    regsvr32 %systemroot%\system32\wups2.dll 
    regsvr32 %systemroot%\system32\wuweb.dll 
    regsvr32 %systemroot%\system32\softpub.dll
    In addition, also Try to disable UAC for your account and reboot, this might help to resolve your issue.
    Source:
    esent 485 event wuaueng.dll
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/27cd64d0-7ec7-4732-a2ac-4c36a0513690/esent-485-event-wuauengdll?forum=winservergen
    Hope it helps!
    Thanks.
    Dharmesh Solanki

Maybe you are looking for