ryan04

We use Host sessions and templates to connect to our systems and this causes every session to report that it is "open" when executing (whether set on the Host session or template). It would be nice to see this feature reworked to function with this type of configuration. It is a great feature to have.

It might be a bit more involved. It looks like there are times when the $Host$ is completely removed from the session when checking the "Use Host Template" but others do not have this. I'm guessing that the sessions that were manually changed from the UI are handled differently than if done via powershell. Not sure this should be a feature request or a support request.

Sorry for the delay. No change using Chrome vs Edge

When using the Host type session with "Use Template Host" option, all of the built in macro's are greyed out. The remote management tools are enabled and function properly. It would be nice for these built-in options to be available if MetaInformation.IPAddress or MetaInformation.MachineName is populated. The tools can be rebuild easily enough... just seems like an afterthought on the Host type sessions.

In addition, when I set this template to show in the Macro\Scripts\Tools section, it does not populate an icon there.

I have Devolutions Server as the data source (v2021.1.19.0) and Enterprise version of RDM.

This is the working "Website" template.

Non-functional Web Browser template

I am having trouble getting a web browser template to use my host session $CUSTOM_FIELD2$ variable (use template host is checked). This works when using the "Website" type session, but not the "Web Browser" type session. The Web Browser just opens with nothing in the address bar. I'd like to use the web browser type session so that it can be added to the Macros\Scripts\Tools tab (also having trouble with this) and filtered by mandatory properties. The Website type session does not offer this in the template settings.

RDM Version: 2021.1.36

The paste feature for images appears to work (and save) in the documentation editor, it just doesn't display in the viewer. Seems this could be an easy fix? Or allow an option to default to the editor view.

I believe DVLS is only available on Windows? If there is not a roadmap to port it to other platforms, the Windows event log would likely be the easiest to implement.

That could work... I have been thinking about moving to the synchronizers. I remember reading something about a potential PowerShell synchronizer somewhere on the forums... is that still in the works?

I'll do some testing with the CSV synchronizer and see what works. There's always more than one way to do something in RDM :)

Would it be possible to add this setting to the search options? Some folks like it and others don't. My users don't have access to the options in our terminal server environment and would like to be able to enable/disable as needed.

https://forum.devolutions.net/topic26971-performance-issues-search.aspx

Is there a non-proprietary way to monitor the DVLS logs besides using syslog? I need to be able to monitor and alert on errors and can't seem to find a native method for monitoring. Every now and again, an error occur which render the service unusable but our current web service monitoring doesn't catch it. In one particular case, large batch edits cause an issue with Windows authentication for all users but none of our current monitors capture this.

Syslog would certainly work, unfortunately this is owned by the security team and is not intended for use for operational systems monitoring.

I'd like to be able to pass an elevated PSCredential for a read only user within PowerShell.

Set-RDMSession $Session -Credential (elevated-PSCredential)

This would allow me to create PowerShell macros for read only users with the ability to update the metainformation of the session. I am using a data source custom variable to pull the password of an account that has edit rights and I can use "Run As" within a template macro but this has been a bit inconsistent and requires the script to validate and change the repository which takes a bit of time.

Thanks David. I setup a quick test database(attached). It's rather basic using Host session and a couple template types. I don't think I can send a personal credential, but if you create a "my personal credential" with the Password List type, then user override credentials for one of the test servers... this will replicate the dual password prompt. With the latest addition of "allow credentials only" in the password vault, this might be a moot point as users can create as many username\password credentials as they want.

If you modify the test host sessions and credentials to a value that is functional, close with multiple active sessions, then reopen... you will get this prompt.

While this will reopen the session, it does not take into account the credential or template that was previously used and prompts again for credential and template. With a large list of opened sessions... it's nearly impossible to identify what device you are connecting to. When prompted again for credentials and/or template.... What is RDM trying to connect to? Which credential to use? What template? Etc.

Regarding repositories, the Restore Connections only pulls information from the currently logged on data source when RDM is first launched.

• Create two repositories. Set one to "always log on to" in the data source properties.

• In the other repository, create and connect to multiple sessions (close RDM with active sessions)

When opening RDM, it will logon to the specified data source that had no active sessions and will not prompt to open previous sessions even when changing repositories.

The ideal behavior (at least for us) would be that the previous session, the credential, and the template are all stored and passed through automatically. Preferably when changing repositories rather than just at application start.

Would it be possible to include a Credential parameter for Set-RDMSession and Set-RDMSessionProperty? My users are read only, but I'd like to be able to elevate their access via a macro or tool so they can modify specific session properties. I've had some pretty inconsistent results attempting to "Run As Different User" on a PowerShell session.

Thank you!

My users really like the password list credential type. The challenge is that they are prompted twice when sending to a template (for obvious reasons). Would it be possible to pass the selected Password List item as a "converted" username\password credential type?

