I'm having a security problem involving Windows Offline Files. I'm using Offline Files in Windows 10 with files located on a server that is running Windows Storage Server 2008 R2. When connected to the network, my account has no problem accessing files located in appropriate shares on the server. But when my computer is offline, I am unable to access any files that I have not previously accessed on the server while connected online, and receive "Access Denied" messages. The folders that I need to access contain literally millions of files, so I cannot simply take the time to access each of those files in advance while connected online, just so that I will later have the ability to access those same files offline.
Note that I suspect this issue could be related to some recent changed permissions on the server. Here is the relevant setup for one of the accounts with this problem:
On the laptop, there is a local user named Kevin, with a certain password.
On the server, there is an identical user named Kevin with the same password, and that user is a member of the group KAM-BTM.
On the server, the group KAM-BTM has Modify, Read & Execute, Read, and Write permissions on the share containing the files that are exhibiting this problem.
On the server, all subfolders and files beneath the top level share inherit their permissions from the share.
It seems as though the laptop may have cached some obsolete permissions from the server, and the only way those obsolete cached permissions get updated is by directly accessing each individual file while the laptop is connected to the network. Is there any other way to correct these problems? If necessary, I could re-initialize and re-populate the offline files client side cache, but I believe that has already been done since the server permissions were changed, and it failed to correct the problems. I want to avoid doing that again unless it is pretty certain to fix the problems, because there are hundreds of gigabytes of files that need to be available offline, and repopulating the client side cache will all of those files take a great deal of time.
P.S. - I just ran "attrib -r *.* /s" on one of the problem shares, and that did appear to fix this issue for most of the files on that share. However, that is only a partial and somewhat undesirable solution, because 1) it fails to access any hidden files (such as Excel autosave files, for example), and 2) it removes the read-only attribute from any files where that attribute may have actually been intended. Something similar to this command might work, but I need something that merely accesses a file *without* potentially changing anything about it.
Thanks in advance for any help,