Hi everyone. I'm sure this is a common problem for those who deploy applications and I have been unable to find an answer. I'm wondering if there is a way to delay the Windows startup so that when deploying an application at startup using SCCM or SMS, you can keep a user from opening programs that could cause the installation to fail. For example, we have software that we regularly deploy to our entire company that requires that all Office applications be closed in order for the installation to complete successfully. It would be nice if I could prevent users from getting the chance to open an Office app before the installation finishes. We can't rely on the user to be patient and wait for the install to complete and alot of times, the installation is silent so the user doesnt even know something is being installed. I'd like to find a way to delay the startup similar to when an app gets installed at startup by GPO and Windows displays the "Please wait while your computer is updated" message (or something to that effect) after the user types in their username and password to log on to Windows. If anybody has any ideas, please let me know. I've written a program that will disable mouse/keyboard activity that I can use if needed but I'd rather not use that if I can find a better way. Thanks in advance!
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
may get more answers from the distribution forum.
Answered 09/26/2008 by: kiptek
Second Degree Green Belt

Please log in to comment
0
It would probably be simpler to educate your users but, given that engaging your head with the nearest wall is probably more productive, consider building a script which your installation mechansim can call. The script would copy the Office app shortcuts somewhere safe (to which the users have no access, of course) and replace them with ones which call another script, one which pops up a message advising them what's happening. When the install completes, the script (which will be monitoring the install progress) brings the original s/c back. Hideously complex and probably over-the-top but that's all I can think of off the top of my head right now.

EDIT:
Not quite true: why not deploy these apps by Group Policy? Hideously lengthy and fraught with pain (no logging available by default, for example) but it will do the job.
Answered 09/29/2008 by: VBScab
Red Belt

Please log in to comment
0
Why not just change the apps so that they check for running apps before they will install, and reiterate in a message that other apps need to be closed before the install will work, make it so the msi wont run with the apps/processes running. That does mean no slient installs, and the user could say 'no" to installing the app.
Or, maybe make the install "full screen". They can still get to the start menu, but hey, if they are that deperate then they probably dont need any new apps or a computer that works.
Answered 09/30/2008 by: reds4eva
Second Degree Blue Belt

Please log in to comment
0
Yep... we once built this really irritating flashing image that kept coming to the front & flashing (&closing outlook if you did not heed the warning to close it in 120s), & after about 30 secs, most users gave up on trying to defeat the deployment & usually stepped away from their machines... Of course, having a manager with good sense of humor went a long way in accomplishing this task [8D]
Answered 09/30/2008 by: kiptek
Second Degree Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity