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

SCCM 2007 Supported Client Operating Systems

Operating SystemEditionService PackSystem Architecture3
Windows 2000
Professional, Server, Advanced Server, or Datacenter Server1
SP4
x86
Windows XP Professional
SP2 or SP3
x86
Windows XP Tablet PC Edition
SP2
x86
Windows XP Professional x64 Edition
SP2
x64
Windows XP Embedded4
SP2 or SP3
x86
Windows Embedded Standard 20094
x86
Windows Embedded Point of Service 1.0 and 1.14
x86
Windows Embedded POSReady 20094
x86
Windows Embedded Standard 74
No service pack or SP1
x86 or x64
Windows Thin PC4
x86 or x64
Windows Embedded POSReady 74
x86 or x64
Windows Fundamentals for Legacy PCs
x86
Windows Vista
Business, Enterprise, or Ultimate
No service pack, SP1, or SP2
x86 or x64
Windows 7
Professional, Enterprise, or Ultimate
No service pack or SP1
 
Windows 85
Pro, Enterprise
No service pack
x86 or x64
Windows Server 2003
Web Edition
SP1 or SP2
x86
Windows Server 2003
Standard Edition
SP1 or SP2
x86 or x64
Windows Server 2003
Enterprise Edition, Datacenter Edition1
SP1 or SP2
x86, x64, or IA64
Windows Server 2003 R2
Standard Edition
x86 or x64
Windows Server 2003 R2
Enterprise Edition or Datacenter Edition1
x86, x64, or IA64
Windows Storage Server 2003
Express Edition, Workgroup Edition, Standard Edition, or Enterprise Edition
SP1 or SP2
x86 or x64
Windows Storage Server 2008
Basic Edition, Workgroup Edition, Standard Edition, or Enterprise Edition
SP1 or SP2
x86 or x64
Windows Storage Server 2008 R2
Basic Edition, Workgroup Edition, Standard Edition, or Enterprise Edition
x86 or x64
Windows Server 20082
Standard, Enterprise, or Datacenter
SP1 or SP2
x86 or x64
Windows Server 2008 R22
Standard, Enterprise, or Datacenter
No service pack or SP1
x64
Windows Server 2008 for Itanium-Based Systems
IA64
Windows Server 20125
Standard, or Datacenter
No service pack
x64
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