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 Folder Replication DB Import Error code: 0x00000005
Hello, I have a server 2016 file server I am trying to setup with DFS folder replication. The volume that I am stuck on has 15.4TB of data and I have already done the preseeding to the downstream server which is within the same network. I have done the dfrs clone export both with basic validation and no validation, the basic validation seems to timeout and error out saying it wasnt able to read the config.xml file in the directory, however when I do no validation it goes right through but then the downstream server on the import gives me a Error code: 0x00000005. I have done my own validation on the preseeded folders and files on the downstream server so I am not worried about doing the validation and just need the downstream server to import it.
Stop DFS replication and remove data from one server
0 Hi, two servers, both servers on the same domain. DFS is setup to replicate between both servers. How do I stop the replication and delete the files from one of the servers, while keeping the data intact on the other server, without causing a mess and potentially making the shares unavailable or experiencing data loss? DFS can stay, just the replication needs to stop. I'm aware how to stop DFS: Open the DFS Management console. Expand the Replication. Select your replication group(s). Right-click on each member server and select Disable. But this will still leave me with the data on both servers, won't it? I want to reclaim the space by deleting the data off of one of the servers because it's quite a lot and the space is needed elsewhere. Thanks!
DFS folder exists in file system but not in DFS management console
I recently added some server 2022 DFS namespace members to an existing DFS namespace running on 2012 R2. I have been having an awful time getting ABE to work properly using dfsutil. In the process of troubleshooting, I deleted a test folder from the console that was not working properly with the ABE (I think it was corrupt) and it deleted it from the console but not on the file system of the dfsroot folder on the DFS servers. So now I have this orphaned dfs folder on file system with no matching object for it in the console. Does anyone know how I go about cleaning this up?Replicación DFS entre sedes
Buenas tardes, Tenemos configurado un servidor DFS en la sede principal con Windows Server 2019 y hemos creado una replicación DFS de algunas carpetas a otra sede. La idea es que en cada sede se trabaje contra los documentos de su servidor y entre ellos se repliquen los datos. El problema es que si un usuario de la sede principal abre un documento el lunes por ejemplo y hasta el viernes no lo guarda y cierra, todos los cambios que hayan realizado sobre ese mismo documento en la sede secundaria al replicar se pierden. Es decir, en caso de que se edite el mismo documento en las dos sedes a la vez, solo se guardan los cambios del último que le ha dado a guardar. Que se puede hacer para que se bloquee el documento en uso, salga algún mensaje o que no permita abrirlo al menos en la segunda sede? Queremos evitar que se pierdan los datos modificados de alguna de las dos sedes en caso de que coincidan. Muchas gracias
Drive Corruption on DFS Root
Hi. The drive where one end of our DFS Namespaces exist has become corrupt. We are unable to solve with chkdsk as the drive is too big and it never finishes. I was planning on creating a new drive (everything is virtual) on the server and use robocopy with a /mir parameter to copy the data to the new location, stop DFS services, recreate the shares in the new location and then start DFS. However, I have read that I shouldn't 'pre-seed' with a /mir - https://docs.microsoft.com/en-us/windows-server/storage/dfs-replication/preseed-dfsr-with-robocopy Does that apply in my situation?? I'm not really pre-seeding the files, just copying the data to a new drive. Do I need to worry about file hashing?
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!!
