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

Similar Messages

Rds 2012 r2 - Connection Broker - Round Robin DNS

I am working on building a 2012 r2 RDS setup with 2 session hosts, a web app, and a CB. We are currently using 2008 r2 in a rds farm setup that is working perfectly, but wanted to get some of the enhancements in 2012 r2.. so that is why i am going
down this path.
It sounds like when doing reading, is that we can no longer just drop the fqdn of the dns rr of the session hosts in the RDP client and it will connect. Instead we need to log onto the web access portal and connect that way? I tried the DNS RR
to point to the session hosts, and that seemed to work, but had issues when disconnecting and reconnecting it would push me to another session host.
Is there a way to get it back to using DNS RR and the session broker work like it did in 2008 r2? I feel like end users are going to struggle when working from home and setting up a RDP client. Or do i just not use the connection broker and use a Load
Balancer like HA PRoxy?
The documentation is very lacking on RDS on the new os...
Thanks in advance for any advice

Hi James,
Thank you for posting in Windows Server Forum.
From Server 2012\R2 we normally have initial connections going to the broker and not to our RDSH server directly as previously for server 2008 R2. Yeah we can use DNS RR for your RDS environment but with DNS RR is that it is unaware if the server is online
or offline while my load balancer is service aware. So in case of a problem with a connection broker the request will be redirected to the active connection broker thanks to my load balancer. DNS RR does not have this feature. So it’s good idea if you can
use NLB or any 3rd party Load balancer for web and gateway services. You can refer
this thread for information.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Server 2012 RDS - Remote Desktop Connection Broker Client failed to redirect the user domain\username. Error: NULL

Seeing the error listed here.
The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database.
Pooled virtual desktop collection name: NULL
Error: Error code: 0xFFFFFFFF.
Broker and Hyper-V are on the same physical machine.
Any ideas on where to start troubleshooting this?
Used the happy wizard to create everything, and got no errors.
I have created a small pool collection, and given rights to domain users. Everything "looks" good.

I have the same problem.
(Making this long hand for those who come after)
I have installed SQl Management Studio Express 2012 SP1
http://www.microsoft.com/en-us/download/details.aspx?id=29062
(You only need the one file "SQLManagementStudio_x64_ENU.exe")
Ran this as Administrator
And typed in the Server Name field
\\.\pipe\MICROSOFT##WID\tsql\query
Then hit connect.
Expanded Databases (+sign)
Expanded RDCms
Expanded Tables
Right Clicked on rds.target, select Edit top 200 rows
Right Clicked and copied, then pasted this into a notepad file on the desktop (As a backup)
Right Clicked and selected Delete to delete the row with the data in it (and PoolID was set to Null in this row)
Did the same for rds.pool
Manually added Remote Desktop server into the MEMBER OF tab of
“Windows Authorization Access Group” via Active Directory Users and Computers. As this domain was Windows 2003 Native when the RDS server was first installed.
Rebooted server and same issue>
Checked SQL again and rows had come back.
Is that what you meant by "delete
the rds.target and rds.pool with pool id = NULL"?
Not a SQL guru, so any help appreciated.

Windows Server 2012 R2 Connection Broker migration

Hi All,
I'm in the process of a VMware to Hyper-V migration and whilst in the process rather than migrating the 2012 RDS VM's over to Hyper-V I have decided to setup a bunch of 2012 R2 VMs. My original setup was
1 x Windows Server 2012 VM running RDSCB, RDSGW & RDSWA
2 x Windows Server 2012 VMs running RDSSH
My new environment runs
1 x Windows Server 2012 R2 VM running RDSCB, RDSGW & RDSWA
2 x Windows Server 2012 R2 running RDSSH
I have the connection broker running in HA mode for SSO purposes and publishing the correct name. This also made life easier when running the upgrade as I joined the new 2012 R2 VM to connection broker group which worked fine.
I then set the new 2012 R2 RDSCB VM as the active connection broker. At this point the old 2012 VM was decommissioned (Without the RDS roles removed). As the old 2012 VM is now offline and un contactable when I add any new session hosts to the collection
I see an error stating it can't contact the old 2012 RDSCB.
I have been through the RDS connection broker database and removed any reference to the old RDSCB VM but this hasn't helped. Does anybody have any other ideas or would you suggest re creating the collections from scratch?
Alex

Hi Alex,
To avoid future problems I recommend you wipe out the RDS deployment and recreate it again so that you will have a fresh database. There is no need to switch to HA mode just so that you can change the published name. I created a cmdlet that allows
you to change it in non-HA environments:
Change published FQDN for Server 2012 or 2012 R2 RDS Deployment
http://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80
-TP

Win 7 client waits a long time at "initializing remote connection" when connecting to RDS Collection through Connection Broker

