Cumulative Update 6 for System Center Operations Manager 2007 R2 is available

Article translations Article translations
Article ID: 2626076 - View products that this article applies to.
Expand all | Collapse all

On This Page

SUMMARY

This article contains a complete description of changes that are contained in Cumulative Update 6 for Microsoft System Center Operations Manager 2007 R2.

Cumulative Update 6 for Operations Manager 2007 R2 includes all previous cumulative updates for Operations Manager 2007 R2 and includes all cross-platform updates.

To download Cumulative Update 6 for Operations Manager 2007 R2, go to the following Microsoft Download Center website:
Download Cumulative Update 6 for System Center Operations Manager 2007 R2

Cumulative Update 6 for Operations Manager 2007 R2 resolves the following issues:
  • RMS promotion fails if NetworkName and PrincipalNames are not in sync for agents.
  • UI is limited to only 100 MB for the Memory Usage field in the wizard.
  • Additional OIDs in auth certificate are not processed correctly.
  • AEM creates duplicate computer objects in OpsMgr based on Agents NetBIOS name.
  • Cannot open reporting pane on OpsMgr 2007 R2 remote console.
  • Cannot view schedule for scheduled report.
  • ManagementServerConfigTool with the option "promoterms" fails because it stops polling the SDK Service.
  • OpsMgr reports are failing on Windows 7 with the error: "Cannot initialize report."
  • ACS events have "n/a" as their category in the ACS database.
  • Watch agentless monitoring listener to detect failure to respond.
  • SCOM SDK memory leak on cryptography keys and cryptography contexts.
  • After you click Edit Schedule, a message box appears, and you cannot save the change value.
  • Audit events can be lost when the AdtServer process crashes.
Cumulative Update 6 for Operations Manager 2007 R2 resolves the following cross-platform issues:
  • The installation process for the IBM AIX 6.1 agent incorrectly checks for AIX 5.3 packages.
  • After a system restart, the OpsMgr agent for Solaris may start to run before local file systems are mounted.
  • On Red Hat Linux version 4 and SUSE Linux version 9, LVM disks are not discovered and cannot be monitored.
  • The OpsMgr agent for AIX does not report the arguments for monitored processes.
  • When Microsoft security update MS12-006 is installed on an OpsMgr management server, that management server can no longer communicate with the OpsMgr agent on any Linux or UNIX server.
  • On HP-UX, OpsMgr cannot discover and monitor a logical volume that is composed of more than 127 physical volumes.
Cumulative Update 6 for Operations Manager 2007 R2 adds the following cross-platform features:
  • Support for IBM AIX 7.1 (POWER).
  • Support for Oracle Solaris 11 (x86 and SPARC).
Note The new agents for IBM AIX 7.1 and Oracle Solaris 11 are included in Cumulative Update 6 for Operations Manager 2007 R2. You can download the management packs for these new operating system versions by going to the following Microsoft website:
System Center Operations Manager 2007 R2 Cross Platform Monitoring Management Packs

MORE INFORMATION

Issues that are resolved by Cumulative Update 6 for Operations Manager 2007 R2

Collapse this tableExpand this table
SymptomsScenario
Installation of the OpsMgr agent on AIX 6.1 fails with a missing dependency.When you install the OpsMgr agent on AIX 6.1 by using the OpsMgr Discovery Wizard or manually, an error is reported about a missing dependency. This dependency is a file from AIX 5.3 that should not be a prerequisite for installing on AIX 6.1.
After a system restart, the OpsMgr agent on Solaris may fail because it cannot find local files that it needs.The installation process for the OpsMgr agent on Solaris creates a startup entry that does not have a dependency on local file systems being mounted. Therefore, timing variations can cause the agent to run before the local file systems are mounted, with the result that the agent cannot find files that it needs.
On Red Hat Linux version 4 and SUSE Linux version 9, LVM disks are not discovered and monitored.The inability to see LVM disks occurs on all Red Hat Linux 4 and SUSE Linux 9 operating systems that are monitored by using OpsMgr 2007 R2 CU5.
On AIX, the OpsMgr agent does not report the arguments for monitored processes.When you create custom monitors by using the CIM class SCX_UnixProcess, the "Parameters" field is always returned as blank on AIX computers.
When Microsoft security update MS12-006 is installed on an OpsMgr management server, all communication from the management server to the OpsMgr agent on Linux or UNIX results in an HTTP 501 error.Security update MS12-006 made a change in the way data is packaged for transport across SSL/TLS in order to remove a security vulnerability. The change is valid. However, the OpsMgr agent for all Linux/UNIX operating systems makes an incorrect assumption and cannot understand this change. This results in HTTP 501 errors for all communications.
On HP-UX, logical volumes that have more than 127 physical volumes are not discovered and therefore cannot be monitored.When it discovers logical volumes on an HP-UX operating system, the OpsMgr agent for HP-UX receives an internal error when it has a volume that has more than 127 physical volumes. The error results in the disk being ignored and not discovered or monitored.

