Depopulation of user data from network

Information

  • Patent Grant
  • 9558195
  • Patent Number
    9,558,195
  • Date Filed
    Friday, February 27, 2009
    15 years ago
  • Date Issued
    Tuesday, January 31, 2017
    7 years ago
  • CPC
  • Field of Search
    • US
    • 709 223000
    • CPC
    • G06F17/30117
    • G06F17/30575
  • International Classifications
    • G06F15/173
    • G06F17/30
    • Term Extension
      1146
Abstract
Embodiments relate to systems and methods for depopulation of user data from a network. A network management platform can communicate with a set of managed machines in a network, and generally manage user accounts including user IDs, associated network processes, services, application files, data files, and/or other user data. In embodiments, a user may have a change in status, such as departing from the organization operating the network, changing their name or user name, or other updates. In such cases, a systems administrator may need to update or delete files, processes, services, and/or other user data associated with the user from the network. The network management platform can interrogate the network for files, processes, or other resources associated with the user ID of interest. The search can exhaustively interrogate every available node in the network, to update or purge all files associated with the subject user ID(s).
Description
FIELD

The present teachings relate to systems and methods for the depopulation of user data from a network, and more particularly to platforms and techniques for automatically scanning a network for files, processes, profiles, and/or other data related to a user whose user ID is changed or deactivated in the network.


BACKGROUND OF RELATED ART

A variety of network management platforms exist to assist network administrators with installing and configuring network resources and services. In many platforms, a management server can be used to issue commands to hosts or other network nodes to manage the configuration of the network hosts, underlying clients or other devices. As part of the management of comparatively large-scale and other networks, a network management platform can have the responsibility of maintaining a set of valid user IDs and resources and privileges associated with those user Ids.


It is a not infrequent occurrence in network operations that a user can undergo a change in status in their employment, subscription, or other relationship to the network to which they are registered. In a corporate setting, for example, a user can have a change in marital status and a resulting change in their legal name, or can depart from a company or other organization. In those and other cases, the accumulated files, user profiles, processes, or other resources associated with the user ID for that user may remain in the network.


In existing network management platforms, a systems administrator confronted with a set of obsolete user IDs has no particular tools or services available to them to locate and remote the undesired residual user IDs, and/or associated files, user profiles, processes, or other resources. Those managers therefore must typically access each individual data store, user machine, or other nodes on the managed network, and look for the out-of-date user data. It may thus be desirable to provide methods and systems that overcome these network management difficulties, and permit an administrator or other user to track down and update or remove obsolete user IDs and related user data.





DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the present teachings and together with the description, serve to explain the principles of the present teachings. In the figures:



FIG. 1 illustrates an overall network in which systems and methods for depopulation of user data from a network can be implemented, according to various embodiments of the present teachings;



FIG. 2 illustrates an overall network in which systems and methods for depopulation of user data from a network can be implemented, according to various embodiments of the present teachings in further regards;



FIG. 3 illustrates an exemplary hardware configuration of a network management platform that can be used in systems and methods for depopulation of user data from a network, according to various embodiments of the present teachings; and



FIG. 4 illustrates overall network management processing for depopulation of user data from a network can be implemented, according to various embodiments of the present teachings.





DESCRIPTION OF EMBODIMENTS

Embodiments of the present teachings relate to systems and methods for depopulation of user data from a network. More particularly, embodiments relate to platforms and techniques in one regard for identifying obsolete or unwanted user IDs via a network management server, and automatically scanning the network to which the user IDs are registered to detect user data associated with those IDs. The user data can be or include, for example, executing processes, services, user profiles, application or data files, or other user data authored by, belonging to, or otherwise associated with a user ID. The user data can be stored or hosted in a variety of locations in the network, including, for example, databases or other data stores, servers, personal computers or workstations, removable media, and/or other locations. When a systems administrator or other user desires to begin a purge of obsolete or undesired user IDs and associated user data, the network management platform can commence a full-network scan to comprehensively access and examine all computing, storage, and/or other nodes in the network and search the directories, memory, storage, and/or other resources therein to detect processes, services, files, user profiles, or other user data associated with those user IDs. The network management platform can then perform any desired modification or update to the user IDs and/or associated user data, such as, for example, changing the user IDs or data, exporting the user IDs or data, and/or deleting the user IDs or data. According to embodiments in one regard, the network management platform can thereby locate, update, and/or dispose of obsolete user IDs and/or user data from one central processing point, using comparatively compact global commands.


Reference will now be made in detail to exemplary embodiments of the present teachings, which are illustrated in the accompanying drawings. Where possible the same reference numbers will be used throughout the drawings to refer to the same or like parts.



FIG. 1 illustrates an overall system 100 consistent with systems and methods for depopulating user data from a network, according to various embodiments of the present teachings. In embodiments as shown, a network management platform 102 can maintain and manage a managed network 116. Network management platform 102 can communicate with a set of supervisory hosts 112 via one or more networks 110. One or more networks 110 can be or include the Internet, or other public or private networks. One or more networks 110 can be or include wired, wireless, optical, and other network connections. Set of supervisory hosts 112 can be or include a set of servers configured to communicate with entities at other levels of one or more networks 110 and/or associated connections. In embodiments, set of supervisory hosts 112 can communicate with an intermediate set or sets of hosts, gateways, or servers. In embodiments, set of supervisory hosts 112 can function as “overlord” hosts or servers which communicate command data 120 to an underlying or low-level set of targets 180, or other devices in managed network 116.


Set of supervisory hosts 112 can support or serve an underlying managed network 116, for example via a local area network, or other network(s) or connections. Managed network 116 including set of targets 180 can be or include a set of personal computers, network-enabled media devices, or other clients, devices, or machines. Other hierarchies, topologies, and connections between network management platform 102, set of supervisory hosts 112, any intermediate hosts, set of targets 180, and/or other entities or devices of managed network 116 can be used. In embodiments, communications between network management platform 102, set of supervisory hosts 112, set of targets 180, and/or other entities or devices in managed network 116 or other entities can be conducted via one or more secure channel 108, such as the secure channel and related resources described in co-pending U.S. application Ser. No. 12/130,424, filed May 30, 2008, entitled “Systems and Methods for Remote Management of Networked Systems Using Secure Modular Platform,” which published as U.S. Patent Application Publication No. 2009/0300180, assigned or under obligation of assignment to the same entity as this application, and which application is incorporated by reference herein.


