Re: Adding terminal server
- From: "kj" <kj@xxxxxxxxxxx>
- Date: Wed, 6 Jun 2007 16:48:16 -0700
Les Connor [SBS MVP] wrote:
Hi Al,
Inline ...
"Al Williams" <donotreplydirect@xxxxxxxxxxxxxxxx> wrote in message
news:ut4r$xIqHHA.4364@xxxxxxxxxxxxxxxxxxxxxxx
I'm adding a new Windows 2003 terminal server box to my SBS2003 R1
SP1 environment. I've read all the whitepapers, setup a test TS
server, but still have a few questions:
1) Is it OK if the new server runs an R2 version if our SBS is still
R1? Or do I just skip the installation of the 2nd "R2" CD? (I did
this for my tests and all is fine)
SBS R2 isn't WS R2, they're different products completely. You could
not do WS R2 on the TS box, or run ADPREP from WS R2 on the SBS box.
(but wait for a more qualified answer on this one, as I've not
personally done this).
Yes, you can upgrade the forest schema to version 31 (W2003R2) using the
SBS2003 server (actually you have to use the schema master so in the case of
an SBS2003 Forest you must use the SBS server).
But, only the Schema is upgraded. SBS 2003 R2 doesn't contain the bits that
use the schema version 31 upgrades (DFS-R, Unix, etc), so no new
functionality will be added to the SBS server, only other Windows 2003
Standard or Enterprise Servers.
2) There is one network printer (our colour photocopier running
"Fiery" PS drivers) that does not show up in my test TS sessions. I
gather this is because no driver exists for it on the new TS (or the
SBS for that matter as I just installed it locally on some clients).
Do I simply need to install the driver for it to work? (It does
have a Server 2003 driver so I'm fairly sure it is stable) Which
server do I install it on - the main SBS (which would trickle down
to the TS) or the TS box itself?
The printer should be installed on the SBS on a TCP/IP port, and
shared from there. That will take care of everything. The 2k3 driver
should be fine.
3) I know that TS should not be on the domain controller but can it
act as a backup domain controller for the SBS or is this a security
issue? The TS will not be used over the Internet, only on the LAN. If
it's OK how do I configure it to be a backup DC anyway - which
role do I add?
Believe it or not, you don't want/need another domain controller.
IMHO, it's added complexity especially if you need to recover your
SBS (which is why you think you need another DC). Backup and a
documented restore strategy of the SBS is the key, not addtional DC's.
4) One of my users has a local FAX modem/printer on his XP box that
doesn't map to TS. I gather this local FAX will never work in TS so
my only choice is to setup the SBS Fax which should work over TS for
all users?
SBS Fax will work on the TS.
5) The TS will handle 10-15 users running a business line
application plus Office 2003. As I've read processing power is
premium for TS the box I've ordered has a Core2Duo E6600 (same as
the Xeon 3060) with 4GB. Sound OK?
You've got lots of horses there ;-).
This may be somewhat OT (there is an SBS in here...) but this group
usually gives the best info so I thought I'd give it a go. Thanks.
--
Allan Williams
--
/kj
.
- Follow-Ups:
- Re: Adding terminal server
- From: Al Williams
- Re: Adding terminal server
- References:
- Adding terminal server
- From: Al Williams
- Re: Adding terminal server
- From: Les Connor [SBS MVP]
- Adding terminal server
- Prev by Date: Re: Tracking email messages
- Next by Date: VPN with SBS 2003 (not R2) and DSL (Part Two)
- Previous by thread: Re: Adding terminal server
- Next by thread: Re: Adding terminal server
- Index(es):
Relevant Pages
|
