Method and system for registry flying in a network

• US 20020165945A1
• Filed: 05/07/2001
• Published: 11/07/2002
• Est. Priority Date: 05/07/2001
• Status: Abandoned Application

• Current Assignee: Wyse Technology Incorporated (Dell Technologies Inc.)
• Original Assignee: Wyse Technology Incorporated (Dell Technologies Inc.)
• Inventors: Le, Bach, Stone, David, Buswell, Randy, Lam, Sui M.
• Application Number:
  US09/850,184
• Publication Number:
  US 20020165945A1
• Time in Patent Office: Days
• US Class Current: 709/221
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/0253 using browsers or web-pages for accessing management information
• CPC Class Codes: H04L 41/0813 characterised by the conditions triggering a change of settings
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/0843 based on generic templates

Abstract

A method and system for updating or making configuration changes to terminals by registry flying in a network is disclosed. The present invention is particularly useful to update or make configuration changes to an individual terminal in a thin client network. A registry is configured at a particular master terminal and the changed registry is transferred or flown via several different types of mechanisms to a management application using a management tool. The management application replicates and pushes the registry to one or more terminals or clients within the thin client network either successively or simultaneously. Several transport mechanisms can also be utilized to fly the registry to one particular terminal or a plurality of terminals.

Claims

1. A computer utility for managing configuration information by registry flying in a thin client network, comprising:

a plurality of thin client devices connected via a plurality of communications links to the thin client network, each thin client device capable of receiving and serving requests connected via one of the communications links to the thin client network, each thin client device having a current registry containing configuration information;

a master thin client device registry containing configuration information changed from the current registry of any one of the plurality of thin client devices;

any one of the thin client devices capable of serving a request to either a software repository or another thin client device to pull the master thin client device registry stored on either the software repository or the other thin client device;

either the software repository or the other thin client device capable of replicating the master thin client registry and transporting the master thin client registry via a transport mechanism to one or more of the plurality of thin client devices.

2. The system for managing configuration information according to claim 1, further comprising:

the transport mechanism selected from the group consisting File Transport Protocol, Trivial File Transport Protocol and other Internet protocols.

3. The system for managing configuration information according to claim 1, further comprising:

the transport mechanism is triggered by Simple Network Management Protocol.

4. The system for managing configuration information according to claim 1, further comprising:

the transport of the changed registry to one or more of the plurality of thin client devices is simultaneous to all selected thin client devices.

5. The system for managing configuration information according to claim 1, further comprising:

the configuration information in the master thin client device registry is an upgrade for a binary or a registry.

6. A thin client network system for managing configuration information by registry flying, the system comprising:

a plurality of thin client devices connected via a plurality of communications links to the thin client network, each thin client device capable of receiving and serving requests connected via one of the communications links to the thin client network, each thin client device having a current registry containing configuration information;

a master thin client device registry containing configuration information changed from the current registry of any one of the plurality of thin client devices;

a software repository residing on a network server and storing the master thin client device registry so that the master thin client registry can subsequently be moved to another thin client device;

any one of the thin client devices capable of serving a request to the software repository to pull the master thin client device registry stored on either the software repository or the other thin client device, either the software repository or the other thin client device capable of replicating the master thin client registry and transporting the master thin client registry via a transport mechanism to one or more of the plurality of thin client devices.

7. The system for managing configuration information according to claim 6, further comprising:

the master thin client device registry having a plurality of fields, each of the plurality of field capable of being individually addressed.

8. The system for managing configuration information according to claim 6, further comprising:

at least one of the plurality of thin client devices having a native user interface for creating the master thin client device registry.

9. The system for managing configuration information according to claim 6, further comprising:

a Virtual Network Computing client and server, the software repository or the thin client device storing the master thin client device registry being in communication with the Virtual Network Computing client which provides a remote interface for creating the master thin client device registry, the Virtual Network Computing client communicates with the Virtual Network Computing server to make changes to the master thin client device registry through shadowing of the interface of the thin client device.

10. The system for managing configuration information according to claim 6, further comprising:

the thin client device storing the master thin client device registry provides a HyperText Markup Language server that is used to create the master thin client device registry, the HyperText Markup Language server provides a web page that reflects the configuration parameters of the master thin client device registry, a Browser is used to make permanent changes to the configuration parameters of the master thin client device registry that is reflected on the web page.

11. The system for managing configuration information according to claim 6, further comprising:

the thin client device storing the master thin client device registry provides a Simple Network Management Protocol agent that is connected to a Simple Network Management Protocol tool, the Simple Network Management Protocol tool is connected to the thin client device.

12. The system for managing configuration information according to claim 6, further comprising:

the thin client device storing the master thin client device registry is a non-native device to the thin client network, a browser connects across the thin client network to communicate with the non-native device providing an HyperText Markup Language server having one or more web pages therein, the HyperText Markup Language server is in communication with the master thin client device registry through an application layer that is used to create the master thin client device registry.

13. The system for managing configuration information according to claim 6, further comprising:

the configuration information in the master thin client device registry is an upgrade for a binary or a registry.

15. The thin client network of claim 14, wherein the second one of the thin client devices is capable of replicating the master thin client registry and transporting the master thin client registry via a transport mechanism to one or more of the plurality of thin client devices.

16. The thin client network of claim 14, wherein the master thin client registry is merged with the current registry of one or more of the thin client devices from a first one of the plurality of thin client devices to create a merged thin client device registry.

17. The thin client network of claim 14, wherein the transport mechanism is selected from the group consisting File Transport Protocol, Transfer File Transport Protocol and other Internet protocols.

18. The thin client network of claim 14, wherein the transport mechanism is triggered by Simple Network Management Protocol.

19. The thin client network of claim 14, wherein the transport of the changed registry to one or more of the plurality of terminals is simultaneous to all selected terminals.

14. A thin client network for managing configuration information by registry flying comprising:

a plurality of thin client devices connected via a plurality of communications links to the thin client network, each thin client device capable of receiving and serving requests connected via one of the communications links to the thin client network, each thin client device having a current registry containing configuration information;

a master thin client device registry containing configuration information changed from the current registry of any one of the plurality of thin client devices; and

a software repository residing on a network server and storing the master thin client device registry so that the master thin client registry can subsequently be pulled by a second one of the plurality of thin client devices so that second thin client device takes on the configuration of the master thin client device.

20. A computer utility for finding a device on a thin client network, comprising:

a plurality of thin client devices connected via a plurality of communications links to the thin client network, each thin client device capable of receiving and serving requests connected via one of the communications links to the thin client network, each thin client device having a current registry containing configuration information; and

any one of the thin client devices capable of receiving a request for discovery to the thin client network.

21. The system for finding a device on a thin client network of claim 20, wherein the discovery is through a Simple Network Management Protocol query to each one of the pluralities of thin client devices, the query identifying a thin client device exists.

22. The system for finding a device on a thin client network of claim 20, wherein the discovery is through a plurality of packets broadcasted by a server to each one of the pluralities of thin client devices, each of the plurality of packets having a unique identification, each one of the pluralities of thin client devices generating a response packet transported back to the server.

23. The system for finding a device on a thin client network of claim 20, wherein the transport mechanism is triggered by Simple Network Management Protocol.

24. The system for finding a device on a thin client network of claim 20, wherein discovery of a device on the thin client network manages the transport of a master thin client device registry to one or more of the plurality of thin client devices selected by the discovery.

25. The system for finding a device on a thin client network of claim 20, wherein the configuration information in the master thin client device registry is an upgrade for a binary or a registry.