Hi Everyone!

I'm looking for a little advice on an office configuration requiring remote
access. Terminal server was one of the suggested applications to resolve
the issue.

In the current setup we have 5 networked computers in an office environment,
4 of which use an application, installed on each PC, that shares a common
Access database stored on a 5th PC. Two or three users are accessing the
database at the same time.

Three remote offices have recently been established, each of which needs
access to this same database in real time for entering data.

The questions are:

!) Is Terminal Server the best way to access the now remote database?

2) Is there some better way to do this?

3) What will we need, both hardware and software, if we choose to use
Terminal Server?

4) Is Terminal Server easy to setup and maintain or is it problematic?

5) Any caveats?

6) Would something such as WebEx and GoToMyPC be better?

Thanks in advance for all your suggestions, etc.

Bob wrote:
> Hi Everyone!
>
> I'm looking for a little advice on an office configuration requiring remote
> access. Terminal server was one of the suggested applications to resolve
> the issue.
>
> In the current setup we have 5 networked computers in an office environment,
> 4 of which use an application, installed on each PC, that shares a common
> Access database stored on a 5th PC. Two or three users are accessing the
> database at the same time.
>
> Three remote offices have recently been established, each of which needs
> access to this same database in real time for entering data.
>
> The questions are:
>
> !) Is Terminal Server the best way to access the now remote database?
>
> 2) Is there some better way to do this?
>
> 3) What will we need, both hardware and software, if we choose to use
> Terminal Server?
>
> 4) Is Terminal Server easy to setup and maintain or is it problematic?
>
> 5) Any caveats?
>
> 6) Would something such as WebEx and GoToMyPC be better?

The first thing to realize is that you are going to run into the
Concurrent Inbound Connection limitations on that "5th PC". You didn't
say what operating system it is running, but both XP Home and Pro have
limitations which will cause you difficulties. The limitations are on
*connections*, not *computers*. Each computer can - and often does -
make more than one connection.

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

concurrent connections:

5 for XP Home
10 for XP Pro/Tablet/MCE
49 for SBS 2000
74 for SBS 2003
Unlimited for full Server O/Ses

Since you are running a Windows program on the pseudo-server (the "5th
PC"), you will need to replace the XP it is running with a real MS
server operating system. Terminal Services is only available on a server
operating system anyway. Since it will be difficult to run TS without
having a domain and Active Directory, the workstations must be running
XP Pro.

Here is a link to an MS TechNet article "A Guide to Deploying Terminal
Services":

http://www.microsoft.com/technet/tec...minalServices/

It is very well written and should answer your questions about TS.

You should contact the tech support for the specific application you are
using. They will know the best way to set up remote access to their
program and have guides for doing so.


Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

Bob <bob1030********.com> wrote:
> Hi Everyone!
>
> I'm looking for a little advice on an office configuration requiring
> remote access. Terminal server was one of the suggested applications
> to resolve the issue.
>
> In the current setup we have 5 networked computers in an office
> environment, 4 of which use an application, installed on each PC,
> that shares a common Access database stored on a 5th PC. Two or
> three users are accessing the database at the same time.
>
> Three remote offices have recently been established, each of which
> needs access to this same database in real time for entering data.
>
> The questions are:
>
> !) Is Terminal Server the best way to access the now remote database?

Well - Access as a front end is a great thing, but Access as a *back* end is
not. You may want to look into SQL.
>
> 2) Is there some better way to do this?
>
> 3) What will we need, both hardware and software, if we choose to use
> Terminal Server?

Hardware with enough firepower to manage this (post in
m.p.windows.terminal_services for help with this and many other things)
W2003 server
Terminal Services CALs
>
> 4) Is Terminal Server easy to setup and maintain or is it problematic?

Not tough at all, and in fact, easier than maintaining a bunch of individual
workstation configs - but as mentioned, Access really isn't the way to go if
you can swing better options.


>
> 5) Any caveats?
>
> 6) Would something such as WebEx and GoToMyPC be better?

That'll work too, probably - but only one person can use the workstation at
a time, so if you don't have spare/idle workstations for the remote users to
access, this won't be a good plan.
>
> Thanks in advance for all your suggestions, etc.

Thanks for the advice. I read the article and although it is well written
it still seems complicated to someone with no MS Server experience. Maybe a
hands-on experience will change that. One point that concerns me is the
use of domain. Will this work if you are only using a workgroup? This is
still a small operation so they are using a standard company name workgroup.

I'm starting to see some major modifications to the overall network setup
ahead. While this is not bad from my perspective, I see major resistence
from the powers that be, seeing this as excessive compared to what they are
used to.

Any more thoughts appreciated.