Network management platform 102 can include or access resources to support the generation and transmission of one or more discovery command 120 via auto-discovered or other pathways to manage set of supervisory hosts 112, set of targets 180, and/or other entities or devices of managed network 116, including a network store 104. Network store 104 can be or include a database or other data store, and in embodiments can store a network map 106. Network map 106 can record information related to the configuration and topology of network connections between set of supervisory hosts 112, set of targets 180, and/or other entities or devices of managed network 116, as well as other data. In embodiments, network map 106 can be recorded in a file, tree, database, or other record.


According to embodiments in one regard, network management platform 102 can access network map 106 to carry out management and maintenance operations on set of user IDs 162. Set of user IDs 162 can contain a set of user names, account names, account numbers, stored passwords, and/or other resources related to the identification and/or validation of users of managed network 116. According to embodiments, in general, each user ID in set of users IDs 162 can have an associated set of user data 164 hosted, stored, or located throughout the network of managed network 116.


Set of user data 164 can be or include any one or more of processes, services, user profiles, data files such as database, word processing, spreadsheet, media, or other data files, application files, passwords or other credentials, and/or other data related to the user identified by a given user ID in set of user IDs 162. Portions of user data in set of user data 164 can be located in diverse or multiple locations, such as in local or remote servers, personal computers or other client machines or devices, workstations, network-enabled mobile devices, databases, archives or RAID sites, or other nodes, facilities, or locations in managed network 116. Set of user data 164 can further comprise, for instance, files that contain references to a user ID which control access to applications or services, such as “/etc/group/.” Set of user data 164 can likewise include information such as aliases, groups, access control lists (ACLs), references by user ID or user name, or other information.


Network management platform 102 can determine a set of target IDs 166 in set of user IDs 162 to locate, modify, and/or remove set of user data 164 in or from managed network 116 and/or associated network or networks. In embodiments, set of target IDs 166 can be imported to network management platform 102, and/or can be manually specified by a systems administrator or other user. In embodiments, set of target IDs 166 can be generated by network management platform 102, for example, by identifying all user IDs that have not been used for a defined period of time, such as one year or other period of time.


As for instance illustrated in FIG. 2, once network management platform 102 has accessed, received, or generated set of target IDs 166, network management platform 102 can issue commands and/or invoke services to locate, modify, and/or purge set of target. IDs 166 and/or set of user data 164 associated with each of those user IDs. Network management platform 102 can generate one or more discovery command 120 to transmit to set of supervisory hosts 112, managed network 116, one or more networks 110, and/or other machines, locations, or resources. One or more discovery command 120 can contain an identification of set of target IDs 166 and other data to locate, identify, authenticate, and/or set of user data 164 associated with those IDs in the overall network. When network management platform 102 generates one or more discovery command 120, network management platform 102 can access network map 106 to identify one or more supervisory hosts in set of supervisory hosts 112 to or through which to transmit one or more discovery command 120. The recipient supervisory host(s) can receive one or more discovery command 120 and, in embodiments, access network map 106 and/or communicate with network management platform 102 to extract a pathway by which to relay or transmit one or more discovery command 120 to managed network 116 and/or other underlying devices. The supervisory host(s) can then transmit or relay the one or more discovery command 120 to a target or targets in managed network 116, using the identified pathway.


In embodiments, network management platform 102 can receive data back from set of supervisory hosts 112, managed network 116, and/or other resources indicating the presence of user data 164 for one or more user IDs in set of target IDs 166. Upon detection of user data 164 for those user IDs, network management platform 102 can proceed to generate one or more modification command 168 to initiate a modification, update, migration, and/or deletion or removal of a portion or all of user data 164, and/or set of target IDs 166. For example, network management platform 102 can direct that files, directories, user profiles, and/or executing processes can be modified, updated, deleted, archived, terminated, removed, or otherwise processed to purge obsolete, inaccurate, insecure, or unwanted data. In embodiments, the modification can include substituting a new user ID for an obsolete user ID. In embodiments, the modification can include substituting new credentials, privileges, or other attributes for the existing attributes for the subject user ID. Other modifications or processing of set of target IDs 166 can be done. For example, two or more user IDs and associated user data 164 can be combined, or a single user ID can be split into multiple user data 164, IDs, or attributes.


According to various embodiments, network management platform 102 can be configured to periodically probe the network including set of manage machines 116, set of supervisory hosts 112, and/or other resources with repeated or additional one or more discovery command 120, to locate files, processes, and/or other user data 164 that was not present, visible, or identifiable during previous scans. In embodiments, a process of repeatedly interrogating the network for user data 164 can be repeated until a termination criteria are met, such as, for instance, the failure to discover any further user data 164 after a predetermined number of discovery attempts, or after a certain amount of time.


In terms of operational scope, it will be appreciated that any of network management platform 102, set of supervisory hosts 112, any intermediate hosts, and/or managed network 116 or other entities can be significantly or substantially geographically distributed, and can represent relatively large-scale groupings or clusters. For instance, different hosts in set of supervisory hosts 112 and/or associated targets in managed network 116 can be located in different metropolitan areas, in different sections of a country, in different countries, or in different continents. For further instance, different hosts in set of supervisory hosts 112 and/or sets of targets in managed network 116 can represent hundreds, thousands, or greater or lesser numbers of collective devices.



FIG. 3 illustrates an exemplary diagram of hardware and other resources that can be incorporated in a network management platform 102 configured to communicate with set of supervisory hosts 112, any intermediate hosts, set of targets 180, and/or other entities or devices of managed network 116 via one or more networks 110 or other connections, according to embodiments. In embodiments as shown, network management system 102 can comprise a processor 124 communicating with memory 126, such as electronic random access memory, operating under control of or in conjunction with operating system 130. Operating system 130 can be, for example, a distribution of the Linux™ operating system, the Unix™ operating system, or other open-source or proprietary operating system or platform. Processor 124 also communicates with network store 104, such as a database stored on a local hard drive. Processor 124 further communicates with network interface 128, such as an Ethernet or wireless data connection, which in turn communicates with one or more networks 110, such as the Internet or other public or private networks. Processor 124 also communicates with a network management module 132, which can be or include logic to monitor and manage the operation of network 110 and associated or connected resources. Network management module 132 can for instance permit a user to view, delegate, and execute configuration operations in set of supervisory hosts 112, set of targets 180, managed network 116, and/or other resources or entities. Other configurations of network management system 102, associated network connections, and other hardware and software resources are possible.



