Location of passphrase seems to have moved
HI. We are in the midst of deploying RDM and I've run into a snag. We need to be able to prepopulate the passphrase for each of our databases into our VM VDI image. It used to be located in the registry and buy taking the GUID of each DB entry and adding the passphrase key I was able to get around each end user form having to enter it for each DB he accessed. Can you tell me the location of the passphrase now? It does not appear to be in the registry (at least not where it was) so it's either encrypted or moved elsewhere. Even better, is the a simpler way to achieve what I'm after?
All Comments (4)
Hi,
I don't recall to have move it. You can save it in the registry for convenience but it always has been in %LocalAppData%\Devolutions\RemoteDesktopManager
David Hervieux
Interesting. I had started putting it in the registry when I first deployed it the VDI environment as we need to preserve the setting. Each of our VDI desktops is re-imaged upon log off, so I need a way to have the passphrase added to the base image. The registry used to work, but now it makes no difference if I have the entries there or not. A VDI desktop user will be prompted for the passphrase upon first use of the database every time. As long as he stays logged in, there is no problem, however logout is a daily event. So I need to be able to make the required entries a part of the default image. I will have a similar issue with my Terminal Server users, although I'd expect the passphrase entries to be part of the user profile so the simply having the end user perform the entry on first use should be acceptable. That said, I don't see the entries in either the appdat\local or appdata\roaming (we use roaming profiles) folders. Any idea where I might locate them in a terminal server environment? I can say that something has changed; the old method of prepopulating entries via the reg entry no longer appears to work.
Could you export me one of your registry key (with a fake passphrase) that use to work? Just make sure to set it in LocalMachine by the way.
David Hervieux
I've just tested it and it work fine for me. However just make to use this key if you use RDM 32 bit:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\RemoteDesktopManager
David Hervieux