Windows 10: Active Directory Replication Status Tool ADREPLSTATUS has expired, 2022-07-01

The Active Directory Replication Status Tool ADREPLSTATUS expired on July 1, 2022 and is no longer functional. I understand from past posts that this happens periodically and Microsoft needs to publish an updated version of the tool with a newer expiration date. I cannot find any way to reach someone to let them know this has expired so I'm posting it here. TechNet page for the tool can be found here: https://social.technet.microsoft.com/wiki/contents/articles/12707.active-directory-replication-status-tool-adreplstatus-resources-page.aspx Thank you.

:)

 

Active Directory replication error

I recently was hit by ransomeware on a Windows 2k8 domain controller that held my FSMO roles. I restored an image of this server from a backup I had made using Windows backup. Then using NTDSUTIL I seized the Naming Master, PDC , RID Master, Schema Master Now
the active directory will not sync between my 2 DCs. I get an Active directory replication error -2146893022 the target principle is incorrect.

Can someone send me in the right direction for a solution ?

Thank You

 

January 2022 Cumulative Updates break Active Directory Users and Computers

2022-01 Cumulative Updates for Windows 10 causes an error when changing from our Parent domain to our Child domain. We receive this error: "Active Directory Domain Services: the domain could not be found because: the user name or password is incorrect" We found that if we remove the 2022-01 cumulative updates and reboot that the issue is resolved. This is happening on Windows 10 20H1, 20H2, 21H1, 21H2, and Windows 11. Is there another way we can resolve this without having to remove the Jan 2022 cumulative updates?

 

DFS-R can be used between Windows 2008r2 and windows 2022 directly or would require an intermediary version of Windows server to get to 2022

1. Research if DFS-R can be used between Windows 2008r2 and windows 2022 directly or would require an intermediary version of Windows server to get to 2022
   
   1. The idea is to replicate the disks live and change the DFS pointers the day we move to 2022.
      
   2. The downtime allowed on FS08-01 (the source) is almost 0 so going with Robocopy would be an alternative method requiring some downtime.
      
   3. With DFS-R I am thinking to use the replication to maintain HA between 2 or more fileserver instead of using an MS cluster.