I have fully patched windows 7 clients with the RDP 8.0 client (Shell Version 6.2.9200) that take over a minute to connect to an RDS session host through a connection broker.
All servers are 2012 R2.
On the RDS Session Host it eventually gets connected to I get this warning
ID 20499
Remote Desktop Services has taken too long to load the user configuration from server \\myserver for user myuser
edit:
My windows 8.1 machine running RDP 8.1 in the same environment connects with no delay. That session connection also gets the warning ID 20499 so that seems to be another issue

Hi,
Did you check with other user account, does it gives same issue?
May be the issue caused by some network related. For that you can set the Auto tuning level. For this refer
this link
which will help to provide you more guide. You can try some command on client system (Quoted from Link).
Run a command prompt (cmd.exe) as an Administrator
Disable the autotunning feature
netsh interface tcp set global autotuninglevel=disabled
If you want to re-enable it:
netsh interface tcp set global autotuninglevel=normal
In some cases you may need to use this command in addition to the above, but I didn't have to:
netsh interface tcp set global rss=disabled
Run this command for faster Network
netsh interface tcp set global autotuninglevel=highlyrestricted
For more troubleshooting related to network issue, you can refer to “HSN for Windows Server 2012”. Also you can refer “Troubleshooting
Slow Logons”.
Hope it helps!
Thanks.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

RDS 2012 re-connection after live migration.

Is there a way to speed up the re-connection after a live migration?
So if i am in a vm that live migrates it feels like it hangs for about 10 seconds the reconnects and is fine..... While this is OK its not ideal. Is there a way to improve this?

Actually 10 seconds sounds like a very long time to me. In my experience using Shared Nothing Live Migration I've seen the switch being almost instantaneous, with a continual ping possibly dropping one or two packets, and certainly quick enough that it's
unlikely any users would notice the change. So in terms of whether it can be improved I'd say yes.
As you can see from the technical overview here
http://technet.microsoft.com/en-us/library/hh831435.aspx the final step is for a signal to be sent to the switch informing it of the new MAC address of the servers new destination, so I wonder if the slow switch over might be connected to that, or perhaps
some other network issue.
Is the network connection poor between the servers which might cause a delay during the final sync of changes between the server copies? Are you moving between subnets?

Connection Broker HA - Error Connecting to Connection Broker

I am trying to setup HA for my three connection brokers.
SQL Server
I have added the instance with the login with the three connection brokers in the group on the domain and have enabled the dbcreator and public for that user login. All named pipes and TCP/IP settings are enabled on the instance with the right IP address
and port numbers.
Connection Brokers
I have installed the native client that matches the SQL installation
I am not able to get this going, I continue to get this error.
FYI, my SQL server is on another server but is working good for my other SQL instances for my other databases
Help me :)

Hi Matthew,
Thank you for posting in Windows Server Forum.
From the error seems there is configuration issue with SQL server on RD server for HA. You need to recheck the configuration for SQL server and also for RDCB HA. Create a folder on the root directory of the SQL Server (C:\RDCB) “if a local path is used”. Ensure
that all RDS servers are added to the Server pool. Check DNS configuration for DNS RR. Check the security permission, security group and all related things. You can folllow below article for information.
- Configure SQL for RDS 2012
- RD Connection Broker High Availability in Windows Server 2012
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]

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

The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database.

When I try to install Connection Broker on a Windows 2012 R2 Server in a Windows 2003 domain I get this error:
The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database.
Pooled virtual desktop collection name: NULL
Error: Logon to the database failed.
I have added both the Connection Broker server and the 2 remote desktop servers (also Windows 2012 R2 Servers) to the "Windows Authorization Access Group" in the domain according to this: http://support.microsoft.com/kb/331951
But it still does not work :-(
I keep getting same error....
Any idea what I might be missing ?

Hi,
Thank you for posting in Windows Server Forum.
Firstly please let us know by which method you have setup RDS role. You can have more advantage and feature when you will install with Standard deployment instead of Quick start deployment. So if you have setup with quick start option then you can try installing
with standard type and check the result.
In addition, please check SQL server database is properly configured for RDS server. Also check that domain controller properly communicates. Kindly go through below thread for more information.
Server 2012 RDS - Remote
Desktop Connection Broker Client failed to redirect the user domain\username. Error: NULL
Hope it helps!
Thanks.
Dharmesh Solanki

RDS 2012 in-place upgrade to 2012 R2

Hello,
we have RDS deployment which consists of three 2012 servers:
connection broker/licensing server
web access/gateway server
session host server
Planning to upgrade to 2012 R2, does the order in which to upgrade servers matter? Or can I start from whichever server I see fit?

I upgraded RDCB/Licencing server first, then Web Access/Gateway server. My RDSH upgrade failed, but deployment seems to work with two 2012 R2 servers and RDSH 2012. Also added a second RDSH server (2012 R2), to replace 2012 which was failing to upgrade.

Windows 2008 R2 with Connection Broker

Hi
Ive been trying to add windows 2008 r2 farm to vdi.
Ive done the steps to install the certificate etc on RDS hosts. I can add either one of the hosts as a desktop provider. But when i want to add 2 or more hosts to one desktop provider VDI complains the host belongs to a different farm. Although i've checked the farm names and loadballancing works.
whats the problem here ?

The name defaults to the hostname. it doesnt pull the farm name from the winrm if you mean that.
That command says it can not find resource.
C:\Users\Administrator>winrm e wmi/root/MicrosoftNLB/* -filter:"select ClusterNa
me from MicrosoftNLB_ClusterSetting"
WSManFault
Message
ProviderFault
WSManFault
Message = The WS-Management service cannot process the request.
The service cannot find the resource identified by the resource URI and selector
s.
Error number: -2144108544 0x80338000
The WS-Management service cannot process the request. The service cannot find th
e resource identified by the resource URI and selectors.
Basicly what i did.
Install RDS Host on 2 servers.
Install RDS Connection broker on 1 server
Add RDS hosts to Connection broker local secuirty group
Joined 2 RDS hosts to the connection broker and same farm. Enabled RDS Load balancing.
added DNS entries for farm name.
Installed selfssl certificate ect... for WinRM.
Here the steps were a bit different than in the docs. 2008 r2 is a bit different.
1. Cant install resource kit 6.0. but i got arround that no problem. I think i saw some IIS resource kit allready available in the Windows "Features" but nevermind. Selfssl worked.
2. I couldnt do the winrrm crate/config/listener.... command. I had to run winrm qc (quickconfig) first. And then it worked.
rest of the story u allready know :)
regards

What ports to open between Connection broker and Web access hosts

I have setup a 4 node 2008 R2 RDS farm (1 connection broker, 1 Web access, and 2 session hosts.) They were all built from the same image, but the web access and connection broker will not talk to each other. They are all on the same subnet, and ips are x.x.x.200-203 The Web access server can ping the Sesions hosts, the session hosts can ping each other, web access and the connection broker. But the Web access and Connection broker cant ping each other. I turned off the windows firewall and they can ping, and connect... So whats ports does it need open?
Thanks!
~M

Hello,
Do you need any further helps? Please let us know it. Thanks.
· Lionel Chen
TechNet Subscriber Support in forum
If you have any feedback on our support, please [email protected]
This posting is provided "AS IS" with no warranties, and confers no rights.

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]

RDS 2012 Connection Broker and round robin DNS?

Hi,
I have a set-up with three session host servers and one of them is also a connection broker. Round robin DNS is configured for the three servers and the clients, who are all on our internal networks, can connect just fine to the farm name. My
questions is, is there any point in having round robin configured since the connections still need to go through the CB? Could i just have one DNS-record for the farm name pointing to the CB? My initial though was that round robin would add
redundancy, but does it realy? I've tried to find answers on this but none of the articles and posts i've found are realy clear to me.
Quite often the initial connection for clients is slow and my theory is that it's caused by the RR DNS records.

Hi,
Thank you for posting in Windows Server Forum.
I think we need to have DNS RR entries for our RDS environment because DNS RR will be used by RDP clients to connect to the RD Connection Broker servers. Once when we allowed the entries of all server to DNS RR, when there is alternate connection need to capture
for following server it will provided by DNS RR.
During the connection process, the end nodes (RDVH, RDSH, RDWA) will get configured with all the RD Connection Broker server names, and they will randomly choose one to connect to. The RDP clients will use the DNS Round Robin name configured to connect to the
RD Connection Broker servers randomly.
More information.
RD Connection Broker High Availability in Windows Server 2012
http://blogs.msdn.com/b/rds/archive/2012/06/27/rd-connection-broker-high-availability-in-windows-server-2012.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

RDS 2012 R2 - open connection in windowed mode?

We built a new RDS 2012 R2 environment and are publishing a full desktop for use with remote users. The issue we are having is we would like the users to be able to open the connection in a windowed mode. Right now when the users logs onto the RD web access
server and clicks the collection icon the connection opens full screen across all the monitors the user has. I see no way to configure this option. Is is possible to have the connection open in a windows VS full screen across every monitor?

Hi Brock,
Firstly sorry for delay response.
You can set RDP setting for RDS Desktopheight & DesktopWidth. Refer this article for more information.
In addition, you can use mstsc option for editing existing RDC(.rdp) configuration file. Also you can use
mstsc /span for multiple monitor. Please check below articles for more details.
1. Mstsc
2. Using Multiple Monitors in Remote Desktop Session
Hope it helps!
Thanks,
Dharmesh

RDS 2012 R2 Connection broker in HA mode SQL mirroring issue

Similar Messages

Maybe you are looking for