Re: Connecting ONE remote PC to SBS 2003
- From: "Gregg Hill" <bogus@xxxxxxxxxxx>
- Date: Tue, 28 Mar 2006 14:57:07 -0800
Using that license to do anything other than server administration violates
the EULA anyway. It is called "Remote Administration Mode" for a reason...so
that the server can be remotely administered via RDC.
you could set up a Win2000 server with TS and not need licenses if the
remote system is 2000 Pro or XP Pro. That makes it a cheaper solution than a
2003 TS.
TS licenses are for systems that can run TS, which SBS 2003 cannot do.
Gregg Hill
"NELVON" <NELVON@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4C6986FF-1084-415C-A348-C02C102884C7@xxxxxxxxxxxxxxxx
We're running 1 SBS 2003 server on our network of 20 users.
We have 1 and only 1 remote site with a PC, shared by 3 users, that we
would
like to connect into our accounts software on the SBS.
I have setup a VPN from this site and accessed the network drives
successfully.
I have also used Terminal services (remote desktop) to access the SBS
server
directly and ran the accounts software.
However, this is using 1 of the 2 licenses that come with SBS and they
only
allow for the Admin user to connect remotely using RDP.
Is there a way of locking down 1 of these licenses to deny access to the
admin functions on the server (only allowing access to the accounts
software)?
Could we purchase 1 additional TS license (per user) and deny access
through
group policy?
Or is it the case that we must purchase an additional server + server 2003
+
TS licenses to allow this 1 PC access to the software (an exspensive
solution!!)?
I would be grateful for any help or advice in avoiding emptying the MD's
wallet further.
Neil
.
- Prev by Date: Re: No desktop after login
- Next by Date: Re: Office 2003 Standard Edition, Windows 2003 Terminal Server
- Previous by thread: Re: No desktop after login
- Next by thread: Re: Connecting ONE remote PC to SBS 2003
- Index(es):
Relevant Pages
|
