Discussion Locked

Trusts for SBS2000 and Server 2003 std

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Company has 2 servers
Problem 1. SBS2000 = name.com.au, 2003 std server = name.local (obviously a problem) they need to be on the same domain any ideas of the best option?
Problem 2. SBS2000 has terminal services with licenses, std 2003 does not, want to us the SBS2000 as the TS connection as it is becoming old and if the users crash it it doesn't matter as the office will continue but can't get them to talk to each other.
Problem 3. std2003 does not have exchange and company will not pay for new exchange when the SBS2000 does have exchange how can I set it up.

4 replies

by andyjg247

Does your 2003 server have any current use? You could always wipe it and make it a secondary dc to the 2000 sbs.
Legally I am pretty sure you cannot put the exchange from sbs onto any other server as it would break the licencing agreement. They will have to live with the current sbs server if they don't want to upgrade. 2003 does have terminal services (in add/remove programs) but it would depend on what additional licences you have for the client connections side of things.
MS recommends that SBS2000 is not setup to use Terminal Services in Application mode which I seem to understand from your paragraph. This could be causeing some of your current problems.

by akalinowski

i agree w/ answer 1, legally, you cannot install SBS exchange on any other servers.
also, you cannot trust other domains if your using SBS

you'll have to either upgrade to full blown version of exchange and server for your DC name.com.au or dcpromo your name.local domain and take that down to a member server, and join it to the sbs 2000 domain as a member server.

This discussion is closed to new replies.