Suppressing "Interact with desktop" property of service
-
We have a windows service which spawns a browser. To enable this operation,the service has been configured to "Interact with Desktop",runig as localsystem account. This does the desired,in most of the windows environments(2000,XP,2003). However,in some of the Windows 2003 boxes(not all),we find no visible browser instance. However,we have confirmed that the browser is indeed spawned under the 'SYSTEM' account through the task manager. This confirms that there is no problem in the execution of the executable as such. We have explicitly set the 'visible' property of the IE browser handle to 'true'. Is there some security setting/configuration that may potentially have been flagged to suppress the 'visibility' of the browser in these specific 2003 hosts? Any help on finding the source of this 'invisibility' of the browser will be much appreciated. Note:This happens only when the browser is spawned from a service.When spwned from command line(interactive),things work fine even in these particular hosts.
-
We have a windows service which spawns a browser. To enable this operation,the service has been configured to "Interact with Desktop",runig as localsystem account. This does the desired,in most of the windows environments(2000,XP,2003). However,in some of the Windows 2003 boxes(not all),we find no visible browser instance. However,we have confirmed that the browser is indeed spawned under the 'SYSTEM' account through the task manager. This confirms that there is no problem in the execution of the executable as such. We have explicitly set the 'visible' property of the IE browser handle to 'true'. Is there some security setting/configuration that may potentially have been flagged to suppress the 'visibility' of the browser in these specific 2003 hosts? Any help on finding the source of this 'invisibility' of the browser will be much appreciated. Note:This happens only when the browser is spawned from a service.When spwned from command line(interactive),things work fine even in these particular hosts.
We've found that it can take a system reboot before the interactivity of a newly-installed service starts working. In addition, this only works if you're logged in on the console session (session 0). For Remote Desktop/Terminal Services, run
mstsc /console. You should move away from this approach ASAP as Windows Vista and Windows Server 2008 have locked down session 0: you can no longer spawn processes that will appear on the user's desktop.DoEvents: Generating unexpected recursion since 1991
-
We've found that it can take a system reboot before the interactivity of a newly-installed service starts working. In addition, this only works if you're logged in on the console session (session 0). For Remote Desktop/Terminal Services, run
mstsc /console. You should move away from this approach ASAP as Windows Vista and Windows Server 2008 have locked down session 0: you can no longer spawn processes that will appear on the user's desktop.DoEvents: Generating unexpected recursion since 1991
Thanks. One clarification - what is the option to do a similar operation on widows vista/2008 server? If we impersonate a logged-on user,though we do not see the browser,it serves the purpose for us. Will impersonating a interactvie user for a process launched from a windows service continue to work in vista/2008? Or will that be clamped on too?