Thanks for the information. From: [email protected] [mailto:[email protected]] On Behalf Of Sherry Kissinger Sent: Tuesday, April 28, 2015 1:51 PM To: [email protected] Subject: Re: [mssms] Application Model and Use of ServiceUi.exe
I recommend https://psappdeploytoolkit.codeplex.com/ instead of using serviceui.exe + a batch file; but I did setup demo's internally of both methods. and quite honestly, different lines of business have chosen to use one over the other and vice versa. So both "work". I recommend you setup a demo of both as well. for serviceui demo, in the source folder for the application is, for example, 4 files. File #1: serviceui.exe File #2: SomeExeWeAreInstalling File #3: WhateverIsUsedtoPopUpANotificationtoTheEndUser.exe File #4: Install.bat Install.bat something like this inside it: >>C:\Windows\temp\stdout.log 2>&1 ( .\ServiceUI.exe -process:explorer.exe WhateverIsUsedtoPopUpANotificationtoTheEnduser.exe .\SomeExeWeAreInstalling.exe /S ) exit /B %errorlevel% Personally, I recommend forgetting serviceui. the app deploy toolkit is really a much better method to do everything you need to do. I think the only reason a certain line of business internally don't use it... is because the main tech is familiar with batch files... and Powershell uh... scares him. the old fuddy duddy. On Tuesday, April 28, 2015 12:31 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?
