Windows 10: Replication error 6408

I am getting error 6408 on my domain controllers. I have tried shutting of dfsr and re-syncing everything following the common posts about replication errors. Everything completes with no error but I keep getting 6408 when i restart the service. In DFS Management I have an invalid item showing up from an old domain controller that I have no idea how to get rid of. It shows the member name in the details but it's Member column is <unknown> and no local path.ERROR:The DFS Replication service failed to initialize replicated folder C:\Windows\SYSVOL because the service detected that one of i

:)

 

UnattendedJoin error: failed to find the domain data (0x6e)

Thanks for the suggestion! I don't want to add a domain account, as this is a generic unattended install that will be used for all company machines. Do you think it's possible that the computer would join the domain if, instead of using UnattendedJoin in specialize, I used your steps but left out the specific account?

The other thing I was thinking was to use a generic account to allow the domain join during the specialize step. I added a machine password in the UnattendedJoin component, and instead of getting the error listed above, I got an authentication error, which makes me think I could probably do a secure join instead of the unsecure join.

Thoughts?

 

Error: No work available to process

Hmm. Either it's put out errors and WCG is limiting the work units available, or the project list may not be set to supply other WU when one runs out. (if the problem lies here and not on your end)

On the options to your left, if you go into Results Status, select the computer from Device Name and then look through results see if either they were returned late, errors or any other kind of issue that would stop the servers supplying WU from that perspective.

If there are no errors then it's maybe down to your project list. So selecting Device Manager from the left menu and then clicking on the profile assigned to that computer and make sure that it's assigned to receive WU for other projects if they run out.

At least those steps will rule out problems from the WCG end.

 

Window Server 2003 can't AD replication

Hi Support Team

I have server install Windows Server 2003. It's old and hardware unstable. I need to change to new Server. I try AD replication to new Server but after completed step.

I can't turn down old Server. When turn down old Server AD users and computer or another feature about AD can't use. I need your suggest.