This also presents a couple challenges when using the "Open existing sessions" option with the password list (or any prompt for credentials). When selecting the option to connect previous sessions on open, they are initially prompted for a password and then a template (with no indication of what system they are connecting to).

Could the credential (possibly index number of password list) and thetemplate ID's be saved and passed to RDM so it doesn't require any action on the users part?

If not, would it be possible to identify what session they are connecting to in the password or template prompt?

Lastly (and likely a major architecture change) , could open previous sessions be allowed to execute against all repositories? Currently, users are only prompted to open sessions within the repository they login to initially.

• An alternative might be to be able to prompt as they switch repositories?

• Most of our users will work in a single repository however, we currently force all users into an initial repository that contains a knowledgebase on how to use the product (for new users). If we change this to "last used repository", new users will get a seemingly random (I think alphabetical) repository which they likely don't have permissions for. If we could force new users into a default repository, we could enable 'last used repository" for everyone else.

• Prompt for repository on open

Sorry for being so long winded. :)

You can do this with Macro's and templates fairly easily by creating a new file explorer template. In the template - use \$HOST$\C$ in the folder field. You can just use open with template or create a Macro using the "Template" type and point it to the new file explorer template you created. This will work as a subconnection as well by using $PARENT_HOST$ but then you have to create entries for every object.

Using a PowerShell template type you could query the system for all available shares and have a user selection popup to choose which share they want to connect to.

I'm not familiar with what features are available in the free version but the enterprise version is worth every penny.

I have been using Open-RDMQuickConnect in a lot of my macros and was looking to add additional parameters. I have been doing this using templates but had a thought that allowing it to dynamically build the session in PowerShell would allow me a lot more granular control of how to display the information. For example, I have a PowerShell macro that executes performance counters against a remote system. It then analyzes the performance metrics, applies thresholds, and provides an HTML report using Open-RDMQuickConnect to embed the report in the RDM UI.

Example 1:

.\script.ps1

$URL = [system.Uri]$global:oPal.ArgsProcessed.HtmlOutputFileName | Select-Object AbsoluteUri -ExpandProperty AbsoluteUri

[System.String]$Template = (Get-RDMTemplate | Where-Object { $_.Name -eq 'HTML Report Viewer' } | Select-Object ID -ExpandProperty ID)

Open-RDMQuickConnect -Host $URL -TemplateID $Template

Example 2:

.\script.ps1

Copy-Item (Get-ChildItem '\$PARENT_IP$\c$\PerfLogs\perfmon.blg') -Destination $env:temp\$PARENT_NAME$.blg -Force

[System.String]$Template = (Get-RDMTemplate | Where-Object { $_.Name -eq 'External Command' } | Select-Object ID -ExpandProperty ID)

Open-RDMQuickConnect -Host "$env:TEMP\$PARENT_NAME$.blg" -TemplateID $Template

.

This actually works very well... except the quick connect cmdlet only has a small number of parameters available I can use (Host, Template, etc.). I'm limited to what I statically defined in the template.

.

Example enhancement:

.\script.ps1

$Session = New-RDMSession -Name $scriptvar -Type $scriptvar1

$session.element1 = $scriptvar1

$session.element2 = $scriptvar2

$session.element3 = $scriptvar3

$etc.etc.etc

Open-RDMQuickConnect -Session $Session

.

Notice that I never actually save the New-RDMSession. Since the data processed by the script is different for every asset I run against, I could... say change the tab color to red for a perfmon counter that is over threshold. Really, the options are endless at that point.

Would it be possible to add Events to Macro\Script\Tools? We are currently adding validation prompts in the scripts but it would be nice to have it in a unified UI. Some of our macro's make system changes and we want to make sure that a user doesn't click on them accidentally.

We can sort of get around this for some things by using the macro to kick off a template but prefer not to have so many templates. BTW... LOVE, LOVE, LOVE the new template options (allow for import, host, etc). Great addition!

... not sure how I missed that one. #facepalm

:whack:

:rtfm:

Rather than having multiple RDP\SSH templates with different Gateway settings, would it be possible to allow the VPN settings configured in the Host session override the template (if not defined in the template)?

Another option would be to allow for a prompt for gateway option (if unable to ping\scan) that can be set in the template and would pull from a list of available sessions within a specific folder.

Personally, I like the prompt for gateway option.

Sorry Mark, I didn't think I was clear. I do not want the "Open with parameters" option in the context menu. In 13.0.4, I was able to remove the option by disabling "Allow special open actions in dashboard".

Hi Mark, I'm testing the latest beta 13.0.8 and discovered this issues if that provides additional insight. I can download and test the 13.0.6 version as well if need be.

To be clear, I do not want the "Open with parameters" in the context menu.

Ah, I misunderstood. Yes, I would like to be able to hide the import options from the private vault.