DC Issue

  • Thread starter Thread starter Network Administrator for Imperial Companies Ltd.
  • Start date Start date
N

Network Administrator for Imperial Companies Ltd.

We are running Small Business Server 2003 as our main DC,
but we decided that using terminal server for our remote
users on the main server was creating too much of a
burdan so we decided to buy another server just for
Terminal Services. Our problem is that when we ran the
DCPROMO.exe we only copied the existing AD to the new
terminal Server. We really wanted to create a child
domain (Main domain is imperial.local, child was supposed
to be terminal.imperial.local). How can we preserve the
exiting domain imperial.local and create the child domain?

Thanks for your help in advance.

Peter D'Aiuto
CIO
Imperial Companies Ltd.
 
Network said:
We are running Small Business Server 2003 as our main DC,
but we decided that using terminal server for our remote
users on the main server was creating too much of a
burdan so we decided to buy another server just for
Terminal Services. Our problem is that when we ran the
DCPROMO.exe we only copied the existing AD to the new
terminal Server. We really wanted to create a child
domain (Main domain is imperial.local, child was supposed
to be terminal.imperial.local). How can we preserve the
exiting domain imperial.local and create the child domain?
Click to expand...

Why not just make it a member server running terminal services? It will run
much better. Based on the information given there is no reason to have a
child domain.

--
Regards,

Michael Holzemer
No email replies please - reply in newsgroup

Learn script faster by searching here
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/scriptcenter/default.asp
 
Correct...unless this is something new to SBS2003 ( which I would strongly,
strongly, strongly doubt! ).

The reason for this is that you can not create any trusts in a SBS
environment. Furthermore, you may have additional DCs in the environment.
You may also have additional member servers in the environment.

I would suggest that you set up a simply WIN2000 Member Server and then
install the Terminal Services on that. Consider using Citrix on top of that
for a more pleasant user experience. If possible, I would avoid installing
Terminal Services on a Domain Controller ( key words being, if possible ).

HTH,

Cary
 
Back
Top