Quantcast
Channel: File Services and Storage forum
Viewing all articles
Browse latest Browse all 13565

Server 2016 Work Folders and Windows 10 1803 Sync Question

$
0
0

We've just deployed Work Folders in our organisation and so far we're loving it. It solves a lot of issues and enhances our user's experience.

I have a question about .ini files. 

We have essentially created a work folder on their laptops containing C:\Users\Username\Work Folders\...

  • Documents
  • Desktop
  • Downloads

We've used GP to redirect their associated folders to this new location using folder redirection. This allows remote workers to save and open files without the files going over the WAN everytime as we've set it to always be available whilst offline. 

One big problem we have at the moment is with the sync icons. When I look at File Explorer, it'll show Desktop, Downloads and Documents with a BLUE Sync Arrows. If I click on those folders, everything is green ticks. This simple GUI glitch throws the user into thinking it's not synchronising correctly. My understanding of this behaviour is a result of the desktop.ini file. Work Folders ignore .ini .tmp files. So if a user has those, then the top level folder shows as continuously syncing, even though it's not. 

Now, I'm new to this feature and as far as I understand, it has been about since Windows Server 2012 R2. Does this always happen? Is it normal behaviour to show the top level folders with the blue sync arrows, even though everything inside has synced or is it a relatively new GUI bug that affects Windows 10 1803?

You can replicate this behaviour simply by adding a .ini file inside a work folder. The top-level folder will show the syncing icons. The sync control panel will show green - syncronised. 

Does anybody have a workaround so I don't throw the users experience off? I'm getting support calls because they think it' not syncing.

Thank you


Viewing all articles
Browse latest Browse all 13565

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>