You are browsing the archive for R2.

Avatar of timdk

by timdk

ConfigMgr R2 SP1 upgrade does not clean up previous Cumulative Update entries in Control Panel > Programs and Features

2:09 pm in Configuration Manager by timdk

Hi All,

Just a quick blog post on a small anomaly with Configuration Manager R2 Service Pack 1.

Description

When upgrading an existing Configuration Manager site it seems the Installed Updates entries related to prior Cumulative Updates are not properly cleaned up. After upgrading a site the end result for Installed Updates looks like this:

image

The above example is based on a site that was up to Cumulative Update 5 – but the same happens with earlier released Cumulative Updates.

Although this is not really an issue and more cosmetics, it is something that could have been handled more properly by the Service Pack installer. A scenario where this potentially may cause unwanted effects is when using this information in your queries (collections, etc.).

Workaround

The entries displayed are read from the registry. The screenshot below shows the entry in the registry for the particular cumulative update:

image

I used the following steps to clean this up:

  1. Start the Registry Editor (regedit.exe)
  2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall .
  3. Locate the key for CU5 (see screenshot) and take a backup (right-click > export).
  4. Delete the key for CU5.
  5. All done – the entry is no longer displayed.

Note that this cleans up the cosmetics part only – any other leftovers (if any) from Cumulative Updates (and alike) will still remain on the system.

Until next time!

Tim

Avatar of timdk

by timdk

Implementing Configuration Manager 2012 R2 Cumulative Update 5

8:04 pm in Configuration Manager by timdk

As mentioned during one of my previous blog posts Microsoft has recently released Cumulative Update 5 for Configuration Manager 2012 R2. This blog post will outline how to implement this Cumulative Update and is based on the steps I followed during the implementation in my lab environment.

Note: this week Microsoft has also released Service Pack 1 for Configuration Manager 2012 R2. The logical question pops up whether to still install this Cumulative Update or immediately go for the Service Pack. Technically there are no constraints for implementing the Service Pack straight away (the CU is not a prerequisite) however my current preferred way to go is to implement the CU first. Based on experiences from the past there could always be some subtle differences, and it seems my friend Kenny already found one here as well.

Now back to implementing the CU. First step is to get the sources. The KB article also gives a full overview of the fixes and improvements in this update. As the name indicates, this update also contains all elements fixed or added in one of the previously released CU’s.

Note that this update is only applicable to Configuration Manager 2012 R2 – if you are currently still running Configuration Manager 2012 SP1 the latest available cumulative update is CU5.

The CU is applicable directly to the following components:

    • CAS
    • Primary Sites (standalone or in a hierarchy)
    • Secondary Sites
    • SMS Provider(s)
    • Console(s)

    Additionally it contains updates for the following components:

    • CAS
    • Primary Sites
    • Secondary Sites
    • SMS Provider(s)
    • Consoles
    • Clients

    The lab we are upgrading does not contain all the components listed above, a CAS and Secondary Site(s) are not present.  The SMS Provider is installed locally on the site server.

Primary site

Cumulative Updates for Configuration Manager are implemented top-down so we start with the site server of the standalone primary site. Before running the installer with elevated privileges ensure there are no more active console connections.

image

The Installation Wizard is started.

image

Click next on the Welcome page.

image

Accept the license terms and click Next.

clip_image001

Verify all prerequisite checks are successful and click Next.

clip_image002

Leave the default option to install the update for the console and click Next.

clip_image003

Leave the default option to update the site database and click Next.

image

Leave the default option for package creation and click Next.

clip_image005

Leave the default settings for the server package and click Next.

clip_image006

Leave the default settings for the console package and click Next.

clip_image007

Leave the default settings for the client packages and click Next.

clip_image008

Review the setup summary and click Install.

image

The installation begins and progress is shown. Click Next when finished.

Note: during the implementation I had noticed that the installer was hanging long time on the first step to stop the services. In this case manually stopping the WinMgmt service (net stop winmgmt from an elevated command prompt) was needed to make the installation continue.

image

All done! Click Finish and reboot the system.

image

The technical details about the installation and what is happening behind the scenes is logged the log file cm12-r2cu5-kb3054451-x64-enu.log  located in the %windir%\temp folder.

Now lets do a few verification steps to see if the update got implemented properly.

First checkpoint are the entries in Programs and Features > view installed updates:

