The Application Deployment Evaluation Cycle tool re-evaluates the requirement rules for all deployments. For applications that are required but not installed, executing the Application Deployment Evaluation Cycle will prompt ConfigMgr to trigger a re-install. The default ConfigMgr runtime value is 7 days.
The Discovery Data Collection Cycle prompts the client to generate a new discovery data record (DDR). when the DDR is processed by the site server, Discovery Data Manager adds or updates resource information from the DDR in the site database.
When a file is specified for collection, the ConfigMgr software inventory agent searches for that file when it runs a software inventory scan on each client in the site. If the software inventory client agent finds a file that should be collected, the file is attached to the inventory file and sent to the site server. This action differs from software inventory in that it actually sends the file to the site server, so that it can be later viewed using Resource Explorer. This is part of the ConfigMgr inventory functionality.
The Hardware Inventory Cycle Tool collects information such as available disk space, processor type, and operating system about each computer. This is part of the ConfigMgr inventory functionality.
The client downloads its policy on a schedule. By default, this value is configured to every 60 minutes and is configured with the option Policy polling interval (minutes). However, there might be occasions when you want to initiate ad-hoc policy retrieval from the client. For example, in a troubleshooting scenario or when testing. This action initiates ad-hoc machine policy retrieval from the client outside its scheduled polling interval.
This tool sends State Messages that are cached on the ConfigMgr client to the ConfigMgr server.
This tool collects software inventory data directly from files (such as .exe files) by inventorying the file header information. Configuration Manager can also inventory unknown files — files that do not have detailed information in their file headers. This provides a flexible, easy-to-maintain software inventory method. You can also have Configuration Manager collect copies of files that you specify. Software inventory and collected file information for a client can be viewed using Resource Explorer. This is a part of ConfigMgr inventory functionality.
This tool collects the data that allows you to monitor and client software usage.
This tool initiates a scan for software updates compliance. Before client computers can scan for software update compliance, the software updates environment must be configured.
Just after a software update installation completes, a scan is initiated to verify that the update is no longer required and to create a new state message that indicates the update has been installed. When the installation has finished but a restart is necessary, the state will indicate that the client computer is pending a restart.
This tool clears State Messages that are cached on the ConfiMgr client.
This tool prompts the Product Source Update Manager to complete a full update cycle. When you install an application using Windows Installer, those Windows Installer applications try to return to the path they were installed from when they need to install new components, repair the application, or update the application. This location is called the Windows Installer source location. Windows Installer Source Location Manager can automatically search Configuration Manager distribution points for the source files, even if the application was not originally installed from a distribution point.