Known issues for this update

There are no known issues for this update.

Recommended installation order

We recommend that you install this cumulative update in the following order:
  1. Root management server (RMS)
  2. Operations Manager database - manually update by running the included stored procedure file that is discussed in the following sections:
    • "Manual operations that must be performed after you update the root management server and the data warehouse"
    • "Manual operations that must be performed after you update the ACS collector"
  3. Management packs that are discussed in the "Import the management packs" section - manually import
  4. Secondary management servers
  5. Gateway servers
  6. Agent update - deploy to agents that used a discovery-based installation 
  7. Operations console role computers

    Note When you update this role, select the Run Server Update option from the Software Update dialog box.
  8. Web Console server role computers 
  9. Manually installed agents - apply the agent update
  10. Audit Collection Services (ACS) role computers

Note After you apply the cumulative update to ACS computers, follow these steps:
  1. Net stop adtserver. 
  2. Run DbUpgV6toV7.sql.
  3. Net start adtserver.
For instructions on how to run DbUpgV6toV7.sql, see the "Manual operations that must be performed after you update the ACS collector" section.

Additional installation notes

  • When you update a component by using the installer splash screen, you have to complete three update installers. When you update a component such as RMS, each installer starts and requires you to click Finish when the update is complete. The next installer starts automatically.

Installation steps

To extract the files that are contained in this update, follow these steps:
  1. Copy the following file to either a local folder or an available network share: 
    SystemCenterOperationsManager2007-R2CU6-KB2626076-X86-X64-IA64-ENU.MSI
  2. Run this file locally on each applicable computer. For example, run this file on the root management server (RMS).

    Notes 
    • Run this file by using either Windows Explorer or a command prompt.
    • To run this file on a computer that is running Windows Server 2008, you must use an elevated command prompt. An elevated command prompt is a command prompt that was started by using the Run as Administrator option. If you do not run this Windows-based installer file under an elevated command prompt, the System Center Operations Manager 2007 Software Update splash screen does not let the hotfix be installed.
  3. In the System Center Operations Manager 2007 Software Update window, select the update option for the role that will be updated.

Recommended steps for applying this cumulative update to a clustered root management server

For more information about the recommended instructions for applying this cumulative update to a clustered root management server, go to the following Microsoft website:
How to apply a SCOM hotfix to a clustered RMS

Manual operations that must be performed after you update the root management server and the data warehouse

Run the SQL scripts

This update contains fixes that must be manually applied. These fixes are applied by running the c:\program files (x86)\System Center 2007 R2 hotfix utility\KB2626076 \SQLUpdate\CU_DataWarehouse.sql file against the Operations Manager data warehouse (OperationsManagerDW) and by running the c:\program files (x86)\System Center 2007 R2 hotfix utility\KB2626076 \SQLUpdate\CU_Database.sql file against the Operations Manager database (OperationsManager). To do this, follow these steps:
  1. Log on to the computer that hosts the Operations Manager 2007 database by using a user account that has database system administrator (SA) rights to the Operations Manager 2007 database instance. To perform the database update remotely, log on to a computer that hosts SQL Server Management Studio by using a user account that has the appropriate SA rights to the Operations Manager 2007 database.
  2. Run SQL Server Management Studio.
  3. In the Connect to Server dialog box, connect to the instance of SQL Server that hosts the Operations Manager database. The default database name is OperationsManager.
  4. On the toolbar, click New Query
  5. From the SQL Editor toolbar, use the Available databases option to select the Operations Manager database.
  6. On the File menu, click Open, browse to C:\program files (x86)\System Center 2007 R2 hotfix utility\KB2626076\SQLUpdate\, select the CU_Database.sql file that was extracted by the Windows installer (.msi file), and then click Open.
  7. When the file is loaded, click Execute in the SQL Editor toolbar.
  8. View the Messages pane to check whether the Transact-SQL commands ran successfully.
  9. Exit SQL Server Management Studio.
  10. For the Operations Manager data warehouse, repeat steps 1 through 8. However, connect to the instance of SQL Server that hosts the Operations Manager data warehouse, and then run the \SQLUpdate\CU_DataWarehouse.sql file.

