Here goes a sugestion quite usefull (for me at least).

Something very similar to the current "SmartCode Reset VNC Server Password Wizard", that lets one reset password on several machines at a time. But with a diference it would ajust only the connection settings for each of the selected machines without trying to access the vnc services on each of the machines.

Can be even a evolution of the "SmartCode Reset VNC Server Password Wizard" with a checkbox added so that one can check it if he or she wants to "update connection settings only, without accessing remote machines" or something similar.

Thanks. Please reply on the possibility of such a option existing in the future.

Once again, thanks in advance.

I'm not sure but I think we have implemented something like that in the Deployment Wizard v3.0.
What was added is an ability to upload custom registry entries. The registry editor control is very flexible, it allows you to browse a remote computer registry, so basically you can copy a registry branches from one computer to another. Also you may load a .reg file or enter your custom registry values.
So what I'm thinking of is that such feature can be used to reset remote VNC server settings. You just upload to a target PC a registry branch with default VNC server settings and that's it.

What do you think about it?

I'm sorry, I guess I made you think of something else.. What i meant was a diferent thing. I hope i am able to better explain it now.

When I said (refering to the Reset VNC Password Wizard):

"reset password on several machines at a time. But with a diference it would ajust only the connection settings for each of the selected machines without trying to access the vnc services on each of the machines"

I was refering not to access the remote machines at all, and just update the settings at the VNC Manager.

I will give you my sittuation: Inside VNC Manager we added 87 new machines. But the vnc password to that group of machines is not the default one. So I only want to update the password that VNC Manager should use when connecting to those machines in particular, cause the machines themselfs are already correctly configurated on the server side. Basically i just want to update the client side. (VNC Manager).

That's why i said on the other post: (Can be even a evolution of the "SmartCode Reset VNC Server Password Wizard" with a checkbox added so that one can check it if he or she wants to "update connection settings only, without accessing remote machines" or something similar.)

Hope u understood what i meant now. I know that i can manually adjust which password vnc manager will use to connect to a machine, but i can only do that one by one.. wich can be pain sticking when being a large quantity of machines that one wants to edit at the same time.

Thanks for the attention. And sorry for the confusion.

OK. Now I understand, and you know what this feature has been a part of VNC Manager since v1.0, or since v2.0 at least
Take a look at: Tools->Options->Defaults->Default VNC Server->Apply to All Servers. In the dialog that appears when you click Apply to All Server button, you should check Login Credentials option. This will reset password on all registered VNC server.

Also, in v3.0 we added "per folder" login credentials support, so it gonna be easier to manage login credentials.

"OK. Now I understand, and you know what this feature has been a part of VNC Manager since v1.0, or since v2.0 at least

Take a look at: Tools->Options->Defaults->Default VNC Server->Apply to All Servers. In the dialog that appears when you click Apply to All Server button, you should check Login Credentials option. This will reset password on all registered VNC server. "

I know, but that's exactly that will reset on "all servers". I, on that ocasion, only wanted to update the 87 selected connections *without* influencing the other 1390 servers that have diferent configurations (yes we have that much ).

So my sugestion mantains: the reset wizard having a option that would make the reset only on the vnc manager and not on the servers (bypassing that part of the code).

The per folder solution seems already ok, cause it permits me to workaround/play with it. (Moving to a temp folder the servers i want to change, making the change in the folder temporaly created and then moving the servers back into place.)

Thanks for the replies.

Greets from sunny Portugal