Unsolved
This post is more than 5 years old
79 Posts
0
1540
April 21st, 2011 00:00
The process's interface pop up in other sessions
AutoStart 5.4 build 195 + Windows Server 2008
The process is configured with "Allow to Windows Desktop", and the OS support multiple sessions.
Remote desktop to this server with user A and start up the process. It turns out that the process is started as it is green. But you can not find any process from the task manager even Show processed from all users.
Remote desktop to this server with another user B, but the process's Interface/GUI will pop up in this session.
I see that the interface should pop up on console session on Windows 2003(you can use mstsc /console to this). And on Windows 2008, the interface should pop up within the opening session.
Can anyone know why? For some servers the testing results are different from the above, the one opening and starting the process can see the GUI and dialog.
Thanks
yito1
262 Posts
0
April 21st, 2011 01:00
Hi,
User A doesn't interactively start the process.
User B interactively starts the process.
Is this recognition all right?
Is there difference in user A and user B?
EnvisionPlus
79 Posts
0
April 21st, 2011 01:00
Yes， User A starts the the process and later RDC with User B from another client, and the GUI pops up in User B's session -- Both sessions are active.
User A is one local user can User B is network domain user.
Thanks
EnvisionPlus
79 Posts
0
April 21st, 2011 02:00
Yes, on Windows 2003 the process GUI pop up in session 0.
yito1
262 Posts
0
April 21st, 2011 02:00
Hi,
As for session 0 of Windows2003 and Windows2008, the specification is different.
yito1
262 Posts
0
April 21st, 2011 02:00
Hi,
I was able to understand a phenomenon.
This problem might be a phenomenon related to Session 0.
In AutoStart, ASPoxy.exe executes the process of the interactive mode.
But, only one ASPoxy.exe is executed though plural number logins are done.
That is, the process might be executed at only first login user.
I think that this is caused by specifications change of Windows2008.
jschrade1
106 Posts
0
April 21st, 2011 06:00
All,
First let me say this is currently being investigated and tested. There are two current cases under invistigation.
However, Windows 2008 did change the rules for security (we think) reasons. When you boot a Windows 2008 node the initial service and applications run is Session 0 (zero). If somone then logs onto the machine with a Terminal session, they will be running in Session 1. Some things that are running in Session 1 may not be seen by Sesson 0. The reverse is also true. The above is also true of automated process starups. For example, if AutoStart starts a process, for example InternetExplorer and then someone opens a terminal session it may not see the INternetExplorer window open. If the new session opens another copy of InternetExplorer it may not appear on the screen either and may post a message saying it is already running.
Setting the application to interact with the Desktop does not seem to work the same as in Windows 2003.
This behavior is believed to be part of an effort by MS to keep one Session from having an affect on anything running in a second Session. In other words one user cannot see or do anything that is happening is another Session.
While we are not sure at this time what, if anything, we can do to explain and/or work around this behavior we are working on it.
jschrade1
106 Posts
0
April 21st, 2011 08:00
All,
For more information on this new MS developed session protection schema please refer to the following documentation:
http://msdn.microsoft.com/en-us/windows/hardware/gg463353.aspx
JS