Manual operations that must be performed after you update the ACS collector

Run the SQL scripts

This update contains fixes that must be manually applied. These fixes are applied by running the %SystemDrive%\Windows\System32\Security\AdtServer\DbUpgV6toV7.sql file against the ACS DB (OperationsManagerAC2). To do this, follow these steps:
  1. Log on to the computer that hosts the ACS database by using a user account that has database system administrator (SA) rights to the ACS database instance. To perform the database update remotely, log on to a computer that hosts SQL Server Management Studio by using a user account that has the appropriate SA rights to the ACS database.
  2. Run SQL Server Management Studio.
  3. In the Connect to Server dialog box, connect to the instance of SQL Server that hosts the ACS database. The default database name is OperationsManagerAC2.
  4. On the toolbar, click New Query
  5. From the SQL Editor toolbar, use the Available databases option to select the ACS database.
  6. On the File menu, click Open, select the %SystemDrive%\Windows\System32\Security\AdtServer\DbUpgV6toV7.sql file that was installed by the Windows installer (.msi file), and then click Open.
  7. When the file is loaded, click Execute in the SQL Editor toolbar.
  8. View the Messages pane to check whether the Transact-SQL commands ran successfully.
  9. Exit SQL Server Management Studio.

Import the management packs

The management packs that are supplied in the ManagementPacks folder must be manually imported by using the Import Management Packs Wizard in the Operations console.

The following updated management packs are located in the ManagementPacks folder of the package installation:
  • Microsoft.SystemCenter.DataWarehouse.Report.Library.mp
  • Microsoft.SystemCenter.WebApplication.Library.mp
  • Microsoft.SystemCenter.WSManagement.Library.mp

Update the Web.Config file on the Web Console server role computers

To make sure that all cookies that are created by the Web Console cannot be accessed by the client cscript, add the following configuration to the Web.Config file on the Web Console server: 
<httpCookies httpOnlyCookies="true"/>

However, if the Web Console is configured to run under SSL, add the following configuration to the Web.Config file instead to make sure that all cookies are encrypted: 
<httpCookies httpOnlyCookies="true" requireSSL="true"/>
Note Only one of these lines has to be added to the Web.Config file. To add one of these lines, scroll down in the Web.Config file until you see the <system.web> tag, and then add the appropriate new line immediately after the line that contains <system.web>.

Install Linux/UNIX management packs, and update Linux/UNIX agents

Cumulative Update 6 for Operations Manager 2007 R2 contains new agents for all supported Linux and UNIX operating systems, together with new management packs for AIX 7.1 and Solaris 11. Therefore, to fully install this cumulative update, you should follow these steps to make sure that your monitoring of Linux/UNIX computers is up to date: 
  1. Download and then install the updated management packs from the following Microsoft website:
    System Center Operations Manager 2007 R2 Cross Platform Monitoring Management Packs
  2. Import the updated management pack for each version of Linux or UNIX that you are monitoring in your environment.
  3. Use the Operations Manager 2007 R2 Discovery Wizard to rediscover the Linux and UNIX computers that you monitor. After you rediscover the computers, the agents on those computers upgrade automatically.

Updated support tools that are included in this cumulative update

The following updated file in the SupportTools folder supports the upgrade from Microsoft SQL Server 2005 Reporting Services to SQL Server 2008 Reporting Services and from SQL Server 2008 Reporting Services to SQL Server 2008 R2 Reporting Services: 
SRSUpgradeTool.exe

Note Use the appropriate platform version of this file instead of the file that is supplied in the SupportTools folder of the Operations Manager 2008 R2 distribution media.

Advanced installation instructions at a command prompt

The installer (hotfix utility) that is downloaded from this site unpacks the bootstrapping application and necessary MSP files to install Cumulative Update 6 for Operations Manager 2007 R2. It is better to run the hotfix utility on each computer and to deploy Cumulative Update 6 for Operations Manager 2007 R2 by using the GUI interface that is invoked after you run the hotfix utility. However, you can avoid multiple installations of the hotfix utility by copying the unpacked directory and files to the appropriate computers. These files are unpacked to the following location by the hotfix utility:
\Program Files (x86)\System Center 2007 R2 Hotfix Utility\KB2626076\

