Profile Container DFS Setup - App doesn't find VHD Profile
I'm trying to Setup FSLogix Profile Container for 2 Terminalsserver for another department of my company. To get some sort of higher availability, I did setup 2 Profile Server Nodes with DFS Namespaces. In my Test-Environment, this worked great, I could take down one of my DFS Server Nodes and FSLogix would just wait for the Profile Path to be available again and mount the vhd file. Now, when I try to set the same thing up in my productive environment, I run into a strange issue. The initial creation of the vhd file of my test-user is working fine, but as soon as I try the failover by taking the DFS Server Node down, where the Profile vhd was initially created, the test-user gets a local profile (after the Path is back online again of course). In the Logfile I can see, that the App says, that it couldn't find the Profile, and therefore tried to create a new one, but as soon as it tries to create it, it says, that the file it tried to create, does already exist. So the problem is, that the Profile is there, but for some reason FSLogix doesn’t “see” the vhd file as the Profile of the Testuser.. Does anyone have any idea where to troubleshoot for this problem?
DFS-N migration to Azure FIle Sync
Hi, We are in the process of migrating our on-prem DFS-Namespace to Azure File-sync. Our on-prem functional forest and domain modes are at 2012R2 which is the minimum level supported by AFS, our DFS Windows mode is 2008. What is the minimum DFS namespace windows mode required? From investigating, all I can see are 2000 and 2008 modes, is there a 2012R2 mode.
DFS Content Freshness Adding Replication Member
I have a server that is added as a DFS target in a DFS namespace. The target is fine but is not added to the existing replication group for replicating contents of that folder. At one point it looks like it was a member as it has the same data and file structure but I'm not sure how long it has been removed from the replication group. I have been researching the issue and it looks like if I add it back to the replication group as a member (being that content freshness is enabled on ALL DFS replication members) it will kick off an initial non-authoritative sync and replicate any files missing since it went offline to the share and NOT replicate any stale data to the other member. Wondering if anyone has done this before Many Thanks!!
