I'm pretty sure this isn't linked to 1511, what I'm using now.

 

Application with TS usage enabled ("also without being deployed.")

The command line says msiexec /i bla.msi /qb!

The type set to whether or not a user is logged with system context,
resulting in the application being able to install in a TS and through
software center, all normal.

 

There is no progress information from Windows installation during
installation in software center, as expected, but why is there one if I put
the same command in a cmd and use that for the command line instead?

I've just noticed that, switched all to use a batch and they all install
during OSD, not showing any dialog then of course, but show progress from
the windows installer when installed manually.

 

Additionally, when using setup.exe from all Office applications, even
without a batch, they also show the dialog (assuming the setup is configured
like that).

 

So, with software center, msiexec doesn't show anything, but a batch file
does, so does the setup.exe from all office apps.

I was under the impression that such an installation would never show any
interactivity because of the session it is running in.

 

What am I missing? Why the difference between a cmd and a direct call?

Was it always like that? Because I never noticed that.

 

-R

 

 



Reply via email to