Windows 7 XP to Win7 migration of a large real-time service with several user windows - help?

[kevinwaite]

A large real-time service (KGW) with several user windows (one graphical under Java) is not compatible with session 0 screen output being removed (Session 0 Isolation) in Win7 (and Vista).

Under XP the first user to logon would be assigned to session 0, and would inherit KGW’s status windows and interactivity.

Under XP KGW’s status windows (up to four) would be managed and updated with or without a user being logged on. And the first user logging on would get access to KGW’s windows as part of session 0 being used for the first user logging on.

In Win7 this just does not work the same. The KGW service is required to start when the computer is booted (no user needed), furthermore, the KGW service requires to regularly update up to 4 windows, 3 are text and could be cashed, the 4[SUP]th[/SUP] is the graphics window as created and updated via a Java virtual machine, this is not really cashable.

One idea is to have a default user defined and have the KGW service AutoLogOn this KGW user, and start a KGW process under this user. This implies the adoption of a specific KGW user who would be the only user having access and interactivity to the KGW process windows.

Is it possible for a Win7 user process to share or transfer a window to another logged on user?

Is it possible for a Win7 for a window to be transfered from session 1 to session 2?


Thank you in advance,
Sincerely,
Kevin Waite

 

[ChatGPT]

It seems like you are facing compatibility issues with a large real-time service (KGW) on Windows 7, particularly related to Session 0 isolation. Here's a breakdown of your queries and suggestions:

Compatibility Issue and Proposed Solution:​

• Issue: In Windows XP, the first user to log on would be assigned to Session 0, inheriting KGW's status windows and interactivity. However, this behavior changes in Windows 7 and Vista due to Session 0 isolation.
• Proposed Solution:
  • Initiate the KGW service when the computer boots without needing a user to be logged in.
  • Have a default user defined and set up AutoLogon for this user to operate as the KGW user, ensuring only this user has access to and can interact with the KGW process windows.

    Queries Raised:​

    1. Sharing or Transferring Windows Between Users in Win7:
    []Question 1: Is it possible for a Windows 7 user process to share or transfer a window to another logged-on user?
    1. Transferring a Window Between Sessions in Win7:
    []Question 2: Is it possible for a window to be transferred from Session 1 to Session 2 in Windows 7?

    Answers to Queries:​

    1. Sharing/Transferring Windows Between Users in Win7:
    []In standard Windows environments, user processes operate within their respective user contexts, making direct sharing or transfer of windows between users challenging. Each user process is isolated and confined within its user session. []Windows APIs and mechanisms limit direct window transfer between different user sessions due to security and isolation reasons. []However, third-party tools or custom software solutions might offer ways to manage interactivity or sharing between user sessions. Still, these methods can be complex and may pose security risks if not implemented correctly.
    1. Transferring Windows Between Sessions in Win7:
    []In Windows 7, moving windows between different sessions (like from Session 1 to Session 2) is not directly supported by the operating system. []Windows restricts direct window manipulation across different sessions to maintain security boundaries and prevent unauthorized access. []Session 0 Isolation enhances security but limits interactions across sessions.
  • Tools like Remote Desktop and specialized applications may enable controlled interaction between sessions, but direct window transfer as described may not be feasible within the standard Windows operating environment. Regarding your proposed solution, setting up a dedicated user for the KGW service with AutoLogon could be a viable workaround to ensure consistent access and interactivity for the KGW process within the constraints of Windows 7's Session 0 isolation. Additional customized software solutions may be required for specific functionalities like window sharing between users or sessions. If you need further assistance or clarification on specific aspects, feel free to ask!