Please enable JavaScript to view this site.

Import Strategies and file format


The most important decision is about if and how to apply a template as part of the process.

Both methods of importing from CSV allows you to choose a template for newly created entries. If you do choose a template as part of the process, it will be apply to ALL entries created from that batch. Sometimes, it may be a good strategy to split the entries in different CSV files by grouping them by type of entries you wish to create.

If you need finer control, you can specify the template to use in a Template column of the CSV file. But since you're able to specify the entry type from within the CSV file it may not be necessary. Please consult CSV Samples below.


Some validations on entry settings are not in the business layer but rather in the property dialogs. This means that using the import process can result in invalid entries that trigger errors. Please validate the resulting entries carefully.

In the CSV file, only the Host field is mandatory. If no template is specified, the RDP type will be used as a fallback type.

We cannot provide the list of all supported fields for all entry types because Remote Desktop Manager uses an open architecture and therefore is not even aware of all the fields of entry types that are provided by our Add-On system. A good method of finding out the field structure is to create an entry of the desired type and to use Clipboard Copy, then paste the content in your favorite editor. You will see the structure and the field names.

Default values for fields are NOT serialized. This means that they are simply left out of the serialized structure.

Implementing support for all fields comes at a cost. The import process is time consuming because of all the dynamic field access that takes place. A massive initial import of entries should be separated in batches of manageable size. Please perform trials and tune the number of entries to achieve acceptable performance.

All of our entries share a basic set of fields, the rest are tied to the specific technology being interfaced with (RDP, SSH, etc). Some fields are grouped in structures like the Information Tab for instance. This means that those fields are accessible only when providing the structure name as a prefix, for example: "MetaInformation\OS" or "MetaInformation\PurchaseDate"

Note that the content of the CSV file can contain our variables and they will be resolved upon saving. For instance you could use the $HOST$ variable in fields like Description, URL, Putty\CustomSessionName, etc. It will be replaced by the corresponding value.

Here is a list of some relevant fields.




Host name of the device, this is the only mandatory field.


Name of the entry


Token representing the connection type. It is best to use the Clipboard-Copy method to obtain the acceptable values.


Destination folder. Note that if the import process itself had a Destination Folder defined as well, the folder listed here would be created below the one from the process.


Description of the entry.

Open (Embedded)

Boolean value (true or false) that indicates to open the session embedded. The default value is false, meaning that the native client will be used depending on the technology. MSTSC.EXE for instance.


Username used to open a session to the device.


Domain used to open a session to the device.


Password used to open a session to the device. Please note that this field is encrypted and stored into another field upon being imported.


Serial Number of the device.


Service Tag of the device


Purchase date in a ISO8601 format, i.e. yyyy-mm-dd

CSV samples

With specified session types

Host,Name,Template,ConnectionType,ConnectionSubType,SubMode,Group,Username,Domain,Password,Description,URL,one,,Microsoft Remote Desktop (RDP),,,QA Lab,,,,Description001,,two,,Web Browser (http/https),,,QA Lab,,,,Description002,,three,,LogMeIn,,,QA Lab,,,,Description003,,four,,"Telnet, SSH, RAW, rLogin",,0,QA Lab,,,,"This is the Putty sub-type",,five,,"Telnet, SSH, RAW, rLogin",,1,QA Lab,,,,"This is the Telnex (Rebex) sub-type",,six,,"Telnet, SSH, RAW, rLogin",,2,QA Lab,,,,"This is the SSH Shell (Rebex) sub-type",,seven,,"Telnet, SSH, RAW, rLogin",,3,QA Lab,,,,"This is the SSH (Rebex) sub-type",,eight,,VNC,,,QA Lab,,,,Description008,,nine,,Citrix,,,QA Lab,,,,Description009,