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

SQL Query to get Information from SCCM Client


This query helps us to find the below mentioned parameters


Hostname
Serial Number
Manufacturer
Model
Processor
Memory (KBytes) 
Disk Size (MBytes)
AD Site
Last user logged in
Operating System
Service Pack
OS Install Date
Creationdate in SMS
LastHWScan

Query :

SELECT  
A.Name0,  
B.SerialNumber0,  
A.Manufacturer0,  
A.Model0, C.Name0 AS 'Processor',  
D.TotalPhysicalMemory0 AS 'Memory (KBytes)',  
E.Size0 AS 'Disk Size (MBytes)',
G.AD_Site_Name0 AS 'AD Site',  
A.UserName0 AS 'Last user logged in',  
H.Caption0 AS 'Operating System',  
H.CSDVersion0 AS 'Service Pack',  
H.InstallDate0 AS 'OS Install Date',
G.Creation_Date0 AS 'Creationdate in SMS',  
I.LastHWScan


FROM
  
v_GS_COMPUTER_SYSTEM A, 
v_GS_PC_BIOS B, 
v_GS_PROCESSOR C, 
v_GS_X86_PC_MEMORY D, 
v_GS_DISK E, 
v_R_System G, 
v_GS_OPERATING_SYSTEM H, 
v_GS_WORKSTATION_STATUS

WHERE
A.ResourceID = B.ResourceID AND 
A.ResourceID = C.ResourceID AND 
A.ResourceID = D.ResourceID AND 
A.ResourceID = E.ResourceID AND 
A.ResourceID = G.ResourceID AND 
A.ResourceID = H.ResourceID AND 
A.ResourceID = I.ResourceID AND
A.ResourceID = H.ResourceID

GROUP BY A.Name0, B.SerialNumber0, A.Manufacturer0, A.Model0, C.Name0, 
D.TotalPhysicalMemory0, E.Size0, G.AD_Site_Name0, A.UserName0, H.Caption0,
 H.CSDVersion0,H.InstallDate0, G.Creation_Date0, I.LastHWScan 



Labels:

Comments

Post a Comment

Popular posts from this blog

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

Operating System Deployment-SCCM 2007 Step By Step Procedure

This post explains the step by step by procedure (flow) to build, capture and deploy Operating System to a bare metal machine. It covers: A] Preparing SCCM Server for OSD B] Building and capturing OS image C] Deploying Operating Systems. There are two methods to capture OS image. a] Using Task sequence to capture  the OS from a reference machine.(Automating BUILD as well) b] Using Manual method.( build an operating system and then capture using SCCM) Here, I am building and capturing the image through Task Sequence. And also not using any USMT to migrate data since it is a plain bare metal deployment, not an upgrade. A]. Preparing SCCM Server for OSD: 1. Install WDS server role WDS 2. Install and configure PXE service point. PXE Service Point 3. General Supported Configurations. 4. Create and set Network access account.  5. Create and distribute the Configuration Manager 2007 package, all the relevant KB updates as packages. This post helps to create...
5 comments
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