Forum Discussion
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?
1 Reply
I see nobody ever addressed this but I can tell you I see this exact same behavior in January 2025 with 2.9.8884.27471. The funny thing is had this working in one datacenter and it was flawless. For various reasons I needed to move the VDI environment that was using it to another datacenter and in that one, same domain and same DFS namespace, FSLogix will behave exactly as you describe....i.e. it reports that it can't find the VHDX, so it will create a new one, and then fails to create the new one because it CAN see that there's an existing one.
If I address the folder target directly, it works just fine. If I set up a procmon on the host, it never sees the call out to the DFS until it tries to create the disk. I'm just dropping the DFS for now but it's weird that it won't work.