image

Next is the registry in HKLM\Software\Microsoft\SMS\Setup

image

And a final check in the console (About Configuration Manager)

image

As we opted to have some packages created to support implementing the CU in our environment these should now also be visible in the console. Go to the software library and select packages. Select the Configuration Manager Updates folder and then type CU5 in the search box to quickly locate those packages.

image

Important: Do not forget to distribute the content of these packages to your Distribution Points!

Important (2): Do not forget to update your boot images. This can be done by selecting a boot image, right-clicking it and then selecting the action to Update Distribution Points.

Secondary Sites

If there are any Secondary Sites in your environment the next step is to implement the CU on those sites. The server update package can be used to automate this. To target the site servers a collection can be built which is populated based on the following query:

    • 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_64 on SMS_G_System_ADD_REMOVE_PROGRAMS_64.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS_64.DisplayName = "System Center 2012 R2 Configuration Manager Secondary Site Setup"

Consoles

    As part of the implementation process on the site server the locally installed console was updated. Any remaining remote consoles in the environment can be updated using the console upgrade package.

    To build a collection containing the machines with the console installed the following query could be 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 = "System Center 2012 R2 Configuration Manager Console"

     

    Clients

    Last but not least we also need to get the CU installed on our clients. There are multiple approaches to accomplish this; one method could be to deploy the client update packages created automatically during the implementation process.

    As there is a package per processor architecture we will also create matching collections to target our deployments. This is an example query for a collection containing all 64-bit clients with a client version not equal to CU5:
  • 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_SYSTEM on SMS_G_System_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_R_System.ClientVersion != "5.00.7958.1601" and SMS_G_System_SYSTEM.SystemType = "X64-based PC"
    The query for the collection with 32-bit clients is identical; just replace “x64-based PC” with “x86-based PC”.

Clients with CU5 will have the following version shown on the properties tab:

image

Version numbers for some of the components are also updated:

imageimage

That’s all for now – Until next time!

Tim

Avatar of timdk

by timdk

System Center 2012 R2 Configuration Manager SP1 and System Center 2012 Configuration Manager SP2 released!

5:10 pm in Configuration Manager, Microsoft Intune by timdk

metrofixToday Microsoft has announced the availability of System Center 2012 R2 Configuration Manager SP1 and System Center 2012 Configuration Manager SP2.

According to the announcement on the Configuration Manager Team blog these service packs deliver full compatibility with existing features for Windows 10 deployment, upgrade, and management. Additionally there are some changes and improvements in the following areas:

  • Infrastructure: sites and hierarchies
  • Application Management
  • Content Management
  • OSD
  • Reporting
  • Hybrid setups with Configuration Manager and Microsoft Intune

Full details on what’s new can be found here.

Both service packs are available for download on the Technet Evaluation Center website.

Until next time!

Tim

Avatar of timdk

by timdk

Cumulative Update 5 for System Center 2012 R2 Configuration Manager released!

7:43 pm in Configuration Manager by timdk

metrofixIn between all the announcements and other stuff that is going on at the Ignite conference Microsoft has also released Cumulative Update 5 for System Center 2012 R2 Configuration Manager today.

This CU contains some important bug fixes and performance improvements. Read about the issues that are fixed and additional functionality this CU has to offer in KB3054451 .

Blog post with more details on how to implement this CU will follow soon.

Until next time!

Tim

Avatar of timdk

by timdk

Implementing Configuration Manager 2012 R2 Cumulative Update 4

3:27 pm in Configuration Manager by timdk

Earlier on I have installed the newly released Cumulative Update 4 for Configuration Manager 2012 R2 in my lab. This blog post outlines the steps done during this implementation and can be used as a step by step guide.

First step is to get the sources for the CU here. The KB article also gives a full overview of the fixes and improvements in this update. As the name indicates, this update also contains all elements fixed or added in one of the previously released CU’s.

Note that this update is only applicable to Configuration Manager 2012 R2 – if you are currently still running Configuration Manager 2012 SP1 the latest available cumulative update is CU5.

