Step by Step Guide to recovery or Move Operations Manager Database from Old Server to New Server

Step by Step Guide to Move Operations Manager Database from Old Server to New Server

• Step1:Stop Operation Manager services

On all the management servers in the management group, stop the Operations Manager services:

* System Center Data Access

* System Center Management

* System Center Management Configuration

• Step2: Create Backup of Old OperationManager Database and move it to new Server

* On the original operational database server, use Microsoft SQL Server Management Studio to create a full backup of the operational database. The DB name is OperationsManager.

* Copy the backup file to a local drive of the new database server.

• Step3: Restore the operational database on the new server

* Use Microsoft SQL Server Management Studio to restore the operational database.In this step, you can change the name of the database and choose the file location.

* Make the database online.verify that the database is online.

• Step4:Update the registries and configuration files on the management servers

* Do these steps on each management server in the management group:

* Update the registry to refer to the new SQL Server-based computer.

*Log on to the management server with Administrator permissions.

* Click Start, select Run, type regedit in the Open box, and then click OK to start Registry Editor.

* Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup.

* For each of the following keys, double-click the name, change the value to the hostname of the SQL Server-based computer now hosting the operational database, and then click OK to save   your changes.

  1. DatabaseName

  2. DatabaseServerName

* Close the Registry Editor.

On each management server, edit the following file:

* %ProgramFiles%\System Center 2012\Operations Manager\Server\ConfigService.config 

* In the <Category> tags named “Cmdb” and “ConfigStore”, change the value for ServerName to the name of the new SQL server.

Step5: Update Operations Database to point to new server

* Open SQL Server Management Studio.

* Expand Databases, OperationsManager, and Tables.

* Right-click dbo.MT_Microsoft$SystemCenter$ManagementGroup, and then click Edit Top 200 Rows.

* Note If the SCOM was installed by upgrading from SCOM 2007 instead of by using the SCOM 2012 install media, you need to modify the dbo.MT_ManagementGroup table instead of the   dbo.MT_Microsoft$SystemCenter$ManagementGroup table.

* Change the value in the SQLServerName_6B1D1BE8_EBB4_B425_08DC_2385C5930B04 column to reflect the name of the new SQL Server-based computer.

  Save the change.

Step6: On the new server, update the operational database with the new database server name to specify the location of the Application Performance Monitoring tables

* Open SQL Server Management Studio.

* Expand Databases, OperationsManager, and Tables.

* Right-click dbo.MT_Microsoft$SystemCenter$OpsMgrDB$AppMonitoring, and then click Edit Top 200 Rows.

* Change the value in the MainDatabaseServerName_5C00C79B_6B71_6EEE_4ADE_80C11F84527A column to reflect the name of the new SQL Server-based computer.

* Save the change.

Step7: Update security credentials on the new server hosting the operational database

Expand Security, expand Logins, and then do the following:

* Add the data writer account. For more information, see How to Create a SQL Server Login.

* Add the action account.

* Add the Data Access Service (DAS) computer account, using the form “domain\computername$”.

For the DAS computer account, add the following user mappings:

* ConfigService

* db_accessadmin

* db_datareader

* db_datawriter

* db_ddladmin

*db_securityadmin

Step8: Execute these SQL commands on new Operations database instance:

 sp_configure ‘show advanced options’,1

 reconfigure

 sp_configure ‘clr enabled’,1

reconfigure

sdk_users

sql_dependency_subscriber

Run the following SQL query:

SELECT is_broker_enabled FROM sys.databases WHERE name='OperationsManager'

If the result of this query was an is_broker_enabled value of 1, skip this step. Otherwise, run the following SQL queries:

ALTER DATABASE OperationsManager SET SINGLE_USER WITH ROLLBACK IMMEDIATE

ALTER DATABASE OperationsManager SET ENABLE_BROKER

ALTER DATABASE OperationsManager SET MULTI_USER

• Step9: Start Operation Manager services

On all the management servers in the management group, start the Operations Manager services:

* System Center Data Access

* System Center Management

* System Center Management Configuration

Test-Connection:Powershell alternate command to Ping is Test-Connection

Powershell alternate command to Ping is Test-Connection

• Ping is the first network utility that we use to test the connection
• In Powershell Ping is called Test-Connection
• It provides the same functionality of Ping

ADD-ADGroupMember:Powershell Command to ADD users to AD group

Powershell Command to ADD users to AD group

• Today we will see how to add Active Directory users to Active directory group.
• To add users to AD group use "ADD-ADGroupMember" command.

Ex: To add 2 users Mark and Kathy to the Security group "WebAdmins" Group

ADD-ADGroupMember WebAdmins Mark,Kathy

SCOM Management Server showing warning with Event ID 1825 - A security package specific error occurred

SCOM Management Server showing warning with "Event ID 1825 - A security package specific error occurred"

