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

What is MSI?

Definition:

msi is "Microsoft Windows Installer"  which allows us to install applications on a system. It allows us to customize the installation as per our requirement. Actually speaking, it is a database which contains several tables and set up information.

It is a built-in Operating System service for Installing and Managing Applications. It provides a standard method for developing, customizing, installing and updating applications.

The service name is msiexec.exe

Versions:

The current version of Windows installer is 5.0 and comes with Windows 7,8 and Windows 2008 R2/2012 . There is no standalone version as of  now. From SCCM perspective, Windows installer 3.0 is sufficient and this is one of the pre-requisite for installing SCCM. 

The below table shows the versions of Windows installer.

Release Version Description
Windows Installer 2.0 2.0.2600.0 Released with Windows XP.
Windows Installer 2.0 2.0.2600.1 Released with Windows 2000 Server with Service Pack 3 (SP3).
Windows Installer 2.0 2.0.2600.1183 Released with Windows 2000 Server with Service Pack 4 (SP4).
Windows Installer 2.0 2.0.2600.2 Released as a redistributable.
Windows Installer 2.0 2.0.2600.1106 Released with Windows XP with Service Pack 1 (SP1).
Windows Installer 2.0 2.0.3790.0 Released with Windows Server 2003.
Windows Installer 3.0 3.0.3790.2180 Released with Windows XP with Service Pack 2 (SP2). Released as a redistributable.
Windows Installer 3.1 3.1.4000.1823 Released as a redistributable. This version is has the same functionality as version 3.1.4000.2435.
Windows Installer 3.1 3.1.4000.1830 Released with Windows Server 2003 with Service Pack 1 (SP1) and Windows XP Professional x64 Edition. Update this version to version 3.1.4000.2435 to address the issue discussed in KB898628.
Windows Installer 3.1 3.1.4000.3959 Released with Windows Server 2003 with Service Pack 2 (SP2).
Windows Installer 3.1 3.1.4000.2435 Released with a fix to address the issue discussed in KB898628. This is the latest version of Windows Installer 3.1.
Windows Installer 3.1 3.1.4001.5512 Released with Windows XP with Service Pack 3 (SP3).
Windows Installer 4.0 4.0.6000.16386 Released with Windows Vista.
Windows Installer 4.0 4.0.6001.18000 Released with Windows Vista with Service Pack 1 (SP1) and Windows Server 2008.
Windows Installer 4.5 4.5.6002.18005 Released with Windows Vista with Service Pack 2 (SP2) and Windows Server 2008 with Service Pack (SP2.)
Windows Installer 4.5 4.5.6000.20817 Released as a redistributable for Windows Vista.
Windows Installer 4.5 4.5.6001.22162 Released as a redistributable for Windows Server 2008 and Windows Vista with SP1.
Windows Installer 4.5 4.5.6001.22159 Released as a redistributable for Windows XP with Service Pack 2 (SP2) and later, and Windows Server 2003 with SP1 and later.
Windows Installer 5.0 5.0.7600.16385 or greater Released with Windows Server 2008 R2 and later and Windows 7 and later.
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