DFS Shares going offline after user's device was converted over to folder redirection

Question

Hello,

Having a hard time trying to figure out the fix on this issue that's been going.

We have two file servers (we will be consolidating it down to one, but that's a project for another time). Both of these file servers live in Azure

One file server contains the necessary drive shares that get mapped to user's individual devices. The other (newer one) contains the home directory where user's base folders are getting redirected to, and FSLogix for Windows Virtual Desktop.

Both of these file servers share the same namespace (\server.local\fileshares).

After converting a user's folders over to folder redirection, their shares that were mapped to this person's device existing at \server.local\fileshares\sharedfolder routinely get disconnected, or don't even map through.

I did some digging and did a few items to help troubleshoot:
-Refined offline files GPO, including boosting the latency to the server before the device goes into offline mode
-Blew away his local profile and let Windows recreate it
-Ran updates and reboots after hours on the file servers
-Recreated the shares on GPO
-Verified all his network settings were good and correct, even refreshed the device so it would get a new IP
-Reformatted offline file cache

It still reoccurs. What I'm noticing is that this may be largely related to offline files. When his drives get disconnected or don't show up, we can only path out to the home directory share on the DFS namespace. If I go into offline files, I see that his offline file status has entered a disconnected state and will periodically drop in and out.

Does anyone know how to help resolve this?

Answer 1

Hello @cz57avenger ,

Thank you for posting here.

When the problem occurs, we can try to do:
1.ping server.local and click Enter.
2.Ping the IP address of the two file servers and click Enter.
3.If we can ping the IP address of the two file servers, but we can not ping the domain name, maybe there is issue related to DNS resolution.
4.Open Command Prompt on client ,type nslookup and type set d2 .Then type server.local, we could find out the problem through the process .
Type NSlookup and click Enter.
Type set d2 and click Enter.
Type server.local and click Enter.

Here is the guide for Nslookup :
Nslookup
https://technet.microsoft.com/en-us/library/cc940085.aspx

5.Meanwhile, we can map the drive manually on one client to see if the issue occurs when the problem occurs we mentioned.

Hope the information above is helpful. If anything is unclear, please feel free to let us know.

Best Regards,
Daisy Zhou

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.