FIG. 4 illustrates overall processing for depopulation of user data from a network, according to various embodiments of the present teachings. In 402, processing can begin. In 404, a secure channel 108 can be established between network management platform 102 and one or more networks 110, set of supervisory hosts 112, set of targets 180, and/or other entities or devices of managed network 116. In embodiments, secure channel 108 can be or include a secure socket layer (SSL) connection, a public/private key infrastructure or connection, or other channel or connection. In 406, network management platform 102 can access, receive, or generate set of target IDs 166 reflecting user IDs whose associated user data 164 is to be scanned for in the overall network. In 408, network management platform 102 can transmit one or more discovery command 120 to one or more networks 110, set of supervisory hosts 112, set of targets 180, or other devices, entities or resources of managed network 116. In 410, network management platform 102 can receive one or more responses from the network indicating the presence of user data 164 associated with set of target IDs 166. User data 164 can be or include processes, services, user profiles, data files, application files, and/or other data.


In 412, network management platform 102 can proceed to generate one or more modification command 168 to initiate a modification, update, and/or deletion or removal of a portion or all of user data 164, and/or set of target Ds 166. For example, network management platform 102 can direct that files, directories, user profiles, and/or executing processes can be modified, updated, deleted, archived, terminated, removed, or otherwise processed to purge obsolete, inaccurate, insecure, or unwanted data. In 414, the modification, updating, and/or deletion of user data 164 can be carried out. In 416, network management platform 102 can update set of user IDs 162 and/or any user data 164 to reflect the modifications or deletions, as appropriate. In 418, network management platform 102 can store a record of all locations in which one or more of set of target IDs 166 and/or user data 164 were found, to record a map of user ID/user data repositories within the network, as appropriate. In 420, as understood by persons skilled in the art, processing can repeat, return to a prior processing point, jump to a further processing point, or end.


The foregoing description is illustrative, and variations in configuration and implementation may occur to persons skilled in the art. For example, while embodiments have been described in which configuration commands or other data are generated and transmitted from one network management platform 102, in embodiments more than one server or other device or resource can serve as a central control point. For further example, while embodiments have been described in which one or more hosts in a set of supervisory hosts 112 coordinate the distribution of commands and data to a managed network 116, in embodiments, implementations can involve the dissemination of commands or other data through different network hierarchies, trees, nodes, or arrangements. For instance, in embodiments, commands or other data can be delegated via supervisory hosts through more than two sub-hosts or other sub-levels. For yet further example, while embodiments have been described involving one level or layer of supervisory hosts, in embodiments, the overall network can be configured with multiple levels or layers of supervisory hosts (or “overlords”). Similarly, various targets in managed network 116 can be configured at different levels within the overall network. For further example, while in embodiments the depopulation activity has been described as operating on a set of user IDs 162 and target IDs 166, in embodiments, other types of identifiers can be used. For example, in embodiments user data 164 associated with a given address, such as an Internet Protocol (IP) address, or other address or identifier, can be used to identify users or other entities for modification and/or removal. Other resources described as singular or integrated can in embodiments be plural or distributed, and resources described as multiple or distributed can in embodiments be combined. The scope of the present teachings is accordingly intended to be limited only by the following claims.

Claims
  • 1. A method comprising: identifying, by a processing device of a network management platform, at least one user ID associated with at least one user having a changed status in a network, wherein the network is associated with the network management platform, data sources, and user data;identifying, by the processing device of the network management platform, data sources hosting a set of user processes, a set of files, and a set of user profiles in the network;accessing communication paths between the network management platform and the processing device-identified data sources hosting the set of user processes, the set of files, and the set of user profiles in the network;generating a discovery command in view of the processing device-identified data sources;transmitting the discovery command from the network management platform to the processing device-identified data sources hosting the set of user processes, the set of files, and the set of user profiles in the network;receiving a response to the discovery command in the network management platform, the response indicating presence of user data in the data sources in view of the communication paths;identifying non-indexed user data associated with the at least one user ID in the data sources in view of the response to the discovery command; andmodifying the non-indexed user data in the network in view of the changed status of the at least one user.
  • 2. The method of claim 1, wherein the modifying comprises migrating the non-indexed user data from the at least one user ID to at least a second user ID.
  • 3. The method of claim 1, wherein the modifying comprises deleting the non-indexed user data associated with the at least one user ID from the network.
  • 4. The method of claim 1, wherein transmitting the discovery command comprises communicating with available nodes in the network via a secure channel to identify the non-indexed user data associated with the at least one user ID.
  • 5. The method of claim 1, wherein the changed status of the at least one user comprises at least one of a change in user name, a change in network user ID, a change in employment status, a change in level of security access level, or a change in network subscription status.
  • 6. The method of claim 1, wherein transmitting the discovery command comprises multiple scanning of the network repeated until termination criteria are met.
  • 7. A system, comprising: an interface to a network, wherein the network is associated with a network management platform, data sources, and user data; anda processing device of the network management platform to communicate via the interface with the network to: identify at least one user ID associated with at least one user having a changed status in the network;identify data sources hosting a set of user processes, a set of files, and a set of user profiles in the network;access communication paths between the network management platform and the processing device-identified data sources hosting the set of user processes, the set of files, and the set of user profiles in the network;generate a discovery command in view of the processing device-identified data sources;transmit the discovery command from the network management platform to the processing device-identified data sources hosting the set of user processes, the set of files, and the set of user profiles in the network;receive a response to the discovery command in the network management platform, the response to indicate presence of user data in the data sources in view of the communication paths;identify non-indexed user data associated with the at least one user ID in the data sources in view of the response to the discovery command; andmodify the non-indexed user data in the network in view of the changed status of the at least one user.
  • 8. The system of claim 7, wherein the processing device is further to migrate the non-indexed user data from the at least one user ID to at least a second user ID.
  • 9. The system of claim 7, wherein the processing device is further to delete the non-indexed user data associated with the at least one user ID from the network.
  • 10. The system of claim 7, wherein the processing device is further to communicate with available nodes in the network via a secure channel to identify the non-indexed user data associated with the at least one user ID.
  • 11. The system of claim 7, wherein the changed status of the at least one user comprises at least one of a change in user name, a change in network user ID, a change in employment status, a change in level of security access level, or a change in network subscription status.
  • 12. The system of claim 7, wherein the processing device is further to repeat scanning of the network until termination criteria are met.
  • 13. A non-transitory computer readable medium storing instructions which, when executed, cause a processing device to: identify, by the processing device of a network management platform, at least one user ID associated with at least one user having a changed status in a network, wherein the network is associated with the network management platform, data sources, and user data;identify, by the processing device of the network management platform, data sources hosting a set of user processes, a set of files, and a set of user profiles in the network;generating a discovery command in view of the processing device-identified data sources;transmit the discovery command from the network management platform to the processing device-identified data sources hosting the set of user processes, the set of files, and the set of user profiles in the network;access communication paths between the network management platform and the processing device-identified data sources hosting the set of user processes, the set of files, and the set of user profiles in the network;receive a response to the discovery command in the network management platform, the response to indicate presence of user data in the data sources in view of the communication paths;identify non-indexed user data associated with the at least one user ID in the data sources in view of the response to the discovery command; andmodify the non-indexed user data in the network in view of the changed status of the at least one user.
  • 14. The non-transitory computer readable medium of claim 13, wherein to modify, the processing device is further to migrate the non-indexed user data from the at least one user ID to at least a second user ID.
  • 15. The non-transitory computer readable medium of claim 13, wherein to modify, the processing device is further to delete the non-indexed user data associated with the at least one user ID from the network.
  • 16. The non-transitory computer readable medium of claim 13, wherein to transmit the discovery command, the processing device is further to communicate with available nodes in the network via a secure channel to identify the non-indexed user data associated with the at least one user ID.
  • 17. The non-transitory computer readable medium of claim 13, wherein the changed status of the at least one user comprises at least one of a change in user name, a change in network user ID, a change in employment status, a change in level of security access level, or a change in network subscription status.
  • 18. The non-transitory computer readable medium of claim 13, wherein to transmit the discovery command comprises multiple scanning of the network repeated until termination criteria are met.