If you decide to install Cumulative Update 6 for Operations Manager 2007 R2 at a command prompt, use the following command:

SetupUpdateOM.exe /x86msp:KB<#>-x86.msp /amd64msp:KB<#>-x64.msp /ia64msp:KB<#>-ia64.msp /x86locmsp:KB<#>-x86-<LOC>.msp /amd64locmsp:KB<#>-x64-<LOC>.msp /ia64locmsp:KB<#>-ia64-<LOC>.msp /UpdateAgent /Silent /noreboot


Note The /Silent flag is not necessary if you want to install Cumulative Update 6 for Operations Manager 2007 R2 by using the GUI interface. Replace the <LOC> parameter with the appropriate language code for the update that you have downloaded. Replace the <#> parameter with the Microsoft Knowledge Base article number for this cumulative update.

For example, run the following command for the English version of Cumulative Update 6 for Operations Manager 2007 R2:
SetupUpdateOM.exe /x86msp:KB2626076-x86.msp /amd64msp:KB2626076-x64.msp /ia64msp:KB2626076-ia64.msp /x86locmsp:KB2626076-x86-ENU.msp /amd64locmsp:KB2626076-x64-ENU.msp /ia64locmsp:KB2626076-ia64-ENU.msp /UpdateAgent /Silent /noreboot


Advanced installation instruction to manually update agents

With Cumulative Update 6 for Operations Manager 2007 R2, you can manually update agents without copying the full contents of the package. To deploy updates to an agent, follow these steps:
  1. Install the hotfix utility by using the instructions in the "Advanced installation instructions at a command prompt" section. By default, the files that you have to have to update the agent are at the following location:
    C:\Program Files (x86)\System Center 2007 R2 Hotfix Utility\KB2626076
  2. Copy the appropriate .msp files to a folder of your choice (for example, C:\temp\CU6_Agent) on each computer on which you want to manually update the agent.
  3. Run the following two commands at a command prompt from the folder that contains the update files. This folder is C:\temp\CU6_Agent if you follow the suggestion here. (ex: x64 architecture and English language):

    msiexec.exe /p "C:\temp\CU6_Agent\KB2626076-x64-Agent.msp" REBOOT="ReallySuppress"

    msiexec.exe /p "C:\temp\CU6_Agent\KB2626076-x64-ENU-Agent.msp" REBOOT="ReallySuppress"

File list and roles

This update installs updated UNIX and Linux agents to the following folder, and this update removes older UNIX and Linux agents in the following folder:
Program Files\System Center Operations Manager 2007\AgentManagement\UnixAgents

The updated agents have file names that use the following format and a version number of 298:
scx-1.0.4-298-ServerType.ServerVersion.Architecture.PackageType


Notes

  • The placeholder ServerType represents the name of the UNIX or Linux server product.
  • The placeholder ServerVersion represents the version number of the server type.
  • The placeholder Architecture represents the processor architecture of the destination computer.
  • The placeholder PackageType represents the kind of installation file.

For example, the following is the file name format for the agent for SUSE Linux Enterprise Server 10 (x86):
scx-1.0.4-298-sles.10.x86.rpm

The agents that are included with Systems Center Operations Manager 2007 R2 Cumulative Update 5 have a version number of 277. All agent files for this version number are removed during the installation of this update.

The agents that are included with Systems Center Operations Manager 2007 R2 Cross Platform Cumulative Update 2 (hotfix 979490) have a version number of 258. All agent files for this version number are removed during the installation of this update.

The agents that are included with System Center Operations Manager 2007 R2 Cross Platform Agent Update (hotfix 973583) have a version number of 252. All agent files for this version number are removed during the installation of this update.

