Re: Application caching
- From: "Jeff Pitsch" <jeff@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 11 Jul 2008 11:12:38 -0400
No this is standard and if you really think of the consequences of changing
an executable while being used you'll realize this is for the better.
Remember, just because something is in memory doesn't mean it's not be ing
used off the disk or locked. You also have to realize that making changes
to a program in the middle of the day is NOT normal by any stretch. You
always make changes on a scheduled basis. Also due to shared memory of
windows, just because an executable has changed doesn't mean it gets
reloaded. The exeuctable is already in memory, why should it reload the
entire thing again?
Can you imagine upgrading Office while users are using the software? What a
disaster that would be.
Jeff Pitsch
Microsoft MVP - Terminal Services
"Toni Van Remortel" <toni.van.remortel@xxxxxxxxxxxxxx> wrote in message
news:ghKdk.157661$8H5.84843@xxxxxxxxxxxxxxxx
I would expect such a behavior for every user session, but not for all
users
logged in at the same time.
In correct multi-user environments, every user has it's copy of the
program
cached in memory, but it is unlikely that when the user closes the
application and start it again, that the OS wouldn't read it again from
disk (specially when it has changed).
So now we are stuck for program updates. Terminal Server users have to
collectively log out of their sessions before they can use the new
software
version.
I don't think that is 'standard OS behavior'. That is a serious bug.
--
Regards,
Toni Van Remortel
Jeff Pitsch wrote:
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
- References:
- Application caching
- From: Toni Van Remortel
- Re: Application caching
- From: Jeff Pitsch
- Re: Application caching
- From: Toni Van Remortel
- Application caching
- Prev by Date: Re: Urgent Problem: Authentication Error
- Next by Date: Re: Publicating a TS Farm in TS Web Access 2008
- Previous by thread: Re: Application caching
- Next by thread: Re: Application caching
- Index(es):
Relevant Pages
|
