b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
c) The Distributed File System (DFS) client has been disabled. If that does not solve it, do the same on the file server. I have no idea why the implemented GPO options don't, though.
If the Win8.1 / Win10 clients connect, sometimes the drives appear, but most of the time they don't.
If I run a But if they click on the drive again, all is well.
Finally, if doesn't cut it, you can look at the source code for update.packages and create your own customized version that will always avoid the common library location in program files. In my own case, it is because our admins want us to use remote virtual disks (on Windows 7) for our files and everything is locked up tight as a drum.
The only way I can use R packages is in a lib directory on that remote virtual disk.
EDIT: Please remember that the hardened UNC Paths were implemented to fix a "critical" Windows security issue, which can be dated back to the year 2000.
By deactivating the hardened UNC paths you actively open that hole again, if it's worth it depends on your topology and / or needed infrastructure security.If that also does not solve it, try to use a different network port on the file server (if possible).) directly. Maybe I did something wrong, but at this time I really don't care anymore, as long as it works.Microsoft will probably release a (new) hotfix soon anyway.I went and deactivated fast boot for all clients via a registry GPO ( with Windows 8.1 and Windows 10 clients (all updates installed).The GPPs map 7 drives, 4 of them are on the main DC and fileserver, the other 3 on DFS shares.With all of this work, I might as well went to Linux (I should, really...) (I updated my post with the above information: I hope it will help someone in the future, Tal If you cannot turn off your antivirus, due to corporate policy for example, here is a workaround that I found.