"Malke" <notreally@invalid.invalid> wrote in message
news:eAI1RXDrHHA.4836@TK2MSFTNGP05.phx.gbl...
> Bob wrote:
>> Hi Everyone!
>>
>> I'm looking for a little advice on an office configuration requiring
>> remote
>> access. Terminal server was one of the suggested applications to resolve
>> the issue.
>>
>> In the current setup we have 5 networked computers in an office
>> environment,
>> 4 of which use an application, installed on each PC, that shares a common
>> Access database stored on a 5th PC. Two or three users are accessing the
>> database at the same time.
>>
>> Three remote offices have recently been established, each of which needs
>> access to this same database in real time for entering data.
>>
>> The questions are:
>>
>> !) Is Terminal Server the best way to access the now remote database?
>>
>> 2) Is there some better way to do this?
>>
>> 3) What will we need, both hardware and software, if we choose to use
>> Terminal Server?
>>
>> 4) Is Terminal Server easy to setup and maintain or is it problematic?
>>
>> 5) Any caveats?
>>
>> 6) Would something such as WebEx and GoToMyPC be better?
>
> The first thing to realize is that you are going to run into the
> Concurrent Inbound Connection limitations on that "5th PC". You didn't say
> what operating system it is running, but both XP Home and Pro have
> limitations which will cause you difficulties. The limitations are on
> *connections*, not *computers*. Each computer can - and often does - make
> more than one connection.
>
> http://support.microsoft.com/?id=314882
>
> concurrent connections:
>
> 5 for XP Home
> 10 for XP Pro/Tablet/MCE
> 49 for SBS 2000
> 74 for SBS 2003
> Unlimited for full Server O/Ses
>
> Since you are running a Windows program on the pseudo-server (the "5th
> PC"), you will need to replace the XP it is running with a real MS server
> operating system. Terminal Services is only available on a server
> operating system anyway. Since it will be difficult to run TS without
> having a domain and Active Directory, the workstations must be running XP
> Pro.
>
> Here is a link to an MS TechNet article "A Guide to Deploying Terminal
> Services":
>
> http://www.microsoft.com/technet/tec...minalServices/
>
> It is very well written and should answer your questions about TS.
>
> You should contact the tech support for the specific application you are
> using. They will know the best way to set up remote access to their
> program and have guides for doing so.
>
>
> Malke
> --
> Elephant Boy Computers
> www.elephantboycomputers.com
> "Don't Panic!"
> MS-MVP Windows - Shell/User

Bob wrote:
> Thanks for the advice. I read the article and although it is well written
> it still seems complicated to someone with no MS Server experience. Maybe a
> hands-on experience will change that. One point that concerns me is the
> use of domain. Will this work if you are only using a workgroup? This is
> still a small operation so they are using a standard company name workgroup.
>
> I'm starting to see some major modifications to the overall network setup
> ahead. While this is not bad from my perspective, I see major resistence
> from the powers that be, seeing this as excessive compared to what they are
> used to.
>
> Any more thoughts appreciated.

In addition to the excellent advice you got from Lanwench, I'm going to
suggest that you have a qualified local professional come on-site to set
you up properly. This will not be someone from your local version of
BigStoreUSA/GeekSquad. Before you have the computer professional come
on-site, have all the information from your specific application's tech
support handly. The computer professional may need to speak to them.

A lot of niche software (industry-specific software) uses some form of
an Access database into which their program hooks. They may also use
some form of SQL Server, either as part of their software or installed
separately.

I understand that this isn't what you wanted to hear, but I feel I would
be doing you a disservice if I said, "oh sure, you can do this with a
Workgroup and you can learn as you go - no problem". This will probably
not be the case. If you were my client, or a prospective client, here's
what I would do:

1. Come on-site and do a survey of what machines/operating systems
you've got, your network, etc. I would also take a look at the
specialized software you're running and see what is required. I might
also contact that program's tech support to talk to them so I had a true
understanding of what was involved. While I can't answer for the
professionals in your area, I normally don't charge anything for this
preliminary work.

2. Then, based on what I found in #1, I would order the proper hardware
and software for you - server, workstations, SQL Server if required,
etc. - and then come in and set you up properly. This would include:

a. Making sure that all workstations are properly secured and running a
good (and current) antivirus.
b. Making sure that all extant workstations (if going to be retained)
are virus/malware-free and updated with Service Packs.
c. Making sure that there was a backup strategy and system included in
the setup.
d. Installing and configuring the specialized software and making sure
it worked, probably also being in contact with their tech support.

The above doesn't cover everything, naturally, but it should give you an
idea of what needs to be done. The payment to the computer professional
is a cost of doing business and trying to do this yourself in a
catch-as-catch-can manner will bring Tears Before Bedtime. You need to
make sure your network is secure, your people can do their jobs, and
that you can recover from a computer disaster quickly and efficiently.

I hope you have not taken my words amiss and have instead taken them in
the spirit they are meant - that I wish you the best success and that
the computing end of your business goes well. One thing to mention to
"the powers that be" is the cost of recovering all your data will be
much higher if you don't do this professionally if 1) your network is
not secured and it is compromised; or 2) you have a hard drive failure
without having a disaster strategy and backups.


Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

It's taken as offered and all good advice. I appreciate all advice when
it's given in this spirit.


