Missing cbclient.h - Remote Desktop Connection Broker client API

Hi,
I am searching for cbclient.h, which is referenced in the "Remote Desktop Connection Broker client API" documentation:
msdn.microsoft.com/en-us/library/hh769100/
However, I could not find cbclient.h in any Windows SDK (I searched in the Windows 7, Windows 8, Windows 8.1 SDKs).
I found a question on these forums from 2012 asking for the same thing, but there is no public answer:
http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/9b51f493-2b32-4feb-a62b-bc74aa163460/remote-desktop-connection-broker-client-api-headers?forum=windowssdk
Where is cbclient.h, and why is it missing if it is referenced by the public documentation?
Thank you!

Did you ever get a response?

Similar Messages

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.

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

Server 2012 R2 Remote Desktop Connection Broker

I have installed RDS on a server named PLUTO on which Windows 2012 R2 datacenter is in. There is a domain controller (domain name: AGROSY) running on a Linux server. We have used Samba 3.6.6 to control the file sharing system.
When I attempt to install RDS in Server Manager, it states as following: could not retrieve the deployment information from RD connection broker server pluto.AGROSY.
Then, I searched a lot of solutions, e.g. and tried as following:
Enter-PSSession -ComputerName pluto --> which works;
but Enter-PSSession -ComputerName pluto.AGROSY --> which gives the error message as: Enter-PSSession : Connecting to remote server pluto.AGROSY failed with the following error message : WinRM cannot process the request. The following
error with errorcode 0x80090311 occurred while using Kerberos authentication: There are currently no logon servers available to service the logon request.
If I ping the pluto.AGROSY, it works as well.
I have no idea how it can be solved, please help me out. Thanks a lot!

Hi,
Thanks for your comment. Sorry for late reply.
Initially please enable the PowerShell remoting in your case.
Enable-PSRemoting
http://technet.microsoft.com/en-us/library/hh849694.aspx
For FQDN name, please see that RDCB is properly configured and also certificate which you have used for RDS environment must be trusted with its private key and must match the FQDN name of the server. Did you seen the certificate has been properly used and
configured. You can go through following article for certificate and also for configuring RDCB role.
Configuring RDS 2012 Certificates and SSO
Configuring HA for the Remote Desktop Connection Broker in a 2012 RDS Farm
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

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/

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

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]

Server 2012 R2 Remote Desktop Connection Broker, Server Name Change.

We have a server that was the connection broker, We changed its name and now the connection broker wont recognize the new name. It continutes to want the old server. Unfortunately we cant change it back. Is there a fix for this?
We tried the powershell command but it doesnt see the old server name and errors out.

Hi,
Changing the name of a RD Connection Broker server is not supported. If you are able to remove RD Connection Broker Role Service and install a new RDS deployment you may be able to get it working again (with perhaps a few registry fixes),
but you will lose all of the configuration data associated with your deployment. If you have a very basic RDS deployment it may not be a big deal to recreate the collections, configure settings, publish
RemoteApps, etc., as they were before.
Another potential option if you were able to temporarily change the name back would be to switch to HA mode with the database stored on the local server (in SQL Express), add another RDCB server, remove RDCB from the original (leaving the SQL Express database
still functional), rename the server, add it back as a RDCB server, then remove RDCB from the second server. I have not tried this procedure but at first glance I believe it should work, although it may be a bit complicated if you are not well versed
with 2012 R2 RDS.
If this is a small environment you may want to consider backing up any data on the servers and then reinstalling all of the RDS servers from scratch.
It is possible to manually fix the issue you are seeing by editing the RDMS database, editing the registries of all the RDS servers, and other related tasks, however, I would not suggest it due to the complexity.
-TP

Remote Desktop Connection Server 2012 Clients only using on DC as Logon Server.

