Kevin Holman's System Center Blog

Posts in this blog are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of UseAre you interested in having a dedicated engineer that will be your Mic

OpsMgr: MP Update: New ConfigMgr 2007 MP–version 6.0.6000.3 - resolves top issues

OpsMgr: MP Update: New ConfigMgr 2007 MP–version 6.0.6000.3 - resolves top issues

Rate This
  • Comments 26

A new MP has shipped for Configuration Manager 2007, which is MP version 6.0.6000.3

 

This MP update will upgrade your existing MP.  It was updated to resolve the top customer issues with this management pack.

 

The following changes, also covered in the updated MP guide, are in version 6.0.6000.3.

 

  • Consolidation Event Rules have been disabled to prevent the generation of false alerts.

This is a big deal, this caused a lot of alert noise to repeat, even for status messages that no longer existed!  I wrote about this previously at the following link – and provided an addendum MP which contained overrides to disable these consolidation rules.  My addendum MP is no longer necessary and can be removed, if you were running it:

Want to drastically quiet down your ConfigMgr 2007 MP-

 

  • Operating system architecture detection logic was updated to determine 64-bit operating systems.
  • You no longer have to run the SQL Server query to clean up the localizedtext tables as part of the post-installation cleanup

If you were running the Post-R2 LocalizedText cleanup scripts on a regular basis to control the size of your localizedtext table – this should no longer be necessary.  I wrote more about that here: 

Clean up LocalizedText

 

  • Scripts that target site database servers now retrieve time values directly from servers running instances of SQL Server instead of site servers to avoid time-zone discrepancies.

This caused a lot of false alerts and script errors previously.  Big fix.

 

  • Site hierarchy discovery now succeeds even if a site or component server does not have a fully qualified domain name (FQDN) configured.

This was a complaint which caused the topology diagrams to not populate.

 

  • The AlertLevel property can now be overridden, giving you control over the severity level.

Now ALL alerts expose overrides for priority and severity, which is critical for your tuning for notifications.

 

  • All monitors and rules are now public.

Which means you can override and add diagnostics/recoveries to anything.

 

  • The "ConfigMgr 2007 Collection Evaluations Tasks" script has been updated to let you monitor a collection that has a NULL StartTime value.The "ConfigMgr 2007 Collection Evaluations Tasks" script now uses CollectionID instead of Collection Name to track collection tasks.

 

 

Sweet update!  Recommend you get this one – and review your existing overrides to ensure they are still needed.  Kudos to the support teams for pushing this through.  Read the official announcement here: 

http://blogs.technet.com/b/configmgrteam/archive/2011/09/30/release-announcement-system-center-monitoring-pack-for-configuration-manager-2007-sp2-converted.aspx

 

 

Known issues in this MP:

 

1.  If your ConfigMgr servers are running on the 64bit Server 2008 R2 platform, you might see alerts about failing to read %PROCESSOR_ARCHITECTURE:

ConfigMgr 2007 Software Update Point Health: Script error

[SERVERNAME]

- ConfigMgr 2007 Software Update Point Health: Script error.

The script 'ConfigMgr 2007 Monitor Server Health' running under processing rule '{D52DF5C6-0ECE-4E64-550A-608AD4E4FC02}' encountered a runtime error.

Failed to read %PROCESSOR_ARCHITECTURE environment variable from Win32_Environment WMI class.

This is an OS issue – with the WMI Win32_Environment class.  The scripts will work most of the time but randomly you will see failures of the scripts due to the inability to read from Win32_Environment

There is a hotfix available – you will need to open a support case with Microsoft to request this until it is available externally or included in a service pack.  The KB number to request is KB2692929

Comments
  • @RHC - Yes - last I heard, there is an update coming for Windows Server 2008 R2 to address the WMI issue.  There should be a KB article released at some point in the future on this topic.

  • Kevin, could you pls send me an email when the KB article comes out? oscar.forero@icbc.com

  • Update to original article:

    Known issues in this MP:

    1.  If your ConfigMgr servers are running on the 64bit Server 2008 R2 platform, you might see alerts about failing to read %PROCESSOR_ARCHITECTURE:

    ConfigMgr 2007 Software Update Point Health: Script error

    [SERVERNAME]

    - ConfigMgr 2007 Software Update Point Health: Script error.

    The script 'ConfigMgr 2007 Monitor Server Health' running under processing rule '{D52DF5C6-0ECE-4E64-550A-608AD4E4FC02}' encountered a runtime error.

    Failed to read %PROCESSOR_ARCHITECTURE environment variable from Win32_Environment WMI class.

    This is an OS issue – with the WMI Win32_Environment class.  The scripts will work most of the time but randomly you will see failures of the scripts due to the inability to read from Win32_Environment

    There is a hotfix available – you will need to open a support case with Microsoft to request this until it is available externally or included in a service pack.  The KB number to request is KB2692929

  • The hotfix is public for this now:  support.microsoft.com/.../2692929

  • On which systems do i have to install the hotfix?

    Only on my SCCM-servers?

    Thanks

  • Yep - only on SCCM server roles.  I cover this on my hotfix page:

    From:  blogs.technet.com/.../which-hotfixes-should-i-apply.aspx

    I recommend this hotfix for Server 2008 R2 machines that also host a ConfigMgr 2007 role, and you are using the ConfigMgr 2006 MP.  This fixes an annoying issue

  • We have an SCCM 2007 R2 environment running on Windows 2003 Server.  In our SCOM 2012 environment, I imported the SCCM MP and immediately got the %Processor_architecture alerts.  That hotfix is for Server 2008 R2.  Is there a fix for Windows 2003?

  • I have the same issue as DDog1111, running on a Windows 2003 server.  Do you know whether there is a fix for this?

    Thanks for your excellent blog posts, they really help.

  • We are running Windows 2008 R2 SP1 x64 and receiving this error on all of our SCCM servers but the patch will not install with "This udpate is not applicable to your computer".

    I have read through the website support.microsoft.com/.../2692929 and don't see how our OS is not applicable?

  • Since I have updated the ConfigMgr MP I got tons of 10706 and 10707 events ( 30 each seconds...)

    10706: The following error occurred connecting to the script data source for management group '%5', target computer '%6',and data type '%7' (HRESULT 0x%8).Some data may be lost.Please verify the Data source is running.%n%nOne or more workflows were affected by this.%n%nWorkflow name: %2%nInstance name: %3%nInstance ID: %4%nManagement group: %1

    10707 : The following error occurred submitting data to the script data source for management group '%5', target computer '%6',and data type '%7' (HRESULT 0x%8).Some data may be lost.Please verify the Data source is running.%n%nOne or more workflows were affected by this.%n%nWorkflow name: %2%nInstance name: %3%nInstance ID: %4%nManagement group: %1

    (example of worklows: SMSv4_Perf_Threshold__MP_DDR_Backlog__10000_over_3_hours_17_Rule

    example of instance name: Microsoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Management_Point_Servers_Installation )

    I have not found anything about thess events, do you know what is happening?

    Regards

  • Great Kevin,

    I have the same "%PROCESSOR_ARCHITECHTURE%" issue (on 2008R2 SCCM Server). I will download the hotfix from MS.

    Thanks.

Page 2 of 2 (26 items) 12
Leave a Comment
  • Please add 4 and 5 and type the answer here:
  • Post
Search Blogs