Which terminal server implementation scheme is better to choose?

Question

Active Directory

There is a terminal server on Windows Server 2003 and there is an Active Directory domain controller based on Windows Server 2019. How best to make friends with them? What is the best way to combine them?
Scenario 1: Just bring Windows Server 2003 into an AD domain.
Scheme 2: Make Windows Server 2003 an additional domain controller in the same AD domain (as was the case with Windows Server 2012).
Scheme 3: Create an additional domain inside the AD domain tree and set up a proxy between them.
Scheme 4: Raise RDS services also on Windows Server 2019 and add a Windows Server 2003 farm to RDS by creating a RemoteApp collection for it.
Requires remote access to the terminal server with authorization in Active Directory.
Which scheme is better? What scheme would you suggest? How can we best implement everything?

Answer 1

Of course, scheme 1.
Scheme 2 cannot be implemented at all - the domain controller on server 2019 wants the minimum forest / domain level - Windows Server 2008R2.
Scheme 3 - why?
Scheme 4 - I'm not sure here, but I doubt that 2003 can be added to one farm from 2019.

Answer 2

Just enter AD as a normal working machine.
Further you add a role of terminals and in permissions it will already be possible to select users from AD. all.
but .. terminal for 2003, this is a separate kind of masochism! When in 2014 passed to 2008 the server-terminal is heaven and earth. What is worth only failures with printers on 2003 ..