Users

All Posts (4)

avatar

hernan1

Sonoma 14 - Corrupted Dictionary

avatar
avatar
avatar
avatar

Hi, since Sonoma update I´m not able to do a custom apple script. The code fails during compile with the error display in the attach image.

That particullar command work just fine before updating to the last version of Mac OS.

Thanks

Unknown error while trying a RDP session MacOS, Apple Silicon

avatar
avatar
avatar
avatar
avatar

Xavier this is fine it really works for me because I dont need to do many changes so i can work it out with the XML file.

Thank you guys for great support and awesome product.

Regards

Hi hernan1,

Unfortunately no. This requires a bit of hacking around to get this information. For instance, you could create a new entry, make minimal changes to it and export it. Afterwards you can make the changes you want to do with it and export it again, you can then compare the two exported files and you should see new/modified properties and this should give you the information.

Note that this is XML, so if a properties (e.g. <TcpAcknowledgementTimeout>) is inside another tag (e.g. <RDP>) this will give you a path (i.e. RDP.TcpAcknowledgementTimeout).

Best regards,

Unknown error while trying a RDP session MacOS, Apple Silicon

avatar
avatar
avatar
avatar
avatar

Hi Richard, it worked just fine, thanks for your input on the matter.

One last question, do you have a link with a list of available properties so we can create our own scripts?

Let me give you and example, now I want to batch edit Scaling to "Optimize for Retina displays" to YES, thanks to you I have the base script and now I have to input the property.

Thanks in advance

Hello

I'll let the RDM Mac team respond to the specific issue of this field not being "batch editable".

However, in case it serves as a workaround in the meantime I'll direct you to check the following thread: https://forum.devolutions.net/topics/39913/batch-edit--password-only. My colleague describes a technique to batch edit fields using a custom script instead of the batch edit interface.

You should be able to follow the advice in that thread but substitute the following script to set the default TCP ack timeout:

set value of _connection of property "RDP.TcpAcknowledgementTimeout" to 30000

save _connection

Please let me know if you have some questions or something isn't clear.

Thanks and kind regards,

Unknown error while trying a RDP session MacOS, Apple Silicon

avatar
avatar
avatar
avatar
avatar

Hello, I recently changed from a PC to a MAC, more specifically a 15-inch airbook with OS Ventura 13.6.

The described problem is happening to me too and is resolved by changing the "Use Default TCP acknowledgment timeout" option from default 9,000 to 30,000.

But on the other hand I have to report a BUG since when I want to execute a BATCH edition of the sessions the objects do not change and maintain the default option of 9,000. This problem was reported a while ago but it seems that it persists.

I have about 500 entries so modifying each of them one by one is not an option.

For what it's worth, all of the MAC entries came from a backup made on devolutions from a Windows PC, meaning I was working on Windows, all connections to the devolutions cloud were backed up and restored to the MAC.

1 - 4 of 4 items