change default folder name suggestion when opening a shared folder

micro

Hello Manfred and Felix,

thanks a lot for clarification and your efforts. I will try it later …

micro

I changed the default behaviour by using the “PluginDebugger.exe” which I found inside the installation directory “C:\program files\kopano\Kopano OL Extension”. This works fine, but: how can I have the desired setting %username% - %foldername% applied to ALL our workstations across the company? I don’t want to set this on each workstation, I’d prefer a global configuration.

How can we set such a global configuration?

fbartels

@micro said in change default folder name suggestion when opening a shared folder:

How can we set such a global configuration?

since this is pure client side code there is no way to enforce this from the server. what you could do however is to set this option through a reg file and apply the reg file in your logon scripts.

micro

can you provide some more information about this .reg file? I already tried through Windows Registry, but without success.

fbartels

Something like the following will work (with your desired template set:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Kopano\Kopano OL Extension\SharedFolders]
@="SuppressHierarchyChanges,AllowImpersonate"
"DefaultFolderNameFormat"="%foldername% - %username%"

micro

Hi Felix,

I did try that before manually with the registry editor but it didn’t work because I used HKLM\Software\Kopano… in your example it works within HKCU key. But I’m not sure if this will take effect when different users logon to a workstation. Is it possible to use this setting under HKLM, too?

It would be nice if someone could add your example to the manual. (take care for the missing space in the name SharedFolders, the manual shows it the other way as it is displayed in PluginDebugger.

fbartels

@micro said in change default folder name suggestion when opening a shared folder:

Is it possible to use this setting under HKLM, too?

I’m not sure. I have to check with the developer for this.

fbartels

Had a quick chat with the developer. KOE already as capable of retrieving settings from hklm, but this only happens if there is no value set in hklu. In addition to this it would not fallback if the value in hklu is an empty string (which happens if settings were unset through the plugin debugger).

So my guess would be is that you applied it to hklm, which there were still settings in hklu.

fbartels

we made a quick fix for this in https://stash.kopano.io/projects/KOE/repos/kopano_ol_extension_source/commits/c8fc2fe78da71385a709941fd596ccb00f0ee20a. can you check the latest installer from https://download.kopano.io/community/olextension:/ ?

micro

will that work on our business productional environment where I run kopano-server 8.5.9.0-0 ? I guess it should because I would only update the OLE extension on my own Windows client workstation, right ?