Error licensing RDS 2022 Farm - 1068, 1069, 50280

Have an existing Server 2019 RDS Single Server Setup (Broker, Licensing, Gateway, and Host on same server) that was working just fine.

Upgrading to Server 2022 and splitting the roles. Server 1 has Broker, Gateway, and Licensing. Server 2 and 3 are just session hosts.

Installed Server 2022 licenses on the new Server 1, and have configured the Licensing Type and role using Server Manager > Remote Desktop Services. Licenses are Per User, and the licensing server is set to Server 1. Server 1 is in the Terminal Server License Server along with the 2019 RDS Single Server.

When I try to access either Server 2 or 3, I get the "The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license". If I run RD Licensing Diagnoser, it does not show Server 1 in the output. I see errors 1068, 1069, and 50280 in Event Viewer which all pertain to the trial expiring and not able to contact a license host.

If I create a GPO and assign it to Server 2 and 3 that specifies Server 1 as the licensing server and Per User as the license type, then RD Licensing Diagnoser shows there are no issues, and can see server 1 plus the 200 licenses. However it does not show any licenses issued.

If I try to RDP into Server 2 or 3, I still get the no licenses errors and still see 1068, 1069, and 50280.

The 2019 server was working fine before I added the new farm. It still allows connections, but it also does not show a license server in RD Licensing Diagnoser. I applied a different GPO to it for licensing to point it to its own licensing server, which helped, but now it just shows the server as being over provisioned for licensing.

I have followed a bunch of different articles trying to troubleshoot this. I have done:

1. The GPO as described above
2. Rebuilt the Licensing portion on Server 1 (Reissue License)
3. Tried updating the certificate keys (https://zcusa.951200.xyz/en-us/troubleshoot/windows-server/remote/cannot-connect-rds-no-license-server#refresh-the-x509-certificate-registry-keys)
4. Removed any GPOs having to do with RDS (I did have an SSO GPO, but it was not applied. I removed it completely just to ensure it was not applying)
5. Tried building a new server, Server 4, that was just licensing.

None of those worked. Any thoughts or directions?

Thanks!