[1607, au] Offline files requiring fully-qualified path for reliable re-connection in Win 10?

[pete]

Short version:

 

Has anyone noticed offline files behaving less reliably with Windows 10 (compared to Windows 7) when using netbios names for the shares?

 

If you have and you've enabled the longer than 256 character option in Windows and then used fully-qualified paths instead, has this bitten you in unexpected ways?

 

Long version:

 

We've been using offline files since Windows 7 made it actually reliable. Various bits and bobs are automatically redirected for staff and students so a device that leaves the premises has certain files on it.

 

We've noticed that for home directories the re-connection isn't always reliable if it's using the netbios name (\\server\share\username) as opposed to the fully-qualified name (\\server.domain.whatever\share\username) or the DFS name (\\domain.whatever\dfsname\sharename\username).

 

We've been leery of using fully-qualifed paths for homedirs in the past because staff can reliably hit the 256 character limit even using netbios names, but since Windows 10 can support greater than 256 characters in a domain name, this may not be a problem.