Archive

Posts Tagged ‘System Center Configuration Manager’

Week in Review – CW20

May 18, 2014 Leave a comment

Weekend again – and a few blips on the radar that I wanted to read up upon:

And off course there was TechEd NA – instead of individually listing up everything that caught my attention here are some quick tips:

See you next week!

Tim

Week in Review – CW19

May 11, 2014 Leave a comment

Last week I promised to publish a weekly list of interesting “things” I see flying by during a busy work week on which I try to catch up over the weekend. This is my second post in the “Week in Review” category and here are the topics that caught my attention during this week.

That’s it for this week. Happy Reading!

Tim

Configuration Manager Field Experience Ebook

October 21, 2013 Leave a comment

CfgMgr_Ebook_FieldExperience Something you cannot afford to miss on your (virtual) bookshelf is the recently released Microsoft Ebook titled Configuration Manager Field Experience.

The book is divided into three main topics.

Part 1: WMI for System Center 2012 Configuration Manager administrators is designed to familiarize you with basic WMI concepts and tools, show you how to use WMI classes to create Configuration Manager queries, and help you understand the underlying database design of Configuration Manager so you can create custom reports for querying the information you need.

Part 2: System Center 2012 Configuration Manager reporting is designed to familiarize you with SSRS and show you how to integrate SSRS with Configuration Manager 2012 and to customize and create new reports using SSRS.

Part 3: Configuration Manager deployment tips provides tips that cover a wide variety of different scenarios to help you ensure the success of your deployments.

The ebook is free and available for download here: Microsoft System Center- Configuration Manager Field Experience

Implementing Configuration Manager 2012 SP1 Cumulative Update 2

July 3, 2013 Leave a comment

Previously I had already published a post on implementing CU1, this is a similar post describing my experiences and findings while installing Cumulative Update 2 for Configuration Manager 2012 Service Pack 1 in my lab environment.

Important: there is a bug in CU2 which prevents you from installing additional Secondary Sites once the CU has been applied. Just now Microsoft has published a blog post on the issue which confirms the issue and also lists possible workarounds.

The installation binaries for the Cumulative Update can be found here: http://support.microsoft.com/kb/2854009

As per the documentation, this CU is applicable directly to the following components:

  • CAS
  • Primary Sites
  • Secondary Sites
  • SMS Provider
  • Console

Additionally it contains updates for the following components:

  • CAS
  • Primary Sites
  • Secondary Sites
  • SMS Provider
  • Consoles
  • Clients

Once we have reviewed the documentation and obtained the binaries we are ready to proceed with the installation. The lab environment infrastructure is rather simple: a standalone server with the site database and all roles hosted on a single (virtual) machine. No secondary sites at implementation time of this CU.

Site

Log on to the site server and make sure all open console connections are closed before running the installer:

image

Click Next on the Welcome Screen.

image

Accept the license terms and click next.

image

Make sure all prerequisite checks are successful and click Next

image

Enable the box to also update the console and click Next. Note this is new in CU2 – previously in CU1 the console update package had to be redistributed to the site server to update the locally installed console.

image

Select the option to update the site database and click Next.

image

Leave the default setting to create the server, console and client packages and click Next. These packages will be useful later on for updating the remaining components in our infrastructure.

image

Provide package and program names for the Server package and click Next.

image

Provide package and program names for the Console package and click Next.

image

Provide package and program names for both Client packages and click Next.

image

Review the setup summary and click Install.

image

Click Next when the installation steps have been completed successfully.

image

Click Finish to close the installation wizard.

image

Note that more detailed information on the installation process can be found in the log file located in the Windows\Temp folder.

image

CU2 Installations are properly registered in ARP.

Entry for the site server:

image

And for the console:

image

In the Software Library workspace the packages for further distributing the CU2 have been created:

image

Do not forget to distribute the content to your distribution points. This is not done automatically during the implementation of the CU.

Consoles

My console on the site server has been updated already as part of the CU2 installation process. See above for details.

Any remaining remote consoles I could easily upgrade using a deployment and a query based collection containing machines with a console installed. This is the query I will use:

  • 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 inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "Microsoft System Center 2012 Configuration Manager Console"

Once the update is installed it is visible in ARP:

image

 

Clients

