J
J. Lutz
Here's the scenario I've got. We had a Windows NT 4.0
domain with Windows 2000 Terminal Services. We went the
upgrade path to Windows Server 2003 for our DCs, which
puts the forest into the Interim mode (no Win2K DCs
allowed). I still have my Win2K Terminal Servers. Terminal
services licensing (which was on one of the terminal
servers since they were in an NT 4.0 domain originally) is
now throwing errors that there is an Active Directory
domain available, thus I need to move my terminal services
licensing server to a DC. However, all my DCs are Win2K3.
How would I be able to install a Windows 2000 terminal
services licensing server in this scenario? It appears
that my choices are one of the following:
1)Bring up a Win2K DC in its own forest, join the Win2K
terminal servers to the Win2K domain, establish an
explicit trust between the Win2K and Win2K3 domains so
that my win2K3 domain users can access the Win2K-laden
terminal servers.
2)Manually change the forest/domain functional level
(which I am sure is not supported), install a Win2K DC
into the Win2K3 domain, install the Win2K Terminal Server
Licensing Service.
Does anyone know how I can make this work without having
to establish a new domain/forest/trust or breaking
supported configurations?
Thanks,
J. Lutz
domain with Windows 2000 Terminal Services. We went the
upgrade path to Windows Server 2003 for our DCs, which
puts the forest into the Interim mode (no Win2K DCs
allowed). I still have my Win2K Terminal Servers. Terminal
services licensing (which was on one of the terminal
servers since they were in an NT 4.0 domain originally) is
now throwing errors that there is an Active Directory
domain available, thus I need to move my terminal services
licensing server to a DC. However, all my DCs are Win2K3.
How would I be able to install a Windows 2000 terminal
services licensing server in this scenario? It appears
that my choices are one of the following:
1)Bring up a Win2K DC in its own forest, join the Win2K
terminal servers to the Win2K domain, establish an
explicit trust between the Win2K and Win2K3 domains so
that my win2K3 domain users can access the Win2K-laden
terminal servers.
2)Manually change the forest/domain functional level
(which I am sure is not supported), install a Win2K DC
into the Win2K3 domain, install the Win2K Terminal Server
Licensing Service.
Does anyone know how I can make this work without having
to establish a new domain/forest/trust or breaking
supported configurations?
Thanks,
J. Lutz