Forum Discussion
Conflicting entries in dfsr schema preventing migration from frs to dfsr
Hello,
I’m experiencing a very similar issue and I’d like to know if the person who posted this managed to resolve it—and if so, how they resolved it—because I still haven’t found a solution. In my environment, I have 3 Domain Controllers: two running Server 2008 R2 and one running Server 2012 R2. The schema version is 88, but I cannot migrate from FRS to DFSR. When I run the command, I get the error: "Error: 87 Incorrect".
I also checked the log file located in C:\Windows\Debug and I'm seeing an error similar to the one shown in the screenshot I’ve attached.
I have not figured out a resolution. Do you also have cnf entries in the schema in adsi edit. The schema version in use in this domain is also a schema version 88 which corresponds to server 2019 version. I had managed to remediate the schema conflicting entries but still had the same results. Being that you are having the same issue I am beginning to wonder if once the schema is past a 2016 version if it makes changes to dfsr that prevents the migration. If you go into dfsr management and try to view replication groups or create a replication group do you also get a error about the schema not being extended or extended incorrectly?
Also I noticed in my paticular instance the DFSR entries get made for the dcs and it is failing at creating the entry for the DFSR subscription (it never populates even after 48 hours). It would be great if Microsoft would actually work on issues that affect businesses that run their products instead of leaving customers out in the cold while they focus all their efforts on AI copilot, but I guess that will require major customer boycotting of even using copilot and Microsofts ai product and a demand to support their products currently in production.