Calling card and GPO

ErikSolem

Hi,

 

I've created a software installation via GPO to deploy to my users, and over all it worked pretty good.

But on some of the users a pop up window that is saying "Interactive Services Detection" appears and in an environment with users that aren't IT-technicians it isn't that good  

 

I did some google on it and what I understand it wasn't the best idea to disable it...

 

Can I do something else to solve this issue?

 

Anon106368

So window you are seeing, the interactive service detection, is windows telling you that a process running from a system level account is trying to open a window (or more technically is trying to run a windows message pump).

 

What this means in non-nerd speak is that something is running at system level (not being run interactively by a logged in user) and it is trying to show some type of UI. This has not been allowed for a while now, im pretty sure windows put the kaibosh on desktop interaction from system processes in xp sp3, and its definitately not allowed in any OS since. If you are using GPO to publish the MSI installer and running that msi, this would be the case.

 

The log me in calling card installer basically just does what it wants. Even when you specify a force-quiet install ( /qb command line switch ), it still displays msgbox in certain situations. If there is an active LogMeIn session, for example, it will pop open a msgbox asking if you want to close the session. Unfortunately, this msgbox shows up on the windows session for process thats running the installer - not on the other (active) logmein process. So if you are running the .msi as a localsystem, you will never see the popup, and will have to kill the installer or wait for windows installer to time out. Since a program is trying to show a window from a process run as localsystem, in this example, you get your 'interactive service detection' warning.

 

Basically the logmein installer needs to be fixed to honor the silent command line switches, I've called a few times about it and left messages regarding this issue and other similarly 'advanced' bundling scenarios and havent heard much back. We bundle and automatically deploy logmein with our software, and we include the manually updated calling card installer with each version we publish through our auto-update services and this (and other issues) have bitten us.