| Robert1105 2005-05-02, 8:25 pm |
| I am curious if you were able to get this to work? We have a similar
situation where we have a TS 2003 Cluster running into a Server 2003
infrastructure. Our Access Database is Access 2000. There is a Tech Note
regarding needing to run the Terminal Services Transform on an Access 2000
database; however, this relates to a Server 2000 environment. I am not able
to find any information on what should be done in a Server 2003 environment.
I am courious abour what you were able to get working?
"kiln" wrote:
> Thanks, again very helpful. The network admin is very good but isn't
> tuned in to Access db names, so I'm checking out that part.
>
> The db backend will be used by both remote user via TS and local LAN
> folks. My first instinct was to put the backend on the TS machine, on
> the 2nd hdd, in order to reduce connections to it over the network (less
> oppty for corruption). The local users would still of course connect
> over the LAN. I think the network admin prefers keeping the backend on
> the other win2003 server, the one that hosts exchange and all of that.
> Is there any reason NOT to put the db backend on the TS server as far as
> your experience goes? Don't expect it'd have any apparent impact on
> responsiveness as I think the TS connection will invoke more lag than
> the speed of the connection to the backend.
>
> The home directory thing sounds great, I've read about it, and this does
> seem to solve some things.
>
> In article <x4Ltd.441692$Pl.83270@pd7tw1no>, fdd@s.com says...
>
|