To know more about what information is sent back to site,refer įile Collection Cycle: This action is to search for specific file that you have defined in client Agent settings(Software inventory-collect Files). If you accidentally delete a computer from the configmgr console, do not be panic, it will automatically 'come back' if it is still active on the network.For this to happen,wait for the next heartbeat inventory cycle or try running Discovery Data Collection Cycle using manual method or use custom tools or script based. This action will resend the client information to site and keeping the client record Active ‘I am live’,also responsible to submits a client's installation status to its assigned site(Status: Yes).If you are migrating the client from SP1 to R2 or R2 to CU1 ,it takes time to get the client version update in Console and update action is carried out by this Cycle.Heartbeat Discovery actions are recorded on the client in the InventoryAgent.log The default value is set to run every 7 days.ĭiscovery Data Collection Cycle : This actions can be considered as Heartbeat Discovery cycle. This action will re-evaluates the requirement rules for all deployments and make sure the application is installed on the computer. More information about Client agent settings and configuration ,refer Īpplication Deployment Evaluation Cycle: This evaluation Cycle is applicable to software deployments (applications).

By default ,if client is installed correctly and assigned to site ,you will around 11 actions (at least I see on my client) which you can run independently from schedules that are configured in Configuration Manager Console.Īll these actions can be configured using Client Agent settings in SCCM console and assign these settings to collections with priority.

This Blog post brings up some basics about Configmgr Client Actions, what they are and what each action does.Īfter you have installed the Configuration manager Client on computers, Client will get install (refer log ccmsetup.log for more information ) with exit code 0 and It takes little while ,to register the client in Configuration manager Database, assigned to Site, load policies etc.Īfter a while, you can open Configuration manager applet from Control panel (shortcut to use: control smscfgrc from Run Command), go to Actions, you should see more than 2 actions, if not ,as usual start troubleshooting by looking into logs.

Control panel configuration manager