Re: Application caching
- From: "Jeff Pitsch" <jeff@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 11 Jul 2008 10:08:47 -0400
This is standard OS behaviour. I'm not sure what your expecting. Windows
has to make sure that the application is "locked" in case it needs to read
from it again. If the application is changed in the middle of user using it
the implications include crashing the user's application and potentially
session and potentially worse.
Jeff Pitsch
Microsoft MVP - Terminal Services
"Toni Van Remortel" <toni.van.remortel@xxxxxxxxxxxxxx> wrote in message
news:RGGdk.121644$jB5.81602@xxxxxxxxxxxxxxxx
Hi all,
We have set up Server 2008 with Terminal Server for about 10 users.
All those users use the same application (a single exe from a network
share).
The drawback is that when we update the application (in-house
development),
we need to ask all TS users to log out before they can use the new
version.
Somehow, the exe is cached by the TS server as long as someone has it
open,
and TS does not check if the exe on the network share is updated.
Is there a way to disable this behavior? When we update the application, a
simple close and reopen should open the new version, not the old cached
version.
Thanks a lot.
--
Regards,
Toni Van Remortel
.
- Follow-Ups:
- Re: Application caching
- From: Toni Van Remortel
- Re: Application caching
- From: jolteroli
- Re: Application caching
- References:
- Application caching
- From: Toni Van Remortel
- Application caching
- Prev by Date: Re: Licensing error on XP Embedded SP2 thin clients
- Next by Date: Re: profiles
- Previous by thread: Application caching
- Next by thread: Re: Application caching
- Index(es):
Relevant Pages
|