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.exeFile #2: SomeExeWeAreInstallingFile #3:
WhateverIsUsedtoPopUpANotificationtoTheEndUser.exeFile #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]> wrote:
<!--#yiv0349473421 _filtered #yiv0349473421 {font-family:Calibri;panose-1:2
15 5 2 2 2 4 3 2 4;} _filtered #yiv0349473421 {font-family:Tahoma;panose-1:2 11
6 4 3 5 4 4 2 4;} _filtered #yiv0349473421 {font-family:Verdana;panose-1:2 11 6
4 3 5 4 4 2 4;}#yiv0349473421 #yiv0349473421 p.yiv0349473421MsoNormal,
#yiv0349473421 li.yiv0349473421MsoNormal, #yiv0349473421
div.yiv0349473421MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Times New
Roman", "serif";}#yiv0349473421 a:link, #yiv0349473421
span.yiv0349473421MsoHyperlink
{color:blue;text-decoration:underline;}#yiv0349473421 a:visited, #yiv0349473421
span.yiv0349473421MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv0349473421
p.yiv0349473421MsoAcetate, #yiv0349473421 li.yiv0349473421MsoAcetate,
#yiv0349473421 div.yiv0349473421MsoAcetate
{margin:0in;margin-bottom:.0001pt;font-size:8.0pt;font-family:"Tahoma",
"sans-serif";}#yiv0349473421 span.yiv0349473421BalloonTextChar
{font-family:"Tahoma", "sans-serif";}#yiv0349473421
span.yiv0349473421EmailStyle19 {font-family:"Calibri",
"sans-serif";color:#1F497D;}#yiv0349473421 .yiv0349473421MsoChpDefault
{font-size:10.0pt;} _filtered #yiv0349473421 {margin:1.0in 1.0in 1.0in
1.0in;}#yiv0349473421 div.yiv0349473421WordSection1 {}-->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?
