![]() This client agent is installed but has not yet retrieved or processed policy. Especially important is to note the Actions tab and the total number of tabs as shown in Figure 3. ![]() The easy way to confirm that the client is retrieving and processing SCCM policy is to first look at the Configuration Manager Properties dialog. For example, the client may not be able to communication with the Management Point, or the client’s Site Code may not match the site’s assigned code. The client agent can still be nonfunctional. Seeing the correct information on the General tab is nice but isn’t verification of functionality. The administrator sees the client properties, verifies that the Assigned Management Point is indeed the correct SCCM server running as a Management Point, and exclaims, “I’m done!” Often this happens about 10 seconds after installation is complete. The Configuration Manager Agent’s properties. The “final” verification usually comes from an administrator clicking the Configuration Manager applet to show the Configuration Manager Agent properties as shown on Figure 2.įigure 2. That isn’t proof that the client is functional. The Configuration Manager applet is there because it is installed. Many folks think they can verify that the Configuration Manager Client Agent is fully installed and functional as soon as the Control Panel item appears as shown in Figure 1.įigure 1. The agent must be running to make client configuration changes, to deploy software, to inventory the system, to process compliance audits, etc. When working with System Center Configuration Manager 2007, 2012, or 2012 R2, one of your primary tasks is to ensure that the Configuration Manager Client Agent is successfully installed and running properly.
0 Comments
Leave a Reply. |