In addition to a laptop, I frequently work directly on a Windows Server 2012 R2 computer. We have Redirected Folders set up on DFS (for failover redundancy) so that my Documents folder is in: network\usersname\documents. This all works fine on Windows 7 and 8 client computers connected to the network.
2 Questions for accessing these files on server computers:
1. On a server that is hosting the files, it has Desktop Experience enabled and Windows Search. If I navigate manually through the DFS root folder to my documents folder, I can search and it properly uses the index. This proves the location is properly indexed. However, if I access the folders through the official "Documents" folder from the Folder Redirection (a network share pointing to the same server computer I'm working on), it performs an un-indexed search (slow and ignores file contents, but does find files eventually if the search term is in their filename). Is there a way to force the server to use the indexed search on the Redirected Folders (my Documents folder in particular) when working on that server when logged in locally on that server?
2. On all servers (and only on servers), the Redirected Folders policy is not being applied properly, or at least the personal folders are not being updated on other servers. There is no problem on workstation/client computers -- those are all correctly showing the Redirected Folders. I looked in the Group Policy and don't see that servers are excluded from Folder Redirection and actually see the notice about applying folder redirections when logging in on other servers, but the folders are not updated to new Redirected Folder network destination. Any ideas why Servers would not gain the Redirected Folders but clients work fine? Maybe I'm looking in the wrong place in the Group Policies. Where should I check?
Thanks,
Colin
Colin