Forum

Posts by r06 (r06)

r06
r06
Posts: 11

Maurice Cote wrote:

Hello,

I will have to discuss this with David, we should respond early this week.

Best regards,

Hello,

Have you made any discoveries so far?

2 yrs Datasource add on session format
r06
r06
Posts: 11

https://imgur.com/a/FPi5Q

2 yrs Datasource add on session format
r06
r06
Posts: 11

Here's a dump of the XML strings I'm providing the add-on with:


<Connection>
<ConnectionType>Group</ConnectionType>
<Group>A.P. van den Berg Fabricage BV\Servers</Group>
<ID>0255be31-a207-4285-8c95-5ebbd9c110b3</ID>
<Name>A.P. van den Berg Fabricage BV</Name>
<Stamp>f53dd251-513b-45b4-adc7-021f322ebbd4</Stamp>
</Connection>
<Connection>
<GroupDetails>
<GroupType>Software</GroupType>
</GroupDetails>
<ConnectionType>Group</ConnectionType>
<Group>A.P. van den Berg Fabricage BV\Firewall</Group>
<ID>80b1548d-2c46-4153-b68a-8ee57943fa5e</ID>
<Name>Firewall</Name>
<Stamp>658e7f88-8b72-4f34-9bba-29ebd662d9b8</Stamp>
</Connection>
<Connection>
<GroupDetails>
<GroupType>Identity</GroupType>
</GroupDetails>
<ConnectionType>Group</ConnectionType>
<Group>A.P. van den Berg Fabricage BV\Sleutel</Group>
<ID>082e7745-f2d9-4a8a-b31f-e482b2160b1a</ID>
<Name>Sleutel</Name>
<Stamp>5aad1fed-9416-4a8a-b0b3-54d33af1323f</Stamp>
</Connection>
<Connection>
<GroupDetails>
<GroupType>Server</GroupType>
</GroupDetails>
<ConnectionType>Group</ConnectionType>
<Group>A.P. van den Berg Fabricage BV\Server</Group>
<ID>a90c2b2b-044c-4b07-bd99-083275bd463c</ID>
<Name>Server</Name>
<Stamp>e3a37f94-7043-4779-b42a-30a59dadb598</Stamp>
</Connection>
<Connection>
<GroupDetails>
<GroupType>Database</GroupType>
</GroupDetails>
<ConnectionType>Group</ConnectionType>
<Group>A.P. van den Berg Fabricage BV\ILO</Group>
<ID>aff0db2e-a752-4135-9394-a8613af8d1a8</ID>
<Name>ILO</Name>
<Stamp>0b59a73e-b9e0-4fa4-a75f-e3caa27f55ba</Stamp>
</Connection>
<Connection>
<GroupDetails>
<GroupType>Database</GroupType>
</GroupDetails>
<ConnectionType>Group</ConnectionType>
<Group>A.P. van den Berg Fabricage BV\Storage</Group>
<ID>ecddafb0-ff0a-4101-b527-4ba480454efa</ID>
<Name>Storage</Name>
<Stamp>ffed4dc8-6cd6-4797-8d5e-fe188e3024b5</Stamp>
</Connection>
<Connection>
<GroupDetails>
<GroupType>Database</GroupType>
</GroupDetails>
<ConnectionType>Group</ConnectionType>
<Group>A.P. van den Berg Fabricage BV\Netwerk Infra</Group>
<ID>c701f69f-5fff-4f52-9ba8-a464da0a7d30</ID>
<Name>Netwerk Infra</Name>
<Stamp>7ffffeb8-3646-409d-91f2-6f0a9dfd67eb</Stamp>
</Connection>
<Connection>
<MetaInformation>
<IP>192.168.1.12</IP>
</MetaInformation>
<ConnectionType>RDPConfigured</ConnectionType>
<Description></Description>
<Group>A.P. van den Berg Fabricage BV\Servers</Group>
<ID>1ae88a31-e0ec-48b7-8be7-e81b9900c7cb</ID>
<Name>AP01</Name>
<Url>192.168.1.12</Url>
</Connection>
<Connection>
<MetaInformation>
<IP>192.168.1.16</IP>
</MetaInformation>
<ConnectionType>RDPConfigured</ConnectionType>
<Description></Description>
<Group>A.P. van den Berg Fabricage BV\Servers</Group>
<ID>dc1fc314-9721-441f-9464-1cad1b07b5b6</ID>
<Name>AP02</Name>
<Url>192.168.1.16</Url>
</Connection>
<Connection>
<MetaInformation>
<IP>192.168.1.23</IP>
</MetaInformation>
<ConnectionType>RDPConfigured</ConnectionType>
<Description></Description>
<Group>A.P. van den Berg Fabricage BV\Servers</Group>
<ID>8f6e4e6b-d9c3-4b4c-b467-6657f4b88694</ID>
<Name>AP03</Name>
<Url>192.168.1.23</Url>
</Connection>
<Connection>
<MetaInformation>
<IP>192.168.1.24</IP>
</MetaInformation>
<ConnectionType>RDPConfigured</ConnectionType>
<Description></Description>
<Group>A.P. van den Berg Fabricage BV\Servers</Group>
<ID>edda96e0-5b42-4326-93b3-1c0ea8cf0cb9</ID>
<Name>AP04</Name>
<Url>192.168.1.24</Url>
</Connection>
<Connection>
<MetaInformation>
<IP>192.168.1.40</IP>
</MetaInformation>
<ConnectionType>RDPConfigured</ConnectionType>
<Description></Description>
<Group>A.P. van den Berg Fabricage BV\Servers</Group>
<ID>446c6ece-83b6-4e01-a702-3b69d1d67909</ID>
<Name>Backup</Name>
<Url>192.168.1.40</Url>
</Connection>
<Connection>
<MetaInformation>
<IP>192.168.1.21</IP>
</MetaInformation>
<ConnectionType>RDPConfigured</ConnectionType>
<Description></Description>
<Group>A.P. van den Berg Fabricage BV\Servers</Group>
<ID>229edc40-a7ea-429a-bc91-672add169827</ID>
<Name>DC01</Name>
<Url>192.168.1.21</Url>
</Connection>
<Connection>
<MetaInformation>
<IP>192.168.1.22</IP>
</MetaInformation>
<ConnectionType>RDPConfigured</ConnectionType>
<Description></Description>
<Group>A.P. van den Berg Fabricage BV\Servers</Group>
<ID>4a7aaaac-3d4e-4a73-baaa-babf10d38ee1</ID>
<Name>DC02</Name>
<Url>192.168.1.22</Url>
</Connection>
<Connection>
<MetaInformation>
<IP>192.168.1.25</IP>
</MetaInformation>
<ConnectionType>RDPConfigured</ConnectionType>
<Description></Description>
<Group>A.P. van den Berg Fabricage BV\Servers</Group>
<ID>ad332067-058b-4f0d-9f09-b98d65758bc5</ID>
<Name>EX2010</Name>
<Url>192.168.1.25</Url>
</Connection>
<Connection>
<MetaInformation>
<IP>192.168.1.28</IP>
</MetaInformation>
<ConnectionType>RDPConfigured</ConnectionType>
<Description></Description>
<Group>A.P. van den Berg Fabricage BV\Servers</Group>
<ID>613e6508-409d-45ee-ba73-ca1be5957047</ID>
<Name>Exact</Name>
<Url>192.168.1.28</Url>
</Connection>
<Connection>
<MetaInformation>
<IP>192.168.1.35</IP>
</MetaInformation>
<ConnectionType>RDPConfigured</ConnectionType>
<Description></Description>
<Group>A.P. van den Berg Fabricage BV\Servers</Group>
<ID>7f1e4181-ca92-4bbc-a77b-c30ae63a088b</ID>
<Name>Insight</Name>
<Url>192.168.1.35</Url>
</Connection>
<Connection>
<MetaInformation>
<IP>192.168.1.230</IP>
</MetaInformation>
<ConnectionType>RDPConfigured</ConnectionType>
<Description></Description>
<Group>A.P. van den Berg Fabricage BV\Servers</Group>
<ID>d0df15cd-af9d-42fe-978a-9b5737af4e95</ID>
<Name>ITNC 530</Name>
<Url>192.168.1.230</Url>
</Connection>
<Connection>
<MetaInformation>
<IP>192.168.1.11</IP>
</MetaInformation>
<ConnectionType>RDPConfigured</ConnectionType>
<Description></Description>
<Group>A.P. van den Berg Fabricage BV\Servers</Group>
<ID>af20bdf5-ce75-4905-94c5-0478fb27ce42</ID>
<Name>OS01</Name>
<Url>192.168.1.11</Url>
</Connection>
<Connection>
<MetaInformation>
<IP>192.168.1.34</IP>
</MetaInformation>
<ConnectionType>RDPConfigured</ConnectionType>
<Description></Description>
<Group>A.P. van den Berg Fabricage BV\Servers</Group>
<ID>91ae3e60-da0e-47d7-a605-9bb449cb74e5</ID>
<Name>SQL01</Name>
<Url>192.168.1.34</Url>
</Connection>
<Connection>
<MetaInformation>
<IP>192.168.1.10</IP>
</MetaInformation>
<ConnectionType>RDPConfigured</ConnectionType>
<Description></Description>
<Group>A.P. van den Berg Fabricage BV\Servers</Group>
<ID>b9d7a139-07bc-4f4e-910b-c62aa1f8b66f</ID>
<Name>SV01</Name>
<Url>192.168.1.10</Url>
</Connection>


