Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import .xml from Remote Desktop Manager (RDM) #2562

Open
Weynoob opened this issue Feb 5, 2024 · 2 comments
Open

Import .xml from Remote Desktop Manager (RDM) #2562

Weynoob opened this issue Feb 5, 2024 · 2 comments

Comments

@Weynoob
Copy link

Weynoob commented Feb 5, 2024

Hi there,

I’m trying to export my database from Remote Desktop Manager to import it in mRemoteNG (it is a professional database).

My orginal file is .xlm which contains 479 hosts, including folder, and ID/password.

The first thing I tried was to import my database from File > Import > Import from File.
But the import doesn't work, and I get this error: « An error occured while importing the file C:\User...\file.xml »

So I searched on the Issues Trackers, and I found this Importing XML wont work · Issue #394 · mRemoteNG/mRemoteNG · GitHub.
As someone said, I tried to open the .xml file instead of import it. One again, I get another error into the notification bar:
----------
WarningMsg
02/05/2024 09:23:10
You are trying to load a connection file that was created with an older version of mRemote, internal errors may occur.
If you encounter an error, please create a new connection file!
----------

It’s the same issue with .csv or .json file.
I have the latest version of mRemoteNG (1.76.20.24615), same for Remote Desktop Manager.

Thank you in advance.
@sparerd @kmscode @Kvarkas @farosch

NB: your email server doesn't accept external email (Outlook error: security@mremoteng.org, 0b43a9497e92, Remote server returned '550 5.0.1 Recipient rejected')

Capture d'écran 2024-02-05 092327
Capture d'écran 2024-02-05 092536

@DaveSchopp
Copy link

I have this issue as well.

@Kvarkas
Copy link
Member

Kvarkas commented Feb 19, 2024

issue is known, problem is what fields are not same so import not happening automatically, suggestion is - create example connection - export file, check fields, manually copy fields data from target, save file. Could be done by PowerShell script - but currently a bit over busy, if not urgent wait till next release, it should be addressed then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants