Operating system and version (Ubuntu 24.04): Ubuntu 24.04.4
Web server and version :Apache 2.4.58
PHP version : 8.3.6
Is this the first time you’ve seen this error? : maybe
When did this problem seem to first start? dont know
Installation method (AIO vmware)
Are you using Cloudflare, mod_security, or similar? NO
Web Browser
Chrome v146
Windows 10
Summary of the issue you are facing:
I use net use R: “https://nc.mydomain.ru/remote.php/dav/files/username/” /user:“username” /persistent:yes
to add lan drive in windows.
AND when i logout/login or reboot Windows i see red cross on my lan Webdav drive.
I need to double click to this disk and enter ldap password again.
Windows Credential Manager saves login and password but it dont use it for webdav nextcloud drive.
How to make it works? (remember password and use it after reboot)
This seems to be more of a Windows question than a Nextcloud one.
By the way, Windows 10 reached end of support in October 2023. Also, the built-in WebDAV client, which never worked particularly well, not even with Microsoft’s own products like SharePoint, has been officially deprecated in 2023. The WebClient service is still present in Windows 11 for now, but it is disabled by default and may be removed entirely in a future version: Deprecated features in the Windows client | Microsoft Learn
I would either switch to an operating system that still supports WebDAV properly, or use the Nextcloud Desktop Client with Virtual Files enabled. That uses the Windows Cloud Files API, just like pretty much every other modern file sync client does nowadays.
On Windows, WebDAV is pretty much a dead horse at this point.
The fact that these features are marked as “Deprecated” does not automatically mean that these services will actually disappear from Windows. It can also just be an announcement that the service has been given a different status, i.e., as in the case of the web client (WebDAV) service, that it will simply no longer be started by default:
Feature
Details and mitigation
Deprecation announced
Webclient (WebDAV) Service
The Webclient (WebDAV) service is deprecated. The Webclient service isn’t started by default in Windows. For more information on WebDAV, see WebDAV - Win32 apps.
November 2023
And then there is the link to the details of the protocol, so there is even a little advertising.
It may be many years before this protocol actually disappears from Windows (if at all). So I wouldn’t make too much of a fuss about it now. Should the service actually be removed in the future (which I really don’t think it will be), but if that is really the case, then I will adapt the app, even if I have to rewrite the WebDAV client from scratch.
The fact that it the URL points to “win32” would worry me a bit, wouldn’t it? I mean, have they ever updated it since its release?
But yeah, I’ve worked in IT support long enough. People want their drive letters, I guess a Nextcloud icon in the sidebar where you can find all your files just doesn’t seem to be good enough.
But even back then, we advised people against mounting their SharePoint folders as WebDAV drives. Officially, we didn’t support that either, but of course we then still had to support it when users called in.
Do you really think that would be worth the effort? I mean, in practice, what is the downside of simply using the Nextcloud Desktop Client with Virtual Files enabled?
Serious question, because I have not actively used Windows for quite some time, so I also have not used the Nextcloud Desktop Client there.
Just a quick note/clarification: Back then with SharePoint, the choice was of course between using the web UI or Windows Explorer. However, with Nextcloud and Virtual Files, you have Explorer integration. This is why I asked whether using WebDAV on Windows is worth the effort.
I don’t want to talk about up- or downsides. They’re simply two different ways to interact with your cloud files. Each has its own pros and cons.
The Nextcloud Desktop Client lacks File locking like my Client supports, that is one of the most important differences.
And then there’s the problem of uninstallation. The virtual file system writes a lot of artifacts to the hard drive, and removing them can become a real pita.
And finally: My app is the tinyest client available. It’s a mere 0.18 MiB compared to 226.7 MiB for the official Windows client. Upon removal, it leaves absolutely no trace; it’s designed for maximum security and privacy and can be used on a USB stick on some other ones computer (in KIOSK mode) without exposing secrtets or leaving a single trace.
Thank you for the explanation. Just to make this clear once again: I did not mean to criticize either your work or the reasons why you are doing it. That is why, alongside my somewhat sarcastic comments, I also added that clarification.
Also, I will certainly mention your solution if someone asks a similar question again. However, I’m not sure I’ll be able to keep my general opinions of Microsoft Windows entirely to myself!
NcDavTray already uses the standard HKCU Run key for autostart, so that part can be managed via GPO without any issues.
The rest is basically typical user-level deployment (providing the binary and a preconfigured config file), which can be handled with logon scripts or GPO preferences.
So while it’s not a native GPO-integrated solution, it can still be deployed centrally using the usual mechanisms.
If you can describe where exactly you’re running into problems with GPO deployment, I might be able to point you in a more specific direction (e.g. via a small deployment script or similar approach).
