Terminal services and Domain controller

  • Thread starter Thread starter Steven Kok
  • Start date Start date
S

Steven Kok

Dear all,

Currently I have a domain controller running ADS, DHCP,
DNS, Terminal services and etc.

In the next few weeks I plan to build another server and
promote that server as the new "DC" and keep the old
server as the terminal server. The question is will that
method slows down the network as far as authenticating
users loggin into the network via local and remote
terminal access?

I appreciate any feedback or suggestion you may all may
have.

Regards, SK
 
No, I wouldn't think so, as long as the TS and the new DC have a
decent connection to each other.

So you're demoting the TS to be a member server, right? That's a
good idea from a security point of view.
You have to think a bit on what you want to do with your TS
Licensing Server. If you leave it on the present machine, it is
possible that the TS can't locate it any more, because it only
searches for a LS on Domain Controllers. If that happens, you can
try to hardcode the address of the LS into the registry of the TS
(even if they are on the same machine).
Your other option is to install TS Licensing on the new DC, where
it will be automatically discovered by the TS. You will have to
phone the Clearinghouse to get unused TS CALs reissued, then.

239107 - Establishing Preferred Windows 2000 Terminal Services
License Server
http://support.microsoft.com/?kbid=239107
 
Back
Top