Megaben
asked on
Adding a W2k server to an SBS2003 domain
After replacing a failed 2000 server with an SBS 2003 server, I find that you can no longer use terminal services on SBS2003. The only solution seems to be to rebuild the 2000 server (replace failed drives) and join it to the domain as a secondary server of some sort. (to act as the TS gateway)
My question is; Can I do the initial 2000 server build offsite, and then take the server onsite and add it to the domain, or do I need it physically connected to the domain when the install is going on?
TIA,
Ben
My question is; Can I do the initial 2000 server build offsite, and then take the server onsite and add it to the domain, or do I need it physically connected to the domain when the install is going on?
TIA,
Ben
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The workgroup option was part of the setup process, so ignore that bit. Adding to the domain should also be obvious when I get to site. I guess the next problem will be licensing, but as 2k allows 90 days before the license needs installing I should have time to get it all working first. I guess it all depends on whether anything else needs to be configured on the 2000 server in relation to its role in the domain. I will point the router to its ip address for terminal services ports, and hope!
After you add the TS server to the domain, add the TS License service to the TS box. Then add TS cals (for the number of people who will use this TS server) to the license server (I would put this in per user mode)
ASKER
Adding the computer to the domain was no problem, but it wouldn't let me set up any users without adding active directory. Added AD as a backup domain controller, and it all worked fine except that users could not logon to the server with the error "the local policy of this machine does not allow you to logon locally" (or something very similar. examination of the Group Policy objects on both the SBS server and the 2k server did not have an "allow users to logon locally" option, so had no choice but to run dcpromo and demote the 2k server tobe a member server. users can now logon from within the network - haven't yet had the chance to try from outside but hopefully when I figure which ports to redirect for Terminal Services that should be OK - providing it doesn't interfere (share ports with) Outlook Web Access...
On the subject of TS cals, I have the original eOpen license confirmation from Microsoft printed out, but no sign of the license key itself. presumably with enough digging about on Microsoft sites I should be able to fins a way to re-aquire this, however I believe that as all the workstations are XP pro, and the TS server is W2k, they shouldn't requre an extra license....
I will post extra questions if I get stuck on this, although any suggestions here would be welcome and might help someone else in the future.
Many thanks,
Ben
On the subject of TS cals, I have the original eOpen license confirmation from Microsoft printed out, but no sign of the license key itself. presumably with enough digging about on Microsoft sites I should be able to fins a way to re-aquire this, however I believe that as all the workstations are XP pro, and the TS server is W2k, they shouldn't requre an extra license....
I will post extra questions if I get stuck on this, although any suggestions here would be welcome and might help someone else in the future.
Many thanks,
Ben
TS port is TCP 3389. It doesn't share a port with Exchange...OWA.
-later
-later
ASKER