US Referenced Citations (333)
Number Name Date Kind
5787246 Lichtman et al. Jul 1998 A
5835719 Gibson et al. Nov 1998 A
5948062 Tzelnic et al. Sep 1999 A
5991758 Ellard Nov 1999 A
6105100 Dean et al. Aug 2000 A
6212585 Chrabaszcz Apr 2001 B1
6240407 Chang May 2001 B1
6243747 Lewis et al. Jun 2001 B1
6269405 Dutcher et al. Jul 2001 B1
6272536 van Hoff et al. Aug 2001 B1
6282652 Scheifler Aug 2001 B1
6381742 Forbes et al. Apr 2002 B2
6415289 Williams et al. Jul 2002 B1
6438711 Woodruff Aug 2002 B2
6477572 Elderton et al. Nov 2002 B1
6496831 Baulier et al. Dec 2002 B1
6516427 Keyes et al. Feb 2003 B1
6526442 Stupek et al. Feb 2003 B1
6550021 Dalphy et al. Apr 2003 B1
6557169 Erpeldinger Apr 2003 B1
6594664 Estrada et al. Jul 2003 B1
6611869 Eschelbeck et al. Aug 2003 B1
6625742 Owhadi et al. Sep 2003 B1
6678888 Sakanishi Jan 2004 B1
6686838 Rezvani et al. Feb 2004 B1
6691225 Suffin Feb 2004 B1
6745189 Schreiber Jun 2004 B2
6751659 Fenger et al. Jun 2004 B1
6757837 Platt et al. Jun 2004 B1
6769022 DeKoning et al. Jul 2004 B1
6779004 Zintel Aug 2004 B1
6845464 Gold Jan 2005 B2
6854010 Christian et al. Feb 2005 B1
6865737 Lucas et al. Mar 2005 B1
6925518 Rudland et al. Aug 2005 B2
6941518 French et al. Sep 2005 B2
6947939 Fujibayashi et al. Sep 2005 B2
6965886 Govrin et al. Nov 2005 B2
6966058 Earl et al. Nov 2005 B2
6986033 Miyamoto et al. Jan 2006 B2
7003560 Mullen et al. Feb 2006 B1
7013461 Hellerstein et al. Mar 2006 B2
7020654 Najmi Mar 2006 B1
7036010 Wray Apr 2006 B2
7051101 Dubrovsky et al. May 2006 B1
7054618 McCullough May 2006 B1
7058797 Miyamoto et al. Jun 2006 B2
7082460 Hansen et al. Jul 2006 B2
7082464 Hasan et al. Jul 2006 B2
7107330 Hamilton et al. Sep 2006 B1
7127742 Kramer et al. Oct 2006 B2
7133822 Jacobson Nov 2006 B1
7165109 Chiloyan et al. Jan 2007 B2
7181444 Porter Feb 2007 B2
7185071 Berg et al. Feb 2007 B2
7197608 Mikuma et al. Mar 2007 B2
7200662 Hasan et al. Apr 2007 B2
7200845 Morrison et al. Apr 2007 B2
7207039 Komarla et al. Apr 2007 B2
7213065 Watt May 2007 B2
7280830 Anderson et al. Oct 2007 B2
7284042 Beadles et al. Oct 2007 B2
7305550 Oliver et al. Dec 2007 B2
7310669 Webb et al. Dec 2007 B2
7315826 Guheen et al. Jan 2008 B1
7330967 Pujare et al. Feb 2008 B1
7340637 Nagoya Mar 2008 B2
7346801 Brunelle et al. Mar 2008 B2
7350112 Fox et al. Mar 2008 B2
7356679 Le et al. Apr 2008 B1
7383433 Yeager et al. Jun 2008 B2
7395322 Harvey et al. Jul 2008 B2
7401137 Gasser et al. Jul 2008 B1
7434253 Crall et al. Oct 2008 B2
7448033 Kruger et al. Nov 2008 B1
7469284 Dubrovsky et al. Dec 2008 B1
7480907 Marolia et al. Jan 2009 B1
7506040 Rabe et al. Mar 2009 B1
7506151 Miyamoto et al. Mar 2009 B2
7509487 Lu et al. Mar 2009 B2
7516218 Besson Apr 2009 B2
7519691 Nichols et al. Apr 2009 B2
7548985 Guigui Jun 2009 B2
7558841 Taboada Jul 2009 B2
7574413 Larson et al. Aug 2009 B2
7574481 Moore et al. Aug 2009 B2
7596227 Illowsky et al. Sep 2009 B2
7600005 Jamkhedkar et al. Oct 2009 B2
7600113 Kuehnel et al. Oct 2009 B2
7606868 Le et al. Oct 2009 B1
7627617 Kavuri et al. Dec 2009 B2
7640325 DeKoning et al. Dec 2009 B1
7653008 Patrick et al. Jan 2010 B2
7668947 Hutchinson et al. Feb 2010 B2
7671735 Karaoguz et al. Mar 2010 B2
7672928 Maloney Mar 2010 B2
7673130 Miyamoto et al. Mar 2010 B2
7681080 Abali et al. Mar 2010 B2
7689664 Karlberg Mar 2010 B2
7716224 Reztlaff, II May 2010 B2
7716316 Nichols et al. May 2010 B2
7734717 Saarimaki et al. Jun 2010 B2
7734910 Nasu Jun 2010 B2
7774791 Appelbaum et al. Aug 2010 B1
7779119 Ginter et al. Aug 2010 B2
7787863 van de Groenendaal Aug 2010 B2
7792986 Donoho et al. Sep 2010 B2
7827261 Griswold et al. Nov 2010 B1
7827590 Hopen et al. Nov 2010 B2
7831692 French et al. Nov 2010 B2
7831997 Eldar et al. Nov 2010 B2
7937437 Fujii May 2011 B2
7971047 Vlaovic et al. Jun 2011 B1
8028048 Karve et al. Sep 2011 B2
8051181 Larson et al. Nov 2011 B2
8060874 Rengarajan et al. Nov 2011 B2
8069341 Fries et al. Nov 2011 B2
8073908 Heins et al. Dec 2011 B2
8078728 Pollan et al. Dec 2011 B1
8103776 DeHaan Jan 2012 B2
8103783 Plamondon Jan 2012 B2
8117314 Croft et al. Feb 2012 B2
8117600 Roeck et al. Feb 2012 B1
8131825 Nord et al. Mar 2012 B2
8131851 Harlow Mar 2012 B2
8132166 DeHaan Mar 2012 B2
8185891 DeHaan May 2012 B2
8205240 Ansari et al. Jun 2012 B2
8244836 DeHaan Aug 2012 B2
8271975 DeHaan Sep 2012 B2
8336089 Ahmed et al. Dec 2012 B1
8346929 Lai Jan 2013 B1
8355407 Wookey et al. Jan 2013 B2
8370528 Bryers et al. Feb 2013 B2
8407687 Moshir et al. Mar 2013 B2
8429630 Nickolov et al. Apr 2013 B2
8498941 Felsher Jul 2013 B2
8504696 Larson et al. Aug 2013 B2
8601539 Bobel Dec 2013 B1
8713177 DeHaan et al. Apr 2014 B2
8875249 Ture Oct 2014 B2
9081816 Krishnaprasad Jul 2015 B2
20010047279 Gargone Nov 2001 A1
20020062259 Katz et al. May 2002 A1
20020078186 Engel et al. Jun 2002 A1
20020095395 Larson et al. Jul 2002 A1
20020099787 Bonner et al. Jul 2002 A1
20020111840 Bagdonas et al. Aug 2002 A1
20020138567 Ogawa Sep 2002 A1
20020138578 Zhou Sep 2002 A1
20020162028 Kennedy Oct 2002 A1
20030005097 Barnard et al. Jan 2003 A1
20030055919 Fong et al. Mar 2003 A1
20030069884 Nair et al. Apr 2003 A1
20030069946 Nair et al. Apr 2003 A1
20030070110 Aija et al. Apr 2003 A1
20030074549 Paul et al. Apr 2003 A1
20030083922 Reed May 2003 A1
20030110173 Marsland Jun 2003 A1
20030119480 Mohammed Jun 2003 A1
20030126585 Parry Jul 2003 A1
20030145083 Cush et al. Jul 2003 A1
20030195921 Becker et al. Oct 2003 A1
20030212992 Ronning et al. Nov 2003 A1
20030233648 Earl et al. Dec 2003 A1
20040006616 Quinn et al. Jan 2004 A1
20040015831 Bowhill Jan 2004 A1
20040015957 Zara et al. Jan 2004 A1
20040019876 Dravida et al. Jan 2004 A1
20040024984 Lanzatella et al. Feb 2004 A1
20040044643 deVries et al. Mar 2004 A1
20040054789 Breh et al. Mar 2004 A1
20040059703 Chappell et al. Mar 2004 A1
20040064501 Jan et al. Apr 2004 A1
20040088405 Aggarwal May 2004 A1
20040128375 Rockwell Jul 2004 A1
20040143664 Usa et al. Jul 2004 A1
20040167975 Hwang et al. Aug 2004 A1
20040215755 O'Neill Oct 2004 A1
20040223469 Bahl et al. Nov 2004 A1
20040226010 Suorsa Nov 2004 A1
20050027608 Wiesmuller et al. Feb 2005 A1
20050028025 Zalewski et al. Feb 2005 A1
20050050175 Fong et al. Mar 2005 A1
20050055350 Werme et al. Mar 2005 A1
20050102154 Dodd et al. May 2005 A1
20050108369 Sather et al. May 2005 A1
20050114474 Anderson et al. May 2005 A1
20050125525 Zhou et al. Jun 2005 A1
20050177829 Vishwanath Aug 2005 A1
20050182796 Chu et al. Aug 2005 A1
20050198629 Vishwanath Sep 2005 A1
20050223374 Wishart et al. Oct 2005 A1
20050246421 Moore et al. Nov 2005 A1
20060039340 Ptasinski et al. Feb 2006 A1
20060041767 Maxwell et al. Feb 2006 A1
20060080656 Cain et al. Apr 2006 A1
20060080659 Ganji Apr 2006 A1
20060095230 Grier et al. May 2006 A1
20060095702 Hickman et al. May 2006 A1
20060155857 Feenan et al. Jul 2006 A1
20060173912 Lindvall et al. Aug 2006 A1
20060174018 Zhu et al. Aug 2006 A1
20060190575 Harvey et al. Aug 2006 A1
20060190773 Rao et al. Aug 2006 A1
20060200658 Penkethman Sep 2006 A1
20060215575 Horton et al. Sep 2006 A1
20060218544 Chakraborty et al. Sep 2006 A1
20060230165 Zimmer et al. Oct 2006 A1
20060282479 Johnson et al. Dec 2006 A1
20070015538 Wang Jan 2007 A1
20070067419 Bennett Mar 2007 A1
20070073894 Erickson Mar 2007 A1
20070078988 Miloushev et al. Apr 2007 A1
20070101118 Raghunath et al. May 2007 A1
20070118654 Jamkhedkar et al. May 2007 A1
20070136265 Hunt et al. Jun 2007 A1
20070168721 Luiro et al. Jul 2007 A1
20070169093 Logan et al. Jul 2007 A1
20070192158 Kim Aug 2007 A1
20070204338 Aiello et al. Aug 2007 A1
20070208745 Ture Sep 2007 A1
20070214129 Ture Sep 2007 A1
20070220268 Krishnaprasad Sep 2007 A1
20070226810 Hotti Sep 2007 A1
20070234337 Suzuki et al. Oct 2007 A1
20070239858 Banerji et al. Oct 2007 A1
20070244996 Ahmed et al. Oct 2007 A1
20070276905 Durand et al. Nov 2007 A1
20070288612 Hall Dec 2007 A1
20070294369 Ginter et al. Dec 2007 A1
20070294376 Ayachitula et al. Dec 2007 A1
20070299951 Krithivas Dec 2007 A1
20080002588 McCaughan et al. Jan 2008 A1
20080016515 Naim et al. Jan 2008 A1
20080028048 Shekar CS et al. Jan 2008 A1
20080040452 Rao et al. Feb 2008 A1
20080046708 Fitzgerald et al. Feb 2008 A1
20080059959 Chen et al. Mar 2008 A1
20080082467 Meijer et al. Apr 2008 A1
20080130639 Costa-Requena et al. Jun 2008 A1
20080170510 Singh Jul 2008 A1
20080189693 Pathak Aug 2008 A1
20080196043 Feinleib et al. Aug 2008 A1
20080209033 Ginter et al. Aug 2008 A1
20080215668 Hu Sep 2008 A1
20080235266 Huang et al. Sep 2008 A1
20080235361 Crosbie et al. Sep 2008 A1
20080244325 Tyulenev Oct 2008 A1
20080263543 Ramachandran Oct 2008 A1
20080270674 Ginzton Oct 2008 A1
20080288938 DeHaan Nov 2008 A1
20080288939 DeHaan Nov 2008 A1
20080294777 Karve et al. Nov 2008 A1
20080298274 Takashige et al. Dec 2008 A1
20080301666 Gordon et al. Dec 2008 A1
20080301780 Ellison et al. Dec 2008 A1
20080313716 Park Dec 2008 A1
20080320110 Pathak Dec 2008 A1
20090007091 Appiah et al. Jan 2009 A1
20090055901 Kumar et al. Feb 2009 A1
20090064132 Suchy et al. Mar 2009 A1
20090089567 Boland et al. Apr 2009 A1
20090089852 Randolph et al. Apr 2009 A1
20090106291 Ku et al. Apr 2009 A1
20090129597 Zimmer et al. May 2009 A1
20090132682 Counterman May 2009 A1
20090132710 Pelley May 2009 A1
20090158148 Vellanki et al. Jun 2009 A1
20090158272 El-Assir et al. Jun 2009 A1
20090164471 Shen Jun 2009 A1
20090164522 Fahey Jun 2009 A1
20090165099 Eldar et al. Jun 2009 A1
20090172430 Takenouchi Jul 2009 A1
20090228629 Gebhart et al. Sep 2009 A1
20090235349 Lai et al. Sep 2009 A1
20090240835 Adelman et al. Sep 2009 A1
20090249296 Haenel et al. Oct 2009 A1
20090249336 Vasilevsky et al. Oct 2009 A1
20090249473 Cohn Oct 2009 A1
20090259665 Howe et al. Oct 2009 A1
20090265707 Goodman et al. Oct 2009 A1
20090282404 Khandekar et al. Nov 2009 A1
20090285199 Strahs et al. Nov 2009 A1
20090300180 DeHaan Dec 2009 A1
20100023740 Moon et al. Jan 2010 A1
20100049838 DeHaan Feb 2010 A1
20100050169 DeHaan Feb 2010 A1
20100054156 DeHaan Mar 2010 A1
20100057833 DeHaan Mar 2010 A1
20100057890 DeHaan Mar 2010 A1
20100057913 DeHaan Mar 2010 A1
20100057930 DeHaan Mar 2010 A1
20100058307 DeHaan Mar 2010 A1
20100058327 DeHaan Mar 2010 A1
20100058328 DeHaan Mar 2010 A1
20100058330 DeHaan Mar 2010 A1
20100058332 DeHaan Mar 2010 A1
20100058444 DeHaan Mar 2010 A1
20100082799 Dehaan et al. Apr 2010 A1
20100083245 DeHaan Apr 2010 A1
20100100876 Glover et al. Apr 2010 A1
20100128639 DeHaan May 2010 A1
20100131632 DeHaan May 2010 A1
20100131648 Dehaan May 2010 A1
20100138521 Dehaan Jun 2010 A1
20100138526 Dehaan Jun 2010 A1
20100138696 Dehaan Jun 2010 A1
20100217837 Ansari Aug 2010 A1
20100217840 DeHaan et al. Aug 2010 A1
20100217843 DeHaan et al. Aug 2010 A1
20100217848 DeHaan et al. Aug 2010 A1
20100217944 DeHaan et al. Aug 2010 A1
20100218243 DeHaan et al. Aug 2010 A1
20100220584 DeHaan et al. Sep 2010 A1
20100223367 DeHaan Sep 2010 A1
20100223504 DeHaan et al. Sep 2010 A1
20100223607 DeHaan Sep 2010 A1
20100223608 DeHaan et al. Sep 2010 A1
20100223609 DeHaan et al. Sep 2010 A1
20100223610 DeHaan et al. Sep 2010 A1
20100235433 Ansari et al. Sep 2010 A1
20100250907 DeHaan Sep 2010 A1
20100306337 DeHaan Dec 2010 A1
20100306380 DeHaan Dec 2010 A1
20100333084 DeHaan Dec 2010 A1
20110010401 Adams Jan 2011 A1
20110061045 Phillips Mar 2011 A1
20110131304 Henson Jun 2011 A1
20110131384 Henson Jun 2011 A1
20120110458 Brown et al. May 2012 A1
20120151470 Dehaan Jun 2012 A1
20120185559 Wesley et al. Jul 2012 A1
Non-Patent Literature Citations (82)
Entry
Engine. Microsoft® Computer Dictionary, Fifth Edition [online]. Microsoft Press, May 1, 2002. Retrieved on Sep. 29, 2010. Retrieved from the Internet: <URL:http://proquest.safaribooksonline.com/0735614954>.
Platform. Microsoft® Computer Dictionary, Fifth Edition [online]. Microsoft Press, May 1, 2002. Retrieved on Sep. 29, 2010. Retrieved from the Internet: <URL:http://proquest.safaribooksonline.com/0735614954>.
Interface. “IEEE 100 The Authoritative Dictionary of IEEE Standards Terms Seventh Edition,” IEEE STD 100-2000 , vol., No., 2000 [online]. Retrieved on Sep. 8, 2010. Retrieved from the Internet: <URL: http://ieeexplore.ieee.org/servlet/opac?punumber=4116785>.
Network. “IEEE 100 The Authoritative Dictionary of IEEE Standards Terms Seventh Edition,” IEEE STD 100-2000 , vol., No., 2000 [online]. Retrieved on Sep. 29, 2010. Retrieved from the Internet: <URL: http://ieeexplore.ieee.org/servlet/opac?punumber=4116785>.
USPTO Office Action mailed Mar. 31, 2011 for U.S. Appl. No. 12/325,056.
USPTO Office Action mailed Mar. 6, 2012 for U.S. Appl. No. 12/325,056.
USPTO Office Action mailed Jun. 19, 2012 for U.S. Appl. No. 12/325,056.
USPTO Office Action mailed Jun. 28, 2013 for U.S. Appl. No. 12/325,056.
USPTO Notice of Allowance mailed Oct. 21, 2013 for U.S. Appl. No. 12/325,056.
USPTO Office Action mailed Mar. 29, 2010 for U.S. Appl. No. 12/130,424.
USPTO Office Action mailed Dec. 10, 2010 for U.S. Appl. No. 12/130,424.
USPTO Office Action mailed May 2, 2013 for U.S. Appl. No. 12/130,424.
USPTO Office Action mailed Aug. 21, 2013 for U.S. Appl. No. 12/130,424.
USPTO Notice of Allowance mailed Dec. 12, 2013 for U.S. Appl. No. 12/130,424.
USPTO, Office Action for U.S. Appl. No. 12/194,754 mailed Apr. 14, 2010.
USPTO, Final Office Action for U.S. Appl. No. 12/194,754 mailed Dec. 3, 2010.
USPTO, Office Action for U.S. Appl. No. 12/194,754 mailed Oct. 9, 2012.
USPTO, Final Office Action for U.S. Appl. No. 12/194,754 mailed May 21, 2013.
USPTO, Office Action for U.S. Appl. No. 12/194,754 mailed Nov. 25, 2013.
USPTO, Advisory Action for U.S. Appl. No. 12/194,754 mailed Apr. 7, 2011.
USPTO, Advisory Action for U.S. Appl. No. 12/194,754 mailed Jul. 30, 2013.
USPTO Office Action for U.S. Appl. No. 12/395,536, mailed Nov. 8, 2011.
USPTO Office Action for U.S. Appl. No. 12/395,536, mailed Apr. 25, 2012.
USPTO Office Action for U.S. Appl. No. 12/395,536, mailed Nov. 6, 2013.
USPTO Office Action for U.S. Appl. No. 12/395,536, mailed Mar. 24, 2014.
Ziegler et al, “Secure Profile Management in Smart Home Networks,” 2005, Retrieved from the Internet <URL: ieeexploreieee.org/xpls/abs—all.jsp?arnumber=1508274>, pp. 1-5 as printed.
Microsoft, “How SNMP Works,” <http://technet.microsoft.com/en-us/library/cc783142(v=ws.10).aspx>, retrieved Aug. 14, 2012, 9 pages.
Microsoft, “How to configure Network Security for the Snmp Service in Windows Server 2003,” <http://support.microsoft.com/kb/324261>, retrieved Aug. 14, 2012, 3 pages.
“Ellison, UPnP Security ceremonies, 2003, Retrieved from the Internet <URL: upnp.org/specs/sec/UPnP-sec-UPnPSecurityCeremonies-v1.pdf>, pp. 1-18 as printed.”
“No stated author, OSGi Service Platform Service Compendium, Apr. 2007, Retrieved from the Internet <URL://osgi.org/download/r4v41 /r4.cmpn.pdf>, pp. 1-5 as printed.”
“No stated author, Understanding Universal Plug and Play, Retrieved from the Internet <URL:web.archive.org/web/20030501 OOOOOO*/http://www.upnp.org/download/UPNP understandingUPNP.doc>, pp. 1-45 as printed.”
Agarwalla et al. “Automating Provisioning of Complete Software Stack in a Grid Environment,” 2004.
Novak, Judit, “Automatic Installation and Configuration for Large Scale Farms”, 2005.
Quintero et al., “Introduction to pSeries Provisioning”, 2004.
HP Storage Essentials SRM 6.0 Installation Guide. Jan. 2008. HP. 1st ed. Part No. T4283-96113. pp. 1-5, 97-136, 219-228.
HP Storage Essentials SRM 6.0 User Guide. Jan. 2008. HP. 1st ed. Part No. T4238-96114. pp. 1-83.
DeHaan, Michael. “Unified Provisioning”. 2007.
DeHaan, Michael. “Provisioning With Cobbler”. 2007.
Tan et al. “A WBEM Basked Disk Array Management Provider”. 2005. IEEE. 2005 International Conference on Cyberworlds.
Lovelace et al. Managing Disk Subsystems Using IBM TotalStorage Productivity Ceneter. Sep. 2005. IBM. 2nd ed. SG24-7097-01. pp. 1-42.
Grosse, “Repository Mirroring”, 1995.
Anderson et al., “Technologies for Large-Scale Configuration Management”, Dec. 9, 2002.
Butt et al., “Automated Installation of Large-Scale Linux Networks”, 2000.
eBook “Microsoft System Management Server 2003 Administrator's Companion”, Microsoft Press. C2004, Ch. 13, Patch Management, pp. 471-507.
Doc Searls “Linux for Suites”, 2005, Specialized System Consultants Inc., vol. 2005.
Maghraoui et al., “Model Driven Provisioning: Bridging the Gap Between Declarative Object Models and Procedural Provisioning Tools”, 2006.
DeHaan et al., “Methods and Systems for Secure Gated File Deployment Associated with Provisioning”, U.S. Appl. No. 12/393,754, filed Feb. 26, 2009.
DeHaan, “Systems and Methods for Integrating Software Provisioning and Configuration Management”, U.S. Appl. No. 12/395,379, filed Feb. 27, 2009.
DeHaan, “Systems and Methods for Abstracting Software Content Management in a Software Provisioning Environment”, U.S. Appl. No. 12/398,273, filed Feb. 27, 2009.
DeHaan et al., “Systems and Methods for Providing a Library of Virtual Images in a Software Provisioning Environment”, U.S. Appl. No. 12/395,351, filed Feb. 27, 2009.
DeHaan et al., “Systems and Methods for Inventorying Un-Provisioned Systems in a Software Provisioning Environment”, U.S. Appl. No. 12/391,588, filed Feb. 24, 2009.
DeHaan et al., “Systems and Methods for Managing Configurations of Storage Devices in a Software Provisioning Environment”, U.S. Appl. No. 12/393,613, filed Feb. 26, 2009.
DeHaan et al., “Systems and Methods for Collecting and Altering Firmware Configurations of Target Machines in a Software Provisioning Environment”, U.S. Appl. No. 12/393,319, filed Feb. 26, 2009.
DeHaan et al., “Methods and Systems for Replicating Provisioning Servers in a Software Provisioning Environment”, U.S. Appl. No. 12/392,508, filed Feb. 25, 2009.
DeHaan, “Systems and Methods for Cloning Target Machines in a Software Provisioning Environment”, U.S. Appl. No. 12/473,014, filed May 27, 2009.
DeHaan, “Systems and Methods for Providing Configuration Management Services from a Provisioning Server”, U.S. Appl. No. 12/414,941, filed Mar. 31, 2009.
DeHaan, “Systems and Methods for Retiring Target Machines by a Provisioning Server”, U.S. Appl. No. 12/475,427, filed May 29, 2009.
DeHaan, “Systems and Methods for Message-Based Installation Management Using Message Bus,” U.S. Appl. No. 12/495,077, filed Jun. 30. 2009.
Henson, “Systems and Methods for Integrating Storage Resources from Storage Area Network in Machine Provisioning Platform,” U.S. Appl. No. 12/628,041, filed Nov. 30, 2009.
Henson, “Systems and Methods for Mounting Specified Storage Resources from Storage Area Network in Machine Provisioning Platform,” U.S. Appl. No. 12/627,988, filed Nov. 20, 2009.
Michael DeHaan, “Methods and Systems for Provisioning Software,” U.S. Appl. No. 11/763,315, filed Jun. 14, 2007.
Michael DeHaan, “Methods and Systems for Provisioning Software,” U.S. Appl. No. 11/763,333, filed Jun. 14, 2007.
DeHaan, “Methods and Systems for Centrally Managing Provisioning Servers,” U.S. Appl. No. 12/201,193, filed Aug. 29, 2006.
DeHaan, “Methods and Systems for Assigning Provisioning Servers in a Software Provisioning Environment,” U.S. Appl. No. 12/201,646, filed Aug. 29, 2008.
USPTO Office Action mailed Oct. 7, 2010 for U.S. Appl. No. 11/763,315.
USPTO Office Action mailed Apr. 20, 2011 for U.S. Appl. No. 11/763,315.
USPTO Notice of Allowance mailed Nov. 2, 2011 for U.S. Appl. No. 11/763,315.
USPTO, Advisory Action for U.S. Appl. No. 11/763,315 mailed Jun. 24, 2011.
USPTO Notice of Allowance mailed May 15, 2012 for U.S. Appl. No. 13/399,998.
USPTO Office Action mailed Oct. 7, 2010 for U.S. Appl. No. 11/763,333.
USPTO Office Action mailed Apr. 20, 2011 for U.S. Appl. No. 11/763,333.
USPTO, Advisory Action for U.S. Appl. No. 11/763,333 mailed Jun. 23, 2011.
USPTO Notice of Allowance mailed Oct. 27, 2011 for U.S. Appl. No. 11/763,333.
USPTO Office Action mailed Dec. 20, 2011 for U.S. Appl. No. 12/239,690.
USPTO Office Action mailed May 14, 2012 for U.S. Appl. No. 12/239,690.
USPTO Office Action mailed Dec. 19, 2012 for U.S. Appl. No. 12/239,690.
USPTO Office Action mailed Apr. 16, 2013 for U.S. Appl. No. 12/239,690.
USPTO Office Action mailed Feb. 29, 2012 for U.S. Appl. No. 12/395,351.
USPTO Office Action mailed Jun. 14, 2012 for U.S. Appl. No. 12/395,351.
USPTO Office Action mailed Oct. 11, 2012 for U.S. Appl. No. 12/395,351.
USPTO Office Action mailed Oct. 12, 2010 for U.S. Appl. No. 12/325,056.
USPTO, Advisory Action for U.S. Appl. No. 12/130,424, mailed Feb. 24, 2011, 3 pages.
Related Publications (1)
Number Date Country
20100223369 A1 Sep 2010 US