SMS/SCCM & Batch Files and Scripting

SCCM 2012 Basic All-in-one Hardware Report

SELECT  distinct
 CS.name0 as 'Computer Name',
 CS.domain0 as 'Domain',
 CS.UserName0 as 'User',
 BIOS.SerialNumber0 as 'Bios serial',
 SE.SerialNumber0 as 'System Enclosure serial',
 CS.Manufacturer0 as 'Manufacturer',
 CS.Model0 as 'model',
 OS.Caption0 as 'OS',
 RAA.SMS_Assigned_Sites0 as 'Site',
 RAM.TotalPhysicalMemory0 as 'Total Memory',
 sum(isnull(LDisk.Size0,'0')) as 'Hardrive Size',
 sum(isnull(LDisk.FreeSpace0,'0')) AS 'Free Space',
 CPU.CurrentClockSpeed0 as 'CPU Speed'

SCCM 2012 Reporting for dummies: How to use SQL Management Studio to build your SCCM Queries

SCCM 2012 Reporting for dummies: Creating your own SSRS reports

Original Article:

So we’ve talked about reviewing reports out of the box using the SCCM console as well as using the web browser. We’ll now get to the nitty gritty and create our own reports using SSRS. I’m sure you’re all eager to learn as you’ve come this far in my “Reporting for Dummies” series.

Disabling/Enabling IPv6 with an Application in Configuration Manager 2012

The idea behind OSD in Configuration Manager is automation.  Right?  We want to create a process to eliminate as many manual tasks as possible.  Some companies have their technicians manually disable IPv6 on all adapters.  Who wants to do all of that manual work when we can have it automated?  My clients occasionally ask for a step in the OSD Task Sequence to disable IPv6.  If you would like to disable IPv6 on all interfaces, you should do it in a way that is easily reversible on your client computers companywide.  Here is how I did this for a recent client:

SCCM 2012 Client Updates Troubleshooting

SCCM 2012 Client Update Logs typical location:  C:\Windows\CCM\Logs






All packages are identified by package UUID not KB#. The UUID can be chosen on reports(add column) with in the SCCM Console




Using SCCM to migrate client computers from Java version 6 to version 7

Original article can be found here:


I’m in the process of upgrading all client computers from Java version 6.31 to Java 7.4.  Like all major version upgrades of Java if you simply install the new version the old version will remain installed.  Therefore, I’ve included instructions that allows you to remove the old version of Java, install the latest version, and then apply an update policy to fit your needs.

Using SCCM 2007 / 2012 to deploy Java Runtime Engine Updates

Original article can be found here:

Here’s some instructions for updating staff computers to the latest version of JRE using Microsoft System Center Configuration Manager 2007 / 2012. These steps will allow you to silently deploy JRE

LAST TESTED: JRE 7.55 on Windows 7

For info on upgrading from version 6 to version 7

Cross Forest Support in System Center Configuration Manager 2012 Part 4: Deploying Sites in Multiple Forests

Cross Forest Support in System Center Configuration Manager 2012 Part 3: Deploying Site Server / Site Systems in an Untrusted Forest


Subscribe to RSS - sccm