Our management wants the package to install whether or not the user is logged on and the user to be able to interact
Sent on the new Sprint Network from my Samsung Galaxy S®4. -------- Original message -------- From: Steve Whitcher Date:04/29/2015 4:24 PM (GMT-05:00) To: [email protected] Subject: Re: [mssms] Application Model and Use of ServiceUi.exe Why not just set the deployment to run when the user is not logged on? If no users are logged on, don't the dialogs asking to close certain programs become unnecessary? On Tue, Apr 28, 2015 at 12:29 PM, Boseman, Marcia H - Raleigh, NC <[email protected]<mailto:[email protected]>> wrote: Many of the applications that we will be deploying via SCCM 2012 display dialog windows informing users of an application that needs to be closed prior to running an installation and/or a dialog window informing users that the machine requires a reboot before or after completing an installation. In order for these dialogs to display when using the Application Model is to require the user to be logged on during the installation. Our preference when deploying applications that go to all workstations is to use the options to ‘Run as System’ and ‘Whether the user is logged on or not’. However, in SCCM 2012 the option to allow the user to interact with the installation is not available with this option combination. Therefore, users will not see any dialog windows that are part of the installation. We are starting to test using ServiceUi.exe. Has anyone had any success using ServiceUi.exe with the application model and would not mind sharing some of the command line options that you have used?