"Malke" <notreally@invalid.invalid> wrote in message
news:elYiOoFrHHA.192@TK2MSFTNGP02.phx.gbl...
> Bob wrote:
>> Thanks for the advice. I read the article and although it is well
>> written it still seems complicated to someone with no MS Server
>> experience. Maybe a hands-on experience will change that. One point
>> that concerns me is the use of domain. Will this work if you are only
>> using a workgroup? This is still a small operation so they are using a
>> standard company name workgroup.
>>
>> I'm starting to see some major modifications to the overall network setup
>> ahead. While this is not bad from my perspective, I see major resistence
>> from the powers that be, seeing this as excessive compared to what they
>> are used to.
>>
>> Any more thoughts appreciated.
>
> In addition to the excellent advice you got from Lanwench, I'm going to
> suggest that you have a qualified local professional come on-site to set
> you up properly. This will not be someone from your local version of
> BigStoreUSA/GeekSquad. Before you have the computer professional come
> on-site, have all the information from your specific application's tech
> support handly. The computer professional may need to speak to them.
>
> A lot of niche software (industry-specific software) uses some form of an
> Access database into which their program hooks. They may also use some
> form of SQL Server, either as part of their software or installed
> separately.
>
> I understand that this isn't what you wanted to hear, but I feel I would
> be doing you a disservice if I said, "oh sure, you can do this with a
> Workgroup and you can learn as you go - no problem". This will probably
> not be the case. If you were my client, or a prospective client, here's
> what I would do:
>
> 1. Come on-site and do a survey of what machines/operating systems you've
> got, your network, etc. I would also take a look at the specialized
> software you're running and see what is required. I might also contact
> that program's tech support to talk to them so I had a true understanding
> of what was involved. While I can't answer for the professionals in your
> area, I normally don't charge anything for this preliminary work.
>
> 2. Then, based on what I found in #1, I would order the proper hardware
> and software for you - server, workstations, SQL Server if required,
> etc. - and then come in and set you up properly. This would include:
>
> a. Making sure that all workstations are properly secured and running a
> good (and current) antivirus.
> b. Making sure that all extant workstations (if going to be retained) are
> virus/malware-free and updated with Service Packs.
> c. Making sure that there was a backup strategy and system included in the
> setup.
> d. Installing and configuring the specialized software and making sure it
> worked, probably also being in contact with their tech support.
>
> The above doesn't cover everything, naturally, but it should give you an
> idea of what needs to be done. The payment to the computer professional is
> a cost of doing business and trying to do this yourself in a
> catch-as-catch-can manner will bring Tears Before Bedtime. You need to
> make sure your network is secure, your people can do their jobs, and that
> you can recover from a computer disaster quickly and efficiently.
>
> I hope you have not taken my words amiss and have instead taken them in
> the spirit they are meant - that I wish you the best success and that the
> computing end of your business goes well. One thing to mention to "the
> powers that be" is the cost of recovering all your data will be much
> higher if you don't do this professionally if 1) your network is not
> secured and it is compromised; or 2) you have a hard drive failure without
> having a disaster strategy and backups.
>
>
> Malke
> --
> Elephant Boy Computers
> www.elephantboycomputers.com
> "Don't Panic!"
> MS-MVP Windows - Shell/User

Thanks for your advice Lanwench. I agree with all that you've said. In
particular, I suggested the change to SQL so that is being considered.


"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmailatya hoo.com> wrote in message
news:u0lDpjDrHHA.3924@TK2MSFTNGP04.phx.gbl...
> Bob <bob1030********.com> wrote:
>> Hi Everyone!
>>
>> I'm looking for a little advice on an office configuration requiring
>> remote access. Terminal server was one of the suggested applications
>> to resolve the issue.
>>
>> In the current setup we have 5 networked computers in an office
>> environment, 4 of which use an application, installed on each PC,
>> that shares a common Access database stored on a 5th PC. Two or
>> three users are accessing the database at the same time.
>>
>> Three remote offices have recently been established, each of which
>> needs access to this same database in real time for entering data.
>>
>> The questions are:
>>
>> !) Is Terminal Server the best way to access the now remote database?
>
> Well - Access as a front end is a great thing, but Access as a *back* end
> is not. You may want to look into SQL.
>>
>> 2) Is there some better way to do this?
>>
>> 3) What will we need, both hardware and software, if we choose to use
>> Terminal Server?
>
> Hardware with enough firepower to manage this (post in
> m.p.windows.terminal_services for help with this and many other things)
> W2003 server
> Terminal Services CALs
>>
>> 4) Is Terminal Server easy to setup and maintain or is it problematic?
>
> Not tough at all, and in fact, easier than maintaining a bunch of
> individual workstation configs - but as mentioned, Access really isn't the
> way to go if you can swing better options.
>
>
>>
>> 5) Any caveats?
>>
>> 6) Would something such as WebEx and GoToMyPC be better?
>
> That'll work too, probably - but only one person can use the workstation
> at a time, so if you don't have spare/idle workstations for the remote
> users to access, this won't be a good plan.
>>
>> Thanks in advance for all your suggestions, etc.
>
>
>