Re: adding a terminal server

Definitely make sure your applications are TS compatible otherwise it
can be a big headache to get them all to work.

yes, you will need the applications residing on the terminal server.

Jeff Pitsch
Microsoft MVP - Terminal Services

On May 4, 9:44 am, Bazzar <Baz...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Thanks once again Jeff

I will read this book and look into the VM approach. I'm assuming the apps
will need to reside in the VM but I will read up and see what is required,
although any hints in this direction would be greatfully received. The old TS
box can remain as a backup box. I will contact the different apps vendors and
see what's the situation with each for TS. Office is simple enough to
reinstall. Some of the others not so simple.

cheers
Barry



"Jeff Pitsch" wrote:
SBS2003 can hold the licensing role but, as I already said, it cannot
be the terminal server.  You will have to move your applications to
the terminal server but this will depend on the application.  Some
applications can be run from a network drive but things like MS Office
cannot as they require registry entries, etc.

Exchange would stay on the SBS box definitely.  I'm assuming your
users are on the domain so you would not need any local users on the
TS.

If your SBS is on high end hardware and you have capacity to spare and
based on wha tyou said about limited usage, etc, i would make your
terminal server a VM.  That, to me at least based on what you've
posted, would seem the best way to leverage what you have.

As for articles, I would point you tohttp://www.brianmadden.com/books/default.aspx
and the FREE Windows 2003 terminanl services advanced architect
guide.  This is an excellent jumping off point.

Jeff Pitsch
Microsoft MVP - Terminal Services

On May 3, 9:12 pm, Bazzar <Baz...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Thanks Jeff
I have not used the TS box yet, only used the two builtin licenses in the
SBS2003 server. The TS box has never been used since someone set it up.
Trouble is all the apps are on the SBS box and nothing is on the TS box yet.
It is on the LAN but only used as one of the locations for placing backups of
the SBS box so far. Now the customer is growing I thought I should use the TS
box. From what I understand of TS the apps must be on the TS box but local
(in the office) users and all apps are currently on the SBS box. The SBS
server is current technology and large capacity. The TS box is old and would
be a backstep to run apps and all local users and remote users. It would at
least need larger drives and a RAID setup. Could upgrade the TS box I guess
but I am looking for assistance on the best solution given this hardware
arrangement.

Like, can TS issue the remote licenses thorugh the SBS server and not have
the apps and local users on the TS box? Then allow the remote users easy
access to user accounts and apps on the SBS box? Remote access does not have
to be fast, although better than VPN! Anything like that possible? From what
I read the virtual server idea is not the best solution but would it work OK
from your experience? Would it slow down the server much?

And then there is the issue of migrating all the apps and users to the TS
(virtual or real) rather than having to reinstall everything. Is that
possible and is it a straight forward task? I am guessing Exchange could stay
where it is on the SBS box.

Essentially I am asking do I really need to have the apps and local users on
the TS box or can they be accessed, maybe a little slower, from the SBS box?
Most work will be local and the remote users will only be a couple of days a
week generally. Would the Internet NIC need to be on the TS box and make the
TS box serve the Internet connection to the LAN? These and many more
questions... (just joking).

I have not had the experience of setting up a TS before but have read about
some severe limitations that seem pointless to me but they exist so I have to
know about them and any workarounds. Reading up about it is one thing,
getting practical knowledge from the experienced is another and is usually
far more valuable. Also are there any articles worth reading that deal with
this in a practical way?

Much appreciated Jeff
Barry

"Jeff Pitsch" wrote:
Unfortunatley SBS2003 cannot be a terminal server.  So your only real
option is to either continue to use the old box or get new hardware for
it or virtualize it like you suggested.

I'm curious, if you already have a terminal server why are you trying to
move it?  is it because the hardware is old and out of date?

Jeff Pitsch
Microsoft MVP - Terminal Services

Bazzar wrote:
I am running a server with SBS2003 with various apps and Exchange server.
This is the DNS/DHCP server too. No ISA. Two NICs, one for the Internet and
one for the LAN. There is a hardware firewall. It is a RAID1 system with a
separate backup HD and other features I prefer to keep with the apps serving.
Clients login normally to this box.

I have a separate older P4 box, single HD and lower performance and has
Windows Server 2003, two NICs. Currently remote logins have used the two TS
licenses on the SBS2003 box. The customer has grown and now needs more TS
licenses. They have a 5 license TS available and it was installed on the
second box previously.

I want to make these TS licenses available to the SBS2003 box. What is the
best/effective way to configure this? Creating a virtual server on the
SBS2003 box is probably not the best solution.

Would it be better to make the SBS2003 box the TS box as well since it has
all the apps/backups/etc etc and is the better performer by far! Then make
the second box the DHCP/DNS and get local clients to login to the SBS2003
box? I have never set up this type of situation before.

Or would it be possible to keep the old box as a TS but somehow connect
remote logins to the SBS2003 box to run the remote clients with the local
clients still logging direct to the SBS2003 box?

I need help on what is the best configuration to take advantage of the best
performance and information on how to do it. References to documents or MS KB
articles sometimes are articles that have little to do with this specific
question.

I appreciate any help offered.

Barry- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -

.

Relevant Pages

  • RE: Re: Remote connections
    ... the TSWeb client is a simple and ActiveX based terminal server ... management remote control programs ...
    (Focus-Microsoft)
  • Re: Witholding Licenses
    ... If the only thing you want is what was called "TS in Remote ... Administration mode" on W2K, ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: Newbie: Access as International solution?
    ... How does one set up a Terminal Server application? ... All copies of Win2K and Win2K3 Server support WTS out of the box. ... They come with two administrative remote logons enabled. ... What is a VPN connection? ...
    (comp.databases.ms-access)
  • Re: Logon to domain via TS server -- how to?
    ... Your last question was the key: I added Authenticated Users to the Remote ... Desktop Users group and that change allowed me to log in to the domain via ... server> Remote desktop users group>is Authenticated Users listed? ... terminal Server, and even less to logon locally to the Domain ...
    (microsoft.public.windows.terminal_services)
  • Re: Logon to domain via TS server -- how to?
    ... Your last question was the key: I added Authenticated Users to the Remote ... Desktop Users group and that change allowed me to log in to the domain via ... server> Remote desktop users group>is Authenticated Users listed? ... terminal Server, and even less to logon locally to the Domain ...
    (microsoft.public.windows.terminal_services)
Loading