Meaning of "HOST" entry

avatar

Hi there,

I can't understand, in terms of RDM/automation, the "host" type entry. What can be useful to?

I have many RDP, HTTP, SSH, etc. entries for each "host" (I simply use the same IP for all his entries) but I don't see any advantage to link them to the same host entry. It is only for name/address resolution in terms of future updates or I missing something?

Thanks

All Comments (5)

avatar

Hello,

They are great for defining an "asset" once and only once, yet connect to it using multiple remote technologies

For example in the linux world : SSH, SCP, SFTP, etc
In the Windows World : RDP, remote powershell, etc

You can read our blog on this topic at https://blog.devolutions.net/2015/07/advanced-session-management-host-and-templates

Best regards,,

Maurice

avatar

Well, thanks Maurice, but take this example:

forum image

For me, it is quite more direct to have an entries list like this instead of subsequent clicks; moreover, with host/templates is not simple to manage credentials. This is a standalone host, so Windows credentials are local. Any of these entries have different credentials, so, for passing them to templates a credential entry for each one would be needed. Am I wrong?

Obviously, I always use templates for all my entries types (RDP, TV, iDRAC, etc.).

Thanks.

avatar

indeed you can choose to use inheritance, for our bigger MSP customers it just creates too many entries.
As for the credentials, they would be assigned to the hosts only (unless you need a special one, like managing the NGINX server on a linux host....)

Both ways are perfectly valid!

Maurice

avatar

Can you clarify me how credentials can be assigned to the host only and then sessions templates can use them? I'm a bit confused.

Moreover, taking my example: different credentials are used for different type of session (Windows user for RDP, Dell iDRAC, TeamViewer, etc.). How can I set them to the host and then use them for templates?

Thanks for your help.

avatar

I've tested a bit and, think, understood. But, as I told up here, this can be good only if one credential is used for all templates, so you can pass it with $VARIABLES$.

In my case, with different credentials for different sessions, I don't see how to take advantage of the host+templates method.

Thanks.