Non-DJI VM Profile Persistence via Automatic Disk Attachment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional technologies fail to effectively personalize non-persistent desktops for non-domain joined instance (non-DJI) virtual machines, as they lack group policy management and domain trust for authentication/authorization, leading to loss of user profile data upon session closure.
Innovation Solution
A system that automatically attaches a user profile disk to non-DJI virtual machines upon session start, allowing seamless per-user customization and decoupling user profiles from the operating system, enabling profile persistence and universal portability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If non-DJI virtual machines are used to maintain stateless benefits, then ease of operation and resource efficiency are improved, but user profile persistence and personalization capability deteriorate
Solution Approach 1:
The system segments the virtual machine into two distinct parts: the stateless VM instance and the separate user profile disk. The profile disk is detached from the VM lifecycle, allowing the VM to remain stateless while user profiles are independently stored and managed. This segmentation enables the VM to be rapidly provisioned and terminated without carrying over user data, while profiles persist separately in storage.
Solution Approach 2:
The system introduces an intermediary profile management service that acts as a mediator between the stateless VM and user profiles. This service handles profile attachment during VM startup, detachment during shutdown, and persistence in storage. The intermediary layer allows the VM to maintain its stateless nature while providing users with persistent profile access through the mediation of this service.
2Adaptability or versatility
If user profiles are attached to non-DJI virtual machines, then user personalization is improved, but device complexity increases
Solution Approach 1:
The profile management system implements self-service mechanisms where the profile attachment and detachment processes are automatically triggered by VM lifecycle events. When a VM starts, the system automatically detects the associated user profile and attaches it. When the VM shuts down, the profile is automatically detached and saved. This automation eliminates the need for manual profile management and reduces operational complexity despite the added functionality.
Solution Approach 2:
The system changes the state parameters of the profile disk dynamically based on VM lifecycle events. The profile disk transitions between attached and detached states automatically, with its mount point and accessibility parameters changing according to whether the VM is running or stopped. This parameter-based management simplifies the complexity by using state transitions rather than complex manual configuration.
3Ease of operation
If automatic profile attachment is implemented, then user login convenience is improved, but authentication reliability may worsen
Solution Approach 1:
The system performs preliminary authentication actions before the user actually logs in to the VM. The profile attachment process includes pre-validation of user credentials and authentication tokens during the VM startup phase, before the user session begins. This preliminary authentication ensures security is verified in advance, maintaining reliability while allowing seamless user login without additional authentication steps.
Data Source
AI summary
An illustrative embodiment disclosed herein is an apparatus including a processor having programmed instructions to receive a request for a computing device associated with a user to remotely access a session on an operating system of a non-domain joined instance (non-DJI) virtual machine (VM). The processor includes programmed instructions to, automatically and responsive to the request, cause a server to attach, to the VM, a disk for storing a profile of the user, assign an account of the operating system to the user, reset a password for the account, login the user to the session on the VM using the account and the password, mount, on the VM, the profile, and cause a connection to be established between the computing device and the VM.