The agents that are included with the original release of System Center Operations Manager 2007 R2 have a version number of 248. These files are not removed during installation. However, these files are replaced with 1 kilobyte (KB) files. You have the option of removing these 1 KB files. These files are as follows: 
  • scx-1.0.4-248.aix.5.ppc.lpp.gz
  • scx-1.0.4-248.aix.6.ppc.lpp.gz
  • scx-1.0.4-248.hpux.11iv2.ia64.depot.Z
  • scx-1.0.4-248.hpux.11iv2.parisc.depot.Z
  • scx-1.0.4-248.hpux.11iv3.ia64.depot.Z
  • scx-1.0.4-248.hpux.11iv3.parisc.depot.Z
  • scx-1.0.4-248.rhel.4.x64.rpm
  • scx-1.0.4-248.rhel.4.x86.rpm
  • scx-1.0.4-248.rhel.5.x64.rpm
  • scx-1.0.4-248.rhel.5.x86.rpm
  • scx-1.0.4-248.sles.10.x64.rpm
  • scx-1.0.4-248.sles.10.x86.rpm
  • scx-1.0.4-248.sles.9.x86.rpm
  • scx-1.0.4-248.solaris.10.sparc.pkg.Z
  • scx-1.0.4-248.solaris.10.x86.pkg.Z
  • scx-1.0.4-248.solaris.8.sparc.pkg.Z
  • scx-1.0.4-248.solaris.9.sparc.pkg.Z

