Skip to main content

Software Update Management- SCCM 2012

The below post explains the end to end process of software updates management in SCCM 2012 Pre-requisites: 1.  WSUS Server (WSUS 3.0 SP2 ) should be installed on the SCCM site server or if you want to install WSUS on another server, it is important that you install WSUS administration console as the SCCM Server uses API. This  link explains the step by step procedure to install WSUS 3.0 SP2 2. Install SUP-Software Update Point on the SCCM Server . 3. Reporting Services Point: Install reporting services point role as described in this link . 4. Client agent: The software update client agent should be enabled(will be enabled by default) and the settings have to specified as per the requirement. On SCCM console, go to Administration>Site Configuration>Client settings>Right click on Default client settings> Click on Properties. If required, we can create custom client settings and then enable client settings for that settings. Unde

Configure Client Agent Settings-Post SCCM Installation -Configuration Task 7

Definition:

Client agents are SCCM 2007 components that run on top of the base client components. Client agent settings are required in order to manage the SCCM clients. Without enabling the SCCM client agent settings, we cannot manage any systems even though the SCCM client is installed on those machines. Every client agent enables different feature, for example: Software inventory client agent: enables software inventory.

Pre-requisites:

It varies with the type of client agent that is going to be enabled.

Enable and configure Client agent:

1. In the Configuration Manager console, navigate to System CenterConfiguration Manager / Site Database / Site Management / <site code> - <site name> / Site Settings / Client Agents.
2. Right-click the client agent that has to be configured, and then click Properties.
3. Enable and configure the client agent.Click OK.


There are 11 client agents available with SCCM 2007 SP2 R3, power management feature being added.

Here, I have attached the screenshot of the configuration of “computer client agent properties” and added the account as well.




Client Agent
Description
Computer Client Agent Properties
Configures how often client computers retrieve the policy that gives them the rest of their configuration settings.
For example, after you configure the other client agent settings, Configuration Manager puts those settings into policy and sends them to the management point and client computers poll for them on the schedule you configure.
This agent also controls settings that are shared by several Configuration Manager features, such as how often users are prompted with reminders and what customized organization names users see with the reminders.
Device Client Agent Properties
Configures the entire properties specific to mobile device clients.
Mobile device clients have settings for software distribution, software inventory, hardware inventory, and file collection.
This agent also controls the polling interval used by mobile device clients.
Hardware Inventory Client Agent
Enables and configures the agent that collects a wide variety of information about the client computer.
Information about the computer hardware is most commonly collected, but you can inventory any information stored in the Windows Management Instrumentation repository of the computer, such as registry keys.
You can configure how often the client computer checks its inventory and sends the information to the site.
Software Inventory Client Agent
Enables and configures which files Configuration Manager inventories and collects.
Copies of collected files are stored in the Configuration Manager database.
Advertised Programs Client Agent
Enables and configures the software distribution feature.
Desired Configuration Management Client Agent
Enables the client agent that evaluates whether computers are in compliance with configuration baselines that are assigned to them.
You can also configure the default compliance evaluation schedule for assigned configuration baselines.
Power Management Client Agent
Enables the power management feature to control the power settings of the clients to be managed.
Remote Tools Client Agent
Enables Configuration Manager remote control and configures Configuration Manager integration with Remote Assistance.
Network Access Protection Client Agent
Enables Configuration Manager Network Access Protection, which allows you to configure how client computers are evaluated for compliance with software updates. If client computers are not in compliance with the configured policies, for example, if they do not have specified software updates, a Network Policy Server on Windows Server® 2008 can prevent the client computers from accessing network resources until they complete remediation measures.
Configuring this client agent without proper planning and deployment can prevent your client computers from accessing the network.
Software Metering Client Agent
Enables the agent that monitors which software is run and how often and configures how often software metering data is collected.
Software Updates Client Agent
Enables the agent that scans for and installs software updates on client computers.
This agent allows you to configure how often clients are re-evaluated for software updates that were previously installed.
Before you can use the software update feature, you must also install Windows Server Update Services and configure a software update point.


There is no client agent for operating system deployment.

Comments

Popular posts from this blog

Registering SPN for SQL Server for SCCM

If using a domain account to install SQL server 2008 R2 for SCCM, you have to register a SPN (Service Principal Name) in Active Directory for that domain account. Two SPNs for the account should be registered,     1. For NETBIOS name of the SQL Server     2. For the FQDN of SQL server. The procedure to do that is as follows 1. Log on to a domain controller; open a command prompt with administrative privileges. 2. Type the below commands replacing SQL server name. setspn –A MSSQLSvc/< SQL Server NETBIOS name >:1433<Domain\Account> setspn –A MSSQLSvc/< SQL Server FQDN >:1433 <Domain\Account> 3. As shown in the below screenshot, the server name here is  CM2012 for NETBIOS name and CM2012.CONTOSO.COM 4.  Verify the registration of SPN by typing the below command Setspn –L  <domain\account>

Consistency validation for SQL Server registry keys failed error -SQL for SCCM

During installation of SQL server, "Consistency validation for SQL Server registry keys failed” error pops up in the below scenarios. 1.   Previous installation of SQL exists. 2.   Inappropriate permissions on the registry keys of Microsoft SQL server. Solution that worked me is explained below. A. Identify the issue: 1. Go to %Program Files%\Microsoft SQL Server\100\SetupBootstrap\Log\”date  and time of installation” 2. Search (in Detail_GlobalRules.txt) for lines containing the following string "Could not fix registry key" 3. Run “regedit”, s et full control permissions for the appropriate registry keys mentioned in "Detail_GlobalRules.txt" file. Re-run the installation. B. Modifying the registry: 1. Locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server in registry. (To open registry, run “regedit”) 2. Right click and go to Permission 3. Click on Advance tab and c heck the below options.     i. Include i

Collection query to find Machines--based on GUID Criteria

You can use the below SQL query to create a new collection based on GUID. select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.SMBIOSGUID = " 18764D56-C91F-83A5-51FB-4AD4B6699D04 " Replace the GUID with the one that you intend to delete. This is particularly useful when performing OSD related tasks. To know how to create a collection , go through this link .