>There's STILL a problem - odds are there's someone in the module you're trying to update (would be true for many of MY apps, anyway). I have used one solution, and heard of another one that give the best of both worlds...
>
>My solution: by redefining the target of your application shortcut icon, you can direct any NEW users to a different EXE (my_app_new.exe) - without them even knowing about it! I do this with Novell's ZenWorks, but WinNT has such management capabilities as well. Next day, everyone who logged in is now using you new application! To clean up, copy your update to the original filename and point things back to the original filename (my_app.exe, if you wish). Let it simmer one more day, and delete the temporary (my_app_new.exe) update.

But doesn't this technique still have the same problems? Users must still logoff/logon if you're going to deliver the new path (via SMS, for example). The problem was that users were not logging off, as well as not even exiting the application itself...I know you can alter settings remotely, too, while a user is logged on, but only manually that I've seen, which defeats the purpose...are you saying you can alter desktop/startup path while users are logged on in an automatic multi-user mode?