Question

How to stop LF Server Service from publishing an SCP every time it restarts

Updated July 23, 2019

asked on May 6, 2014

Hi,

How would one configure the Laserfiche Service to not try and automatically publish a SCP each time the service restarts?

For example, my client has multiple Laserfiche Servers, DEV / QA / PRODUCTION etc. The end user does not need to see DEV and QA servers and their respositories. Removing the SCP is easy, but each time the service is restarted, LF publishes the SCP again.

Thanks

Sheldon

0 0

Answer

SELECTED ANSWER

replied on May 7, 2014

We're looking at including an option for turning off publishing SCPs in the next service pack for 9.1.1.

0 0

Replies

replied on May 6, 2014

There is no way to turn off publishing SCPs when the server starts. However, you can stop the clients from picking up the broadcasts by turning off "Scan for network repositories" in the Client's start screen. You would have to manually attach the repository for any new installations (or you could push out the corresponding registry keys through the Windows user's login script).

0 0

replied on May 7, 2014

Hi Miruna,

Thank you for the feedback.This would be a rather labour intensive task, since this would mean manually setting this for over 300 LF Clients who may not all be geographically located in the same place.

Adopting this approach would also mean having to manually add new repositories for each LF Client as well. Another administratively long task to execute.

Is this not something that can be seen as a feature request? Alternatively, is there no way to manage this on the domain through login scripts for adding and removing repositories for each user?

Perhaps another option would be to implement some sort of script that checks and then removes the SCP that is not needed on a daily basis. What do you think? Is this possible?

I am in the process of investigating this since it is already a pressing issue and for this particular customer, there will an addition of another 12 LF Servers on the domain in the near future. Imagine the confusion for the users.

Regards,

Sheldon

0 0

replied on May 7, 2014

Hi Miruna,

That would be great! Thank you for considering this feature.

Regards,

Sheldon

0 0

replied on October 22, 2014

Hello Miruna,

Has an option in the Laserfiche Administration Console been including for turning off publishing SCPs in any of the latest service packs? We are having the same issue with multiple repositories and different groups of users who do not need to see our test repositories and other agency repositories.

Thank You,

Zach Merrill

0 0

View 4 previous replies

replied on October 22, 2014

This is available in Laserfiche 9.1.1 SP1 and later. Please review KB 1013480 where it states

You can now configure the registry to stop the Laserfiche Server from automatically attempting to republish a service connection point in order to prevent client programs from being able to automatically detect the existence of the Laserfiche Server instance. Using the Windows Registry Editor, browse to the HKEY_LOCAL_MACHINE\SOFTWARE\Laserfiche\Engine\8.0 key. Modify the value of SCPBindingPath by deleting the LDAP:// protocol prefix. (114274)

1 0

replied on October 23, 2014 • Show version history

Alexander,

I deleted the LDAP:// protocol prefix from the HKEY_LOCAL_MACHINE\SOFTWARE\Laserfiche\Engine\8.0 the Registry on our Test Server. I have also tried deleting the GUID. Our test repositories are still being broadcast. I have restarted the Laserfiche Service on the Server and also restarted my local client. You can see that our two test repositories on our test server are still broadcasting to the client.

0 0

replied on October 23, 2014

Can you try a Client on a different machine than the server?

0 0

replied on October 23, 2014

Miruna,

The client I tested is on my local machine. I've tested it several times throughout the morning and the test repositories are still being broadcast.

0 0

replied on October 23, 2014

On your Client machine, are any repositories listed under HKCU\Software\Laserfiche\Client8\Profile\IPDatabase or HKCU\Software\Laserfiche\Client\Profile\IPDatabase or HKLM\Software\Laserfiche\Wow6432Node\Laserfiche\Client8\Profile\IPDatabase or HKLM\Software\Laserfiche\Wow6432Node\Laserfiche\Client\Profile\IPDatabase?

The Client caches repositories you've logged into before. Try deleting those keys and restarting the Client.

1 0

replied on October 28, 2014 • Show version history

Miruna,

I have also deleted the repositories on my local machine under the paths you specified. As my results are shown below, the repositories are still seen after restarting my local Laserfiche Client.

0 0

replied on November 11, 2014

Prior to making the registry change, did you first delete the originally registered SCP? Please confirm by performing the following steps:

Use the lfscpcfg delete command to delete the registered SCP
Use the lfscpcfg list and/or query command to confirm that the SCP is no longer present
With the registry change in place, restart the Laserfiche Server service
Use the lfscpcfg list and/or query command to confirm that the SCP is not registered back

0 0

replied on August 10, 2018

If you ensure your Laserfiche server service user is NOT a network admin, the it cannot register the SCP.

Source: Me. Our IT staff removed network admin from the LF user and the new servers SCP records haven't been created. I had to ask someone w/ network admin privileges to run the command to create it.

0 0

replied on July 23, 2019

Adding some additional detail...

"Network admin" doesn't sufficiently describe what you're looking for. What it should say is to ensure your Laserfiche service's service identity is not Local System or Network Service. Both of these accounts will present the computer's "machine account" when connecting to network resources, for example to AD to publish an SCP.

If you roll the service identity over to an AD user/service account, even if that service account is in the local administrator group, the service will not be able to publish the SCP.

So the proper steps would be:

set the LF Server service identity to a domain account, restart the service
run "c:\program files\laserfiche\server\lfscpcfg.exe delete" from the server itself, it will delete any existing SCP for the server.

On subsequent restarts of the LF Server service, it will not be able to republish the SCP.

1 0

You are not allowed to follow up in this post.

Question

Question

How to stop LF Server Service from publishing an SCP every time it restarts

Answer

Replies

Sign in to reply to this post.