Building/Using Terminal Server?

  • Thread starter Thread starter (PeteCresswell)
  • Start date Start date
P

(PeteCresswell)

Guest
I've got a half-dozen MS Access applications that currently run
across a corporate LAN.

Dunno if it's all the streaming video that people are watching on
their desktops or what, but response time on all my apps has
slowly degraded over the months until at this time I would call
it totally unacceptable to people who need to get their work
done.

I spent some time optimizing code here and there and did manage
to pick up a little time. But we're talking 5% here, 3%
there... and I'm looking for 50% plus.

In another NG somebody alluded to setting up a really fast box
with Windows XP Server on it, having his MS Access apps live
there, and having the people who use them Remote Desktop to the
box.

From what says, it could be a real, live silver bullet.

But I've never done anything like that before.

- Get a PC.... a *Fast* PC with plenty memory

- Install Windows XP Server...

- Install some sort of host so multiple people can RD to it

.....

But what then? Better choices than Remote Desktop? Maybe
something where the user still has an application-specific icon
on their desktop and clicking the icon does it all: RD to the
host, open up the app....?

Anybody been here?

More appropriate places to ask a question like this?

--
PeteCresswell
 
Re: Building/Using Terminal Server?

XP Server? Never heard of it. Are you sure you mean XP?

There is Windows Server 2003 (in many flavors), Windows Home Server (based
on WS2003), Windows Server 2008 (in many flavors), but no XP Server. XP is
NT5.1 but there is no server in the NT5.1 family.

"(PeteCresswell)" <x@y.Invalid> wrote in message
news:2q6iq3t5208en3ai5oueggl8gckj3ases7@4ax.com...
> I've got a half-dozen MS Access applications that currently run
> across a corporate LAN.
>
> Dunno if it's all the streaming video that people are watching on
> their desktops or what, but response time on all my apps has
> slowly degraded over the months until at this time I would call
> it totally unacceptable to people who need to get their work
> done.
>
> I spent some time optimizing code here and there and did manage
> to pick up a little time. But we're talking 5% here, 3%
> there... and I'm looking for 50% plus.
>
> In another NG somebody alluded to setting up a really fast box
> with Windows XP Server on it, having his MS Access apps live
> there, and having the people who use them Remote Desktop to the
> box.
>
> From what says, it could be a real, live silver bullet.
>
> But I've never done anything like that before.
>
> - Get a PC.... a *Fast* PC with plenty memory
>
> - Install Windows XP Server...
>
> - Install some sort of host so multiple people can RD to it
>
> ....
>
> But what then? Better choices than Remote Desktop? Maybe
> something where the user still has an application-specific icon
> on their desktop and clicking the icon does it all: RD to the
> host, open up the app....?
>
> Anybody been here?
>
> More appropriate places to ask a question like this?
>
> --
> PeteCresswell
 
Re: Building/Using Terminal Server?

Per Colin Barnhorst:
>There is Windows Server 2003 (in many flavors), Wind

Mea Culpa.

"Windows Server"....

But what now?
--
PeteCresswell
 
Back
Top