Cloud Registry Modification via Polling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for modifying the Windows Registry are inadequate for remote system management across network boundaries, particularly due to firewall restrictions and the risk of destabilizing the operating system setup.

Innovation Solution

A method and system for stateless modification of operating system registry data across network boundaries, involving a processor that receives and queues modification requests, polls the target device, and transmits the queued data for application to the registry, enabling remote configuration through a cloud-service RESTful API.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If registry modification is restricted to local or on-premises access only, then operating system stability is maintained, but remote system management capability is lost

Engineering Contradiction:
Improveoperating system stabilityVSAvoidremote system management
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

A cloud-based intermediary service is introduced between remote administrators and the target device registry. This service receives registry modification requests over the network, queues them securely, and delivers them to the target device through authorized channels (such as local agents or scheduled tasks), enabling remote management while maintaining system stability through controlled access mechanisms

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If firewall restrictions are implemented to secure network access, then network security is improved, but access to services on non-standard ports is blocked

Engineering Contradiction:
Improvenetwork securityVSAvoidservice accessibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

Instead of having the cloud service initiate outbound connections to pierce firewalls, the system inverts the approach by having the target device or local agent periodically poll or fetch configuration updates from the cloud service on authorized ports. This allows the cloud service to listen on standard authorized ports while the target device initiates the communication, effectively bypassing firewall restrictions without compromising security

Inventive Principle:
Principle #13The other way round (Inversion)

3Productivity

If stateless RESTful operations are used for registry modification, then service scalability is improved, but the complexity of managing stateless communication across networks increases

Engineering Contradiction:
Improveservice scalabilityVSAvoidcommunication management
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The cloud service pre-queues registry modification requests in a stateless manner before the target device needs them. Requests are validated, authenticated, and prepared in advance, then delivered to the target device when ready. This preliminary action simplifies the communication model by separating request preparation from execution, maintaining stateless RESTful operations while reducing communication management complexity

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10853091B2Cloud to on-premises windows registry settings
Publication Date: 2020.12.01 CITRIX SYSTEMS INC
  • US10853091B2 patent drawing
  • US10853091B2 patent drawing
  • US10853091B2 patent drawing

AI summary

Described embodiments provide systems and methods for stateless modification of operating system registry data across network boundaries. The system includes a processor coupled to memory and configured to execute instructions to receive, within a first network, a request to apply a modification to an operating system registry of a second device within a second network different from the first network. The processor queues data describing the requested modification, receives a polling request from the second device, and transmits, to the second device responsive to the polling request, the queued data describing the requested modification for the second device to apply to the operating system registry of the second device. For example, the requested modification may be to create a key, to create a value, to delete a key, or to delete a value.