• Today when i checked the SCOM management Server it was in Warning state.
• When i open the health explorer i could see only "Failed to access event log" is selected and its in warning state with error in details "A security package specific error occurred".
• When i tried to access the event log from the SCOM management server it failed with the same error.
• so i decided to do a nslookup of the server and found that the reverse lookup is pointing to the alias of the server rather then the actual server name.
• Once it was resolved things got health again.
• So when you have this issue, its usually issue with the DNS entries which needs to be fixed

How to get list of All commands for SCOM 2012 R2 Module in Powershell

How to get list of All commands for SCOM 2012 R2 Module in Powershell

• Today i am going to Show you how get list of all commands available in SCOM module.
• First Open the Powershell and Import the SCOM module

                    Import-Module OperationsManager

• This will load the SCOM module in Powershell
• Then to see all the commands in the OperationsManager Modulle type the below command

                   get-command - module OperationsManager | more

• This will list all the commands in SCOM.

Easy way to access your network cards and configure them - ncpa.cpl

Easy way to access your network cards and configure them -ncpa.cpl

• Opening the network card is a bit of challenge in the computer. It usually takes to network page from where you have to again click on another tab to go to your network card. I was always feeling if there is easy way to do it and the yes there is
• Click on Start --> in search box type "ncpa.cpl"
• This will directly open the Network card page.
• I hope it makes your life easier like mine :)

Known Issues and Troubleshooting for Windows Server Base OS Management pack

Known Issues and Troubleshooting for Windows Server Base OS Management pack

• Disk Partitions Which Correspond to Mounted Disks Are Not Monitored

Issue: Disk partition discovery is not enabled by default, but when enabled, disk partitions that correspond to mounted disks cannot be monitored properly and will show up as “Not Monitored” in the Operations Console. Management is still provided by way of other means in this management pack, but the disk partition perspective will not work in these instances.

Workaround: There is no workaround currently available. 

• The “Core Windows Services Rollup” Monitor for Windows Server 2008 Includes Services That It Should Not

Issue: The Core Windows Services Rollup monitoring that exists in all server operating system management packs aggregates the state of a number of monitors that are watching the state of various “core services” and will change state if any one of those services is not running. The Windows Server 2008 version of this monitor includes a monitor for the “Computer Browser Service Health,” which is not accurate because the service is no longer required for the Windows Server 2008 operating system to function properly.

Workaround: The monitor can be safely ignored, but it can also be disabled by overriding it.

• Remote Desktop (Admin) Not Always Accessible

Issue: There are times when Remote Desktop (Admin) is not accessible.

Workaround: The new Remote Desktop (Admin) functionality of Windows Server 2008 is supported by way of the /admin switch. However, it is available only in Windows Server 2008 and the Windows Vista operating system with SP1.

• The Console Session Does Not Work in Windows Server 2008

Issue: Attempts to use the /console switch do not work properly.

Workaround: The console session no longer exists in Windows Server 2008. Use of the /console switch will be ignored, and the behavior is the same as a simple Remote Desktop task.

• Behavior for Accessing the Console Session of Windows Server 2003 Has Changed

Issue: There is a change in behavior for accessing the console session of Windows Server 2003.

Workaround: For the Windows XP operating system with SP1 or earlier and Windows Vista, use the Remote Desktop (Console) task in Windows Server 2003. Remote Desktop (Admin) will cause an error dialog. For Windows Vista with SP1, use the Remote Desktop (Admin) task in Windows Server 2008. Remote Desktop (Console) will work as the Remote Desktop task without any notice.

• SUBST Drive Mappings Are Not Supported by Logical Disk Monitoring

Issue: There is a command-line tool (SUBST.exe) that can be used to associate a path (such as c:\windows\system32) with a drive letter (such as D:\). Because these mappings are exposed in WMI, logical disk monitoring discovers them and attempts to monitor them as such, but will subsequently generate errors.

Workaround: There is no workaround currently available, and this configuration is not supported.

Known Issues with Localized Versions of the Management Pack:

•  Object discoveries scoped to Windows Server 2008 Computer and Windows Server 2008 Operating System may not display correctly in the Authoring pane.
• Some instances of localized display strings may not display correctly in the Operations console.

Known Issue: Cluster Disks Managed by Third-Party Software are Not Monitored

• Issue: If the Cluster disks are managed by third party software, and they change the resource type to anything other than “Physical Disk”, these disks will be discovered but we do not provide monitoring for these.
• Workaround: There is no workaround currently available. In future, we will be removing discovery for these too.

Known Issue: PowerShell in 2012 MP failed if .NET is uninstalled from Core OS agent by user

• Issue: .NET 4.5 and PowerShell are installed by default on Core OS and PowerShell depends on .NET, if they are uninstalled from Core OS agent by user, some workflows depending on PowerShell in 2012 MP will be failed.
• Workaround: Install .NET Framework 4.5 and PowerShell on Core Operating System.