General discussion

Locked

Terminal Services with Exchange 2K

By dyano ·
We recently had a new server installed Win2000, we upgraded our exchange from version 5.0 to 2K, which is still causing minor irritations, but the big problem I have is that my boss use to connect to our system from his home office via an ISDN line and an MCK unit using Terminal Services. The Tech installing the new server first of all did not set up the Term Serv. in the initial install, and now they are also telling me that I can not have it running on the same server as exchange 2K. Is thisthe case? any suggestions? Also any tips on smoothing the E2K migration from 5.0, I believe they used the migration tool that was intended for 5.5 or above. We still have three pc's on the network that are being hung up for a few minutes while logging in to outlook(2000). One of the installers is suggesting we reload the operating systems on the pc's , but this is happening on an NT, a 98, and a 95 system, so I have trouble thinking the operating system is to blame.

This conversation is currently closed to new comments.

1 total post (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Terminal Services with Exchange 2K

by Steve Merrill In reply to Terminal Services with Ex ...

I can only answer 1 piece here.

A terminal server can be run on the same server as E2K, but it isn't a good idea. Terminal servers often use up a great deal of system resources, as does E2K. E2K ends up actually taking control of all the resources, then distributing them to programs if/when they need it, otherwise it uses everything. Unless you have a totally decked out computer, it's usually best to separate these 2 services.

Back to Windows Forum
1 total post (Page 1 of 1)  

Related Discussions

Related Forums