I am using Server 2012 and have an RDC Server running on a VM. Originally I had ordered the licensed version as Essentials was provided to me which does not allow for a full domain environment, which is required for the RDC server. Anyway, I
used Eval versions to get started, not thinking or realizing that the DC would never be able to get Activated since it is an Eval. So after 4 days I have finally, loaded Server 2012 on a new VM, promoted to DC, Transferred FSMO roles...DNS is up and
replicating across both DC's. The Eval keeps shutting off and was going to demote it and remove, but whenever it is shutdown the Clients receive a "No Logon Servers are available " error. I start up the old DC and it works. I doublechecked
all of the roles have been moved, I checked the RDC gateway, everything points to the same Domain information, but when I check an account using 'CMD set' it shows the old DC as the Logon Server. Is there something I am missing in the RD Gateway or somewhere
else. Is there a way to force it to use the new DC? I have tried setting the options in remote desktop connection to use a particular TS Gateway setting and it doesnt seem to work. Can someone please help me think about this and offer a
suggestion or let me know if you need more info. I can figure nothing else out at this point.
Thanks so much in Advance.
-T

it sounds like your clients / rdc servers may still be pointing to the old DC for DNS.
Can you check you have updated DNS on the clients to talk to your new domain controller.
Regards,
Denis Cooper
MCITP EA - MCT
Help keep the forums tidy, if this has helped please mark it as an answer
The new DC is the only DNS server listed on the RDC Server and is the only DNS listed for the clients other than the gateway which have as a secondary. If I change the static on the old DC I cannot login, as soon as I put it back, I can login and it
shows that DC as the logon server.
I did a simple recursive test on both DNS servers....The new Domain Controller passes, the Old One which I am trying to remove, does not.
I will reply with any other updates as I continue to look into this and thanks for the suggestions.
So I also Pinged the domain from the RDC Server as suggested and it replies back with the old DC IP.
Not sure why.

Remote Desktop Connection Client 9.3.9600 unable to connect to Server 2012 RDS via Gateway

Hi,
I have a Windows Sever 2012 R2 RDS environment with two Gateways servers configured in high availability mode (RD Web Access, RD Gateway, RD Connection Broker roles installed) and four Windows Server 2012 R2 RDS Session Hosts. The servers are all running
the most recent public server updates. With this configuration I when connecting externally using a Windows 7 computer with the older Remote Desktop Connection client (6.1.7601) I am able to connect without any problems however when I try connecting with a
newer client from a computer running Windows 8.1 and the 9.3.9600 client I am unable to connect.
At the moment a NAT rule is configured to pass 80/443 traffic to only one of the RDS gateway servers, I've removed our load balancer from the configuration for the moment to reduce the complexity.
No error is generated by the client when it tries to connect it just stops trying to connect after a while.
On the Gateways servers event logs for
Things I have looked into so far.
- I've double and triple checked the RDS configuration and checked it against one of my other clients configurations that is working and they are identical.
- Connecting from an older client version works fine.
I'm not sure what else can be checked does anyone have any ideas?

Hi,
1. What entries are you seeing in the RD Gateway's log? Event Viewer\ Applications and Services Logs\ Microsoft\ Windows\ TerminalServices-Gateway
2. How come you are not forwarding UDP port 3391 in addition to TCP port 443? It should work without UDP, but you will not have UDP support which is one of the benefits of RDP 8.0/8.1.
3. Are there any non-default group policy settings being applied to the servers and/or client PCs? To be clear, I'm asking if any changes have been made to the default local and domain security policies, group policy objects, new GPOs that may have
been added, etc., that are applicable to the servers and or client PCs.
-TP

T5325 Thin Clients losing remote desktop connection

My company just bought about 50 of these thin clients and they are setup to run an automatic remote desktop connection. I have the connection setup to auto start when the thin client is powered on and it just brings the user to a windows login screen. After they have logged in and leave their thin client to go on break sometimes it just brings them to a blank screen with an HP logo and the thin client has to be restarted to get back into the remote desktop, or I have to go into admin and restart the RDP connection. Any idea why this is happening? Is there a setting somewhere I need to change?
Any help would be great!

