You are viewing limited content. For full access, please sign in.

Question

Question

Automatic repository discovery on non domain joined machines

asked on September 19, 2024

We are deploying LF Windows Client on Azure joined machines and I'm wondering how I would prepopulate the repository list. Is this possible?

0 0

Replies

replied on September 23, 2024

I'm not sure if the Azure joined status would affect this but the Windows Client picks up the repository list from the HKCU registry if they have been manually attached. By default, the LF Windows Client will attempt to scan the network for repositories and this can cause a delay when loading this list, hence it can be disabled (Right Click the repository selection area and de-select "Scan network for repositories"). Under the hood this adds/updates the "Thunk" registry setting under HKCU\Software\Laserfiche\Client8\Profile\Options to 0 (disabled) or 1 (enabled, scans network).

For the repositories though, these correspond to registry keys under HKCU\Software\Laserfiche\Client8\Profile\IPDatabase with the key name being the name of the repository (string value, "Repository1") and the key data is the FQDN of the Laserfiche server ("lfserver.domain.local"), i.e.

0 0
replied on September 24, 2024

How does it "scan the network for repositories" though? Best I can tell, this is via an SCP record in AD, not really a network scan.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.