Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: Embodiments relate to systems and methods for secure distributed storage. In aspects, a set of remote storage hosts, such as personal computers, servers, media devices, cell phones, or others, can subscribe or register to provide storage via a cloud-based or other distributed network. Source data from an originating computer, such as a data file, can be decomposed into data storage subunits, each of which is encrypted via a cloud management system or other logic or control. The data storage subunits can comprise data blocks or even or uneven size. The set of encrypted data storage subunits can be registered to a table or other record, and disseminated to the remote storage hosts. In the event of data loss at the originating computer or at other times, the remotely stored data storage subunits can be extracted, decrypted, and reassembled to reconstruct the original source data.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

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 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).

Abstract: 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.

Abstract: 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.