RDM embedded issue

If I check the connection Broker logs I get the following :
Under TerminalServices-SessionBroker/Admin :
RD Connection Broker failed to process the connection request for user DOMAIN\user.
Farm name specified in user's RDP file (hints) could not be found.
Error: The farm specified for the connection is not present.

Under TerminalServices-SessionBroker-Clietn/Operational :
Remote Desktop Connection Broker Client failed to redirect the user DOMAIN\user.
Error: NULL

and

Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.
User : DOMAIN\user
Error: Element not found.

Like I said before, with rdp file it works with same parameters with all the collection I have.
The strange thing is that I have one collection that is working on RDM, but all others are not working with RDM :/

Regards

Hello Robin,

Thank you for contacting us on that matter!

Would it be possible for you to compare the XML of the RDP entry that works in RDM and the one that doesn't? By doing so, you should be able to see which parameters differ.

To obtain the XML of your entries, you will need to select them 1 at a time, right-click -> clipboard -> copy -> go under the "Preview" tab and copy its content in the text editor tool that you will use to compare them. If you prefer, you can also send me a copy of the XML of your entries, after making sure that the sensitive information it contains has been replaced with test data, via Private Message in order for me to compare them.

Best regards,

Hello James,

Thanks for your answer.
It looks like it the same data

<?xml version="1.0"?>
<ArrayOfConnection>
<Connection>
<RDP>
<AlternateFullAddress>FARM.local</AlternateFullAddress>
<KeyboardLayoutText>Default</KeyboardLayoutText>
<LoadBalanceInfo>tsv://MS Terminal Services Plugin.1.CollectionNAME1</LoadBalanceInfo>
<NetworkLevelAuthentication>true</NetworkLevelAuthentication>
</RDP>
<ConnectionType>RDPConfigured</ConnectionType>
<CreatedBy>MyUSER</CreatedBy>
<CreationDateTime>2021-01-13T13:24:15</CreationDateTime>
<ID>c2ee88ee-5bc3-4b96-be6b-0146851db879</ID>
<Name>FARM-Name</Name>
<OpenEmbedded>true</OpenEmbedded>
<Stamp>66291bf5-0a67-42d7-bbd8-4b845c15f105</Stamp>
<Url>FARM.local</Url>
<UsesSerialPorts>false</UsesSerialPorts>
</Connection>
</ArrayOfConnection>


<?xml version="1.0"?>
<ArrayOfConnection>
<Connection>
<RDP>
<AlternateFullAddress>FARM.local</AlternateFullAddress>
<KeyboardLayoutText>Default</KeyboardLayoutText>
<LoadBalanceInfo>tsv://MS Terminal Services Plugin.1.CollectionNAME2</LoadBalanceInfo>
<NetworkLevelAuthentication>true</NetworkLevelAuthentication>
</RDP>
<ConnectionType>RDPConfigured</ConnectionType>
<CreatedBy>MyUSER</CreatedBy>
<CreationDateTime>2021-01-19T08:14:18</CreationDateTime>
<ID>f308a505-d75c-4b7c-83d2-f7c82b7fff4d</ID>
<Name>FARM-Name</Name>
<OpenEmbedded>true</OpenEmbedded>
<Stamp>0dacc90c-b386-465b-8b0d-ba8e2fa4a849</Stamp>
<Url>FARM.local</Url>
<UsesSerialPorts>false</UsesSerialPorts>
</Connection>
</ArrayOfConnection>

Regards

Robin

Hello,
You can try to export the .rdp instead of the .rdm and open it from mstsc.exe. You can also try to open the connection in External mode from RDM. This method will call mstsc with the generated .rdp.

Regards

Hello David,

Yes it works accross rdp or using external (tabbed) but I want to use it as embedded.
What could be the issue ?
Because when I launch my first shortcut linked to my first collection, the embedded option work
If I use my second shortcut linked to a second collection, it's not working as embedded but work as external (tabbed)
If I only change the loadbalanceinfo of the second shortcut with the loadbalanceinfo of the first shortcut... It works...
But why the second collection works with mstsc but dont work with RDM ?

This is really strange behavior :/

Hello,
This is strange and it for sure related to the connection broker. I really don't know what could be the problem. Could you try the opposite and set the load balance info from the second collection to the first one and check if the first one still connect?

Regards

I have made the change, it's not working, it's related to the collection but why ?
All collection have the same security settings.
I will try to reboot the connection broker server or change the primary server

Thanks again

Hello,

I still have the problem.
As you may know, I have different collections on my broker. Some collections are working with the embedded display and some not..
here is a little update: when I want to connect on the collection that is not working with and admin account. It doesnt work
BUT if I check the "Open console (Admin mode)" on the "general tab" and connect with the same admin account, it works.
So why did it work with the admin mode and not with the normal mode ?
And why it's working with display external but not embedded ?

Regards

Robin

Hello Robin,

Thank you for reaching back to us on that matter. Since our last communication, we have implemented a new RDP engine in RDM and I am curious to see if you experience the same issue with it.

Would it be possible for you to go under File -> Options -> Remote Desktop -> Use the first dropdown to change the RDP engine from "Latest" to "MSRDC"?


In the meantime, I will see why "Open console (Admin mode)" allows the connection to work with your admin account.

Best regards,