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

SCCM 2012 Site Server Installation-Primary Stand alone


This post is a step by step procedure on how to install SCCM 2012 Site Server and also preparing the Windows Server 2008 R2 for SCCM server installation.
SCCM 2012 SP1 Software is used here, you can download from the below Microsoft link.

http://care.dlservice.microsoft.com//dl/download/D/7/9/D792FC0F-D278-43CB-8ABB-ECAF2A52DAA7/SC2012_SP1_RTM_SCCM_SCEP.exe

AD schema has to be extended, the steps mentioned in the below  link can be used for the same.

http://being-sccmadmin.blogspot.in/2013/04/extend-active-directory-schema-for.html


If the schema is extended for SCCM 2007 already, there is no need to extend the schema again for SCCM 2012.

* Install SQL Server 2008 R2 as per the steps mentioned in the below link.

http://being-sccmadmin.blogspot.in/2013/04/installation-of-sql-server-2008-r2-for.html


Install SQL Server 2008 R2 SP1 with Cumulative Update 6 or Install SQL Server 2008 R2 SP2.

I have installed SQL Server 2008 R2 SP1 with Cumulative update 6 here.

Register SPN for SQL service account name if you are using domain account for installing SQL server.

Use the below link to register the SPN in AD.

http://being-sccmadmin.blogspot.in/2013/06/registering-spn-for-sql-server-for-sccm.html

Install Dotnet 4.00 framework which is a pre-requisite if you are installing on a Windows Server 2008 R2 and Dotnet 4.5 on Windows Server 2012

* Download and install Windows Assessment and Deployment Kit( ADK) for SCCM 2012 SP1 (previously WAIK). 

http://being-sccmadmin.blogspot.in/2013/07/installing-windows-adk-for-sccm-2012-sp1.html

* Download and install Windows management framework.

http://www.microsoft.com/en-in/download/details.aspx?id=34595

I have broken down the steps into 3 sections:

A] Configuring Windows Server for SCCM Installation

B] SCCM Site Pre-requisite checks and Installation
C] Verifying Installation of SCCM

This is the primary stand alone server in this lab environment.


A] Configuring Windows Server for SCCM installation:


The below TechNet link provides the detailed Windows Server requirements.

http://technet.microsoft.com/en-us/library/gg682077.aspx

1. Login to server>>> Verify OS version. It should meet the windows server requirements defined in the above link.





2.Check the disk size and decide which drive to install SCCM on-it should meet the minimum recommended size by Microsoft.



3.Add computer to SCCM SERVERS AD group as shown below.This group should have full control permissions on Systems Management Container in AD.




4. Check the installation permissions of the account with which SCCM 2012 is installed

The account must be created in the Active Directory Domain Services database. The account must have administrator rights on the following computers.
The site server computer
The computer running SQL Server, if it is remote from the site server
The SMS Provider computer, if it is not installed on the site server or site database server
Here am using “SCCMADMIN” which is local admin on the server computer.





5. Add required roles for SCCM and Features on Site Server.


       
Features:
• Remote Differential Compression (RDC Feature)
Site servers and branch distribution points require Remote Differential Compression (RDC) to generate package signatures and perform signature comparison

• BITS-Back Ground Intelligence Transfer Service.



Addition of BITS feature will add the following Web Server components 


Common HTTP Features: 

* Static Content
* Default Document
* Directory Browsing
* HTTP Errors
* HTTP Redirection

Application Development: 
* .Net Extensibility
* ISAPI Extensions

Health and Diagnostics: 

* HTTP logging
* Logging Tools
* Request Monitor
* Tracing

Security 
* Request Filtering Performance 
*Static Content Compression Management Tools 
*IIS Management Console
*IIS 6 Metabase Compatibility




Roles:
• Web Server (required for MP&FSP)
• File Services 
• Windows Deployment Server (required only if using PXE point)
• Windows Server Update Services (WSUS- required only if using SUP)
We cannot install WSUS along with other roles, install it separately

On Web Server role>> asp , windows authentication, IIS 6 wmi compatibility



Webdav is not required for  SCCM 2012 because it is included  with  the SCCM 2012 already and it doesnt use the windows server feature anymore.

No need to install or enable Webdav as you did for SCCM 2007 previously.

B] SCCM Site Pre-requisite checks and Installation:

6. Open the SCCM installable extract go to smssetup/BIN/X64/Prereqchk.exe from a Command prompt and specify the parameter /adminui as shown in the screenshot below.

Extracted  SCCM2012\SMSSETUP\BIN\X64\PREREQCHK.EXE /ADMINUI


Open a command prompt with administrator permissions and execute prereqchk.exe /adminui to check if there are any missing pre-requisites.
And also check the Configmgrprereq.log to check for any errors.
It is available in Root directory of the machine.

