Setting Default Connection Settings not applying

Hello Chuck,

Thank you for contacting the Devolutions support team.

I have tried it on the latest version, 2024.2.20.0.
All the settings from the template created are applied by using the convert to the template as a batch edit.

Have you tried it with the 2024.2 or 2022 version on SQL?

Best regards,

Hello Chuck,

Thank you for contacting the Devolutions support team.

I have tried it on the latest version, 2024.2.20.0.
All the settings from the template created are applied by using the convert to the template as a batch edit.

Have you tried it with the 2024.2 or 2022 version on SQL?

Best regards,

I am on SQL Server 2022.

Yes, the options do in fact populate. BUT, you will lose the vmID that is stored, and whatever host is stored when you do the convert with template.

Hello Chuck,

Thank you for this feedback.

Could you try this with 2024.2 with the local data source and see if this issue still occurs?
An export of some of your entries + a new template could be enough to have an accurate result.

Best regards,

Good morning Patrick, and sorry for the delay.

So, here is what came up when I just did a vCenter Sync:


HOWEVER... This is what is currently set up for VMRC under "Settings > Templates > Default session settings > VMRC":


Without making any changes at all to that screen, I am doing an "Edit > Special Actions":



When I did that, I now have this as the saved entry looking as it should. The VM Id is completely removed by RDM:


By doing that, I now get this whenever trying to connect:


When I add the appropriate VM ID back to that entry, it connects just as expected:


Hopefully this helps.

Good morning.

Any updates on this? I have two new vCenters I need to add to RDM and get them imported.

I don't want to have to edit each entry one-by-one.

Thanks!

Hello Chuck,

We have reproduced this issue.

An internal ticket is now open.

I'll let you know when I have news on this.

Best regards,

Hello Chuck,

The batch edit in this case seems to be working "as intended". All the settings not customizable in your convert with template prompt will be overridden by your template through the convert action.

To avoid this behavior in your case we would recommend using the "Template" field of your VMWare synchronizer.

This setting will make it so all the entries generated from your VMWare Sync will use the selected template as the base and then the information queried from the synchronizer will be added on top of that base.

Here is a screenshot of the setting in question :



Please do let me know if this works for you.

Best Regards,

Michael,

This seems to have been fixed in the release the ticket was worked that Patrick mentioned where the team was able to replicate the issue I was having.

That issue was resolved, and now when you do a VM Sync, it is back to working as it did a few versions ago before it bused.

Thanks for the follow up.

PS: This is where the option to mark topics as Resolved for the original poster would come in extremely handy. ;-)