You are browsing the archive for 2013 June.

Avatar of timdk

by timdk

How to retrieve the list of SMS Providers

5:32 pm in Configuration Manager by timdk

During a recent rollout of a Configuration Manager 2012 update I also had to target all systems hosting the SMS Provider. In smaller environments it is pretty common the SMS provider is installed locally on the site server, but in larger environments there can be multiple SMS providers spread across different remote systems. This blog post is a step-by-step guide on how to retrieve the list of SMS Providers in just a few minutes.

On the site server run WBEMTest and click Connect.

image

Fill in the namespace SMS\Root and click Connect.

image

Next hit the Query button.

image

Type in the query “Select * from SMS_Providerlocation” and click Apply.

image

The query result returns all SMS Providers.

image

As you can see, in my lab environment there is currently only one SMS Provider installed.

Hat tip to @theWMIGuy for teaching me this trick..

Until next time.

Tim

Avatar of timdk

by timdk

System Center 2012 Configuration Manager R2 Preview available!

6:37 pm in Configuration Manager by timdk

Today at TechEd Europe 2013 Microsoft has announced the availability of the System Center 2012 R2 and Windows Server 2012 R2 previews. 

The binaries for Microsoft System Center 2012 R2 Configuration Manager and Endpoint Protection Preview can be downloaded here:  http://technet.microsoft.com/en-US/evalcenter/dn205297.aspx 

Important sidenote: this morning I noticed there was an issue with the downloads: instead of downloading ConfigMgr R2 I ended up with the binaries for Operations Manager R2. This may be fixed in the meantime but you might want to double check what you are downloading. Just to make sure.

clip_image002

Avatar of timdk

by timdk

Implementing Configuration Manager 2012 SP1 Cumulative Update 1

8:00 am in Configuration Manager by timdk

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 describes the implementation details and findings during the rollout of the CU. With the release of CU2 a few days ago, 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.

Until next time!

Tim

Avatar of timdk

by timdk

Technet Webcast – Deploying and managing Configuration Manager Clients

11:24 pm in Configuration Manager by timdk

Metro-Event

The session recording from my Technet webcast on deploying and managing Configuration Manager Client was published earlier today. You can watch and/or download the session recording and slides on Technet Edge.

Session abstract:

The client is a very essential part in any Configuration Manager implementation. During this session we will look into the various methods and best practices for deploying the Configuration Manager 2012 client in the enterprise. Additionally we will outline how to properly manage and maintain these clients throughout their lifecycle using the built-in client health features. If you still need to plan your client deployment, or if you are looking for information on how to improve you client coverage within your organization, this is a session you cannot afford to miss.

Until next time!

Tim