Upgrading any existing clients in the environment can easily be done using the pre-created packages. We will created query based collections for targeting the deployments. This is an example query for all x86 SP1 clients:

  • select * from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_R_System.ClientVersion = "5.00.7804.1000" and SMS_G_System_SYSTEM.SystemType = "X86-based PC"

For the x64 clients we can use the same query but we need to replace “X86-Based PC” with “X64-based PC”.

Once the CU2 has been applied the client version number is changed to 5.00.7804.1300.

image

Some of the client components also get the 1300 build number:

image image

If you would like to build additional collections for the SP1 CU2 clients you can use this query:

  • select * from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_R_System.ClientVersion = "5.00.7804.1300" and SMS_G_System_SYSTEM.SystemType = "X86-based PC"

Again replace the "X86-based PC" with "X64-based PC" for the 64 bit clients.

The implementation of Cumulative Update 2 in our lab environment is now completed.

Until next time!

Tim

Implementing Configuration Manager 2012 SP1 Cumulative Update 1

July 2, 2013 1 comment

A while back I had implemented Cumulative Update 1 (CU1) for System Center 2012 Configuration Manager Service Pack 1 in my lab environment. This post was published earlier on my SCUG blog and describes the implementation details and findings during the rollout of the CU. With the release of CU2 recently, I am aware that I am running behind with posting this, but as the implementation process for this CU will be very similar I decided to still post this information.

An overview of the issues fixed in this CU are outlined in the following article: http://support.microsoft.com/kb/2817245/en-us .
This is also the location where you can download the installation binaries from.

As per the documentation this CU is applicable directly to the following components:

  • CAS
  • Primary Sites
  • Secondary Sites
  • SMS Provider

Additionally it contains updates for the following components:

  • CAS
  • Primary Sites
  • Secondary Sites
  • SMS Provider
  • Consoles
  • Clients

Let’s continue with the details on the actual implementation. Note that in the lab environment there is only a Standalone Primary site. There is no CAS or secondary sites to which the CU is to be applied.

 

Site

Make sure all open console connections are closed and run the installer:

image 

Click Next on the welcome screen.

image

Accept the license terms and click Next.

image

The prerequisite checker will run some initial checks. Click Next once all checks are successful.

image

Leave the option to update the database and click Next.

image

Leave the option to create the packages – these will come in handy for updating the other components in your Configuration Manager infrastructure.

image

Modify the Server package details if needed. Click Next.

image

Modify the Console package details if needed. Click Next.

image

Modify the details for the Client packages if needed. Click Next.

image

Review the installation summary and click Next to start installing.

image

Click Next once all installation tasks have completed successfully.

image

Click Finish. In my lab a reboot of the server was required.

image

Note that the site version remains unchanged after implementing CU1.

image

The CU1 is listed in Control Panel > Programs & Features.

image 

The packages for upgrading the other components have been created successfully.

image

At this point do not forget to distribute the content to your Distribution Points.

This concludes the upgrade of the site itself. Now we can further upgrade the remaining components in our infrastructure.

 

Consoles

Note that you have to deploy the console update also to the site server if the console was installed locally.

For deploying the CU1 to all consoles I had created a query based collection. This is the query that was used:

  • 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 inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "Microsoft System Center 2012 Configuration Manager Console"

Deploy the console update package to the collection to update all remote consoles.

Once the CU1 for the console is installed it is also listed in Control Panel > Programs & Features:

image

 

Clients

Also for the clients I have created query based collections to deploy the CU1.

This is the query for the collection containing all x86 SP1 clients:

  • select * from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_R_System.ClientVersion = "5.00.7804.1000" and SMS_G_System_SYSTEM.SystemType = "X86-based PC"

For the x64 clients I used the same query but replaced “X86-Based PC” with “X64-based PC”

Deploy the client update packages to the x86 and x64 client collections to update all existing clients.

The client version is updated to 5.00.7804.1202 once the CU1 has been applied:

image

To keep track of different client versions and for easy targeting in the future (additional hotfixes and updates) I also created collections for my SP1 CU1 clients.

image

This is the query for the collection containing all x86 SP1 CU1 clients:

  • select * from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_R_System.ClientVersion = "5.00.7804.1202" and SMS_G_System_SYSTEM.SystemType = "X86-based PC"

For the x64 clients I used the same query but replaced “X86-Based PC” with “X64-based PC”

This concludes the implementation of System Center 2012 Configuration Manager SP1 Cumulative Update 1 in my lab environment.

CU Around!

Tim