Offline files frustrations

[mrbios]

I'm trying to use offline files and i think the way in which my folder structure is setup is the factor causing me issues, and I'm not entirely sure if i can fix it (at least during term time!)

 

Our folder structure for staff and students home folders is as follows:

\\servername\home$\Staff\staffname

\\servername\home$\Yearofstudents\studenthomefolder

 

for example

\\fs1\home$\2015\00aaa0000 would be the full path to a year 7, or \\fs1\home$\staff\joebloggs would be a staff folder.

 

Staff and students don't have read access to home$ or 2015/staff. They are owners of their own folders with full access though obviously. I think it's that in between section and not having read access that's causing me issues.

 

As a test i've shared a students home folder as a full share, so \\fs1\00aaa0000 for example with nothing inbetween, mapped it as an offline files directory and low and behold it works flawlessly, mapping first time, syncing faultleslly. Whereas folders such as the ones with the non-readable folders in between don't show up in my sync partnerships list and have all sorts of problems actually syncing.

 

Any idea how to resolve this? I've seen examples of what permissions users need on the "in between" folders, then i've seen countless things disputing that, now i've no idea what to believe or how to get this working properly.

[Sagima]

I think you need to give them the traverse folder permission for the folders they need to go through or share staff to the staff with read access

[mrbios]

I've tried adding that, and meanwhile i've made a student account with higher access (run etc.) but i can't seem to browser to \\server\share$ it tells me "You do not have permission to access..." but if i run the effective access simulation on the file permissions, adding in the specific user and computer it tells me that user should have read access.

 

I can't figure out what is stopping me from accessing, at least at the most basic, read only level to that folder! >_<

[mrbios]

Fixed it, created a duplicate share and folder tree to play with, messed with some permissions on there. Not 100% certain what the fix was, but i think adding "SYSTEM" with full control of the folder tree is what fixed it, but i could be wrong....though i can't see anything else i did different on the test setup i made compared to the live folder tree.