I need to be able to push out a registry entry to clients so that the repository is attached (doesn't need to be manually attached because it is on a subnet). Which registry key should be pushed out and what should the value of the key be?
Question
Question
What is the registry key and value to set to avoid having to manually attach a repository?
Answer
You can disable the scanning of available repositories as follows:
- Open up HKCU -> Software -> Laserfiche -> Client8 -> Profile -> Options in the Registry Editor.
- Create a new String Value called "Thunk" and set that value to "0".
With this key created, the Client will NOT scan the network for repositories by default, and will instead display the recently selected repositories (found under HKCU -> Software -> Laserfiche -> Client8 -> Profile -> IPDatabase). You can right click inside the Available Repositories window and check Scan Network for Repositories to re-enable network scan.
Replies
If you want to set it for machine-wide, such as when you want to push it out like you are talking about here, you should be able to use the same locations under HKLM and the Client will check that value too. Since pushing out keys to HKCU can be annoying.
I believe it is "HKCU\Software\Laserfiche\Client8\Profile\IPDatabase" new string value
Value name=Repository Name Value data= ServerName or IPAddress
The easy way is to set it on one machine by manually attaching and then export the key I have found.
Is there a reason you can't have it broadcasted?
I do not want to speak for Donald as to his situation, but our customers with very large domains have found that if they "scan the network" for the repository, it can take 40 to 60 seconds for the client to populate the repository list. These customers are never happy if they have to wait that long before they are able to log in.
So instead, we turn off the network scan and map the repository. Then they are able to log in without the long wait and everyone is happy.
Another reason is that if DNS is not working properly or, as in this case, the IT department doesn't want the users on different subnets dealing with the issue at all, it is easier to just set it via an exported registry entry updated with a logon script than to touch each workstation.
FYI, it doesn't work under HKLM. I tried both the 64-bit and the 32-bit sides of HKLM and it still scanned and didn't have the attached repositories.
Did you already have the Client key under HKCU? HKLM is used as a fallback mechanism if there aren't any values under HKCU.
Yes. I think that was the reason. Fortunately, these are all new PCs, so the end users haven't logged in yet. Hopefully the HKLM keys will take effect when they open LF Client for the first time.
Adding the same key under HKLM doesn't work for us.
What exactly does not work?
Confirming Paul Bateman's comment at the top of this chain.
I deleted the HKCU IPDatabase key, then added HKLM -> Software -> Laserfiche -> Client8 -> Profile -> IPDatabase and created a String key with the repo name, and LF Server address as the value. The desktop client still doesn't pick it up. So the "fallback mechanism" you mentioned doesn't seem to work, at least on 10.3 Update 1.
There really should be an "attach this repository for everyone on this machine" option when attaching a repository, because that's pretty standard for terminal server setups. The alternative (having IT fiddle with registry keys) is not good.
To add a repository machine-wide (I tested this on the 10.4 client), create they key HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Laserfiche\Client8\Profile\IPDatabase and create a REG_SZ with the repository name and LFS host:
The "Thunk" setting for scanning the network does not read from HKLM, but if you set the above value the repository will show up in the list and be selected by default.