The CU is applicable directly to the following components:

    • CAS
    • Primary Sites (standalone or in a hierarchy)
    • Secondary Sites
    • SMS Provider(s)
    • Console(s)

    Additionally it contains updates for the following components:

    • CAS
    • Primary Sites
    • Secondary Sites
    • SMS Provider(s)
    • Consoles
    • Clients

    The lab we are upgrading does not contain all the components listed above, a CAS and Secondary Site(s) are not present.

    Primary site

    Cumulative Updates for Configuration Manager are implemented top-down so we start with the site server of the standalone primary site. Before running the installer with elevated privileges ensure there are no more console connections.

image

 

The installation wizard kicks off.

clip_image001

On the welcome screen, click next.

clip_image002

Accept the License Agreement and click Next.

clip_image003

Verify the prerequisite checks and click Next.

clip_image004

Leave the option to update the locally installed console.

clip_image005

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

clip_image006

During the setup process we can opt to create packages to support updating other components in the infrastructure. Leave the options to have these packages created and click Next.

clip_image007

Leave the default settings for the servers package and click Next.

clip_image008

Leave the default settings for the console package and click Next.

clip_image009

Leave the default settings for both the x86 and x64 client package and click Next.

clip_image010

Review the setup summary and click Install when ready.

clip_image011

Progress is shown for each action.

clip_image012

Install completed! Click Finish to close the wizard.

Notice the mention that a reboot is required.

clip_image013

If you are interested in the more technical details about the installation and would like to see what is happening behind the scenes, have a look at the log file cm12-r2cu4-kb3026739-x64-enu.log  located in the %windir%\temp folder.

After the installation you can do a few verification checks to see if the CU got implemented.

First one is to look for the following entries in Programs & Features > View Installed Updates.

clip_image014

Second one would be to look in the registry in HKLM\Software\Microsoft\SMS\Setup

image

And lastly you can also check the version in the console (see About Configuration Manager):

image

 

As we opted to have some packages created to support implementing the CU in our environment these should now also be visible in the console. Go to the software library and select packages. Select the Configuration Manager Updates folder and then type CU4 in the search box to quickly locate those packages.

image

Important: Do not forget to distribute the content of these packages to your Distribution Points!

Important (2): Do not forget to update your boot images. This can be done by selecting a boot image, right-clicking it and then selecting the action to Update Distribution Points.

Secondary Sites

If there are any Secondary Sites in your environment the next step is to implement the CU on those sites. The server update package can be used to automate this. To target the site servers a collection can be built which is populated based on the following query:

    • 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_64 on SMS_G_System_ADD_REMOVE_PROGRAMS_64.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS_64.DisplayName = "System Center 2012 R2 Configuration Manager Secondary Site Setup"

Consoles

    As part of the implementation process on the site server the locally installed console was updated. Any remaining remote consoles in the environment can be updated using the console upgrade package.

    To build a collection containing the machines with the console installed the following query could be 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 = "System Center 2012 R2 Configuration Manager Console"

    Clients

    Last but not least we also need to get the CU installed on our clients. There are multiple approaches to accomplish this; one method could be to deploy the client update packages created automatically during the implementation process.

As there is a package per processor architecture we will also create matching collections to target our deployments. This is an example query for a collection containing all 64-bit clients with a client version not equal to CU4:

  • 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_SYSTEM on SMS_G_System_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_R_System.ClientVersion != "5.00.7958.1501" and SMS_G_System_SYSTEM.SystemType = "X64-based PC"
    The query for the collection with 32-bit clients is identical; just replace “x64-based PC” with “x86-based PC”.

A client with CU4 installed will display the following version in its properties:

image

Version numbers for some of the components are also updated:

imageimage

 

As you can see the experience for implementing this CU is pretty straightforward and identical to the previously released CU’s.

Until next time!

Tim

Avatar of timdk

by timdk

Cumulative Update 4 for System Center 2012 R2 Configuration Manager released!

3:00 pm in Configuration Manager by timdk

metrofixMicrosoft has released Cumulative Update 4 for System Center 2012 R2 Configuration Manager.

This CU includes a large list of fixes for various issues. Details on those fixes and information on added functionality can be found in KB3026739.

PowerShell changes are documented in a separate KB article KB3031717. Additionally the update includes performance optimizations for data replication, an Endpoint Protection platform update (KB2998627) and OS Support for Max OSx 10.10 and Suse Linux Enterprise Server 12.

A few interesting reads about this CU which were published earlier today:

Until next time!

Tim

Avatar of timdk

by timdk

Cumulative Update 3 for System Center 2012 R2 Configuration Manager released!

