Re: What do I need to use Terminal Server?

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


"Malke" <notreally@xxxxxxxxxxxxxxx> wrote in message
news:elYiOoFrHHA.192@xxxxxxxxxxxxxxxxxxxxxxx
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


.

Relevant Pages

  • Re: XP home network issue
    ... It's good advice, Chuck. ... but here's all teh extra ... In 'View Network Computers', both machines can see the icon of the other. ...
    (microsoft.public.windowsxp.network_web)
  • Re: detect Inf or NaN
    ... You know they're IEEE functions because of the MODULE ... named thingos are excellent examples of proper naming practices. ... Excellent advice for languages like C where there are no module ...
    (comp.lang.fortran)
  • Re: Architecture Advice
    ... >> I'm going to be using SQL Server for a distributed ... >> application and I'd appreciate any advice on architecture. ... >> Simplest approach would be 2-tier client server and be done with it. ... it would be nice to be able to provide some data caching at the ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Wireless Network Key
    ... This is excessively bad advice, and you even tell why it is bad. ... wireless network works like that out of the box. ... I never said anything other than a shell script CAN be used. ... warn that it's a security risk and to lock it down tight. ...
    (Ubuntu)
  • Re: XP Home Networking Issue
    ... Thanks for the advice but I'm still not having any luck. ... XP_Home1 had a node type of 'Hybrid' ... Open the Network Connections folder. ... > Default Node Type for Microsoft Clients ...
    (microsoft.public.windowsxp.network_web)