Re: TS on domain controller
- From: Hank Arnold <rasilon@xxxxxxx>
- Date: Thu, 05 Oct 2006 04:10:36 -0400
As everyone else has said... Don't do it..... Frankly, your almost better off with a single DC... Definitely don't make the Exchange server a DC...
A DC doesn't have to be very high end hardware. The only "want" I would make is to have RAID 1 for the boot drive. Other than that, you don't need much memory or hard drive space. Buy two low end servers and make them DCs. Move all the FSMOs and anything else running go the current DC and DCPROMO It. *THEN* add TS and your application(s)....
If the customer whines about the cost, you can take a decent workstation and make it the second DC..... I've done that with good success...
Regards,
Hank Arnold
Jetze Mellema wrote:
Microsoft does not advice to install Terminal Services on a domain controller, according to this quote:.
"Plan to install Terminal Server on a standalone server, not on a domain controller. When installed on a domain controller, Terminal Server performance is affected because of the additional memory, network traffic, and processor time required to perform the tasks of a domain controller in a domain."
At this customer of us we want to enable TS on a domain controller because the only alternative is making an Exchange server domain controller. The server is a brand new box, dual Xeon 3.4 GHz with 5 GB. The amount of users is low, not more than 30 and we plan to install a second domain controller. The network is also upgraded to gigabit.
So, that's plenty of processorpower, bandwith and memory. Any advice?
- References:
- TS on domain controller
- From: Jetze Mellema
- TS on domain controller
- Prev by Date: Re: Confused about CALs
- Next by Date: Quickbooks pro 2003 on Windows Standard 2003 Terminal server -hope this helps
- Previous by thread: Re: TS on domain controller
- Next by thread: is there any regular expression tool for vs2005? from hkhellhkhell@hotmail.com
- Index(es):
Relevant Pages
|
Loading