Collapse this tableExpand this table
File nameVersionServer roleAgent roleGateway roleACS roleX-Plat role
Access_Violation_-_Unsuccessful_Logon_Attempts.rdlNot applicableX
ActionsPane.ascxNot applicableX
AdtAgent.exe6.1.7221.99XX
AdtServer.exe6.1.7221.99X
AdtSrvDll.dll6.1.7221.99X
AlertPropertypage5.ascxNot applicableX
AuditingMessages.dll6.1.7221.99X
Blank.aspxNot applicableX
DataViews.jsNot applicableX
DetailsTypeAlert.aspxNot applicableX
DetailsTypePerformance.aspxNot applicableX
DetailsTypeTaskStatus.aspxNot applicableX
DisableForwarding.ps1Not applicableX
EnableForwarding.ps1Not applicableX
EventCommon.dll6.1.7221.99XXX
Forensic_-_All_Events_For_Specified_User.rdlNot applicableX
FormatTracing.cmdNot applicableXXX
HeaderControl.ascxNot applicableX
HealthExplorer.cssNot applicableX
HealthExplorerView.ascxNot applicableX
HealthService.dll6.1.7221.99XXX
HealthServiceMessages.dll6.1.7221.99XXX
HealthServicePerformance.dll6.1.7221.99XXX
HealthServiceRuntime.dll6.1.7221.99XXX
HSLockdown.exe6.1.7221.99XXX
Login.aspxNot applicableX
MainStyles.cssNot applicableX
Microsoft.EnterpriseManagement.DataWarehouse.DataAccess.dll6.1.7221.99X
Microsoft.EnterpriseManagement.HealthService.Modules.DataWarehouse.dll6.1.7221.99X
Microsoft.EnterpriseManagement.HealthService.Modules.Notification.dll6.1.7221.99X
Microsoft.EnterpriseManagement.HealthService.Modules.WorkflowFoundation.dll6.1.7221.99XXX
Microsoft.EnterpriseManagement.Modules.Azure.dll6.1.7221.99XXX
Microsoft.EnterpriseManagement.OperationsManager.ClientShell.Console.psc1Not applicableX
Microsoft.EnterpriseManagement.OperationsManager.ClientShell.dll6.1.7221.99X
Microsoft.EnterpriseManagement.OperationsManager.ClientShell.dll-help.xmlNot applicableX
Microsoft.EnterpriseManagement.OperationsManager.ClientShell.Format.ps1xmlNot applicableX
Microsoft.EnterpriseManagement.OperationsManager.ClientShell.Functions.ps1Not applicableX
Microsoft.EnterpriseManagement.OperationsManager.ClientShell.NonInteractiveStartup.ps1Not applicableX
Microsoft.EnterpriseManagement.OperationsManager.ClientShell.Startup.ps1Not applicableX
Microsoft.EnterpriseManagement.OperationsManager.ClientShell.Types.ps1xmlNot applicableX
Microsoft.EnterpriseManagement.OperationsManager.Common.dll6.1.7221.99X
Microsoft.EnterpriseManagement.OperationsManager.DataAbstractionLayer.CommonSetup.dll6.1.7221.99X
Microsoft.EnterpriseManagement.OperationsManager.DataAbstractionLayer.dll6.1.7221.99X
Microsoft.EnterpriseManagement.OperationsManager.dll6.1.7221.99X
Microsoft.EnterpriseManagement.OperationsManager.Web.ConsoleFramework.dll6.1.7221.99X
Microsoft.EnterpriseManagement.UI.Administration.dll6.1.7221.99X
Microsoft.EnterpriseManagement.UI.Authoring.dll6.1.7221.99X
Microsoft.EnterpriseManagement.UI.Authoring.resources.dll6.1.7221.99X
Microsoft.EnterpriseManagement.UI.Reporting.dll6.1.7221.99X
Microsoft.Mom.Common.dll6.1.7221.99XXX
Microsoft.Mom.ConfigServiceHost.exe6.1.7221.99X
Microsoft.Mom.DataAccessLayer.dll6.1.7221.99X
Microsoft.Mom.DiscoveryDatabaseAccess.dll6.1.7221.99X
Microsoft.Mom.Modules.ClientMonitoring.dll6.1.7221.99X
Microsoft.Mom.Modules.DataTypes.dll6.1.7221.99XXX
Microsoft.Mom.RecorderBarBHO.dll1.0.0.2X
Microsoft.Mom.Sdk.ServiceDataLayer.dll6.1.7221.99X
Microsoft.Mom.Sdk.ServiceHost.exe6.1.7221.99X
Microsoft.Mom.ServiceCommon.dll6.1.7221.99X
Microsoft.MOM.UI.Common.dll6.1.7221.99X
Microsoft.MOM.UI.Components.dll6.1.7221.99X
Microsoft.MOM.UI.Console.exe6.1.7221.99X
Microsoft.Mom.UI.Wrappers.dll6.1.7221.99X
MicrosoftRSChart.dll2.0.0.175X
MicrosoftRSChartDesigner.dll2.0.0.175X
MobileWebConsole.dll6.1.7221.99X
MomADAdmin.exe6.1.7221.99X
MOMAgentInstaller.exe6.1.7221.99XX
MOMAgentInstallerPS.dll6.1.7221.99XX
MOMAgentManagement.dll6.1.7221.99XX
MomBidLdr.dll5.2.3790.1290XXX
MOMConnector.dll6.1.7221.99XXX
MomConnectorMessages.dll6.1.7221.99XXX
MOMConnectorPerformance.dll6.1.7221.99XXX
MomIISModules.dll6.1.7221.99XXX
MOMModuleMsgs.dll6.1.7221.99XXX
MOMModules.dll6.1.7221.99XXX
mommodules2.dll6.1.7221.99XXX
MOMMsgs.dll6.1.7221.99X
MOMNetworkModules.dll6.1.7221.99XXX
MOMPerfSnapshotHelper.exe6.1.7221.99XXX
MOMScriptAPI.dll6.1.7221.99XXX
MOMSCXLogModules.dll6.1.7000.277X
MOMV3.SP2_7221_signed.cabNot applicableXXX
MomWsManModules.dll6.1.7221.99XXX
MonitoringHost.exe6.1.7221.99XXX
MPConvert.exe6.1.7221.99X
MPExport.exe6.1.7221.99X
MPImport.exe6.1.7221.99X
MPVerify.exe6.1.7221.99X
OperationalDataReporting.exe6.1.7221.99X
OpsMgrVssWriterService.exe6.1.7221.99X
Planning_-_Logon_Counts_of_Privileged_Users.rdlNot applicableX
PrereqResource.dll6.1.7221.0X
RootWebConsole.dll6.1.7221.99X
RSSWebConsole.dll6.1.7221.99X
ScopingForm.aspxNot applicableX
SCXAgents.dll6.1.7000.295X
scxcertconfig.exe6.1.7000.277X
SecureStorageBackup.exe6.1.7221.99X
SecureStorageSDK.dll6.1.7221.99X
StateSummary.ascxNot applicableX
TitleBar.jsNot applicableX
TraceConfig.exe6.1.7221.99XXX
tracefmtsm.exe6.1.7221.99XXX
TraceLogSM.exe6.1.7221.99XXX
Usage_-_Privileged_logon.rdlNot applicableX
Usage_-_User_Logon.rdlNot applicableX
ViewTypeFavoritesOverview.aspxNot applicableX
ViewTypeOverview.aspxNot applicableX
Web.ConfigNot applicable
WSSDiscovery.exe6.1.7221.99XX

Properties

Article ID: 2626076 - Last Review: May 15, 2012 - Revision: 1.0
APPLIES TO
  • Microsoft System Center Operations Manager 2007 R2
Keywords: 
KB2626076

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com