7:26 am in Configuration Manager by timdk

Yesterday Microsoft has made available Cumulative Update 3 for System Center 2012 R2 Configuration Manager.

Details on the issues that were fixed, and other additional changes introduced by this CU, can be found here: http://support.microsoft.com/kb/2994331

As we saw with earlier Cumulative Updates the changes related to Powershell are documented in a separate article. Read more about those here: http://support.microsoft.com/kb/2999304

Stay tuned for more details on how to implement this CU soon.

Tim

Avatar of timdk

by timdk

Implementing Configuration Manager 2012 R2 Cumulative Update 2

5:37 pm in Uncategorized by timdk

This blog post outlines the installation of Cumulative Update 2 for Configuration Manager 2012 R2 in our lab. Details about this update are documented in KB2970177. Note that this CU introduces some changes to Windows PowerShell which are documented in a separate KB article KB2962855. Additionally CU2 also adds support for Ubuntu v14.04 – details about this update for the Linux/Unix Client are documented in a third article KB2976481.

Note that this update is applicable for Configuration Manager R2 only, if you are currently still running Configuration Manager 2012 SP1 please refer to my previous blog post on implementing Cumulative Update 4 for ConfigMgr SP1.

Before we begin we need to get the sources for the CU here.

The CU is applicable directly to the following components:

    • CAS
    • Primary Sites (standalone or in a hierarchy)
    • Secondary Sites
    • SMS Provider(s)
    • Console(s)

    Additionally it contains updates for the following components:

    • CAS
    • Primary Sites
    • Secondary Sites
    • SMS Provider(s)
    • Consoles
    • Clients

    The lab we are upgrading does not contain all the components listed above, a CAS and Secondary Site(s) are not present.

        Primary Site

      Cumulative Updates for Configuration Manager are implemented top-down so we start with the site server of the standalone primary site. Before running the installer with elevated privileges ensure there are no more console connections.

    image

        The installation is started.

      image

        Click Next on the welcome screen.

      image

      Accept the license terms and click Next.

      image

      Verify all prerequisite checks were passed and click Next.

      image

      Leave the option to update the (locally installed) console.

      image

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

      image

      During the setup process we can opt to create packages to support updating other components in the infrastructure. Leave the options to have these packages created and click Next.

      image

      Leave the default settings for the servers package and click Next.

      image

      Leave the default settings for the console package and click Next.

      image

      Leave the default settings for both the x86 and x64 client package and click Next.

      image

      Review the setup summary and click Install when ready.

      image

      Installation progress is shown.

      image

      Click next when the installation is finished. In our small lab it took about 10 minutes.

      image

      Click Finish to close the installation wizard. As indicated we will need to do a reboot.

      image

      More details about the installation and what is happening under the hood can be found in the log file located in the %windir%\temp folder. The last lines of the log should also state successful installation and the reboot requirement.

      Once the system is back online there are a few ways to verify the CU2 installation. First method is to look for the following entries in Programs & Features > View Installed Updates.

      image

      In the registry we can also verify the CU level (in HKLM\Software\Microsoft\SMS\Setup)

      image

      And also in the properties through the Console:

      image

       

      During the setup we opted to have some packages created to support implementing CU2 on other components in our infrastructure. These packages should now be visible in the Software Library. Browse to packages and type R2 CU2 in the search box to quickly locate those packages.

      image

      Important: Do not forget to distribute the content of these packages to your Distribution Points!

      Important (2): Do not forget to update your boot images. This can be done by selecting a boot image, right-clicking it and then selecting the action to Update Distribution Points.

      Secondary Sites

      If there are any Secondary Sites in your environment the next step is to implement the CU on those sites. The server update package can be used to automate this. To target the site servers a collection can be built which is populated based on the following query:

        • 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_64 on SMS_G_System_ADD_REMOVE_PROGRAMS_64.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS_64.DisplayName = "System Center 2012 R2 Configuration Manager Secondary Site Setup"

        Consoles

        As part of the implementation process on the site server the locally installed console was updated. Any remaining remote consoles in the environment can be updated using the console upgrade package.

        To build a collection containing the machines with the console installed the following query could be 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 = "System Center 2012 R2 Configuration Manager Console"

      Clients

      Also our clients within the environment need to be brought up to the level of the Cumulative Update. There are multiple approaches to accomplish this; one method could be to deploy the client update packages created automatically during the implementation process.

      As there is a package per processor architecture we will also create matching collections to target our deployments. This is an example query for a collection containing all 64-bit clients with a client version not equal to CU1:

      • 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_SYSTEM on SMS_G_System_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_R_System.ClientVersion != "5.00.7958.1303" and SMS_G_System_SYSTEM.SystemType = "X64-based PC"
        The query for the collection with 32-bit clients is identical; just replace “x64-based PC” with “x86-based PC”.

      A client with CU2 installed will display the following version in its properties:

      image

      Also the component version numbers are updated, looks like the same components were in scope as with CU1 a few months ago.

      imageimage

       

      That’s it for now in our lab.

      Good luck with your CU2 implementation!

      Tim

      Avatar of timdk

      by timdk

      Cumulative Update 2 for System Center 2012 R2 Configuration Manager released!

      9:30 pm in Configuration Manager by timdk

      Just before the weekend kicks off Microsoft has released Cumulative Update 2 for System Center 2012 R2 Configuration Manager. This update contains all previously released updates and hotfixes for Configuration Manager R2.

      Details about the issues fixed in this Cumulative Update and also download information can be found here: http://support.microsoft.com/kb/2970177

      Note that, similar to CU1, the Powershell changes in Cumulative Update 2 are outlined in a separate KB Article: http://support.microsoft.com/kb/2962855 . To coincide with the release of CU2 a new version of the Windows Phone 8.1 extension has also been made available. More details about that can be found here.

      Enjoy the weekend!

      Tim

      Avatar of timdk

      by timdk

      ConfigMgr Toolkit 2012 R2 – Collection Evaluation Viewer

      8:56 am in Configuration Manager by timdk

      A while back I have blogged about the DP Job Queue Manager. Today we will have a further look into another great utility in the Configuration Manager 2012 R2 toolkit: the Collection Evaluation Viewer (CEViewer.exe).

      The main purpose of the Collection Evaluation viewer is to assist in troubleshooting issues related to collection evaluation. We will now test drive the tool in a lab to further explore the possibilities.

      In case you did not download the toolkit yet, you can get it from the Microsoft download site here. The installation is really straightforward and we will not outline those details during this post. Instead we will fire up the utility straight away.

      image

      Before doing anything else I would recommend to first have a look at the last tab entitled about Collection Evaluation. This tab contains details on how to collection evaluation process runs and will help you to better understand the other queue tabs.

      image

      Now that we have some insights on how the queuing works, lets go to the first tab and provide the connection details to connect to the primary site. Connection details are shown at the bottom of the window.

      image

      Moving on to the Full Evaluation tab – this is where things become interesting. When looking specifically into performance issues the columns Run Time (Seconds) and Percent will be the most interesting ones: the first one logs how long the last evaluation took and the Percent column shows the percentage of evaluation time for this collection over the total (all collections) evaluation time. This should help you spot problematic collections straight away.

      Additionally we can also find more details about the last time the collection was evaluated, when the next evaluation time will be, and what the result of the last evaluation was in regards to membership and when that change took place.

      image

      The Incremental Evaluation tab show information similar to the Full Evaluation tab, but this time for collections that have the incremental evaluation setting enabled. Also here we can easily spot problematic collections based on the Run Time and Percent columns.

      image

      The All Queues tab gives a complete overview of the different queues. Before taking the screenshot above I triggered a membership update on a few demo collections. As this is a manual action the collections are listed in the manual update queue. Notice that an estimated completion time is listed for both collections of which the membership is currently being evaluated.

      image

      The remaining (color-coded) tabs each represent a different queue. The screenshot above for to the manual update queue and lists a set of collections for which I had triggered a membership update. Here we can see the estimated run time and estimated completion time for each of the collections.

      The remaining tabs are for the queues for new collections, collections with full updates or collections with incremental updates and work in the exact same way.

      To finish up this post I would like to add that this tool can only be used with Configuration Manager 2012 R2. It will not work with previous versions. On an SP1 site we were able to connect to the site but when browsing to any of the other tabs in the tool it errors out as shown in the screenshot below.

      clip_image002

       

      That concludes our overview and test drive of this very interesting tool in the Configuration Manager 2012 R2 Toolkit. I hope this information was useful and will encourage you to download the toolkit and start using these tools.

      See you around!

      Tim