Troubleshooting
WebDav
Webdav is not working with FQDN
If the full DNS name of the server is not in the same domain as the client (e.g. abc.fake.net and userpc.domain.local), an entry must be made in the registry for the Windows client to send its credentials.
On each client PC, open the Registry and browse to this key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters
Edit the Multi-String value AuthForwardServerList (REG_MULTI_SZ) and for example insert this values:
https://abc.fake.net
http://abc.fake.net
This causes Windows authentication to be used even if the name is a full-qualified domain name!
See: Prompt for credentials when you access WebDav-based FQDN sites in Windows
After this change, the WebClient service must be restarted!
First open of any document fails
This could be a problem on the client side, when the WebClient service which is used to process webdav requests takes too long to start. The second request will succeed, because the service is then already running.
To resolve this, change the start-up type of the WebClient service to automatic.
How to re-enable office plugins after being disabled on startup
When Outlook is opened and the inPoint.OutlookAddin loading took too long, it can happen that Outlook is showing a Question Dialog (Enable OR disable the inPoint.OutlookAddin). If the User once clicked "disable", the inPoint.OutlookAddin gets disabled forever!
Outlook creates a new registry value in the current users registry and sets the loadbehaviour=0, which means the Addin is not loaded anymore.
Remove this key completely and restart Outlook.