Monday 3 December 2012

How to troubleshoot Event ID 2115 in Operations Manager


In Operations Manager, one of the performance concerns surrounds Operations Manager Database and Data Warehouse insertion times. The following (link) is a description to help identify and troubleshoot problems concerning Database and Data Warehouse data insertion.

Troubleshoot Event ID 2115 in Operations Manager


Event ID 2115 A Bind Data Source in Management Group  (Courtesy Kevin Holman)



Cheers

Varun

Saturday 24 November 2012

SCCM Site Role Hardware used in MSIT


ConfigMgr Site Role Hardware used in Microsoft IT   courtesy 


For more details on sizing and recommended hardware please refer product documentation -



Microsoft IT Configuration Manager Virtualization Technical case study is available on 




Cheers...

Varun 

SCCM 2012 SQL Recommendations


System Center 2012 Configuration Manager SQL recommendations with spreadsheet


I have two SQL related question that comes up in all of my ConfigMgr 2012 projects. Those are:

· Where are we going to install the SQL server?
· How are we going to configure SQL?
Recommendations from Kent Agerlund (Microsoft MVP)

Cheers...
Varun 

SCCM 2012 Guide and References

SCCM 2012 Guide and References




Cheers

Varun 



The IPD guide for System Center 2012 and next version of Windows Server


Overview

Infrastructure Planning and Design guides share a common structure, including: 
  • Definition of the technical decision flow through the planning process.

  • Listing of decisions to be made and the commonly available options and considerations.

  • Relating the decisions and options to the business in terms of cost, complexity, and other characteristics.

  • Framing decisions in terms of additional questions to the business to ensure a comprehensive alignment with the appropriate business landscape.



Cheers....

Varun 


Saturday 4 August 2012

Cumulative Update Rollup 2 (UR2) for OpsMgr 2012 has shipped

Cumulative Update Rollup 2 (UR2) for OpsMgr 2012 has shipped. This, like other CU’s or Update Rollups, is *Cumulative*.  This means that you can apply UR2 directly to a SCOM 2012 deployment with no previous updates, OR you can apply UR2 to a SCOM 2012 UR1 level management group.

Download: http://www.microsoft.com/en-us/download/details.aspx?id=30421
KB link: http://support.microsoft.com/kb/2706783

As usual Kevin has shared his experience in the below link:

http://blogs.technet.com/b/kevinholman/archive/2012/07/31/opsmgr-2012-update-rollup-2-ships-and-my-experience-installing-it.aspx


Cheers

Varun

Saturday 16 June 2012

Windows Server 2012 Hyper-V Network Virtualization Survival Guide

Windows Server® 2012 Hyper-V Network Virtualization Survival Guide available now

Windows Server 2012 enables you to create an agile, multi-tenant cloud on top of your existing infrastructure by virtualizing the network. Network virtualization decouples server configuration from network configuration to provide a virtual dedicated network to each tenant. This allows seamless migration of workloads, while continuing to provide security isolation between tenants. Partners have the opportunity to become multi-tenancy aware and provide the next generation of services, devices, appliances, both physical and virtual, to augment and complete the Windows offering to build secure, scalable, multi-tenant public and private clouds.
For more information visit:
http://social.technet.microsoft.com/wiki/contents/articles/11524.windows-server-2012-hyper-v-network-virtualization-survival-guide.aspx



Thanks,

Varun

SCCM 2012 Tech Documentation

Technical Documentation Download for System Center 2012 Configuration Manager is available here




Thanks,

Varun

Friday 18 May 2012

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

Wednesday 11 April 2012

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

Friday 6 April 2012

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

Thursday 5 April 2012

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 3rd 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 3rd party systems.


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:


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

Wednesday 4 April 2012

Updated SCOM Active Directory Management Pack Released

Recently updated ADMP released - version 6.0.7822.0

The March 2012 revision of the Monitoring Pack for Active Directory includes the following changes:
  • Corrected some Publisher names (for example, changed from PublisherName=KDC to PublisherName=Microsoft-Windows-Kerberos-Key-Distribution-Center)
  • Updated rules to generate Alerts and not only go to the Event Viewer
  • Removed unnecessary check for Event Source Name for all NTDS rules (for example, removed EventSourceName=”NTDS General”)
  • Corrected event parameter validation
  • Updated queries to search for correct event IDs
  • Fixed spelling errors
  • Added missing descriptions to rules
  • Fixed problems with Health Monitoring scripts
  • Removed user name checks from Userenv rules
Use below url for more information and to download the MP
 http://www.microsoft.com/download/en/details.aspx?id=21357


Thanks,

Varun

System Center 2012 Operations Manager Survival Guide

Survival Guide can be used to learn the fundamentals; increase your current knowledge; or stay current on Operations Manager and events... so connect to
http://social.technet.microsoft.com/wiki/contents/articles/7809.system-center-2012-operations-manager-survival-guide-en-us.aspx


Thanks & Regards,

Varun Kaura

Wednesday 14 March 2012

SCOM 2007 R2 SLD Service Level Dashboard

I just want to share my experince on SCOM SLD which I configured on a machine in test env. I specfically used test environment as I was not sure whether it would work or not on a single server.

Before this test I've already installed these products/applications on different servers and it just work .. no issues...

So, my env has a Server running Windows 2003 + SP2 + SQL 2005 and SQL SP2, SCOM 2007 R2 + CU5 everything on one machine.


SCOM SLD/WSS on a same server and some consideration if you are testing
-Everything was working fine (from SCOM perspective) before instaling WSS and SLD configuration. SCOM was running fine.. reports were accessible
-Then i installed WSS 3.0 + SP2/SLD 2.0 on the same server and configured as required using SLD doc. Though i was little apprehensive but then thought of just giv a try setting up on same server
-So after installation I checked WSS and could configure SLD in sharepoint
-Now, when i went to scom monitoring section and tried to open report directly for the alert generated then it failed ... oh!... then i relaized the mistake i did. I came back to reporting section and tried opening reports frm there as well.. no luck... it just failed with the long error message.

Steps taken for identifying the issue
-----------------------------------
-Report url did not run
-Default web site and report sites were stop in IIS which was after WSS installation

Solution
--------
Changed Default web site port
Checked setting under Reporting Service Configuration .. which was ok
Most important change report url port in SCOM console under admin tab
restart the server --- tested again and worked


Hope this helps anyone who is using the same kind of scenario as used by me here

Varun

Saturday 11 February 2012

Download System Center 2012 Release Candidate for your Private Cloud

Download Microsoft Private Cloud Evaluation Software. Microsoft private cloud solutions are built on System Center and Windows Server 2008 R2 SP1 available at below url:

http://technet.microsoft.com/en-us/evalcenter/hh505660.aspx