meperera
asked on
How to install service to bypass Vista Interactive Services Detection Service
Hi experts,
I have a Interactive service that I install on my client's PCs. This works perfectly on Windows XP and Windows 2003 server machines. My problem is every time that service is started on a Windows Vista machine I get the Vista Interactive Services Detection Service dialog and my users find it annoying. Is there a way to get around this by changing the parameters for the service in the Services panel or in the registry.
Cheers
I have a Interactive service that I install on my client's PCs. This works perfectly on Windows XP and Windows 2003 server machines. My problem is every time that service is started on a Windows Vista machine I get the Vista Interactive Services Detection Service dialog and my users find it annoying. Is there a way to get around this by changing the parameters for the service in the Services panel or in the registry.
Cheers
ASKER
Hi cybrexus,
I have checked that and the startup type is set to manual
I have checked that and the startup type is set to manual
ok try change it to Disable then and see if it bothers you again
ASKER
Hi Cyberexus,
When that service is disabled my service doesn't intercat with the desktop at all
When that service is disabled my service doesn't intercat with the desktop at all
try to run the interactive detection service from a different account - in service Properties set to run as for example System account
also try disabling UAC
also try disabling UAC
ASKER
still no luck sorry
as I understand in Vista the services and the user are in different sessions, unlike in previous versions of windows. That's why it is "asking for permission" to display messages. Maybe try setting your application/service to run as System user..
ASKER
My service runs as a system user. It can also interact with the user if need be. but still a system user
Theres something interesting I've just read:
"The goal is to get the application running in the context of the logged in user(s). Therefore you need to run an app that runs in the user's context. The only easy way to do this is with a program that starts when the user logs in through the registry or the Startup group. This application should be used to periodically poll for another application and ensure that it restarts. This completely eliminates security issues and the service isolation problem. Of course if the user terminates this helper app then there is nothing you can do about it (with a service or otherwise) but that is not a bad thing. However if you use the registry to start the helper app and you don't display any UIs then the user will likely be unaware of the helper application at all."
maybe there's a way you could implement something like that...
"The goal is to get the application running in the context of the logged in user(s). Therefore you need to run an app that runs in the user's context. The only easy way to do this is with a program that starts when the user logs in through the registry or the Startup group. This application should be used to periodically poll for another application and ensure that it restarts. This completely eliminates security issues and the service isolation problem. Of course if the user terminates this helper app then there is nothing you can do about it (with a service or otherwise) but that is not a bad thing. However if you use the registry to start the helper app and you don't display any UIs then the user will likely be unaware of the helper application at all."
maybe there's a way you could implement something like that...
Hi,
Has your vista computer SP1 installed?
Has your vista computer SP1 installed?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
then set startup type in Properties to Manual
you shouldn't get anymore messages