7.  Initiate the Configuration manager 2012 installation from the SCCM media as shown.

a]Start:
Click on Install Configuration Manager 2012



b]Before you begin screen

Click Next once you get the below screen.

c]Available Setup Options

Select “Install a Configuration Manager Site Server”


d] Product Key:  Select evaluation if you are testing it or provide the product key for production environment.



e] Microsoft Software License Terms

Check "I accept the license terms" and click next.


f] Pre-requisite Licenses:

Check "I accept the license terms" and click next.



g] Prerequisite downloads:

There are two options to do this. One is to check the first option " Download  required files" if you have internet connectivity to the SCCM Server and the second option " Use the previously downloaded files" . Specify the location of files that are downloaded previously.
The following link helps to understand how to pre-download the files.


I have pre-downloaded  the required files and selected the second option " Use the previously downloaded files" specifying the location.


Click Next and wait until the verification is completed for the downloaded  files.

h] Server Language selection:

Select English or the language you need and click Next.



i] Client Language Selection:

Select the languages that needs to be enabled on the clients. Here, I am going with English


j] Site and Installation Settings:

The most important step is setting the site code and site name during the installation.
The following rules apply when you set the site code
* Do not use Microsoft Windows reserved names such as AUX, CON, NUL, or PRN as site codes.
* Setup does not verify that the site code entered is not already in use.
* Use Alphanumeric site codes- letters [A-Z], numbers [0-9] Ex : PR1,
* Changing the site code or site name after installation is not supported.
* Do not re-use site codes.

Reference: http://technet.microsoft.com/en-us/library/bb633287.aspx


Enter the appropriate site code , site name and click next.
Here, I have provided the site code as “PR1” and the site name as “Primary Site Server”
Specify the installation folder, here am installing on E drive.
The difference between SCCM 2007 and SCCM 2012 during installation is we have an option whether to install the administration console or not. I have checked  the "Install the Configuration Manager console"


k] Primary Site Installation:

I am installing a stand alone primary , so second option " Install the Primary site as a standalone site" has to be checked. In case if there is already an existing SCCM 2012 heirarchy, the first option "Join the primary site to an existing heirarchy " can be selected.

Click Next  and select Yes when it  prompts.





l ] Database Information:

Specify the Database server information:

* SQL Server FQDN : CM2012.CONTOSO.COM
* Instance name : Leave it blank if default.
* Database name : CM_Sitecode , here it is CM_PR1
* Service Broker Port : 4022
Click Next.

m] SMS Provider Settings:

Specify the SMS Provider server name here, FQDN.
The local server name is pre-populated, change it if installing SMS Provider on other computer.



n] Client Computer Communication Settings

This setting is equavalent to Site mode setting in SCCM 2007.( Mixed & Native mode).

Select the second option as shown so that we have the flexibility to install each site system role as desired.
The first option almost resembles native mode( using HTTPS) , more secure.
Make sure that you have a PKI infrastructure in place before implementing HTTPS mode.



o] Site System Roles

Management Point and Distribution Point site system roles can be installed in this step.
Select HTTP or HTTPS if PKI infra is in place.
Here, I am going with the HTTP mode.


p ] Customer Experience Improvement program:

Select first option to join and second option to join at a later stage.


q] Settings Summary :

Review the summary settings and click Next to begin the Pre-requiste check again before the actual installation.



r] Prerequisite Check:

Checks again for the prerequisites before installation. Click on 'Begin Install' to start the installation.

You can ignore the warnings , worry only about the errors ;)





s] Install :

This is where the actual installation progress is displayed. There is also ' view log' that provides detailed information of the installation. It  opens up the "configMgrsetup.log" present in the root directory.

There are 2 more logs that give a fair idea on the installation and prerequisite checker part.

1. ConfigMgrprereq.log- info about the prerequisite checking.
2. ConfigMgrsetupwizard- info about the wizard.




Eventually you will get a screen that the setup is completed successfully. Click Finish and the installation is done!

C] Verifying Installation of SCCM


The log files that need to be checked to verify successful installation are as follows.
You can use CMTRACE error log reader to view the logs

  • ConfigMgrSetup.log- provides information about the setup.
  • ConfigMgrPrereq.log- provides information about the prerequisites
  • ConfigMgrSetupWizard- provides information about the installation wizard
  • ConfigMgrAdminUISetup-provides information about the Configuration manager admin console setup.
To open the SCCM Administration Console, browse through Start>All Programs>Microsoft System Center> Configuration Manager Console




Comments

  1. Does 'Primary Standalone' mean that this SCCM can exist in a domain where there is already another SCCM? I want to run my own SCCM for my OU which I admin but I do not have privilege outside OU. Will it work?

    ReplyDelete
  2. Hi Santhosh can you tell me where SCCM is installed , say in AD server or I need to use 2 servers.

    ReplyDelete

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 .