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

  • Comments 27
  • Likes

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
  • Have you removed "Want to drastically quiet down your ConfigMgr 2007 MP"? The link doesnt work?

    Does this also work for 6.0.6000.3?

  • @Maekee

    Yes - I deleted that post since I didnt want people to download it anymore - as it no longer applies.  It is not necessary for this new version

  • Hi Kevin

    After we imported the new MP for SCCM - we are getting a lot of Alert with "Script error."  

    e.g. this one:

    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.

    Commen for all of them is this:

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

    Is this a known error?

  • @RHC - I have been hearing that one.  Are you running SCCM on 64bit Server 2008R2 by chance?

  • We have the same %PROCESSOR_ARCHITECTURE error.

    The error seems to be random - i.e. not every time the script runs. I have verified the namespace, class and value exist on all our servers.

    We are running on Server 2008 R2.

    Perhaps this is due to a timeout querying the value which the script does not handle correctly?

  • Hi,

    did you find a solution for the "%PROCESSOR_ARCHITECTURE error."?

    we have the same problem, windows 2008 r2 with config manager 2007 SP2 R3...

    thanks

    Adrian

  • Hi,

    Quite a long thread about this issue on SC Central, no solution though.

    I'm also experiencing the problem, Server 2008 R2, Config Mgr 2007 SP2

    www.systemcentercentral.com/.../Default.aspx

  • Hi all,

    Just wondering if there is a solution to the %PROCESSOR_ARCHITECTURE issue?  I'm getting 700+ alerts with high repeat counts since the upgrade.

    Running Server 2008 R2 SP1 with SCCM R3 SP2.

    Cheers, Leigh.

  • Hi,

    I'm getting the same issue here too...

    Just out of curiosity shouldn't the variable be '%PROCESSOR_ARCHITECTURE%' rather than having a missing trailing percent symbol? Maybe that's why it can't be read?

  • Looking at the script (in the C:\Program Files\System Center Operations Manager 2007\Health Service State\Management Packs\Microsoft.SystemCenter.ConfigurationManager.2007.{15B57583-68DE-902F-D349-2D4718F3A7A2}.{2C1F473C-4D0F-85B4-EA00-C36190EEDEFF}.xml file) I can see that the error is just a typo in the error string.

    Interestingly there is a section commented out with "Removing use of unreliable CheckWow64RegistryKeyExists function" and a bit underneath "Adding this instead" where the error is being generated from

    I've recommissioned the 'unreliable' CheckWow64RegistryKeyExists function to see if the error goes away.

    J.

  • The above file had a bunch of sections with the "Removing use of unreliable CheckWOW64RegistryKeyExists function" lines in them. On the OpsMgr central server I edited the file replacing each section with this:

    'Removing use of unreliable CheckWow64RegistryKeyExists function

    If (CheckWow64RegistryKeyExists() = True) Then

       REG_PATH_SMS = "SOFTWARE\Wow6432Node\Microsoft\SMS"

    Else

       REG_PATH_SMS = "SOFTWARE\Microsoft\SMS"

    End If

    'Adding this instead

    'On Error Resume Next

    'Dim sCimv2namespace, sProcArchQuery, oProcArchObjectSet, oProcArchObject, sProcArch

    'sCimv2namespace = "winmgmts:\\.\root\cimv2"

    'sProcArchQuery = "Select * From Win32_Environment Where Name = ""Processor_Architecture"""

    'Set oProcArchObjectSet = WMIExecQuery (sCimv2namespace, sProcArchQuery)

    'Set oProcArchObject = oProcArchObjectSet.Item("Win32_Environment.Name=""PROCESSOR_ARCHITECTURE"",UserName=""<SYSTEM>""")

    'sProcArch = oProcArchObject.VariableValue

    'On Error GoTo 0

    'Select Case sProcArch

    'Case "AMD64"

    ' REG_PATH_SMS = "SOFTWARE\Wow6432Node\Microsoft\SMS"

    'Case "x86"

    ' REG_PATH_SMS = "SOFTWARE\Microsoft\SMS"

    'Case Else

    ' ScriptError "read %PROCESSOR_ARCHITECTURE environment variable from Win32_Environment WMI class."

    'End Select

    Then deleted the contents of the "C:\Program Files\System Center Operations Manager 2007\Health Service State\Management Packs" folder on the clients and restarted the System Center Management service.

    Problem has now gone and no more have surfaced (so far) so I presume that the script is now working reliably on my servers.

    __________

    boredazfcuk

  • same issue here...

    ' ScriptError "read %PROCESSOR_ARCHITECTURE environment variable from Win32_Environment WMI class."

    we have an open case on this, but now resolution till now. seems to be another WMI bug...

    meanwhile will try the workaround check registry instead of wmi...

    another issue could be fixed for us - we had problems with the time zone settings:

    alert: Collection Evaluation task 'xxxx'' is still running. The task started at 'xxxxx' and was expected to complete within '300' seconds. It has now run for '3601' seconds.

    There is a script error how to handle summer/wintertime!

    best regards,

    peter

  • On the "%PROCESSOR_ARCHITECHTURE%" issue - we are pretty sure we have the root cause nailed down to a WMI issue with how Win32_Environment queries work.... it is a random issue.  The script works most of the time but you do end up with some of these.  It comes down to multiple scripts running at the same time hitting this same namespace.  I am working to identify which scripts call on this, and how to create a strategy to limit them stepping on each other as a short term workaround.

  • I just set up an SCOM 2007 R2 instance with the 6.0.6000.3 MP monitoring my SCCM server, and I've gotten a couple of the:

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

    Errors, on PXE and and NLB Management point (we aren't using any NLB).  The Collection Evaluation error messages:

    Current Task Duration (seconds):

    3603

    Maximum Task Duration (seconds):

    300

    Are also occurring--glad to know that my rules are fine and it's just daylight savings time throwing things off.  Looking forward to a MP update (or patch/fix) for these since I'm not so keen on manually editing the MP scripts on the servers right now.

  • @Kevin

    Do you have any update on "%PROCESSOR_ARCHITECHTURE%" issue?

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Search Blogs