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 fallback status point -Post SCCM Installation -Configuration Task 5


Definition:

The fallback status point is an optional but recommended site system role that helps you manage clients and identify any client-related problems. It receives state messages from Configuration Manager 2007 clients when they install and when they fail to communicate with a management point. The state messages sent to the fallback status point provide administrators with information about client status.

Using the Fallback Status Point for Client Deployment:

Examples of state messages a client might send to a fallback status point if it encountered problems during client deployment include the following:
  •     The client failed to install properly (for example, because of incorrect setup options or syntax errors, or because it failed to locate the required files).
  •     The client failed to be assigned to a site.
  •     The client failed to register with its assigned site.
  •     The client failed to locate its management point.
  •     There was a network connectivity problem between the client and the management point.
  •     The management point is not configured correctly (for example, Internet Information Services (IIS) is not configured correctly for a Configuration Manager Management point).
  •     In addition to sending state messages when there is a problem during client deployment, the client will send a state message to the fallback status point when it is successfully installed and when it is successfully assigned to a Configuration Manager 2007 site. In this scenario, the client will also report if a restart is required to complete the installation.

Do not install a fallback status point in the site if the following condition applies:
  •     The security risks of running a Web site with unauthenticated connections and clear text transfers outweigh the benefits of identifying client communication problems.

Pre-requisites:

·         Install IIS on the computer where the FSP is going to be installed.
Note that SMS 2003 client computers cannot use a fallback status point.

Installation:

1.  In the SCCM console, navigate to System Center Configuration Manager /          Site Database / Site Management / <site code> - <site name> / Site Settings /Site Systems/Server Name 

2. Click on “New Roles”, enter the FQDN name of the server and click on next.

3. Select an account to use to install the fallback status point. If no Windows domain user account is specified, the site server computer account is used.

4.On the System Role Selection page, select Fallback Status Point and then click Next.




5. On the Fallback Status Point page, specify the following information:

    a]Confirm that the option Allowed client connections displays the correct  setting for the site system's server placement and configuration: ( Non Configurable)
  • Allow intranet-only connections
  • Allow both intranet and Internet client connections


b] Number of messages: Specify the number of state messages that the fallback status point can process within the specified throttle interval.

c]Throttle interval (in seconds): Specify the throttle interval in seconds. Only the specified number of state messages will be processed during this interval.


6.Click Next, check summary and click close to finish the installation.

Verifying the Installation of Fallback Status Point:

There are 2 log files to check to verify whether the Fallback status point is successfully installed or not.

1. SMSFSPSETUP.LOG:
§  Location: SCCM installation directory\logs or SMS\Logs if the FSP is installed on a different system.
§  Search string: Installation was successful.


2.       FSPMSI.LOG:
§  Location: SCCM installation directory\logs or SMS\Logs if the FSP is installed on a different system.
§  Search for any errors from this log file.
3.       FSPMGR.LOG:
§  Location: SCCM installation directory\logs or SMS\Logs if the FSP is installed on a different system.
§  Search string: SMS_FALLBACK_STATUS_POINT successfully STARTED.






Comments

Post a Comment

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 .