I asked the FixIt team for this a while back and they have delivered. Now if you ever run into the symptoms below the chances are good we can automatically fix it with just a few clicks of the mouse:
The Symptoms: When you use the fully qualified domain name (FQDN) or a custom host header to browse a local Web site that is hosted on a computer that is running Microsoft Internet Information Services (IIS) 5.1 or a later version, you may receive an error message that resembles the following:
HTTP 401.1 – Unauthorized: Logon Failed
Note You only receive this error message if you try to browse the Web site directly on the server. If you browse the Web site from a client computer, the Web site works as expected.
Additionally, an event message that resembles the following event message is logged in the Security Event log. This event message includes some strange characters in the value for the Logon Process entry:
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 537
Date: Date
Time: Time
User: NT AUTHORITY\SYSTEM
Computer: Computer_Name
Description: Logon Failure:
Reason: An error occurred during logon
User Name: User_Name
Domain: Domain_Name
Logon Type: 3
Logon Process: Ðùº
Authentication Package: NTLM
Workstation Name: Computer_Name
Status code: 0xC000006D
Substatus code: 0x0
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: IP_Address
Source Port: Port_Number
The Cause: This issue occurs when the web site uses Integrated Authentication and has a name that is mapped to the local loopback address.
The Fix: If you happen to come across any symptoms like this then take a look at the following Knowledge Base article:
896861 - You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or a later version
The cool part is that this KB article contains a link to a Wizard that will fix this issue for you automatically. All you have to do is download and run it. This Loopback issue impacts almost any product that uses IIS, including your very own favorite, System Center Operations Manager 2007.
Jarrett Renshaw | Content Quality Program Manager
The updated Configuration Manager 2007 SP2 Management Pack adds support for monitoring Configuration Manager 2007 SP2 in a 64-bit environment with Operations Manager 2007 R2 or Operations Manager 2007 SP1 with hotfix (KB971541) installed. This enables the Configuration Manager 2007 SP2 Management Pack to work with either the 32-bit or the 64-bit Operations Manager 2007 agent. Except for the 64-bit support, the other features and guidance for Configuration Manager 2007 Management Packs remain intact.
Note: As of today, KB971541 is not yet available. This update should be available within the next few days. When it becomes available it should be found here.
For all the details and to download the updated MP see http://www.microsoft.com/downloads/details.aspx?FamilyID=a8443173-46c2-4581-b3b8-ce67160f627b&displaylang=en
J.C. Hornbeck | Manageability Knowledge Engineer
Being able to react to a changing server infrastructure is important for achieving a rationalized or dynamic IT infrastructure. This becomes a necessity with virtualization and the dynamic natures of workloads sharing an infrastructure. With Microsoft System Center Server Management Suite Datacenter, understanding and reacting to the dynamic nature of workloads becomes possible with our Performance and Resource Optimization (PRO) Tips.
In this webcast, we detail the architecture of PRO Tips explaining the configuration, setup, and content of a PRO Tip along with a demonstration on how PRO Tips can rebalance the workload of a virtualized infrastructure, allowing customers to achieve savings in a more dynamic environment.
http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032429329&EventCategory=4&culture=en-US&CountryCode=US
J.C. Hornbeck | Manageability Knowledge Engineer
The Windows Client Monitoring Management Pack is built to detect, diagnose, and resolve hardware and software problems pertaining to Client 2000, XP, Vista and Windows 7 operating systems. Information and analysis on the issues that the system detected are collected by the MPs through an agent on the client machine and sent to OpsMgr where this data is converted into health state, alerts (if need be) and processed for business critical and aggregate reports. The MP gives a clear picture of catastrophic failures in your mission critical machines, trend-based alerts of significant changes to computer groups, in-depth views of health of individual machines, and reports that provide a landscape view of the health of all monitored clients.
Feature Summary
- Key Processor Performance Indicators
- Logical and Physical disk performance and free space
- Memory utilization
- Network health
- Health monitoring of key Windows Operating System services
- Comprehensive performance collections
- Availability and event reports
Release History
- 3/23/2007 - Original release of the English version of Client 2000/XP management packs, version 6.0.5000.0
- 5/11/2007 - Original release of the English version of Vista management pack, version 1.0
- 1/15/2008 - Guide update of Client 2000/XP management packs, version 6.0.5000.0
- 2/22/2008 - Updated release of Client 2000/XP management packs, version 6.0.6278.0
- 5/27/2008 - Release onto Microsoft Download Center of Client 2000/XP management packs, version 6.0.6278.0
- 2/16/2009 - Update release that includes business Critical monitoring for Vista and bug fixes for performance and aggregate monitoring, version 6.0.6520.0
- 10/26/2009 - Updated release, version 6.0.6729.0, with bug fixes for Vista MP and support for monitoring Windows 7
For more information and to download the updated Management Pack see http://www.microsoft.com/downloads/details.aspx?FamilyId=F55F1803-EAE6-4ED5-B2D2-9E1ADF98E325&displaylang=en&displaylang=en
J.C. Hornbeck | Manageability Knowledge Engineer
The DFS Replication Management Pack for System Center Operations Manager 2007 monitors the health of the DFS Replication service on Windows Server 2003 R2 and Windows Server 2008.
The DFS Replication Management Pack for System Center Operations Manager 2007 monitors the health of the DFS Replication service on Windows Server 2003 R2 and Windows Server 2008 computers. This management pack monitors events generated by the DFS Replication service. These events provide an insight into the health of the service and folders replicated on monitored computers. This management pack includes a dashboard view which can be used to monitor replication backlogs.
The management pack also features consolidation rules that monitor computers for frequent occurrences of certain operational conditions such as staging cleanups, sharing violations, replication conflicts etc.
Feature Summary
The following features are new in this release of the DFS Replication Management Pack:
- Alerts indicating outages of the DFS Replication service on monitored computers.
- Alerts indicating configuration issues that require administrative intervention.
- Dashboard view that enables tracking of replication backlogs on monitored computers.
- Tracking of intermittent operational conditions. These conditions are tracked by the management pack and show up either as warnings/errors. Transient warnings/errors flagged for conditions that are resolved over time are automatically corrected by the management pack, once those conditions are resolved.
- Intuitive state view indicating red, yellow and green states of the service, replication groups, and replicated folders configured on monitored computers.
- Monitoring of important service parameters such as staging area usage and replication conflicts generated.
For all the details and to download the MP see http://www.microsoft.com/downloads/details.aspx?FamilyID=c97b22a1-1fd6-426f-94ab-2a6e6db4aed0&displaylang=en
J.C. Hornbeck | Manageability Knowledge Engineer
A lot went on last week surrounding System Center Operations Manager 2007 so in case you might have missed one or two I have a quick recap below:
The System Center Operations Manager 2007 R2 Authoring Resource Kit was released: http://blogs.technet.com/momteam/archive/2009/10/21/system-center-operations-manager-2007-r2-authoring-resource-kit.aspx
The Failover Clustering Management Pack was updated: http://blogs.technet.com/momteam/archive/2009/10/22/failover-clustering-mp-updated.aspx
The Network Load Balancing Management Pack was updated: http://blogs.technet.com/momteam/archive/2009/10/23/updated-network-load-balancing-management-pack-available.aspx
Enjoy!
J.C. Hornbeck | Manageability Knowledge Engineer
Let’s say you’ve got a mixed version (SP1 and R2) Operations Manager 2007 environment and agents are commonly multi-homed. This works and is supported to enable a phased upgrade approach.
However, if you’re planning to multi-home new agents in this mixed version environment and you’re using the Discovery Wizard, be sure to first discover and install the agent in the SP1 Management Group first. If you discover and install the agent in the R2 Management Group first, the Discovery Wizard will fail in the SP1 Management Group because the R2 version of the agent will already be installed (downgrades via the wizard are not possible).
The Discovery Wizard will return something like this:
If you have already discovered and installed the agent in the R2 Management Group, you’ll need to modify the agent installation locally in Add or Remove Programs.
Here’s the actual text, to facilitate searching this post.
The Agent Management Operation Agent Install failed for remote computer computername.opsmgrlab.com.
Install account: OPSMGRLAB\administrator
Error Code: 80070643
Error Description: Fatal error during installation.
Microsoft Installer Error Description:
For more information, see Windows Installer log file "C:\Program Files\System Center Operations Manager 2007\AgentManagement\AgentLogs\computernameAgentInstall.LOG
C:\Program Files\System Center Operations Manager 2007\AgentManagement\AgentLogs\computernameMOMAgentMgmt.log" on the Management Server.
Hope this helps,
Jonathan Almquist | Microsoft Premier Field Engineer
We just published a new Knowledge Base article for System Center Operations Manager 2007. This one describes the OpsMgr 2007 R2 Cross Platform agent update.
This update enables System Center Operations Manager 2007 R2 to support the following platforms:
- SUSE Linux Enterprise Server 11 (32-bit and 64-bit)
- Solaris Zones (whole and sparse zones)
The latest versions of all Operations Manager 2007 R2 Unix and Linux Agents are included in this update.
Additionally, this update fixes the following problems:
Problem 1
The Operations Manager 2007 R2 Cross Platform Agent intermittently creates defunct processes on the UNIX system or on the Linux system. This behavior occurs in the following scenario:
- The password for the account that connects to the server is changed on the UNIX system or on the Linux system. For example, the password for the UNIX Action Account or for the UNIX Privileged Account RunAs Account is changed.
- The password is not updated on the Operations Manager server.
When this problem occurs, the defunct processes (scxcimservera) continue to exist until the Cross Platform Agent restarts. Therefore, additional resources are consumed.
Problem 2
The Cross Platform Agent may not discover soft partitions on Solaris systems. Therefore, the disk provider may be unloaded, and then the Cross Platform Agent may stop collecting information from the system disks.
Problem 3
The Cross Platform Agent may not restart after the AIX server restarts.
For more information and to download the update see:
KB973583 - Description of System Center Operations Manager 2007 R2 Cross Platform Agent Update
J.C. Hornbeck | Manageability Knowledge Engineer
Updates to the Exchange Management Packs for Operations Manager 2007 are now available on the Management Pack Catalog.
The following list contains the issues that are fixed in version 6.0.6702.0 of the Exchange Server 2003 Management Pack.
· Fixed issues in product knowledge articles.
· Fixed issue with version number for Exchange Server 2003 discovery. The discovery now checks the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\setup\newestbuild for a range of version numbers that are greater than or equal to 6944 and less than 9000.
· Added missing descriptions.
· Changed default time-out value to 300 seconds for the following discovery rules:
· Exchange 2003 Topology Discovery
· Exchange 2003 Database Discovery
· Exchange 2003 Active Sync Discovery
· Exchange 2003 Outlook Mobile Access Discovery
· Exchange 2003 Outlook Web Access Discovery
· Exchange 2003 Queue Discovery
· Exchange 2003 Server Role attribute Discovery
· Exchange 2003 Mailflow Discovery
· Changed default time-out value to 300 seconds for the following monitors and rules:
· SSL should be enabled
· Log Files Truncated Monitor
· SMTP Queues Monitor
· Performance Collection Rule for Exchange ActiveSync logon latency
· Performance Collection Rule for MAPI logon latency
· Performance Collection Rule for Outlook Mobile Access logon latency
· Performance Collection Rule for Outlook Web Access logon latency
· Performance Collection Rule for Mail flow receiver
· Event Collection Rule for Publish_ExMP_Data
· Check Mailbox Store Monitor
· Check Services Monitor
· Check Services Frontend Monitor
· Disk Space Monitor
· Disk Space Monitor (Three States)
· Exchange Active Sync Monitor
· Exchange MAPI Logon Monitor
· Outlook Mobile Access Monitor
· Outlook Web Access Monitor
· Exchange Mail Flow Monitor (Receiver Part)
· Exchange Mail Flow Monitor (Sender Part)
· Query local Domain Controllers
· Fixed sort in alert views.
· Changed display name for class Microsoft.Exchange.ApplicationComponent from “Exchange Component” to “Exchange Application Component” to differentiate it from the class Microsoft.Exchange.ExchangeComponent.
· Fixed issue where topology discovery would fail when an Exchange Server did not have an agent installed. The topology discovery script now only discovers agent-managed Exchange servers, and each agent discovers only itself. The topology script needs to be enabled on all Exchange servers in order to see a complete topology.
· Fixed an issue with some performance rules failing to collect data.
You can access the updated MP here: http://www.microsoft.com/downloads/details.aspx?FamilyId=9FF454F4-6D34-4FB9-9E0B-F5B68C6EDC4F&displaylang=en&displaylang=en
J.C. Hornbeck | Manageability Knowledge Engineer
The System Center Operations Manager 2007 R2 Cross Platform Update adds fixes for a defunct process issue on Unix/Linux Servers, as well as, adds support for SUSE Linux Enterprise Server 11 (both 32-bit and 64-bit versions) and Solaris Zone support.
Feature Summary:
The System Center Operations Manager 2007 R2 Cross Platform Update supports the monitoring of Unix/Linux Servers including:
-
Monitoring of SUSE Linux Enterprise Server 11 servers (both 32-bit and 64-bit versions)
-
Support of Solaris Zones
-
Fix for defunct Process issue
-
The Cross Platform Agent may not discover soft partitions on Solaris systems. Therefore, the disk provider may be unloaded, and the Cross Platform Agent may stop collecting information from the system disks.
-
The Cross Platform Agent may not restart after the AIX server reboots.
The latest versions of all the Operations Manager 2007 R2 Unix/Linux agents are included in this update.
For all the details and to download the update see http://www.microsoft.com/downloads/details.aspx?FamilyID=4a41a8be-0a37-4bd2-b5b1-026468b317fb&displaylang=en
J.C. Hornbeck | Manageability Knowledge Engineer
You’ve heard about it and read about and now you’ll soon have the chance to try it out yourself. The System Center Online Desktop Manager beta is coming soon:
The System Center Online team has been working hard in preparation for its next beta release of System Center Online Desktop Manager, expected in the fall of this year. This exclusive beta will only be available to a select number of customers. Our last beta was only offered to a small audience and resulted in a lot of great feedback from the customers who participated. This time we are widening the scope to include a few hundred customers.
Here's what will be included in the upcoming release:
- Updates Management Workload: Manage the Microsoft updates from a web-based console. Review available updates, choose updates and deploy to selected computers or groups of computers. Imagine WSUS from the cloud.
- Policy Workload: Provides the ability to configure operational settings of the Windows Update and Anti-Malware agents installed on the client computers.
- Anti-malware Workload: Review anti-malware, anti-virus status and remedial actions from the SCODM console. Ensure managed computers have up-to-date signatures.
- Assets Workload: Collect detailed hardware and software inventory on managed computers. View this information in reports. Use the License reconciliation feature to load your Microsoft volume license agreement information and compare installed application quantities with licensed quantities.
- Alerts Workload: Helps you quickly and easily find problems (or potential) on your computers. You can also get help on how to solve the problem or how to start troubleshooting.
We are looking for customers who are interested in participating in the fall beta! If you are an IT Pro who manages an IT environment and are interested in participation, we'd like to hear from you.
For all the details see http://blogs.technet.com/systemcenteronline/archive/2009/09/23/system-center-online-desktop-manager-beta-is-coming-soon.aspx
Enjoy!
J.C. Hornbeck | Manageability Knowledge Engineer
The Operations Manager Product Team blog just posted a request for feedback and a vote for which new features you’d like to see in the next version of the product. If you want to make your voice heard then now’s your chance:
Most of you know we recently launched an easy to reach feedback portal for you all to file bugs and/or suggestions for the next version of Operations Manager - located here:
https://connect.microsoft.com/OpsMgr/Feedback
All you need to do is be registered on Connect. What is cool is that we are now able to utilized the "Vote" feedback mechanism to help prioritize our work based on feedback from YOU. For example, today I can see 4 items that have had at least 3 votes. The first (scheduling maintenance mode) which we plan to do for v.next; the second being adding the OE tool in the product, etc., etc…
For all the details see http://blogs.technet.com/momteam/archive/2009/10/13/we-need-your-vote.aspx
Enjoy!
J.C. Hornbeck | Manageability Knowledge Engineer
Just in case you missed it, last week the Operations Manager Product Team announced that:
“…the first out of band update to the Operations Manager Management Pack has been released to the MP catalog! This MP package (Version 6.1.7533.0) is specific to OpsMgr 2007 R2 and will not import on product versions prior to that.
Following are some changes made in this release that I’d like to highlight, but you can refer to the MP guide for the full list:
1. Based on customer and blogger feedback we’ve improved the monitoring around excessive agent memory utilization.
a. For starters, the monitors have been updated so that the value of the sample must exceed the threshold for a specific number of consecutive samples, as opposed to the average of the samples over the consecutive samples. This will increase the accuracy of the monitors by handling periodic spikes in resource utilization better.
b. Secondly the thresholds have been made less stringent on the agents to better align with a more realistic baseline (6,000 handle counts and 300 MB in private bytes)
2. Tons of missing display names, descriptions, and product knowledge where added. For a good example of the improvements check out the rule Data Access Service Spn Registration.
3. We’ve added the rule “Collects Opsmgr SDK Service\Client Connections” to collect the number of connected clients for a given management group. This data is shown in the view “Console and SDK Connection Count” under the folder “Operations Manager\Management Server Performance”.
4. The following rules and monitors are now disabled by default as they are generally not actionable:
a. A GroupPopulator module unloaded due to an unrecoverable error
b. Health Service Cannot Find Management Group
c. Data Validity Check
d. Root Connector Data Validity Check
5. Updated the alert suppression criteria for the rule “Alert on Dropped MultiInstance Performance Module” in order to significantly reduce the alert volumes generated by this rule and make it easier to identify the root cause.
6. Fixed the configuration of the rule “IIS Discovery Probe Module Execution Failure” so that the parameter replacement will now work correctly for alert suppression and generating the details of the alert’s description.”
For all the details see http://blogs.technet.com/momteam/archive/2009/10/07/opsmgr-2007-r2-mp-version-6-1-7553-0-is-released.aspx
J.C. Hornbeck | Manageability Knowledge Engineer
Learn how to optimize Microsoft System Center Operations Manager for cross-platform devices, applications, and regulatory auditing requirements, and see how to create advanced line-of-business (LOB), geographic, and executive-level dashboards in Microsoft Office SharePoint Server 2007. This webcast includes more than 40 minutes of demonstrations, and we provide customer examples of:
- Supporting Sarbanes Oxley (SOX) and PCI audit requirements using Secure Vantage Technologies.
- Building intelligent views across solutions using Savision Live Maps.
- Integrating solutions with SharePoint Server.
Presenters: Jeremiah Beckett, President, Secure Vantage Technologies, Ryan Brennan, Chief Technology Officer, Secure Vantage Technologies, Rob Doucette, Software Development Manager, BridgeWays, and Dennis Rietvink, President, Savision
Language(s): English.
Product(s): Microsoft System Center Configuration Manager.
Audience(s): IT Generalist.
Duration: 60 Minutes
Start Date: Friday, October 09, 2009 8:00 AM Pacific Time (US & Canada)
http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032425621&EventCategory=4&culture=en-US&CountryCode=US
J.C. Hornbeck | Manageability Knowledge Engineer
Steve Rachui posted Part 3 in his series on monitors in Operations Manager 2007. If you liked the first two then you’ll love this one:
This is part 3 (and last) of my series of posts describing monitors. The first post, found here, discussed unit monitors, which are the engine of monitoring. The second post, found here, discussed aggregate monitors, the ‘umbrella’ monitor sitting above unit monitors and reflecting their collective health forward – ultimately all the way to the class level.
To continue reading see http://blogs.msdn.com/steverac/archive/2009/10/05/understanding-monitors-in-opsmgr-2007-part-iii-dependency-monitors.aspx
J.C. Hornbeck | Manageability Knowledge Engineer
