Re: Application caching

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
.

Relevant Pages

  • Re: Cant see local network printer from Remote Desktop session over VPN
    ... Within the remote session, I can ping the network address of the local printer, and can even connect to its administrative "web" page, but I can't print to it. ... If I understand you correctly, you're using remote desktop to connect to a terminal server at the other end, but you're trying to print directly from the terminal server to the network printer at your end. ...
    (microsoft.public.win2000.networking)
  • Re: Win32 Application development
    ... When you write to Winsta0, you are addressing session 0, which is ... Terminal Server, they will get a different session, with numbers ... > Windows application to work seamlessly with Windows terminal ... We want to make the GUI launch to the ...
    (microsoft.public.win2000.termserv.apps)
  • Re: while disconnecting its shows other user name - Terminal Serve
    ... And that they have a personal, unique profile? ... MCSE, CCEA, Microsoft MVP - Terminal Server ... To Log out the remote session, instead of Log off option the ... order to disconnect from their session. ...
    (microsoft.public.windows.terminal_services)
  • Re: printing from Terminal Server
    ... STABILITY of your terminal server. ... Matt is asking about printing from within one session to the ... clients out at different job sites. ...
    (microsoft.public.windows.terminal_services)
  • Re: Sessions "Time Out" but server still thinks active
    ... in the disconnected state, the user will be able to connect to the ... same session again and continue where she was before. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... something on the client machine itself). ...
    (microsoft.public.windows.terminal_services)