And the result in RDM:
image
image

2 yrs Datasource add on session format
r06
r06
Posts: 11

Is there an answer yet. I cannot find any documentation on this. And experimenting has some varying results like sometimes groups don't show up, missing information, etc.

2 yrs Datasource add on session format
r06
r06
Posts: 11

Hello,

I am creating a datasource add-on because we want to be able to integrate our CMDB directly with Remote Desktop Manager. That's why we chose for the datasource add-on as it is the easiest to configure and work with securely.

I hope this can be of some help.

2 yrs Datasource add on session format
r06
r06
Posts: 11

No newtonsoft cannot encode its only use to me is json de/serializing.

2 yrs Corrupted debugging installation
r06
r06
Posts: 11

I will try to find a version that supports this version of .NET. I cannot find one at the moment. Do you have a link by chance?

2 yrs Corrupted debugging installation
r06
r06
Posts: 11

I cannot find any documentation about formatting the sessions for the ISessionDataSource.GetConnections method. I realise it uses the same XML format you can see in the connections.xml files but sadly I get very weird results trying to format these connections.

For example leaving out or including certain fields in the XML can cause connections to not have any names or data at all. Or leaving out certain fields yields connection data but subsequently does not place them under the group I need them to be under.

An example of what I am trying to do:


public string formatRDPConnection(string name, string address, string description, string domain, string branch)
{
Guid id = Guid.NewGuid();
return "<Connection><MetaInformation><Domain>" + domain + "</Domain><IP>" + adres + "</IP></MetaInformation><ConnectionType>RDPConfigured</ConnectionType><Description>" + description + "</Description><Group>"
+ branch + "</Group><ID>" + id.ToString() + "</ID><Name>" + name + "</Name><Url>" + adres + "</Url></Connection>"
}


