CCMEXEC.COM – System Center blog

CCMEXEC.COM – by Jörgen Nilsson

This Configuration Manager 2007 report will display a Operating System count per collection, including Service Pack level as displayed below. It is very useful to get an overview of how many computers with a specific OS and Service Pack there is in the environment.


When implementing it, create a prompt for the report called “varcollection” which is the prompt for a CollectionID.

Here is the query:

SELECT Caption0 as 'Operating System',CSDVersion0 as 'Service Pack', Count(Caption0) AS 'Number',@varcollection as 'CollectionID'

join v_FullCollectionMembership FCM on FCM.ResourceID = v_GS_OPERATING_SYSTEM.ResourceID
Where FCM.CollectionID = @varcollection
Group by CSDVersion0,Caption0
Order by CSDVersion0,Caption0

SELECT Caption0 as 'Operating System',CSDVersion0 as 'Service Pack', Count(Caption0) AS 'Number',@varcollection as 'CollectionID'


join v_FullCollectionMembership FCM on FCM.ResourceID = v_GS_OPERATING_SYSTEM.ResourceID

Where FCM.CollectionID = @varcollection

Group by CSDVersion0,Caption0

Order by CSDVersion0,Caption0

Prompt query for the CollectionID prompt:


if (@__filterwildcard = '')

select distinct CollectionID, Name from v_Collection order by Name


select distinct CollectionID, Name from v_Collection

WHERE CollectionID like @__filterwildcard

order by Name


Some of the System Center 2012 Configuration Manager session from presented at TechEd Orlando is now available online at TechEd online.

Here are the System Center 2012 Configuration Manager Sessions that are available already, including the one where SP1 was announced!

Microsoft System Center 2012 Configuration Manager Overview (including SP1 info)

Patch and Settings Management in Microsoft System Center 2012 Configuration Manager

Microsoft System Center 2012 Endpoint Protection Overview

Enjoy, I will!

Today at Teched Orlando Microsoft announced some features in the upcoming Service Pack 1 for Configuration Manager 2012. One of the long awaited news are support for MAC OS X, Windows 8 and Linux/Unix.

For more information see the blog post from Kent Agerlund at here:

Great news!!

An Update for Windows Server Update Services 3.0 Service Pack 2 is available.
The update replaces/includes the hotfix we are used to installing to be able to publish updates using System Center Updates Publisher when you have .NET framework 4.0 installed.
The update includes an update for the Windows Update Client agent that will be installed automatically from the WSUS server.

From the Technet Article:

The following Microsoft Knowledge Base articles describe the issues that are included in this update:

  • 2530678 ( ) System Center Update Publisher does not publish customized updates to a computer if WSUS 3.0 SP2 and the .NET Framework 4.0 are installed
  • 2530709 ( ) “Metadata only” updates cannot be expired or revised in WSUS 3.0 SP2

This update strengthens the WSUS communication channels. This includes trusting only files that are issued by the Microsoft Update certification authority.

Known issues

  • Consider the following scenario:
    • You connect to Windows Update through a network proxy that uses HTTPS or SSL content inspection.
    • An intermediate server is in between the SSL traffic of the client and Windows Update.

    In this scenario, you have to create exception rules in your HTTPS inspection server so that the Windows Update traffic is tunneled without inspection. For more information about how to create HTTPS inspection exceptions for Microsoft Forefront Threat Management Gateway (TMG), go to the following Microsoft website:

    Excluding sources and destinations from HTTPS inspection (

    For a list of URLs and domains to exclude, click the following article number to view the article in the Microsoft Knowledge Base:

    885819 ( ) You experience problems when you access the Windows Update Version 6 website through a server that is running ISA Server
  • If you install the executable file (.exe) manually, you will have to restart the computer to apply the update.
  • Remote Microsoft SQL Server administrators must download and install the update by using an account that has SQL Server Administrator permissions. Remote SQL Server installation will always require manual installation.
  • To apply this update, you must be running Windows Internal Database or SQL Server.
  • The IIS and WSUS services must be stopped to prevent the database from being accessed while the Network Load Balancing (NLB) clusters are upgraded. For more information about how to upgrade NLB, see the “To upgrade NLB on all computers” section.

The whole article can be found here:

For all of us not going to TechEd North America, the Keynotes and some of the most popular session can be streamed live here:

It sounds interesting, System Center 2012 is of course in the live stream description!
Watch the live stream of Microsoft TechEd North America 2012 Keynote Address and some of our most popular sessions, covering a variety of technology topics like Windows Azure, Windows Server 2012, Microsoft System Center 2012, Windows PowerShell and more.

I will be watching the live stream!

This summer Microsoft Sweden invites everyone to some free learning before summer vacation, called Sommarkollo. A great way to get some information about new technology and to prepare for the fall and some exciting released coming up!
The agenda is packed with many sessions!

I have the great pleasure to talk about System Center 2012 Configuration Manager both in Helsingborg and Stockholm(in Swedish), don’t miss it!

2012 -06-26 : 13:00 –  Helsingborg at Elite Hotel Marina Plaza

2012 -06-28 : 13:00 – Microsoft in Stockholm

2012 -08-14 : 13:00 – Microsoft in Stockholm

Registration is free :


In System Center 2012 Configuration Manager it is really easy to upgrade an installation that was made using the Evaluation option when you installed it to a fully licensed installation by simply entering the Product key. This it useful in so many scenarios.

It is done by using the “Configuration Manager Setup” which can be found on the Start menu or by simply running install from the installation source.

When the setup starts select the “Perform site maintenance or reset this Site” in the following wizard you can convert the installation from an evaluation to a fully licensed installation.

Here is a step-by-step guide:

  1. Start Configuration Manager Setup either from the start menu or the installation source.
  2. Select the “Perform site maintenance or reset Site” option
  3. Then you get the option to “Convert from Evaluation to Full Product Version. Enter your 25-character product key:”
  4. In the next screen accept the license agreement
  5. Finished!
    CM2012_Lic5 It is truly a great feature that is so easy to convert from an installation using the Evaluation License to a Licensed product, it makes Proof-of-concepts much easier to perform and afterwards upgrade the environment to a licensed product in minutes.

I have written a couple of scripts before to install the SCCM 2007 console which is a challenge with R3 and hotfixes e.t.c. In System Center 2012 Configuration Manager this has now changed, it is really simple to install the Admin Console unattended.

There is no need to run Setup and use an unattended file anymore, the setup files for the Adminconsole is located on the Primary Site Server in the Configuration Manager installation folder under Tools\ConsoleSetup. In that folder there are two files ConsoleSetup.exe and Adminconsole.msi(if you install more languages there will be more files)

Compared to using the ConfigMgr2012 installation media you will save a lot of disk space on the DP’s using this method.


The installation must be done using the ConsoleSetup.exe as it provides more functionality than simply running the AdminConsole.MSI file.

Here is how to do it:

  1. Simply copy the whole ConsoleSetup Directory to my package source share
  2. Create a new Application and Manually enter the information needed.
  3. Name it for instance AdminConsole with Script Installer(Native) as the deployment type.
  4. As detection method use Windows Installer and select the Adminconsole.msi file.
  5. In the Command Line use the following:
    “consolesetup.exe /q TargetDir=”C:\Program Files\ConfigMgr” EnableSQM=0”
  6. Replace with the FQDN for your site.
  7. Deploy it to the collection of your choice and you are finished.

Incredibly simple!!

Don’t forget that the AdminConsole requires the Full .Net Framework 4 to be installed before so either add it as a dependency or requirement, dependent on how you have designed you application management.

For more information including how to install the AdminConsole in different languages see Technet :