Remote Window Station Prelaunch for Client-Free Sessions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional client-server prelaunch solutions depend on native client software installed on user endpoints, which light clients lack, preventing them from supporting prelaunch capabilities.
Innovation Solution
A prelaunch manager determines primary and secondary window stations remotely across a computer network, enabling prelaunch without endpoint dependency, allowing for nested sessions and fast user switching among different user identities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional client-server prelaunch is used with native client software installed on user endpoints, then prelaunch capability is achieved, but device complexity and endpoint dependency increase
Solution Approach 1:
The patent extracts the prelaunch capability from the endpoint client and relocates it to the server-side session manager. The session manager now performs window station prelaunch operations independently, eliminating the need for native client software on endpoints. This extraction resolves the contradiction by maintaining prelaunch capability while removing endpoint dependency and associated device complexity.
Solution Approach 2:
The session manager acts as an intermediary between the endpoint and window stations, performing prelaunch operations on behalf of endpoints. This intermediary approach allows light clients without native prelaunch software to still benefit from prelaunch capabilities, as the session manager mediates the prelaunch process server-side, thus resolving the contradiction between versatility and device complexity.
2Loss of time
If window stations are prelaunched early, then user wait time is reduced, but computing resource consumption increases
Solution Approach 1:
The session manager performs preliminary window station prelaunch actions based on predicted user login events or scheduling policies. By initiating window station creation and configuration before actual user login, the system reduces user wait time while allowing resources to be allocated in advance during off-peak periods, thus balancing the contradiction between time savings and resource consumption.
Solution Approach 2:
The prelaunch mechanism implements dynamic resource allocation by adjusting prelaunch behavior based on system load, user patterns, and resource availability. The session manager can dynamically decide when and how to prelaunch window stations, scaling resource consumption according to actual needs, thus resolving the contradiction between reducing wait time and managing resource usage efficiently.
Data Source
AI summary
Prior to a user login event associated with a first user identity, a prelaunch manager determines an occurrence of a primary window prelaunch trigger condition. A primary window station is prelaunched for a first user identity at a user endpoint. Based on an occurrence of a user login event associated with the first user identity, a user session associated with the first user identity is connected with the primary window station. In some examples, the user endpoint is located remotely across a computer network from the prelaunch manager and does not require local capacity for prelaunch. In some examples, further window stations are prelaunched, nested within the primary window station, with the nested window station being associated with user identity having different privileges than the first user identity.