Hi everyone. I posted this in the Package Development forum as well but someone mentioned that I may get more answers from this "Distribution" forum so I apologize for the double-post. Anyway, 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 Windows Updates are run at startup 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   [ - ] Hide Comments


Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity