SCOM 2007 R2 CU6 available

CU6 for SCOM 2007 R2 is available now

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.

For complete information on SCOM CU6 read:

http://support.microsoft.com/kb/2626076


Thanks,
Varun

SCCM 2012 Quiz

SCCM 2012 quiz is now available...to test your knowledge

http://quizapp.cloudapp.net/default.aspx?quiz=Configmgr2012


Thanks,

Varun

OpsMgr Tools

For updated tools on SCOM please visit blog @: 

http://blogs.msdn.com/b/dmuscett/archive/2012/02/19/boris-s-tools-updated.aspx


Thanks,

Varun Kaura

Event ID 29112 logged after upgrading to System Center 2012 Operations Manager

After Upgrading from System Center Operations Manager 2007 R2 CU5 to System Center 2012 Operations Manager, the following error may be logged in the Operations Manager Event Log
Log Name: Operations Manager
Source: OpsMgr Management Configuration
Date:
Event ID: 29112
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
OpsMgr Management Configuration Service failed to execute bootstrap work item 'ConfigurationStoreInitializeWorkItem' due to the following exception

Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.DataAccessException: Data access operation failed
at Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.DataAccessOperation.ExecuteSynchronously(Int32 timeoutSeconds, WaitHandle stopWaitHandle)
at Microsoft.EnterpriseManagement.ManagementConfiguration.SqlConfigurationStore.ConfigurationStore.ExecuteOperationSynchronously(IDataAccessConnectedOperation operation, String operationName)
at Microsoft.EnterpriseManagement.ManagementConfiguration.SqlConfigurationStore.ConfigurationStore.Initialize()
at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.ConfigurationStoreInitializeWorkItem.ExecuteWorkItem()
at Microsoft.EnterpriseManagement.ManagementConfiguration.Interop.ConfigServiceEngineWorkItem.Execute()
-----------------------------------
Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.DataAccessException: Data access operation failed to run SQL script. The following are the first 200 characters of the first failed batch
------

Please visit following KB article for more information

2700028 : Event ID 29112 generated after upgrading to System Center 2012 Operations Manager

http://support.microsoft.com/kb/2700028

SCOM discovery fails

Hi,

In case you are unable to discover devices on your network and see error related to SQL broker service not running then run below sql query against OperationsManager DB to check the status and enable it:

SELECT is_broker_enabled FROM sys.databases WHERE name='OperationsManager'   if status 0, means disable and need to be enabled using following queries

ALTER DATABASE OperationsManager SET SINGLE_USER WITH ROLLBACK IMMEDIATE

ALTER DATABASE OperationsManager SET ENABLE_BROKER

ALTER DATABASE OperationsManager SET MULTI_USER

SELECT is_broker_enabled FROM sys.databases WHERE name='OperationsManager'  if status 1, then you are good to run discovery now.


Thanks,
Varun

SCOM 2012 sizing helper tool available now

The OpsMgr 2012 Sizing Helper is an interactive document designed to assist you with planning & sizing deployments of System Center 2012 Operations Manager. It helps you plan the correct amount of infrastructure needed for a new OpsMgr 2012 deployment, removing the uncertainties in making IT hardware purchases and optimizes cost. A typical recommendation will include minimum hardware specification for each server role, topology diagram and storage requirement.

Tool is available at below link:

http://blogs.technet.com/b/momteam/archive/2012/04/02/operations-manager-2012-sizing-helper-tool.aspx


Thanks,

Varun

SCOM Remedy connectors

Hi

I just thought of sharing my experience recently had on SCOM Remedy Integration...

SCOM Integration with 3^rd Party Product (BMC Remedy ARS 6.3)… using  connectors.

        The environment I've used is officially not tested by Microsoft ...

My environment consist of SCOM 2007 R2 running on Windows 2008 R2 SP1, ARS 6.3. I’ve tested both on SQL DB 2005 & SQL 2008 DB

ü Operations Manager 2007 R2 Connectors provide Operations Manager 2007 R2 alert forwarding to remote systems, such as an Enterprise Management System (EMS) or a service desk system. After Operations Manager 2007 R2 forwards an alert to a remote system, that alert data is synchronized throughout the lifetime of the alert. The result of that data synchronization is a robust and seamless systems management environment.

ü  Following are the minimum requirement for SCOM Remedy Integration. As part of integration two components gets installed

§  Provider, runs on remedy environment

§  Connector, runs on SCOM environment

ü  Tool can be downloaded from below Microsoft url. The SCInterop_R2_RTM.exe has ref guide and connector & provider for all supported 3^rd party systems.

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=20333

Pre-requisite for Provider & Connector components:

•             A server with Remedy User application (v6.3 or higher) at least (don’t need Remedy Server specifically). Minimum OS Windows 2003 + SP2  (for provider)

•             The English version of Microsoft Visual C++ 2008 Redistributable Package (x86) if Visual C++ 2008 is not installed. (for both connector and provider)

•             WS-Management 1.1 (for both connector and provider)

•             Local admin permission for Domain account on the given Remedy server

•             A User in Remedy with administrative privileges

•             .NET Framework 3.0 SP1 or a later version (connector)

•             Server running SCOM console at least and DB Instance running on SQL 2005 minimum.     OS Windows 2003 + SP2 minimum

Installation order:

i. First install provider on a windows 2003 server. For that execute SciProviderSetup.exe and click next to begin Installation.

ii. Select BMC Remedy ARS 6.3 Provider, click next next and finish the installation.

iii. Reboot the server after provider installation.

iv. Install connector on the server by executing SciConnectorSetup_x64.exe.

v. select BMC Remedy connector service and connector configuration option and click next.

vi. On SQL server configuration wizard specify your Database server. Database Name would remain default as (SCInterop) with default SQL Server port (1433) and click next.

vii. On next screen specify connector login service name and password click next and complete the installation.

viii. Now opsmgr configuration wizard comes up here specify the configuration for Remedy server, version and ws-man server credentials. Click next and complete the configuration.

ix. on next screen click next for connector certificate installation. Reboot the server after successful installation.

x. Provider and connector are installed now. It’s time to import Interface Forms, Filters, and Data Files

on Remedy server.  The .xml file that contains these forms and filters are copied to the Interop Provider installation folder.

The files are SCIOpsMgr2007Interface-63.xml and SCIStateTransitions.xml. For import of files please follow step by step process on the below link:

http://technet.microsoft.com/en-us/library/ee210412.aspx

xi. Once definition files are imported on the Remedy server you can check forwarding alerts to the Remedy server.

xii. Now remedy dll file need to be updated on the server running provider component. ScInteropRemedy63.dll file needs to be updated (if running ARS 6.3 only). For updating the dll file stop WMI service à go to %windows%\system32\wbem and replace the ScInteropRemedy63.dll. Reboot the server after overriding the file.

xiv. Check forwarding alerts to the Remedy server by right clicking on any alert in SCOM console à right click à forward to à opsmgr connector for  BMC Remedy.

xvi. Check the status in Remedy for the ticket created against the alert.

xvii. Install SCOM 2007 R2 connector hotfix OM2007R2Connectors-KB2274165 on both provider and connector to stay updated.

Thanks,

Varun Kaura