Is there a way to determine which specific domain controller LFDS is connected to?
Question
Question
Is there a way to determine which specific domain controller LFDS is connected to?
Answer
Easy to check in PowerShell with:
# Get current domain controller of host $dc = $env:LogOnServer $dc nslookup $dc
Replies
You would determine this the same way as for any Windows machine, since being joined to a domain is a machine-wide property.
If you are referring to specific domain controller host that the default Identity Provider uses, that is determined by the domain controller known to that host machine.
You can specify additional hosts if necessary:
Easy to check in PowerShell with:
# Get current domain controller of host $dc = $env:LogOnServer $dc nslookup $dc
Hi
One thing I have noticed is if you install and configure LFDS on a fresh machine it will automatically add the current Domain as an AD Identify Provider.
If you look at the Database Table the HOST value will be NULL.
However if you manually add an Identify Provider the HOST Value is required.
Adding New Identify Provider in LFDS 11
I have a customer where LFDS was implemented a number of years ago before they had AD. We then added an AD Provider manually subsequently, when AD was implemented, so it appears the HOST is hard coded.
Does it still use this Hard Coded Host? or the current HOST Domain as above. Interesting enough when you add a provider the HOST value shows but once it is added in LF11 the HOST field in LFDS Web is not available to view or modify on LF10.4.4 the Host value is visible.
10.4.4 Visible Host
LF11 (provider was added manually in LF10 prior to upgrades)
The customer will be changing the DC Host so it does not appear there is a way to modify the Host for this existing AD Identity Provider or even better make it NULL like the default installation / configuration provider?
We are also wondering if this could be related to NTLM requests. The customer is looking to disable NTLM on the network but it appears we are getting NTLM requests from the Laserfiche Server every 30 minutes which we suspect is LFDS Polling the DC?
This provider also uses a Username versus the Service Account in case that can be related to the NTLM requests.
Any background / guidance would be greatly appreciated as always.