Highly-scalable native fleet management
A method of providing native scalable management of a fleet of managed devices, which includes establishing a Trust Community, which includes a sub-set of the managed devices, organizing the Trust Community, configuring one of the managed devices in the organized Trust Community as a Root Device to publish files via a file sharing function, adding the Root Device to a distribution profile stored in a database, creating or downloading files via the Root Device, and sharing the files with other devices in the organized Trust Community via the Root Device. Any devices on hold or offline are placed in a temporary working area for reorganizing. Download and install schedules are set up on a per device or a bulk basis according to policies. Files are placed into a staging area before re-distribution and checked for security, integrity, and/or completeness via checksums, digitally signed certificates, and/or internal structure checks.
1. A method of providing native scalable management of a fleet of managed devices, the method comprising:
establishing a Trust Community, which includes a sub-set of the managed devices in the fleet, wherein each of the managed devices includes a processor;
organizing the Trust Community;
configuring one of the managed devices in the organized Trust Community as a Root Device to publish files via a file sharing function;
adding the Root Device to a distribution profile stored in a database;
creating or downloading one or more files via the Root Device; and
sharing the one or more files with other devices in the organized Trust Community via the Root Device,
wherein any devices in the Trust Community that are on hold or offline are placed in a temporary working area for reorganizing,
wherein download and install schedules for the one or more files are set up on a per device or a bulk basis according to one or more policies such as installing if new content and/or installing always,
wherein files that are to be shared are placed into a staging area before re-distribution and checked for security, integrity, and/or completeness via checksums, digitally signed certificates, and/or internal structure checks.
2. The method of claim 1 , wherein the Trust Community is organized as a graph including layers, as a tree, by using a static topology which is changed only by explicit demand of a system administrator, and/or by using a dynamic topology which is self-organizing and includes dynamic routing.
3. The method of claim 2 , further comprising traversing the topology and the database to locate missing or incorrect relationship information and exporting graph topology information for analysis.
4. The method of claim 1 , wherein the managed devices are organized as nodes of a tree structure, wherein one of the managed devices in the tree structure is defined as the Root Device and each device in the tree has a Parent Device, zero or one or more sibling devices, and zero or one or more Child Devices.
5. The method of claim 1 , wherein the one or more files shared comprise one or more of software update files, user-content files such as print jobs, fax jobs, scanned images or other user generated files, encrypted configuration files, and workflow templates add-on files.
6. The method of claim 1 , wherein the fleet of managed devices comprises one or more of printers, copiers, scanners, and multifunction devices (MFDs).
7. The method of claim 1 , wherein transfer of control of the fleet between peer devices is made for disaster recovery, for convenience, for local sub trees, and/or for upgrading to external management systems.
8. A system for providing native scalable management of a fleet of managed devices, the system comprising:
memory and a processor configured to:
establish a Trust Community, which includes a sub-set of the managed devices in the fleet, wherein each of the managed devices includes a processor;
organize the Trust Community;
configure one of the managed devices in the organized Trust Community as a Root Device to publish files via a file sharing function;
add the Root Device to a distribution profile stored in a database;
create or download one or more files via the Root Device; and
share the one or more files with other devices in the organized Trust Community via the Root Device,
wherein any devices in the Trust Community that are on hold or offline are placed in a temporary working area for reorganizing,
wherein download and install schedules for the one or more files are set up on a per device or a bulk basis according to one or more policies such as installing if new content and/or installing always,
wherein files that are to be shared are placed into a staging area before re-distribution and checked for security, integrity, and/or completeness via checksums, digitally signed certificates, and/or internal structure checks.
9. The system of claim 8 , wherein the Trust Community is organized as a graph including layers, as a tree, by using a static topology which is changed only by explicit demand of a system administrator, and/or by using a dynamic topology which is self-organizing and includes dynamic routing.
10. The system of claim 9 , wherein the memory and the processor are further configured to traverse the topology and the database to locate missing or incorrect relationship information and export graph topology information for analysis.
11. The system of claim 8 , wherein the managed devices are organized as nodes of a tree structure, wherein one of the managed devices in the tree structure is defined as the Root Device and each device in the tree has a Parent Device, zero or one or more sibling devices, and zero or one or more Child Devices.
12. The system of claim 8 , wherein the one or more files shared comprise one or more of software update files, user-content files such as print jobs, fax jobs, scanned images or other user generated files, encrypted configuration files, and workflow templates add-on files.
13. The system of claim 8 , wherein the fleet of managed devices comprises one or more of printers, copiers, scanners, and multifunction devices (MFDs).
14. The system of claim 8 , wherein transfer of control of the fleet between peer devices is made for disaster recovery, for convenience, for local sub trees, and/or for upgrading to external management systems.
15. A non-transitory computer readable medium operable to perform a set of instructions, wherein when said instructions are executed on a computer, cause the computer to perform a method of providing native scalable management of a fleet of managed devices, the method comprising:
establishing a Trust Community, which includes a sub-set of the managed devices in the fleet, wherein each of the managed devices includes a processor;
organizing the Trust Community;
configuring one of the managed devices in the organized Trust Community as a Root Device to publish files via a file sharing function;
adding the Root Device to a distribution profile stored in a database;
creating or downloading one or more files via the Root Device; and
sharing the one or more files with other devices in the organized Trust Community via the Root Device,
wherein any devices in the Trust Community that are on hold or offline are placed in a temporary working area for reorganizing,
wherein download and install schedules for the one or more files are set up on a per device or a bulk basis according to one or more policies such as installing if new content and/or installing always,
wherein files that are to be shared are placed into a staging area before re-distribution and checked for security, integrity, and/or completeness via checksums, digitally signed certificates, and/or internal structure checks.
16. The non-transitory computer readable medium of claim 15 , wherein the Trust Community is organized as a graph including layers, as a tree, by using a static topology which is changed only by explicit demand of a system administrator, and/or by using a dynamic topology which is self-organizing and includes dynamic routing.
17. The non-transitory computer readable medium of claim 16 , further comprising traversing the topology and the database to locate missing or incorrect relationship information and exporting graph topology information for analysis.
18. The non-transitory computer readable medium of claim 15 , wherein the managed devices are organized as nodes of a tree structure, wherein one of the managed devices in the tree structure is defined as the Root Device and each device in the tree has a Parent Device, zero or one or more sibling devices, and zero or one or more Child Devices.
19. The non-transitory computer readable medium of claim 15 , wherein the one or more files shared comprise one or more of software update files, user-content files such as print jobs, fax jobs, scanned images or other user generated files, encrypted configuration files, and workflow templates add-on files and wherein the fleet of managed devices comprises one or more of printers, copiers, scanners, and multifunction devices (MFDs).
20. The non-transitory computer readable medium of claim 15 , wherein transfer of control of the fleet between peer devices is made for disaster recovery, for convenience, for local sub trees, and/or for upgrading to external management systems.