Server Maintenance Mode with Isolated Admin Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Network administrators face challenges in troubleshooting and maintaining user applications hosted on enterprise networks, as existing methods do not distinguish between administrator and user connections, leading to restrictions that hinder maintenance and troubleshooting processes.
Innovation Solution
The integration of a process to remove servers from load balancing and publish extra user applications in an isolated directory accessible only to network administrators and selected users, allowing them to troubleshoot problematic applications or virtual desktops without disrupting user access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of repair
If the server operates in maintenance mode to allow network administrators to perform updates and troubleshooting, then maintenance capability is improved, but user access is blocked and administrators cannot log in either
Solution Approach 1:
The system segments user access and administrator access into separate pathways. When a server is in maintenance mode, regular users are load-balanced to other servers while administrators can still access the maintenance-mode server through a dedicated mechanism (Ctrl+Alt+Delete sequence), allowing both maintenance and user operations to proceed simultaneously without conflict
Solution Approach 2:
The Ctrl+Alt+Delete sequence acts as an intermediary mechanism that enables administrators to bypass the maintenance mode restriction. This intermediary input sequence triggers a special authentication pathway that allows administrator login even when the server is in maintenance mode, while regular user login attempts are still blocked
2Ease of operation
If network administrators modify the server's load balancer or remove servers from worker groups to access problematic servers, then administrator access is improved, but user access is disrupted and load balancing is affected
Solution Approach 1:
The system implements dynamic access control based on user role and input sequence. The server dynamically responds to different login attempts: regular users attempting to login during maintenance mode are redirected via load balancer, while administrators using the Ctrl+Alt+Delete sequence are granted direct access. This dynamic behavior allows administrator access without disrupting load balancing for regular users
3Ease of repair
If extra copies of user applications are published to specific servers for administrators and test users, then troubleshooting capability is improved, but system complexity and resource consumption increase
Solution Approach 1:
The system creates temporary duplicate instances of user applications specifically on servers placed in maintenance mode. These duplicate applications are made accessible only to administrators and test users through the special login mechanism, allowing them to troubleshoot and test fixes without affecting regular user access to the primary application instances. The duplicates are removed when maintenance is complete
Data Source
AI summary
The embodiments are directed to methods and systems for determining whether a server should be placed in maintenance mode. The methods and systems can create a user group comprising one or more client devices connected to one or more permanently installed applications or one or more virtual desktops hosted on the server. The methods and systems can create a temporary directory containing duplicates of the one or more applications or one or more virtual desktops that the one or more client devices are connected to. The methods and systems can disconnect the one or more client devices from the one or more permanent applications or virtual desktops, and connect the one or more user devices to the one or more duplicate applications or virtual desktops.