Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I was wondering if I could use my old server as a terminal server for Terminal Services. I have a new server running Windows 2k3 SMB but I dont want to bog it down with terminal services. If I put my old server on the network can it be a stand alone terminal server and not interfere with the other server if I make sure DHCP is turned off? Should I demote it? What steps should I take? Thanx for any help.

Hi,
Have you got a domain that you want it joined to that's hosted on your new server?
If so, you shouldn't have a problem with that. Give it a static IP, point the DNS of the NIC in the server you want to install Terminal Services on and then join it to the domain.
Then add a bunch of file shares such as UserHome$ and stuff like that to map network drives to the SBS server for things like the users' home drive if you want to use roaming profiles etc.
If you want any more help, either PM me or email me at daniel.wright@adwebsuk.co.cc
Cheers,
Dan

Well, I have a local domain as of right now and its the same domain the old server was a member of already. The old server was here before me and the new server was installed before I got here also.

Is the new server a member of the domain on the old server?? If so, promote the new server to a domain controller and then demote the old server as a member server.

The old server has been sitting in a closet collecting dust for about 2 years now. Should I open active directory on the old server and check for the new servers name?

In that case I would presume that the domain you are running is only on the new server. In that case, backup any data off the old server that you want to keep and then rebuild with windows 2000 server, join to the domain and then install Terminal Services. If you're going to be deploying this for a high volume of users, I'd recomend investing in software such as Citrix XenApp (Formerly Presentation Server) or Citrix Access Essentials - simply because the colour quality on Windows 2K Terminal Services is crap.

Thanks for all your input. Wiping and reloading is a good idea. Its an older box so I hope it goes over well.
Only 5 ppl will be using the terminal for testing initially so Critix might be something for the future. My next biggest concern is how well the connection will be with 5 users on at once. I'm wondering how much lag they will experience.

Microprocessor type:
Intel® Pentium™ III microprocessors with a minimum internal operating frequency of 933 MHz and an external operating frequency of 133 MHz
Memory:
3 GB of
72-bit ECC PC-133 SDRAM, 2-to-1 interleavedWith Tons of Hard drive space

Should be ok for 5 concurrent users. Are they going to be running very demanding applications?

No, most of them run a MS Access application that is stored on the file server. They also might open a spreadsheet or word document from time to time.

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |