avoid interactive service desktop but need to launch application from service on vista & windows 7
-
request all to help me for the following issue... 1.As a part of the requirements in my application there will be a windows service running 24/7. 2.this windows service will launch a windows application(GUI) to take user input.. The above application worked fine till windows XP... but on windows vista & windows 7 before launching application from windows service an "interactive Service Desktop" pop-up is launched automically with options "view my app" and "ask me later" by clicking on "view my app"...my application GUI popup is launched....otherwise it is not launched... How to avoid the intermediate popup i.e.,"interactive service desktop"? Please help me..
-
request all to help me for the following issue... 1.As a part of the requirements in my application there will be a windows service running 24/7. 2.this windows service will launch a windows application(GUI) to take user input.. The above application worked fine till windows XP... but on windows vista & windows 7 before launching application from windows service an "interactive Service Desktop" pop-up is launched automically with options "view my app" and "ask me later" by clicking on "view my app"...my application GUI popup is launched....otherwise it is not launched... How to avoid the intermediate popup i.e.,"interactive service desktop"? Please help me..
The problem is that your service is running in an elevated security context, while the user's desktop is not. Putting a window on the user's desktop exposes the service (running elevated) to interaction with the user's programs (non-elevated). That's why Vista and Win7 put service displays on a separate desktop, and ask the user to switch to it. Note that having interactive services is strongly discouraged, the current implementation is a compatibility measure. If you want to display stuff on the workstation, your service can do the following: 1) use WTSSendmessage for simple dialog boxes. 2) Create a new process from the service (with CreateProcessAsUser). Use the credentials of the currently logged on user (note that there may be more than one user: fast user switching may be active)