Patent application number | Description | Published |
20100217843 | SYSTEMS AND METHODS FOR COLLECTING AND ALTERING FIRMWARE CONFIGURATIONS OF TARGET MACHINES IN A SOFTWARE PROVISIONING ENVIRONMENT - A provisioning server can provide and interact with a firmware tool on target machines. The firmware toot can communicate with the firmware of the target machines and collect data representing the configuration of the firmware of the target machines, independent of the types of the target machines. To communicate independent of the type of target machine, the firmware tool can include a translation library. The translation library enables the firmware tool to receive common instructions for interacting with firmware and convert those common instructions into specific instructions that are compatible with different types of the target machines. | 08-26-2010 |
20100217848 | SYSTEMS AND METHODS FOR INVENTORYING UN-PROVISIONED SYSTEMS IN A SOFTWARE PROVISIONING ENVIRONMENT - A provisioning server can utilize an inventory tool on new target machines in order to collect specification data from the target machines, prior to provisioning software. The inventory tool can be configured to operate on the new target machines without software, such as an operating system, being installed on the new target machines. The inventory tool can be configured to communicate with the hardware of the new target machines and collect data representing the specifications of the new target machines. The inventory tool can be configured to operate and execute on any new target machine regardless of the type and configuration of the new target machine. | 08-26-2010 |
20100217944 | SYSTEMS AND METHODS FOR MANAGING CONFIGURATIONS OF STORAGE DEVICES IN A SOFTWARE PROVISIONING ENVIRONMENT - A provisioning server can provide and interact with a storage device tool on target machines. The storage device tool can communicate with the storage devices of the target machines, independent of the types of the storage devices. To communicate independent of the type of the storage device, the storage device tool can include a translation library. The translation library enables the storage device tool to receive common commands and/or instructions for interacting with the storage devices and convert those common commands and/or instructions into specific commands and/or instructions that are compatible with different types of the storage devices. | 08-26-2010 |
20100218243 | METHODS AND SYSTEMS FOR SECURE GATE FILE DEPLOYMENT ASSOCIATED WITH PROVISIONING - A software provisioning server can be configured to communicate with a certificate authority to evaluate security credential requests received from one or more target machines prior to a software installation. The certificate authority can issue certificates to the one or more target machines and notify an administrator and the software provisioning server of the issued certificates. The software provisioning server can manage the software installation to the one or more target machines based on the issued certificates and other specifications. | 08-26-2010 |
20100220584 | SYSTEMS AND METHODS FOR AUTOMATICALLY GENERATING SYSTEM RESTORATION ORDER FOR NETWORK RECOVERY - Embodiments relate to systems and methods for automatically generating a system restoration order for network recovery. A set of managed machines, such as personal computers or servers, can be managed by a network management platform communicating with the machines via a secure channel. The network management platform can access a dependency map indicating a required order for restoration of machines or nodes on a network. The network management platform likewise access a reverse kickstart file for each machine to be automatically restored in order to ensure proper functioning of the network, and extract a current configuration of that machine for purposes of restoring the overall network. | 09-02-2010 |
20100223274 | SYSTEMS AND METHODS FOR GENERATING A CHANGE LOG FOR FILES IN A MANAGED NETWORK - Embodiments relate to systems and methods for generating a change log for files in managed network. A set of managed machines, such as personal computers or servers, can be managed by a network management platform communicating with the machines via a secure channel. The network management platform can employ a package management tool to manage files stored or hosted in the managed network. The network management platform can further employ a change monitor or other logic to locate additional files located in the managed network but that may not be under the control of or registered to the package management tool. A systems administrator or other user can invoke both the package management tool and the change monitor logic to initiate a discovery process and locate all available files associated with the network, and generate a unified change log recording all available files and/or their changes. | 09-02-2010 |
20100223369 | SYSTEMS AND METHODS FOR DEPOPULATION OF USER DATA FROM NETWORK - 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 lDs, 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). | 09-02-2010 |
20100223375 | SYSTEMS AND METHODS FOR SEARCHING A MANAGED NETWORK FOR SETTING AND CONFIGURATION DATA - A network management server can be configured to search the components of computing systems and devices in a managed network for specified settings and configurations in order to determine if the computing systems or devices contain the specified settings and configurations. The network management server can receive a request containing search parameters. The search parameters can identify specific settings and configurations to search for in the components of the systems and devices of the managed network. The network management server can initiate a search of the components of all the systems and devices in the managed network based on the search parameters. | 09-02-2010 |
20100223473 | SYSTEMS AND METHODS FOR NETWORK MANAGEMENT USING SECURE MESH COMMAND AND CONTROL FRAMEWORK - Embodiments relate to systems and methods for network management using a secure mesh command and control framework. A network management server can communicate with a set of supervisory hosts, which in turn communicate with an underlying set of targets. The set of targets can have associated digital certificates which can be authenticated by common certificate authorities. A controlled target can authenticate one or more other target requesting access to the controlled target via the trusted common certificate authority. One authenticated target can therefore mesh on a trusted basis with another target to perform installation, monitoring, testing, or other activities directly on the target of interest, without channeling commands through an intervening supervisory host. | 09-02-2010 |
20100223504 | SYSTEMS AND METHODS FOR INTERROGATING DIAGNOSTIC TARGET USING REMOTELY LOADED IMAGE - Embodiments relate to systems and methods for interrogating one or more diagnostic targets using a remotely loaded image. A set of managed machines, such as personal computers or servers, can be managed by a network management engine communicating with the machines via a secure channel. The network management engine can access a selected diagnostic target to temporarily deactivate the installed native operating system on that target, insert a substitute operating environment, and remotely interrogate the target to perform hardware, software, security, or other diagnostics or installs. The network management engine can connect to the diagnostic target, extract security keys from the native operating environment, remotely load the substitute environment, and then perform diagnostic or provisioning activities while the native environment is deactivate and the diagnostic target is effectively off-network. Installations, diagnostics, or other activities that require the diagnostic target to be isolated from other machines can therefore be safely conducted. | 09-02-2010 |
20100223609 | SYSTEMS AND METHODS FOR AUTOMATIC DISCOVERY OF NETWORK SOFTWARE RELATIONSHIPS - Embodiments relate to systems and methods for automatic discovery of network software relationships. A set of managed machines, such as personal computers or servers, can be managed by a network management platform communicating with the machines via a secure channel. The network management platform can issue a set of discovery commands interrogating nodes of the network to report software or services which they consume. The network management platform can build a dependency map encoding the dependency or other relationships between nodes in the managed network based on their use of software resources. Network restorations can therefore be conducted in a rational order, maintaining stability in the restored nodes and network. | 09-02-2010 |
20110055544 | SYSTEMS AND METHODS FOR TRACKING A HISTORY OF CHANGES ASSOCIATED WITH SOFTWARE PACKAGES AND CONFIGURATION MANAGEMENT IN A COMPUTING SYSTEM - In order to track actions performed by a package manager or a configuration management system, a computing system can be configured to include a tagging tool. The tagging tool can be configured to cooperate with the package manager and the configuration management system in order to determine and generate a history of the actions performed by the package manager and the configuration management system. The history can include a description of the actions, the reasons why the actions were performed, and a list and description of the software programs, files, and software libraries that are affected by the actions. | 03-03-2011 |
20110055636 | SYSTEMS AND METHODS FOR TESTING RESULTS OF CONFIGURATION MANAGEMENT ACTIVITY - Embodiments relate to systems and methods for testing results of configuration management activity. In embodiments, a configuration management server can control and maintain the configuration state of one or more targets, hosts, servers, clients, or other machines in a managed. In aspects, a testing tool hosted on the configuration management server can verify the correct implementation of configuration instructions. In embodiments, the testing tool can access or receive an anticipated or target configuration state for one or more target(s) or other machines, indicating the status of services, memory, security, storage, and/or other configuration parameters after a selected configuration command is to be transmitted and run on the recipient machine. After the configuration change or update is performed, the test tool can receive results indicating the actual configuration state achieved after running the configuration management command(s), and compare those to the anticipated configuration state. Any discrepancies can be flagged, and corrective commands can be issued. | 03-03-2011 |
20110055669 | SYSTEMS AND METHODS FOR DETECTING MACHINE FAULTS IN NETWORK USING ACOUSTIC MONITORING - Embodiments relate systems and methods for detecting machine faults in a network using acoustic monitoring. In embodiments, one or more servers, clients, or other machines in a managed network can have a microphone or other acoustic sensor integrated into motherboard or other hardware. The sensor can sample acoustic signals from inside or near the machine, and can digitize that data. The resulting set of acoustic data can be transmitted to a management server or other destination for analysis of the operating sounds related to that machine. For instance, the acoustic data can be analyzed to detect indications of a failed or failing hard drive, for instance by detecting spindle whine or head movement noises, or a failed or failing power supply based on other sounds. The management server can respond to potential fault events for instance by issuing configuration commands, such as instructions to power down the malfunctioning component. | 03-03-2011 |
20110055826 | SYSTEMS AND METHODS FOR TRACKING A HISTORY OF CHANGES ASSOCIATED WITH SOFTWARE PACKAGES IN A COMPUTING SYSTEM - In order to track actions performed by a package manager, a computing system can be configured to include a tagging tool. The tagging tool can be configured to cooperate with the package manager in order to determine and generate a history of the actions performed by the package manager. The history can include a description of the actions, the reasons why the actions were performed, and a list and description of the software programs, files, and software libraries that are affected by the actions. | 03-03-2011 |
20110078301 | SYSTEMS AND METHODS FOR DETECTING NETWORK CONDITIONS BASED ON CORRELATION BETWEEN TREND LINES - Embodiments relate systems and methods for detecting network conditions based on a correlation between trend lines. In embodiments, a network management server can monitor the status and operation of network machines, such as servers or targets, as well as network transmission hardware (e.g. routers). Streams of network operation data from those sources can be captured and stored. The management server or other logic can examine the network operation data to identify trend lines for network conditions, such as application faults, attempted intrusions, or other events or conditions. Trend line data can be treated to generate second or other higher-order derivatives, such as third-order derivatives or others. A time correlation between two or more trend lines and/or their higher order derivatives, for instance, the occurrence of a peak value in the same time window, can be used to identify an event, state or condition. | 03-31-2011 |
20110078302 | SYSTEMS AND METHODS FOR DETECTING NETWORK CONDITIONS BASED ON DERIVATIVES OF EVENT TRENDING - Embodiments relate systems and methods for detecting network conditions based on derivatives of event trending. In embodiments, a network management server can monitor the status and operation of network machines, such as servers or targets, as well as network transmission hardware (e.g. routers). Streams of network operation data from those sources can be captured and stored. The management server or other logic can examine the network operation data to identify trend lines for network conditions, such as application faults, attempted intrusions, or other events or conditions. trend line data can be treated to generate second or other higher-order derivatives, such as third-order derivatives representing the rate of change of acceleration (or jerk) in the time series of one or more conditions. The presence of acceleration or jerk for one or more trend lines, such as attempted network intrusions, can reflect an event and trigger a flag or other automated response. | 03-31-2011 |
20110107300 | SYSTEMS AND METHODS FOR UTILIZING A HISTORY OF CHANGES ASSOCIATED WITH SOFTWARE PACKAGES AND CONFIGURATION MANAGEMENT TO MANAGE MULTIPLE COMPUTING SYSTEMS - An administrator system can utilize a history generated by a tagging tool to determine the current configuration of computing systems. The administrator system can utilize the current configuration to verify that the computing systems have been configured properly and verify, over time, that the computing systems maintain the desired configuration. The administrator system can compare the current configuration with the desired configuration for the computing systems. | 05-05-2011 |
20110107419 | SYSTEMS AND METHODS FOR IMPROVED IDENTIFICATION AND ANALYSIS OF THREATS TO A COMPUTING SYSTEM - A security tool can access a tagging tool and the history generated by the tagging tool in order to identify potential threats and analyze the identified threats. When a potential threat is detected or an actual threat is identified, the security tool can request the history of actions from the tagging tool corresponding to the threat. The security tool can compare the potential or actual threat with the history of any action recorded by the tagging tool in order to classify a potential threat as an actual threat or determine the source or cause of an actual threat. | 05-05-2011 |
20110131564 | SYSTEMS AND METHODS FOR GENERATING A VERSION IDENTIFIER FOR A COMPUTING SYSTEM BASED ON SOFTWARE PACKAGES INSTALLED ON THE COMPUTING SYSTEM - An administrator system can generate a version identifier for a computing system based on the software packages installed on a computing system. The version identifier can represent the software packages installed on the computing system. The administrator system can identify the software packages installed on a computing system and data specific to the software packages. The administrator system can apply a hash function to the specific data to generate hashed data. Then, the administrator system can concentrate the hashed data to generate the version identifier. | 06-02-2011 |
20110131565 | SYSTEMS AND METHODS FOR MANAGING A NETWORK OF COMPUTER SYSTEM USING A VERSION IDENTIFIER GENERATED BASED ON SOFTWARE PACKAGES INSTALLED ON THE COMPUTING SYSTEMS - An administrator system can generate a version identifier for a computing system based on the software packages installed on a computing system. The version identifier can represent the software packages installed on the computing system. The administrator system can utilize the version identifier to manage a network of computing systems. The administrator system can compare the version identifiers of the computing system to verify that the computing system have the same software packages installed. Likewise, the administrator system can compare the version identifiers of the computing system to a test version identifier. | 06-02-2011 |
20110131566 | SYSTEMS AND METHODS FOR MANAGING A NETWORK OF COMPUTER SYSTEM USING A VERSION IDENTIFIER GENERATED BASED ON SOFTWARE PACKAGES INSTALLED ON THE COMPUTING SYSTEMS - An administrator system can generate a version identifier for a computing system based on the software packages installed on a computing system. The version identifier can represent the software packages installed on the computing system. The administrator system can utilize the version identifier to manage a network of computing systems. The administrator system can compare the version identifiers of the computing system to verify that the computing system have the same software packages installed. Likewise, the administrator system can compare the version identifiers of the computing system to a test version identifier. | 06-02-2011 |
20110214018 | SYSTEMS AND METHODS FOR DIAGNOSTIC NOTIFICATION VIA PACKAGE UPDATE MANAGER - Embodiments relate to systems and methods for diagnostic notification via a package update manager. A physical or virtual client machine can host a set of installed software packages, including operating system, application, and/or other software. A package manager tracks the set of installed packages and updates available for the installed set. A notification tool, in conjunction with the package manager, can monitor the user's selection of package update options, and compare those updates to a diagnostic database and/or current state of the client machine. Based on those determinations, the notification tool can generate notifications to the user advising them of potential conflicts, faults, or other conditions that may arise due to, or may surround, the prospective package update. The notification can permit the user to continue or terminate selected updates, and the notification tool can re-analyze any potential faults after an update is completed. | 09-01-2011 |
20110214021 | SYSTEMS AND METHODS FOR INITIATING SOFTWARE REPAIRS IN CONJUNCTION WITH SOFTWARE PACKAGE UPDATES - Embodiments relate to systems and methods for systems and methods for initiating software repairs in conjunction with software package updates. A physical or virtual client machine can host a set of installed software packages, including operating system, application, and/or other software. A package manager tracks the set of installed packages and updates available for the installed set. A notification tool, in conjunction with the package manager, can monitor the user's selection of package update options, and compare those updates to a diagnostic database, current state of the client machine, or other resources. Based on those determinations, the notification tool can generate one or more potential software repair actions to correct or avoid potential conflicts, faults, or other conditions that may arise due to, or may surround, the prospective package update. | 09-01-2011 |
20110214111 | SYSTEMS AND METHODS FOR DETECTING COMPUTING PROCESSES REQUIRING REINITIALIZATION AFTER A SOFTWARE PACKAGE UPDATE - Embodiments relate to systems and methods for detecting computing processes requiring reinitialization after a software package update. A physical or virtual client machine can host a set of installed software packages, including operating system, application, and/or other software. An restart tool can track the set of executing processes on the client, and identify both corresponding executable files which spawned those processes, and any installed package updates which correspond to those executable files. The restart tool can compare the timestamp or other indicator of the version of the executable file which spawned currently running processes, and the timestamp or other indicator of any newer executable files which may have been installed after the application or other process was initiated. A user can be alerted to terminate and restart any processes running off of out-of-date executable files, or in embodiments those reinitializations can be set to be performed automatically. | 09-01-2011 |
20110214112 | SYSTEMS AND MEHTODS FOR GENERATING PREDICTIVE DIAGNOSTICS VIA PACKAGE UPDATE MANAGER - Embodiments relate to systems and methods for generating predictive diagnostics via a package update manager. A physical or virtual client machine can host a set of installed software packages, including operating system, application, and/or other software. A package manager tracks the set of installed packages and updates available for the installed set. A notification tool, in conjunction with the package manager, can monitor the user's selection of package update options, and compare those updates to a diagnostic database, a current state of the client machine, and/or other resources. Based on those determinations, the notification tool can generate notifications to the user advising them of potential conflicts, faults, or other conditions that may arise due to, or may surround, the prospective package update. The notification can permit the user to continue or terminate selected updates, before those updates are attempted and cause potential conflicts. | 09-01-2011 |
20110214114 | SYSTEMS AND METHODS FOR DETERMINING COMPATIBILITY OF A SOFTWARE PACKAGE UPDATE USING A VERSION IDENTIFIER - An administrator system can generate a version identifier for a computing system based on the software packages installed on a computing system. The administrator system can utilize the version identifier to determine if software package updates will install properly on a computing system. When the computing system request an update to a software package, the administrator system can generate a version identifier for the software package, as installed on the computing system and to be updated. The administrator system can compare the generated version identifier to a test version identifier. The test version identifier can be a version identifier generated for a version of an exemplary software package known to properly install the update. Once compared, the administrator system can notify the user of the computing system of the comparison, for example, if the version identifier and the test version identifier are different indicating potential problems in the update. | 09-01-2011 |
20110214116 | SYSTEMS AND METHODS FOR MANAGING SOFTWARE PACKAGE UPDATES USING COMMUNICATION PIPES - Embodiments relate to systems and methods for managing software package updates using communication pipes. According to aspects, one or more client machines can initiate package update activity, for instance a software package update using a package manager. In aspects, instead of accessing a package repository directly via the update manager or utility, the package manager can be configured to communicate with a set of communication pipes, such as inter-process communication (IPC) sockets, pipes, or other resources. The user can thereby invoke a pipeable update process, perform enhanced update activity, and share the results with various programs or threads. For example, the user can set the update process to generate a report of prospective or available update activity, without actually implementing the updates. Error codes during these and other types of diagnostic processing can be generated and logged for debugging purposes. | 09-01-2011 |
20110214118 | SYSTEMS AND METHODS FOR GENERATING AND STORING TRANSLATION INFORMATION AS PACKAGE METADATA - Embodiments relate to systems and methods for generating and storing translation information as package metadata. A physical or virtual client machine can host a set of installed software packages, including operating system, application, and/or other software. A package manager tracks the set of installed packages and language resources available for the installed set. The package manager can host or access a set of package attributes which include language specifications which indicates a language that should be used for search, display, and/or other activities. The language specifications be used to link to remote a remote repository storing various language metadata, including translations of source text. The resulting translated descriptions of source text from applications or other objects can be received and locally stored as translation information on the client machine. Translations can be periodically generated and/or updated. | 09-01-2011 |
20110265073 | SYSTEMS AND METHODS FOR GENERATING ENCODED IDENTIFICATIONS OF SELECTED SUBSETS OF INSTALLED SOFTWARE PACKAGES ON A CLIENT MACHINE - Embodiments relate to systems and methods for generating encoded identifications of selected subsets of installed software packages on a client machine. A physical or virtual client machine can host a set of installed software packages, including operating system, application, and/or other software. A package manager tracks the set of installed packages and updates available for the installed set. The package manager can be configured to capture an inventory of the installed packages, and generate an encoded identification of one or more selected subsets of the set of hosted or installed packages based on size, timestamp, and/or other attributes of the subsets and/or constituent files. An administrator or other user can for instance select only that subset or subsets related to a certain project, application, user group, or other selection criteria, and generate encoded identifications of those subsets for package updating, network management, and/or other purposes. | 10-27-2011 |
20110265074 | SYSTEMS AND METHODS FOR GENERATING EXPORTABLE ENCODED IDENTIFICATIONS OF NETWORKED MACHINES BASED ON INSTALLED PACKAGE PROFILES - Embodiments relate to systems and methods for generating exportable encoded identifications of networked machines based on installed package profiles. A physical or virtual client machine can host a set of installed software packages, including operating system, application, and/or other software. A package manager tracks the set of installed packages and updates available for the installed set. The package manager can be configured to capture an inventory of the installed packages, and generate an encoded identification of the entire package complement and/or selected subsets of those packages. In aspects, the encoded identification can be based on a set of attributes of the installed packages and/or their constituent files, such as file names, version numbers, size, and/or other attributes. The encoded identification for the client machine can be transmitted to one or more remote management platforms, such as package servers, network management servers, or others for remote operations on the client machine. | 10-27-2011 |
20110296248 | SYSTEMS AND METHODS FOR RESTORING MACHINE STATE HISTORY RELATED TO DETECTED FAULTS IN PACKAGE UPDATE PROCESS - Embodiments relate to systems and methods for storing machine state history related to detected faults in a package update process. A classification tool can interface with a data store that can store machine state data on a client. The classification tool can record an initial machine state on the client and initiate a package update on the client. The classification tool can further record an updated machine state of the client subsequent to initiating the package update and detect a fault condition in the client subsequent to initiating the package update. The classification tool can examine the initial machine state and the updated machine state to categorize one or more causes of the fault condition as either related to the package update or to systemic conditions of the client. The classification tool can further notify a user of the client of the one or more causes of the fault condition. | 12-01-2011 |
20110296390 | SYSTEMS AND METHODS FOR GENERATING MACHINE STATE VERIFICATION USING NUMBER OF INSTALLED PACKAGE OBJECTS - Embodiments relate to systems and methods for generating a machine state verification using a number of installed package objects. A physical or virtual client machine can host a set of installed software packages, including operating system, application, and/or other software. A package manager installed on the client machine can track the installed package complement, and updates available for those packages. To verify that a target of a package update is prepared and in the correct state to receive the update, the package manager inventory the set of package objects installed on the client machine. The resulting sum can be reported to a remote management platform, such as a package server. The counted package objects can be the packages themselves, and/or their set of component files. Machines having a package sum that does not match an expected target number can have a package re-installation performed, and/or other diagnostics carried out. | 12-01-2011 |
20110296393 | SYSTEMS AND METHODS FOR GENERATING AN ENCODED PACKAGE PROFILE BASED ON EXECUTING HOST PROCESSES - Embodiments relate to systems and methods for generating an encoded package profile based on executing host processes. A physical or virtual client machine can host a set of installed software packages, including operating system, application, and/or other software. A package manager tracks the set of installed packages and updates available for the installed set. The package manager and/or other logic can identify currently executing processes on the client, and determine which package(s) corresponding to that set of executing processes are hosted on the client. The package manager can generate a report to a package server and/or other remote management platform to perform management operations on the client, such as, for example, to terminate executing processes on a target client to permit package update processes to take place. Other network management actions, such as inventorying or grouping virtual machines in a cloud or other network, can likewise be performed. | 12-01-2011 |
20110296394 | SYSTEMS AND METHODS FOR GENERATING CACHED REPRESENTATIONS OF ENCODED PACKAGE PROFILE - Embodiments relate to systems and methods for generating cached representations of an encoded package profile. A physical or virtual client machine can host a set of installed software packages, including operating system, application, and/or other software. A package manager installed on the client machine can track the installed package complement, and updates available for those packages. The package manager can be configured to capture attributes of the set of installed packages, and generate an encoded identification of the installed packages using a hash or other algorithm. The encoded identification can be transmitted to one or more package servers or other management platform. The package server(s) can receive and decode the identifier, and insert that identifier and other package-related data into a local package cache. The package server(s) or other platform can configure package update or other activity using the cached representation of package profiles for one or more client machines. | 12-01-2011 |
20110296395 | SYSTEMS AND METHODS FOR GENERATING CLIENT QUALIFICATION TO EXECUTE PACKAGE UPDATE MANAGER - A compatibility tool can certify compliance between software packages managers, used by or known to a user, and software packages to be updated or installed on a computing system. Additionally, the compatibility tool can identify a software package manager that is compatible with the software packages to be updated or installed, if the user does not have or know of a compatible software package manager. To certify software package managers or identify compatible software package managers, the compatibility tool can maintain a database of software package managers associated with software packages that are compatible with the software package managers. | 12-01-2011 |
20110296397 | SYSTEMS AND METHODS FOR GENERATING CACHED REPRESENTATIONS OF HOST PACKAGE INVENTORIES IN REMOTE PACKAGE REPOSITORIES - Embodiments relate to systems and methods for generating cached representations of host package inventories in remote package repositories. A physical or virtual client machine can host a set of installed software packages, including operating system, application, and/or other software. A package manager installed on the client reports an inventory of the installed packages to one or more package servers. The package server(s) can receive the inventory from machines populating the managed network, and generate an encoded identification for each constituent package, such as a hash-based output based on package attributes. The encoded identification and other data can be stored to an aggregate package cache in the one or more package servers, for more efficient management of the host machines in the managed network. In embodiments, the package update files for each identifier can also be stored in the cache for even more efficient inventorying and package update operations. | 12-01-2011 |
20110296398 | SYSTEMS AND METHODS FOR DETERMINING WHEN TO UPDATE A PACKAGE MANAGER SOFTWARE - Embodiments relate to systems and methods for determining when to update a package manager software on a client. An update tool can interface with a package manager running a first version of the package manager software to inspect an available update to a package installed on the client. The update tool can determine that a second version of the package manager software is require to install the update to the package. The update tool can access the second version of the package manager software, remove the first version of the package manager software from the package manager, and unpack and install the second version of the package manager software on the package manager. Further, the update tool can install the update to the package installed on the client, and can update other resources associated with the client as appropriate. | 12-01-2011 |
20120079471 | SYSTEMS AND METHODS FOR AUTOMATIC UPGRADE AND DOWNGRADE IN PACKAGE UPDATE OPERATIONS - Embodiments relate to systems and methods for automatic upgrade and downgrade in package update operations. A physical or virtual client machine can host an installed software distribution including a set of installed software packages, such as an operating system, application, and/or other software. A package manager on the client can manage the set of installed packages, and report the installed distribution including version and component packages to one or more package servers. When a distribution upgrade is initiated, the package manager and/or other distribution logic can analyze the target distribution, to determine whether each package in the target distribution represents the most-current version of each component package. Packages which represent the most-current can be installed. Packages which do not represent the most-current version, e.g. due to slippage in vendor updates or versions, can be substituted with a most-current version automatically retrieved from a software repository or other source. | 03-29-2012 |
20120137283 | SYSTEMS AND METHODS FOR TRACKING COMPUTING SYSTEMS UTILIZING SOFTWARE REPOSITORIES - A software repository can capture and record a universal unique identifier (UUID) associated with a software package manager accessing the software repository. To capture the UUID, the software repository can be encoded as a base Universal Resource Locator (URL) that includes a redirection (e.g. undefined field) to capture the UUIDs of the software package managers. Once captured, the UUIDs can be stored in a record along with any other relevant information such as the software packages downloaded, the date/time of download, and the like. | 05-31-2012 |