I will be setting up a terminal server to allow for Access based
database to be run over vpn at tolerable speeds, but would like to draw on
the advice of the group for this implemenation if at all possible. I
really would appreciate any feedback that could help smooth the process.

Here is my scenario:

A sbs2k server w/50 client access licenses
a large database built on ms-access
15 local users
3 remote workers with potentially 5 remote workers in the near future.

My goal is to:

Install a separate Windows 2003 server that can act as a terminal server
allow remote users to use our existing vpn to connect to the terminal server
to run the access db.


My current questions are:

#1 I need to purchase win 2k3 server, but do I need to purchase CALs for
server access? I am of the understanding that a member server does not need
separate cals to be purchased for it as long as it is in the sbs2k domain.
Is this true, _and_ does this hold true with a win2k3 server on a sbs2k
domain being 2k3 is newer than the domain OS?

#2 What do I need to purchase for access licenses for TS? Do I use user
or device licenses? What critieria should I use to decide which method to
use?

#3 Is there a good walkthrough guide on setting up a terminal server?
Where can I get instructions to help me do this process properly?

#4 Where can I go to get hardware recomendations for a server for this
3-5 user terminal server?


What I do know:

I do not want to run terminal services on the sbs2k server - for
compatibility and hardware requirement reasons - I have already determined
this is an option I should not do.

Thanks so much in advanced for any wisdom as I go through this install. You
guys are great!

Sincerely,
Joe

Re: Setting up a terminal server. by Duncan

Duncan
Wed Jan 26 18:36:18 CST 2005

In article <eiyLuJABFHA.4072@TK2MSFTNGP10.phx.gbl>, nojunk@nojunk.com
says...
> I will be setting up a terminal server to allow for Access based
> database to be run over vpn at tolerable speeds, but would like to draw on
> the advice of the group for this implemenation if at all possible. I
> really would appreciate any feedback that could help smooth the process.
>
> Here is my scenario:
>
> A sbs2k server w/50 client access licenses
> a large database built on ms-access
> 15 local users
> 3 remote workers with potentially 5 remote workers in the near future.

IMO, this just won't work - with that number of uses - just *locally*.
I'd bet your network will be well and truly bogged with traffic. MS
Access (as I'm sure you know) is *not* a client/server database.

Use SQL Server!!! :)

--
Duncan

Re: Setting up a terminal server. by Phil

Phil
Thu Jan 27 13:08:15 CST 2005

In article <MPG.1c62feadd80451d4989784@msnews.microsoft.com>, Duncan McC
<hard@work.ok> writes
>In article <eiyLuJABFHA.4072@TK2MSFTNGP10.phx.gbl>, nojunk@nojunk.com
>says...
>> I will be setting up a terminal server to allow for Access based
>> database to be run over vpn at tolerable speeds, but would like to draw on
>> the advice of the group for this implemenation if at all possible. I
>> really would appreciate any feedback that could help smooth the process.
>>
>> Here is my scenario:
>>
>> A sbs2k server w/50 client access licenses
>> a large database built on ms-access
>> 15 local users
>> 3 remote workers with potentially 5 remote workers in the near future.
>
>IMO, this just won't work - with that number of uses - just *locally*.
>I'd bet your network will be well and truly bogged with traffic. MS
>Access (as I'm sure you know) is *not* a client/server database.
>
>Use SQL Server!!! :)
>

Could this be why a Citrix-based site I help with has some network
issues. - They use Sage Payroll, which uses an Access-style (Jet??)
back-end I believe?

Phil Partridge
philp@pebbleGRIT.demon.co.uk
Remove the grit to reply

Re: Setting up a terminal server. by M

M
Thu Jan 27 17:34:29 CST 2005

I used an Access application with a similar set-up 3 or 4 years ago.
Depending on how "active" the use is and how large the mdb file you may run
into corruption problems. Toward the end (before upgrading to sql) we had to
repair the mdb file at least once a day. If the mdb file is small and there
is not alot of activity you will be able to use it as you plan but beware,
you may have trouble.

A W2K3 TServer requires access licences for each user, W2K TServer includes
unlimited access licences for XPPro and W2K Clients. For this reason, I
installed W2K Server for our separate TServer.

The big thing with TServer is locking down and securing the box so that your
users don't acidentaly shut it down, delete system files, etc. This process
is somewhat confusing for people llike me that are new to Group Policy.
There is good step by step instructions at:

http://support.microsoft.com/?id=278295

http://support.microsoft.com/default.aspx?scid=kb;en-us;260370

Using various group policy settings you can prohibit chnages to the desktop,
set a standard strat menu, hide drives and much much more.

There are also programs available to help you lock down TServers:

http://www.tricerat.com/?page=desktop2k1

Do alot of reading beofre you move... and protect the TServer box. Without
the correct settings your users can basically trash the Server. You can
even set-up the TServer to only run a single app for select users and when
they close it they are logged off.

Best of luck...
MM






"Joe Letter" <nojunk@nojunk.com> wrote in message
news:eiyLuJABFHA.4072@TK2MSFTNGP10.phx.gbl...
> I will be setting up a terminal server to allow for Access based
> database to be run over vpn at tolerable speeds, but would like to draw on
> the advice of the group for this implemenation if at all possible. I
> really would appreciate any feedback that could help smooth the process.
>
> Here is my scenario:
>
> A sbs2k server w/50 client access licenses
> a large database built on ms-access
> 15 local users
> 3 remote workers with potentially 5 remote workers in the near future.
>
> My goal is to:
>
> Install a separate Windows 2003 server that can act as a terminal server
> allow remote users to use our existing vpn to connect to the terminal
server
> to run the access db.
>
>
> My current questions are:
>
> #1 I need to purchase win 2k3 server, but do I need to purchase CALs for
> server access? I am of the understanding that a member server does not
need
> separate cals to be purchased for it as long as it is in the sbs2k domain.
> Is this true, _and_ does this hold true with a win2k3 server on a sbs2k
> domain being 2k3 is newer than the domain OS?
>
> #2 What do I need to purchase for access licenses for TS? Do I use
user
> or device licenses? What critieria should I use to decide which method to
> use?
>
> #3 Is there a good walkthrough guide on setting up a terminal server?
> Where can I get instructions to help me do this process properly?
>
> #4 Where can I go to get hardware recomendations for a server for this
> 3-5 user terminal server?
>
>
> What I do know:
>
> I do not want to run terminal services on the sbs2k server - for
> compatibility and hardware requirement reasons - I have already determined
> this is an option I should not do.
>
> Thanks so much in advanced for any wisdom as I go through this install.
You
> guys are great!
>
> Sincerely,
> Joe
>
>
>
>
>
>



Re: Setting up a terminal server. by Joe

Joe
Fri Feb 04 15:09:43 CST 2005

Thanks for the very helpful information!

The database we are using that is designed in access is a
predesinged app for non-profit organizations to track the clients they
provide aid to. The product is in use by similar non-profit organizations
and so I feel somewhat confident that we won't experience any major
problems, and unfortunately we already have a vested interest ($) in the
product. I don't believe the company that designed and maintains the
database would not be willing to convert the app to a sql based app.

Thanks for the suggestion w/using TS2k, however we have very
inexpensive copies of TS2k3 available to us through a microsoft non-profit
donation program. With this program w2k ts in not available. So how does
licensing work with ts2k3?

Lastly.. Does anyone know how I should go about spec'ing a server
for this configuration?

Thanks again!
Joe Letter



