Windows 2003 Server - Domain Controller and Terminal Server - Loopback Processing - Bad Idea?

I have a Windows 2003 server with Terminal Services installed.  It is also a Domain controller.
There is another DC (part of this domain) in another location (users do not access).  This second server is really just for AD backup.  

First question - off the bat - is it a bad idea to have a DC that is also a TS - and why?
Will I experience any issues because it is a TS and a DC?

Second - I am thinking of applying Loopback processing to the Server.  
Because the server is part of the Domain Controllers OU - and therefore part of the Default Domain Controllers Policy - do I turn on GP Loopback Processing - in the Defaualt Domain Controllers Policy?
Or do I create a second policy and apply it to the Domain Controllers OU?
Or do I move the server out of the Domain Controllers OU to a new OU and then apply the policy that has the Loopback Processing enabled?  (I'm thinking no on this last one - as I do not want to lose any of the Default Domain Controllers Policy settings).
kstetAsked:
Who is Participating?
 
andrew_aj1Connect With a Mentor Commented:
It is not a good idea to install terminal services on a domain controller, but i have seen it done before. The following link provides a bit more information why:
http://technet.microsoft.com/en-us/library/cc758409.aspx
I have never done loopback processing of group policy, but this information should help:
http://support.microsoft.com/kb/231287
i hope this helps. Good luck.
0
 
andrew_aj1Commented:
kstet, can we get an update please.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.