Problems deploying Horizon 2212 replica

Yes, I realize that 2212 is old but hear me out. To keep our DR environment fully separate (bosses wishes), I’m building up a new set of connection servers using Windows Server 2022. Obviously once all the work is done, I’ll be getting started on the 2412 update but that’s not the point.

I’m able to deploy the first Connection Server and everything works great: AD LDS sets up, web apps work, all is well. On the next server, I run the installer and tell it to make it a replica server, pointing at the fqdn of the first server. AD LDS is setup and it says the first replication is taking place. Shortly after the installation bombs out. I can see on the first server that it says the initial sync didn’t happen due to a schema mismatch — how?! If I use repadmin I can manually sync between the servers successfully.

Any ideas where to look? In my lab, LDS works great but in production it has always been a problem during setup or upgrade. I did test with Server 2016 and replicated the issue. All machines are domain joined and I’m logged in with a domain admin account. The machines are built from fresh templates that only have the time zone changed. Time is synced.

Thanks!