"M.M." <nosend2me@hotmail.com> wrote in message
news:Ouv5MjMBFHA.1404@TK2MSFTNGP11.phx.gbl...
>I used an Access application with a similar set-up 3 or 4 years ago.
> Depending on how "active" the use is and how large the mdb file you may
> run
> into corruption problems. Toward the end (before upgrading to sql) we had
> to
> repair the mdb file at least once a day. If the mdb file is small and
> there
> is not alot of activity you will be able to use it as you plan but beware,
> you may have trouble.
>
> A W2K3 TServer requires access licences for each user, W2K TServer
> includes
> unlimited access licences for XPPro and W2K Clients. For this reason, I
> installed W2K Server for our separate TServer.
>
> The big thing with TServer is locking down and securing the box so that
> your
> users don't acidentaly shut it down, delete system files, etc. This
> process
> is somewhat confusing for people llike me that are new to Group Policy.
> There is good step by step instructions at:
>
> http://support.microsoft.com/?id=278295
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;260370
>
> Using various group policy settings you can prohibit chnages to the
> desktop,
> set a standard strat menu, hide drives and much much more.
>
> There are also programs available to help you lock down TServers:
>
> http://www.tricerat.com/?page=desktop2k1
>
> Do alot of reading beofre you move... and protect the TServer box. Without
> the correct settings your users can basically trash the Server. You can
> even set-up the TServer to only run a single app for select users and when
> they close it they are logged off.
>
> Best of luck...
> MM
>
>
>
>
>
>
> "Joe Letter" <nojunk@nojunk.com> wrote in message
> news:eiyLuJABFHA.4072@TK2MSFTNGP10.phx.gbl...
>> I will be setting up a terminal server to allow for Access based
>> database to be run over vpn at tolerable speeds, but would like to draw
>> on
>> the advice of the group for this implemenation if at all possible. I
>> really would appreciate any feedback that could help smooth the process.
>>
>> Here is my scenario:
>>
>> A sbs2k server w/50 client access licenses
>> a large database built on ms-access
>> 15 local users
>> 3 remote workers with potentially 5 remote workers in the near future.
>>
>> My goal is to:
>>
>> Install a separate Windows 2003 server that can act as a terminal server
>> allow remote users to use our existing vpn to connect to the terminal
> server
>> to run the access db.
>>
>>
>> My current questions are:
>>
>> #1 I need to purchase win 2k3 server, but do I need to purchase CALs
>> for
>> server access? I am of the understanding that a member server does not
> need
>> separate cals to be purchased for it as long as it is in the sbs2k
>> domain.
>> Is this true, _and_ does this hold true with a win2k3 server on a sbs2k
>> domain being 2k3 is newer than the domain OS?
>>
>> #2 What do I need to purchase for access licenses for TS? Do I use
> user
>> or device licenses? What critieria should I use to decide which method
>> to
>> use?
>>
>> #3 Is there a good walkthrough guide on setting up a terminal server?
>> Where can I get instructions to help me do this process properly?
>>
>> #4 Where can I go to get hardware recomendations for a server for this
>> 3-5 user terminal server?
>>
>>
>> What I do know:
>>
>> I do not want to run terminal services on the sbs2k server - for
>> compatibility and hardware requirement reasons - I have already
>> determined
>> this is an option I should not do.
>>
>> Thanks so much in advanced for any wisdom as I go through this install.
> You
>> guys are great!
>>
>> Sincerely,
>> Joe
>>
>>
>>
>>
>>
>>
>
>



Re: Setting up a terminal server. by M

M
Fri Feb 04 21:20:59 CST 2005

I believe that if you have W2K3 Server you can "downgrade" to W2K Server for
only the cost of media. someone else here may know the licensing cost
MM

