Protected Users Security Group (AD)
Thanks for not forgetting about it.
It's a pity, but I no longer have access to update the application.
If use creds in Apple keychain then connection is fails.
Hi,
I understood my mistake!
At first I tried to use already existing records created by another application (Microsoft Remote Desktop). It turned out that the application does not explicitly enter the user name in the keychain, but assigns an identifier. Therefore, RDM could not use it.
If create a keychain manually, it works.
My inattention. Thanks.
If use creds in Apple keychain then connection is fails.
Hi!
I added a credential of the type of Apple a keychain in the "My Account Settings" and assigned to the directory with connections type RDP "user specific settings".
Connection fails, it is reset.
The same thing happens if use the type of apple keychain in "my private Vault".
Profiler:
--> select TOP 1 ConnectionID, RepositoryID, UserID, State, Comment, ExpirationDate, MachineName, CreationDate, CreationUsername, CreationLoggedUserName
from dbo.ConnectionState
where ConnectionID = ? and State = ? and (ExpirationDate is null or ExpirationDate > ?)
order by CreationDate desc
: 56 ms
--> INSERT INTO dbo.ConnectionLog (
[ID]
,[Username]
,[MachineName]
,[Message]
,[MessageType]
,[ConnectionName]
,[ConnectionTypeName]
,[ConnectionID]
,[ConnectionUserName]
,[StartDateTime]
,[EndDateTime]
,[StartDateTimeUTC]
,[EndDateTimeUTC]
,[GroupName]
,[Comment]
,[LoggedUserName]
,[Prompt]
,[SecurityGroup]
,[Cost]
,[Data]
,[UserInfoID]
,[SupportClose]
,[CloseMode]
,[OpenMode]
,[HostName]
,[Application]
,[Version]
,[IsEmbedded]
,[RepositoryID]
,[TicketNumber]
)
VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) : 138 ms
--> UPDATE dbo.ConnectionLog SET
[EndDateTime] = ?,
[EndDateTimeUTC] = ?,
[ManualEndDateTime] = ?,
[ManualClosedBy] = ?,
[CloseMode] = ?,
[ClosePrompt] = ?,
[ActiveTime] = ?
WHERE [ID] = ? : 62 ms
If check account apple keychain: These credentials are valid.
If use a different type of account: User / Password or Passwords list, the problem does not reproduce, the connections are successful.
OS: macOS Mojave [10.14.3]
App: Remote Desktop Manager Enterprise (6.2.1.0)
Incorrect clipboard behavior
Oh, oh, sorry.
Apparently from our past experiments I did not change the engine mode.
Indeed, this problem is reproduced only in the modern engine.
Incorrect clipboard behavior
As you remember, I'm using the Legacy engine. :)
Thank you, I will wait for the news from you.
Incorrect clipboard behavior
Hi,
Faced an unpleasant problem with the general clipboard. 100% success of copying only English text and numbers.
Russian, Japanese, Korean, Chinese, French, Icelandic, as well as special characters are either not copied in full or not copied at all.
To make it easier for you to understand, I recorded a video.
A list of what I tried to copy:
Текст на русском языке
Text in English
Texte en français
Texti á íslensku
中文文字
한국어 텍스트
日本語のテキスト
1234567890
!"№%:,.;()_+
}{|":?><~`§±
RDM vs Dark Mode in MacOS Mojave
No, there is no such thing anywhere else.
Now I tried to start and close the application several times, and the problem does not reproduce.
Floating problem, I'll try again tomorrow.
RDM vs Dark Mode in MacOS Mojave
Hi,
Sometimes after starting, there is no list of connections - a "black hole".
"Window -> Reset Layout" repairs the list of connections.
It's interesting that the screenshot looks different than the real image.
RDM vs Dark Mode in MacOS Mojave
Hi,
If dark mode is enabled, sometimes "RDM" is started so that the connection list is invisible.
OS: MacOS Mojave [10.14 (18A391)]
App: Remote Desktop Manager Free (5.5.1.0)
Protected Users Security Group (AD)
Hello,
If the user account is added to the Protected Users group, it is impossible to authenticate using RDM. This problem does not exist on the version for Windows.
Application log:
[24.09.2018 11:39:09 - 5.5.1.0 64-bit]ERROR ERRCONNECT_ACCOUNT_RESTRICTION (0x00000017)
Session Log:
[12:05:25:027] [51640:07b4a000] [DEBUG][com.freerdp.channels.cliprdr.client] - VirtualChannelEntryEx
[12:05:25:027] [51640:07b4a000] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
[12:05:25:029] [51640:07b4a000] [DEBUG][com.freerdp.core.nego] - Enabling security layer negotiation: TRUE
[12:05:25:029] [51640:07b4a000] [DEBUG][com.freerdp.core.nego] - Enabling restricted admin mode: FALSE
[12:05:25:029] [51640:07b4a000] [DEBUG][com.freerdp.core.nego] - Enabling RDP security: TRUE
[12:05:25:029] [51640:07b4a000] [DEBUG][com.freerdp.core.nego] - Enabling TLS security: TRUE
[12:05:25:029] [51640:07b4a000] [DEBUG][com.freerdp.core.nego] - Enabling NLA security: TRUE
[12:05:25:029] [51640:07b4a000] [DEBUG][com.freerdp.core.nego] - Enabling NLA extended security: FALSE
[12:05:25:029] [51640:07b4a000] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_NLA
[12:05:25:029] [51640:07b4a000] [DEBUG][com.freerdp.core.nego] - Attempting NLA security
[12:05:26:034] [51640:07b4a000] [DEBUG][com.freerdp.core.nego] - RequestedProtocols: 3
[12:05:26:038] [51640:07b4a000] [DEBUG][com.freerdp.core.nego] - RDP_NEG_RSP
[12:05:26:038] [51640:07b4a000] [DEBUG][com.freerdp.core.nego] - selected_protocol: 2
[12:05:26:038] [51640:07b4a000] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_FINAL
[12:05:26:039] [51640:07b4a000] [DEBUG][com.freerdp.core.nego] - Negotiated NLA security
[12:05:26:039] [51640:07b4a000] [DEBUG][com.freerdp.core.nego] - nego_security_connect with PROTOCOL_NLA
[12:05:35:026] [51640:07b4a000] [DEBUG][com.winpr.sspi] - InitSecurityInterfaceExA
[12:05:35:027] [51640:07b4a000] [DEBUG][com.freerdp.core.nla] - nla_client_init 348 : packageName=Negotiate ; cbMaxToken=12256
[12:05:35:027] [51640:07b4a000] [DEBUG][com.freerdp.core.nla] - Sending Authentication Token
...
...
[12:05:35:028] [51640:07b4a000] [DEBUG][com.freerdp.core.nla] - CredSSP protocol support 6, peer supports 6
[12:05:35:029] [51640:07b4a000] [DEBUG][com.freerdp.core.nla] - Sending Authentication Token
...
...
[12:05:36:035] [51640:07b4a000] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_ACCOUNT_RESTRICTION [0x00020017]
[12:05:36:035] [51640:07b4a000] [ERROR][com.freerdp.core.rdp] - rdp_recv_callback: CONNECTION_STATE_NLA - nla_recv_pdu() fail
[12:05:36:035] [51640:07b4a000] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1
[12:05:36:035] [51640:07b4a000] [DEBUG][com.freerdp.core.rdp] - transport_check_fds() - -1
For some reason, the debug in the profiler does not show anything:
Connection States: Refresh...
CreateConnectionStateDictionary : 0 ms
Connection States: Refresh : 5 ms
The problem disappears if you delete a user of their group.
App: Remote Desktop Manager Free (5.5.1.0)
RDP engine = Legacy
Activate sandboxing = True
High load CPU in the authentication window
Hi,
That's great! Thank you.
When will the updated version be available for download?
I prefer to install the software with a HomeBrew, so I'll wait for the release.
High load CPU in the authentication window
Hi,
On both computers set: Activate sandboxing = True
High load CPU in the authentication window
Yes, yes, the image is different.
For the bug of the authentication window being hidden:
1. Open the application;
2. Switch to full screen mode (^⌘F);
3. Try to connect to the server - there will not be a problem;
4. Open the settings (⌘,);
5. Close the settings;
6. Try to connect to the server - the authentication window does not appear;
7. Using the mission control, drag the application to the desktop and notice the hidden authentication window that can not be called.
I recorded the video for you.
High load CPU in the authentication window
The image on the modern engine seems to me more cloudy. After 10 minutes my eyes start to hurt.
In the settings only the engine parameter was changed: Modern or Legacy.
While I was making screenshots, I noticed one more problem:
After opening and closing the settings and attempting to connect to the server, the authentication window hides behind the main window of the RDM and it can not be called. I had to kill the process.
High load CPU in the authentication window
I use only Legacy.
In Modern I do not like the quality of the picture.
High load CPU in the authentication window
When connected from iMac, I pre-set the VPN connection using a tunnelblick.
When connected from Mac mini, the local network is used.
But I think that for the RDM application there should be no difference. Or not?
The settings should be the same, I'll take screenshots a little later.
High load CPU in the authentication window
Given the fact that the iMac is much more powerful than the Mac mini, this is very weird. :)
High CPU usage starts immediately after the authentication window. As well as it disappears immediately after I enter the login / password or cancel.
I tried to reinstall the software, but it does not help.
I did installs from both the brew and the dmg image from the site.
The problem is always reproduced.
High load CPU in the authentication window
Hello.
The problem is always reproduced in iMac 5k 2017. When the authentication window pops up, the operating system starts to run very slowly, processor load 100-130%. After authentication, a large processor load is lost and holds around 20-30%.
P.S.
The problem will not be reproduced on the Mac mini 2012, the processor load is always around 20-30%.
Hardware: iMac 5k 2017
OS: High Sierra (10.13.6)
App: Remote Desktop Manager Free (5.5.1.0)
Memory leak
Hi.
My XML file in which addresses for connections are stored. Also I used only Microsoft RDP, but at the file there are https and ssh types.
For once I use no more than 10 MSRDP connections.
In total in the XML file there are 350 records.
Memory leak
Hello
The application has been opened four days, during this time I have noticed serious leakage of memory.

The majority of connection to Windows server 2012 R2.
Hardware: Mac mini late 2012
OS: High Sierra (10.13.3)
App: Remote Desktop Manager Free (5.1.0.0)