IP Library Granted Patent US 11,582,287
Granted Patent B2
US 11,582,287 · App. 17/295,794 · Granted Feb 14, 2023

Hidden desktop session for remote access

Inventors: Jake Morgan (Raleigh, NC); Max Booth (Raleigh, NC)
Assignee: ConnectWise, LLC
H04L67/025G06F3/038G06F9/452H04L41/082H04L41/22H04L41/5074H04L67/56G06F2203/0383
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,582,287
App. No.
17/295,794
Granted
Feb 14, 2023
Kind
B2
Abstract

Systems and methods of the present disclosure are directed to providing remote access capabilities in information technology infrastructure. In particular, systems and methods of the present disclosure can provide remotely access capabilities to facilitate the management, configuration, or maintenance of information technology infrastructure.

Claims (51)

1. A method of remotely managing computing devices, comprising:

identifying, by a remote management server, a first remote computing device according to a first support ticket;

establishing, by the remote management server, one or more connections communicatively coupling the first remote computing device to a host computing device;

hijacking, by the remote management server via the one or more established connections, a system session executed on the first remote computing device;

transitioning, by the remote management server via the one or more established connections, the hijacked system session from a non-interactive state to an interactive state;

generating, by the remote management server, a hidden desktop within the hijacked system session to be displayed on a display device of the host computing device;

identifying, by the remote management server, one or more instructions inputted through the hidden desktop by the host computing device to update a configuration of the first remote computing device; and

terminating, by the remote management server responsive to a command from the host computing device, the hijacked system session by transitioning the hijacked system session from the interactive state to the non-interactive state.

2. The method of claim 1 , further comprising:

closing, by the remote management server, the first support ticket in response to the one or more instructions being executed, in a hidden manner, in the hijacked system session of the first remote computing device.

3. The method of claim 1 , further comprising:

receiving, by the remote management server from a database storing the first support ticket associated with the first remote computing device, responsive to the first remote computing device generating the first support ticket;

receiving, by the remote management server from the database storing a second support ticket associated with either the first remote computing device or a second remote computing device, the second support ticket responsive to the first or second remote computing device generating the second support ticket;

determining, by the remote management server communicating with the database, a first priority of the first support ticket based on a first status of the first support ticket;

determining, by the remote management server communicating with the database, a second priority of a second support ticket based on a second status of the second support ticket; and

determining that the first priority is higher than the second priority to identify the first remote computing device.

4. The method of claim 1 , wherein transitioning the hijacked system session from the non-interactive state to the interactive state further comprises:

adding, by the remote management server via the one or more established connections, a registry key to a registry of the first remote computing device to cause the hijacked system session to transition from the non-interactive state to the interactive state.

5. The method of claim 1 , wherein the hidden desktop includes at least one of an interactive power shell and an interactive command prompt.

6. The method of claim 1 , further comprising:

communicating, by the remote management server, with one or more web applications to provide one or more interactive user interfaces on the hidden desktop.

7. The method of claim 1 , further comprising:

composing, by the remote management server, one or more windows stations within the hijacked system session to generate the hidden desktop.

8. The method of claim 1 , further comprising:

transmitting, by the remote management server via the one or more established connections, the one or more instructions to the first remote computing device to be executed, in a hidden manner, to close the first support ticket.

9. The method of claim 1 , wherein the one or more instructions are inputted through the hidden desktop by one or more input devices communicatively coupled to the host computing device.

10. The method of claim 1 , further comprising:

providing, by the remote management server, one or more toolboxes to launch one or more web applications on the hidden desktop.

11. A system to remotely manage computing devices, comprising:

a remote management server comprising one or more processors and memory configured to:

identify a first remote computing device according to a first support ticket;

establish one or more connections communicatively coupling the first remote computing device to a host computing device;

hijack a system session executed on the first remote computing device via the one or more established connections;

transition the hijacked system session from a non-interactive state to an interactive state;

generate a hidden desktop within the hijacked system session to be displayed on a display device of the host computing device;

identify one or more instructions inputted through the hidden desktop by the host computing device to update a configuration of the first remote computing device; and

responsive to a command from the host computing device, terminate the hijacked system session by transitioning the hijacked system session from the interactive state to the non-interactive state.

12. The system of claim 11 , wherein the remote management server is further configured to close the first support ticket in response to the one or more instructions being executed, in a hidden manner, in the hijacked system session of the first remote computing device.

13. The system of claim 11 , wherein the remote management server is further configured to add a registry key to a registry of the first remote computing device to cause the hijacked system session to transition from the non-interactive state to the interactive state.

14. The system of claim 11 , wherein the hidden desktop includes at least one of an interactive power shell and an interactive command prompt.

15. The system of claim 11 , wherein the remote management server is further configured to communicate with one or more web applications to provide one or more interactive user interfaces on the hidden desktop.

16. The system of claim 11 , wherein the remote management server is further configured to compose one or more windows stations within the hijacked system session to generate the hidden desktop.

17. The system of claim 11 , wherein the remote management server is further configured to transmit the one or more instructions via the one or more established connections to the first remote computing device to be executed, in a hidden manner, to close the first support ticket.

18. The system of claim 11 , wherein the one or more instructions are inputted through the hidden desktop by one or more input devices communicatively coupled to the host computing device.

19. The system of claim 11 , wherein the remote management server is further configured to provide one or more toolboxes to launch one or more web applications on the hidden desktop.

20. The system of claim 11 , wherein the remote management server is further configured to:

receive, from a database storing the first support ticket associated with the first remote computing device, responsive to the first remote computing device generating the first support ticket;

receive, from the database storing a second support ticket associated with either the first remote computing device or a second remote computing device, the second support ticket responsive to the first or second remote computing device generating the second support ticket;

determine a first priority of the first support ticket based on a first status of the first support ticket;

determine a second priority of a second support ticket based on a second status of the second support ticket; and

determine that the first priority is higher than the second priority to identify the first remote computing device.

Assignments (2)
CHANGE OF NAME Recorded Oct 24, 2022
From: CONNECTWISE INC.
To: CONNECTWISE, LLC
Reel/Frame 061749/0987 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 1, 2022
From: MORGAN, JAKE; BOOTH, MAXWELL H
To: CONNECTWISE INC.
Reel/Frame 060962/0912 →
Continuity (3)
Provisional Application 62755728 · Nov 5, 2018
Provisional Application 62745049 · Oct 12, 2018
Related Publication 20220200846A1 · Jun 23, 2022