"Joe Letter" <nojunk@nojunk.com> wrote in message
news:uvatq4vCFHA.3536@TK2MSFTNGP15.phx.gbl...
> Thanks for the very helpful information!
>
> The database we are using that is designed in access is a
> predesinged app for non-profit organizations to track the clients they
> provide aid to. The product is in use by similar non-profit organizations
> and so I feel somewhat confident that we won't experience any major
> problems, and unfortunately we already have a vested interest ($) in the
> product. I don't believe the company that designed and maintains the
> database would not be willing to convert the app to a sql based app.
>
> Thanks for the suggestion w/using TS2k, however we have very
> inexpensive copies of TS2k3 available to us through a microsoft non-profit
> donation program. With this program w2k ts in not available. So how
does
> licensing work with ts2k3?
>
> Lastly.. Does anyone know how I should go about spec'ing a server
> for this configuration?
>
> Thanks again!
> Joe Letter
>
>
>
> "M.M." <nosend2me@hotmail.com> wrote in message
> news:Ouv5MjMBFHA.1404@TK2MSFTNGP11.phx.gbl...
> >I used an Access application with a similar set-up 3 or 4 years ago.
> > Depending on how "active" the use is and how large the mdb file you may
> > run
> > into corruption problems. Toward the end (before upgrading to sql) we
had
> > to
> > repair the mdb file at least once a day. If the mdb file is small and
> > there
> > is not alot of activity you will be able to use it as you plan but
beware,
> > you may have trouble.
> >
> > A W2K3 TServer requires access licences for each user, W2K TServer
> > includes
> > unlimited access licences for XPPro and W2K Clients. For this reason, I
> > installed W2K Server for our separate TServer.
> >
> > The big thing with TServer is locking down and securing the box so that
> > your
> > users don't acidentaly shut it down, delete system files, etc. This
> > process
> > is somewhat confusing for people llike me that are new to Group Policy.
> > There is good step by step instructions at:
> >
> > http://support.microsoft.com/?id=278295
> >
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;260370
> >
> > Using various group policy settings you can prohibit chnages to the
> > desktop,
> > set a standard strat menu, hide drives and much much more.
> >
> > There are also programs available to help you lock down TServers:
> >
> > http://www.tricerat.com/?page=desktop2k1
> >
> > Do alot of reading beofre you move... and protect the TServer box.
Without
> > the correct settings your users can basically trash the Server. You can
> > even set-up the TServer to only run a single app for select users and
when
> > they close it they are logged off.
> >
> > Best of luck...
> > MM
> >
> >
> >
> >
> >
> >
> > "Joe Letter" <nojunk@nojunk.com> wrote in message
> > news:eiyLuJABFHA.4072@TK2MSFTNGP10.phx.gbl...
> >> I will be setting up a terminal server to allow for Access
based
> >> database to be run over vpn at tolerable speeds, but would like to draw
> >> on
> >> the advice of the group for this implemenation if at all possible. I
> >> really would appreciate any feedback that could help smooth the
process.
> >>
> >> Here is my scenario:
> >>
> >> A sbs2k server w/50 client access licenses
> >> a large database built on ms-access
> >> 15 local users
> >> 3 remote workers with potentially 5 remote workers in the near future.
> >>
> >> My goal is to:
> >>
> >> Install a separate Windows 2003 server that can act as a terminal
server
> >> allow remote users to use our existing vpn to connect to the terminal
> > server
> >> to run the access db.
> >>
> >>
> >> My current questions are:
> >>
> >> #1 I need to purchase win 2k3 server, but do I need to purchase CALs
> >> for
> >> server access? I am of the understanding that a member server does not
> > need
> >> separate cals to be purchased for it as long as it is in the sbs2k
> >> domain.
> >> Is this true, _and_ does this hold true with a win2k3 server on a sbs2k
> >> domain being 2k3 is newer than the domain OS?
> >>
> >> #2 What do I need to purchase for access licenses for TS? Do I use
> > user
> >> or device licenses? What critieria should I use to decide which method
> >> to
> >> use?
> >>
> >> #3 Is there a good walkthrough guide on setting up a terminal
server?
> >> Where can I get instructions to help me do this process properly?
> >>
> >> #4 Where can I go to get hardware recomendations for a server for
this
> >> 3-5 user terminal server?
> >>
> >>
> >> What I do know:
> >>
> >> I do not want to run terminal services on the sbs2k server - for
> >> compatibility and hardware requirement reasons - I have already
> >> determined
> >> this is an option I should not do.
> >>
> >> Thanks so much in advanced for any wisdom as I go through this install.
> > You
> >> guys are great!
> >>
> >> Sincerely,
> >> Joe
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
>
>