DC/ GC placement

[derf238]

I’d like some input on dc/server role placement.
Company has two locations. Location A has 25 users location B has. 15. There is a point to point t1 between Loc A nd Loc B, and a T1 to the inter net from Loc A. Location B will not have a server. Location A will have a Win2003 Terminal Server, a Win2003 server for applications (including entire business management system used by all users all the time) and an Exchange 2003 server. All location B users will access applications, internet and email via Terminal Server.
Which server(s) should be DC, GC, DNS and other roles?
Server specs:
Exchange – dual processor, 2gb RAM, separate drive sets for OS and database
TS - dual processor, 2gb RAM
Application – single processor 1gb RAM

Second question – Exchange server –drive set 1 is mirror on array controller, drive set 2 is Raid 5. Which should have OS and which should have exchange databases?

I have reasons for various solutions on this, looking for some objective viewpoints.
Thanks in advance for your help

 

[tfg13]

I find that the hardware kind of matches the needs of the particular role of the server, but I also find that you could face some interesting problems. I, myself, would prefer to have a DC/GC on one server, then start dishing to my other servers from there. The TS wouldn't be a bad DC/GC, but, would you want people using the TS if it were a DC? Would you let someone at location A log directly onto it? Most wouldn't.
Straight from Microsoft:

"A simple method of redundancy and fault tolerance planning is to have a DNS server running on each domain controller. For each subnet, have two domain controllers running the DNS Server service and hosting Active Directory-integrated zones."

Well, I don't think it is a great idea to have the DC on the exchange server (a crash would make life "interesting") so in my opinion, that leaves one server to be the DC/GC, DNS. You could use one of the other servers for DHCP if you plan on using it....