Archive

Posts Tagged ‘R2’

Implementing Configuration Manager 2012 R2 Cumulative Update 2

July 7, 2014 Leave a comment

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 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

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

      June 27, 2014 Leave a comment

      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.

      Stay tuned for more information as soon as I have had the chance to implement this CU in my lab environment.

      In the meantime: enjoy the weekend!

      Tim

      ConfigMgr Toolkit 2012 R2–Collection Evaluation Viewer

      April 16, 2014 Leave a comment

      A few weeks ago 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, it is available 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.

      Until next time!

      Tim

      Implementing Configuration Manager 2012 R2 Cumulative Update 1

      April 10, 2014 7 comments

      This post outlines the implementation of Cumulative Update 1 for Configuration Manager 2012 R2 in a lab environment. Note that this update is applicable for 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.

      The detailed description and download link for this Cumulative Update  are available here: http://support.microsoft.com/kb/2938441/en-us .

      The CU is applicable directly to the following components:

        • CAS
        • Primary Sites
        • 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 infrastructure on which we will implement the CU is rather small: a standalone primary site with the site database and all site system roles installed on a single server. Additionally there is one remote Distribution Point. There are no secondary sites.

      Primary Site

      A CU implementation needs to be done from top to bottom so we start with the site server first.  Make sure there are no console connections open and then run the installer with elevated privileges.

      image

      The installation wizard is started:

      image

      Click Next on the welcome screen.

      image

      Accept the license terms and click Next.

      image

      Review all checks and click Next.

      image

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

      image

      Leave the option to update the Site Database and click Next.

      image

      As part of the setup process Configuration Manager can create packages to update other components part of the environment. Leave the options to have these packages created and click Next.

      image

      Leave the default options for the first Update Package and click Next.

      image

      Leave the default options for the update package for consoles and click Next.

      image

      And finally also leave the default options for the remaining packages for clients. Click Next.

      image

      Review the setup summary and click Install to kick off the installation.

      image

      Installation progress is shown.

      image

      If you are interested in what is happening under the hood make sure to have a look at the installation log files in the %windir%\temp directory.

      image

      Click Next once all steps have been completed successfully.

      image

      Click Finish and restart the server.

      In ARP there should be two entries indicating that the Cumulative Update was installed on the system: one for the site server and one for the console. Both are shown in the screenshot below:

      image

      Also in the registry the CU level for the site can be verified:

      image

      When opening the About Configuration Manager window from the console the version should show 5.0.7958.1203

      image

      Remember that at one point we opted to have packages created to implement the CU on other components. These packages are now available in the Software Library workspace:

      image

      Do not forget to distribute the content for these packages to your Distribution Points. This is not something that is done automatically!

       

      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 as well. Any remote consoles in the environment can be updated using the console upgrade package which was automatically created during the installation process.

        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 also the 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 which were also 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.1203" 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 the CU installed should have the following version displayed in the properties:

      image

       

      And the updated components:

      image  image

       

      That concludes the work in our lab. I hope this post gives you a good overview on how you could implement the Cumulative Update in your environment.

      Until next time!

      Tim

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

      March 28, 2014 Leave a comment

      Microsoft has released Cumulative Update 1 for System Center 2012 R2 Configuration Manager. This update contains all previously released updates and hotfixes for Configuration Manager R2.

      Full details and download information can be found here: http://support.microsoft.com/kb/2938441/en-us 

      Note that next to fixing issues, the CU also introduces some changes for Windows Powershell. These changes are documented in a separate KB: 2932274

      I will be test driving this CU in my lab shortly so stay tuned for more information.

      ConfigMgr Toolkit 2012 R2 – DP Job Queue Manager

      March 24, 2014 Leave a comment

      One of the new server tools in the Configuration Manager 2012 R2 Toolkit is the Distribution Point Job Queue Manager (DpJobMgr.exe). This tool helps the Configuration Manager administrator in managing, monitoring and troubleshooting content distribution throughout his environment.

      Lets have a closer look at the tool and how it can be used.

      image

      On the connect tab the Primary Site Server name needs to be specified before clicking on Connect. Connection status and results are shown in the bottom left corner. Make sure the connection is successful before moving on.

      image

      The overview tab shows a list of all Distribution Points within our lab environment. Note that the locally installed Distribution Point on the site server is not displayed and also not taken into account in the Total Distribution Points count.

      You can opt to manually refresh the list if you are in the process of doing content deployments. Alternatively the tool can auto-refresh the list based on a set interval. Note that the default interval is 2 minutes. You cannot set a value lower than those 2 minutes.

      image

      The Distribution Point info tab displays details about the ongoing content transfers. Once the transfer is completed, the entry for that content is removed from the list. The progress column seems to be updated at a slow pace and as a result I found that smaller content was distributed even before any percentage was ever displayed.

      image

      Managing jobs is done from the next tab. Here you can change priorities in the queue and also cancel any distribution jobs that are ongoing.

      image

      The last tab is the help tab. This tab is purely informational and displays some general help information.

      Now in a lab off course the amount of content to be distributed and DP’s to be targeted is very low. In large enterprise environments where there is much content and many Distribution Points to be targeted I believe this will be a very helpful utility.

      Important: this tool only works with Configuration Manager 2012 R2 and is not compatible with previous versions. On an SP1 site for example we were able to connect to the site but while retrieving data the tools throws multiple errors like the one displayed below:

      DPQueueMgr_SP1_Error

       

      Until next time!

      Tim

      Mastering System Center 2012 R2 Configuration Manager Book

      January 31, 2014 Leave a comment

      CfgMgr_Book_MasteringR2 This book, written by Dutch MVP Peter Daalmans and two Microsoft Premier Field Engineers Santos Martinez and Brett Bennett, is definitely one to add to your bookshelf as a Configuration Manager administrator.

      Just today Peter has announced on his blog that the book is almost ready to hit the presses and is expected to be released sometime in March. This is the description published on Amazon:

      Completely updated for System Center 2012 R2 Configuration Manager, this comprehensive book provides intermediate and advanced coverage of all aspects of the product, including planning and installation, migrating from previous versions of Configuration Manager, deploying software and operating systems, security, monitoring and troubleshooting, and automating and customizing.

      Click here for more info and pre-ordering.

      Enjoy Reading!

      Tim