We are having this same issue and it is maddening. I have contacted HP on several occasions and I don't know if it is the language barrier or simple ignorance, but so far the issue is ongoing. I have looked high and low on the net and no one seems to be able to tell me why this is happening despite a number of plausible theories. We have a couple hundred terminals throughout the company which are spread across three servers none of which are close to congested yet.. However, the 10 or so t5325's we have are used specifically for digital signage. They run automated sessions that launch animated JAVA windows. They run great for the most part, but seemingly at random they will freeze in their tracks. The sessions drop from our terminal server and cannot be restarted remotely. After the units are power cycled they come back up directly and begin their sessions again. You can shadow these units (VNC) and the moment the display come on the unit closes the RDP session and reopens the same and start running again, odd behavior. I have tried changing session logout timers, disabling / enabling TCP settings, creating client-side refresh scripts, restarting the sessions at regular intervals via admin script, flashing BIOS and ThinPro OS to the current level, voodoo rituals, and pagan sacrifice. Yet, they still behave in exactly the same manner with no actions on my part having any apparent affect.. Currently, I am of the mind to purchase small all-in-one pc's to do the job. If anyone knows of any way to fix this PLEASE respond to this post.

Easy print not working on a 64 bit Windows 8.1 client with Remote Desktop connection version 8.1

Easy print is not working on a 64 bit Windows 8.1 client with Remote Desktop connection version 8.1 . Printers dont get redirected when you connect to the terminal server. The server we are connecting to has Windows 2008 server. On 32 bit Windows
7 and windows XP clients Easy print is working fine and printers get redirected in terminal server.

I am having the exact same problem. Windows 7 works fine, but 8.1 will not redirect printers. Others said to check local policy terminal services settings and my setting are all set as they should.
I think Windows 8.1 is not telling the terminal server what printers it has.

Bug report: Under Remote Desktop Connection, local units and resources menu has OK button missing

I've noticed that the "Local units and resources" in Remote Desktop Connection is missing an OK button. It seems to be a localization issue because I changed my Windows profile language to English, logged out and back in again, started RDC and
the Ok and Cancel button became visible. Changed my language back to Norwegian again and the buttons are gone again.
I have also confirmed this by testing the same on a clean new installation.
Temporary Work-around: Select an option, press tab-key once (it will select the OK button which you cannot see), then press Enter.

Hi,
Based on my test,I got the same result.
Thanks for your feedback.
We will submit this issue to Microsoft product team.
Regards,
Kelvin Xu
TechNet Community Support

Universal or alternativ Remote Desktop Connection client

Hi everyone,
I was wondering whether one of you, know of a better and maybe even in Universal of the Microsoft 'Desktop Remote Connection' client.
It's because I have an Intel iMac, and remotes my company desktop, but the DRC application are a bit slow in screenupdates and key strokes compared to the Windows client. I am guessing that it as to do with the Rostatta layer, which slows the application.
Any surgestion?

Hi,
I wasn’t able to find group policy setting to optimize memory usage for Windows Server 2012/2012 R2, could be due to its added new features need to consume more memory.
Besides, memory usage of remote desktop connection depends on the programs running within the session, you may try to check programs those are open within different sessions to determine which one is causing too much memory.
If memory usage is abnormally high, please keep systems fully patched.
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]

Microsoft Remote Desktop Connection Client for Mac Not Working

I recently purchased Office 2011 for Mac. I work at home on my Mac at work on Windows 7. I also have a work laptop, running Windows 7, that comes home with me. My goal is to RDC my Mac to the laptop running Windows 7 to reduce desktop clutter, and easily work between machines.
I CAN NOT FIGURE OUT how to get Microsoft RDC:mac to connect to my pc.
I know that the pc allows remote desktop connections because I often use RDC at work from PC to PC.
SOME PLEASE HELP! I have spent hours and hours trying to figure this out and I think it is the time capsule that is causing the problem.
My research has found that I have to use port 3389 to get this done. I am pretty computer savy but when it comes to networking I guess I have no clue. I have tried just about everything a and can't figure it out.
Thanks to anyone that can dedicate some time to configureing my time capsule to allow for RDC.

I cannot quite put together your whole network..
I work at home on my Mac at work on Windows 7. I also have a work laptop, running Windows 7, that comes home with me. My goal is to RDC my Mac to the laptop running Windows 7 to reduce desktop clutter, and easily work between machines.
So this is in local lan.. the PC laptop running win7 and the Mac loaded with RDC software. If this is local lan then the issue is nothing to do with TC.
That is only if you are trying to connect from work. to home through the router at work and TC at home. On local lan there is no blocking to ports. Are you using the local network IP of the PC Laptop?
Explain a bit further as it needs a bit more clarification.

Missing cbclient.h - Remote Desktop Connection Broker client API

Similar Messages

Maybe you are looking for