Can anybody help point me to some clear rules on this?

2 yrs Datasource add on session format
r06
r06
Posts: 11

Ronan Vonk wrote:

Ronan Vonk wrote:
Recently I have started development on a datasource add-on for RDM. While doing so I seem to have corrupted some part of the debug installation. That is the version of RDM I copied from the normal installation to my visual studio project.

No matter what I do, and this is includes completely removing the installation and the configurations in the Appdata folder, when I start the application it attempts to load the local data store and consequently crashes.

Visual studio reports a stack overflow exception in external code so I can't see what's going on precisely. Does anyone have any idea on how I could repair this installation.

On RDM 12.6.8.0

UPDATE: reinstalled everything on a virtual machine and I am still having the same issue. The problem is the application enters a break state and does not seem to report any usefull information. It is not my own code that causes the problem.

UPDATE 2: I think it may be caused by a dependency I have in my project. I am using JWT.dll for encoding purposes. Could this be an issue for RDM?


I solved the problem. It was indeed the JWT assembly that caused the problem. This is however a little bit of an issue. I would love to be able to encode some of the data that is going to be handled by my add-on.

2 yrs Corrupted debugging installation
r06
r06
Posts: 11

Ronan Vonk wrote:

Recently I have started development on a datasource add-on for RDM. While doing so I seem to have corrupted some part of the debug installation. That is the version of RDM I copied from the normal installation to my visual studio project.

No matter what I do, and this is includes completely removing the installation and the configurations in the Appdata folder, when I start the application it attempts to load the local data store and consequently crashes.

Visual studio reports a stack overflow exception in external code so I can't see what's going on precisely. Does anyone have any idea on how I could repair this installation.

On RDM 12.6.8.0

UPDATE: reinstalled everything on a virtual machine and I am still having the same issue. The problem is the application enters a break state and does not seem to report any usefull information. It is not my own code that causes the problem.

UPDATE 2: I think it may be caused by a dependency I have in my project. I am using JWT.dll for encoding purposes. Could this be an issue for RDM?

2 yrs Corrupted debugging installation
r06
r06
Posts: 11

Recently I have started development on a datasource add-on for RDM. While doing so I seem to have corrupted some part of the debug installation. That is the version of RDM I copied from the normal installation to my visual studio project.

No matter what I do, and this is includes completely removing the installation and the configurations in the Appdata folder, when I start the application it attempts to load the local data store and consequently crashes.

Visual studio reports a stack overflow exception in external code so I can't see what's going on precisely. Does anyone have any idea on how I could repair this installation.

2 yrs Corrupted debugging installation