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
4 comments

Reporting Point-Post SCCM Installation -Configuration Task 6


Definition:

A reporting point is an optional but recommended site server role that hosts files used by Configuration Manager 2007 so that you can see information in reports about the clients you are managing.
Reporting points communicate only with the local site database; thus, you implement reporting points only in primary sites, not secondary sites.

Pre-requisites:

  •        The site system computer must have Internet Information Services (IIS) installed and enabled.
  •         Active Server Pages must be installed and enabled.
  •         Microsoft Internet Explorer 5.01 SP2 or later must be installed on any server or client that uses Report Viewer.
  •         To use graphs in reports, Office Web Components (Microsoft Office 2000 SP2, Microsoft Office XP, or Microsoft Office 2003) must be installed.
  •         When you install ASP.NET on a Windows Server 2008 operating system reporting point, you must also manually enable Windows Authentication.

Note:
Office Web Components is not supported on 64 bit operating systems. If you want to use graphs in reports, use 32 bit operating systems for your reporting points.

Installation:

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

2. Determine whether to create a new site system or modify an existing site system, and then follow the associated step.

   To create a new site system and add the reporting point role:

          Right-click Site Systems, click New, and then click Server.

   To add the reporting point role to an existing site system:

         Right-click the site system name, and then click New Roles.

    Here, we are adding the reporting point role to an existing site system as  shown.

3. Configure the general site system settings, and then click Next.



4. Select Reporting point, and then click Next.




5. Specify the Report folder for the reporting point. Configuration Manager creates a folder with the specified name under \Inetpub\wwwroot. The default folder name is SMSReporting_sitecode.

Specify whether the Configuration Manager console opens the Report Viewer Web page using hypertext transfer protocol (http) or secure hypertext transfer protocol (https), and what port number is used. The default port for http is 80, and the default port for https is 443.

I have selected HTTP here...

6.Click Next, and then click Close to finish the installation.



Verifying installation of Reporting Point:

 There are 2 log files to check to verify whether the Reporting point is successfully installed or not.
1.SMSReportingInstall.LOG: Provides information about the installation of  a reporting point.

  • Location : Installation Directory\logs
  • Search string: “Installation of Reporting point complete”

2.smsreporting.log: Provides information about using the reporting components, including the connection to the site database, the queries used on the site database to retrieve the items displayed in a report and dashboard, and so on.
  • Location : Installation Directory\logs
  • Search string: depends on the report run or  the information that is queried from DB
Labels:

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>
1 comment
Read more

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
6 comments
Read more

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 .
3 comments
Read more