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

Installation of SCCM 2007 R3


Pre-requisites

1. KB977384 Hotfix should be installed.
2. Configuration Manager 2007 SP2 should be installed already since R3 is not a full version.
Link
3. Close any open MMC files.
4. Take a backup of Configuration.MOF and SMS_Def.MOF from the site server that is to be upgraded.

Below table indicates the site roles where this upgrade is applicable.

RoleWhat to InstallComments
Site Server (Primary Site)Hotfix & R3 Installation
Site Server (Secondary Site)Hotfix & R3 Installation
Provider (if on remote server)Hotfix
MP, DP, SUP, SQL DB Server (if remote)Not RequiredNo specific steps required for other roles.
Admin ConsoleHotfix & R3 InstallationWithout Console upgrade, the UI of power management may be incorrect. Hence before configuring power policies upgrade consoles.

Download Link:

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

Registration is required to download it.

Installation:

1. After successful installation of KB977384 hotfix, initiate the splash.hta to start the R3 installation. Click next.

  2. Accept the License agreement and click next.




 3. Provide the registration information and Product key.


4. Click Next to start the installation.




5.Click Finish and R3 is installed on the site server.




Verifying Installation:

1. Open SCCM Console & navigate to Site Database – Site Management - <Site Code> - <Site Name> and view properties to confirm that R3 Installed is “Yes”.


2. Verify that the Client hotfix package & program that are created during installation are available in ConfigMgr Console under ‘Software Distribution’ – Packages Node.


3.During R3 installation, the source bits for the client hotfix package will be copied to <ConfigMgr Installation Directory>\client\i386\hotfix\KB977384 folder. Validate that this folder exists, and is the same as the source directory for the ConfigMgr package in console.


R3 is installed and the version when you upgrade R3 on the client , the version would be 4.00.6487.2157
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