Search This Blog
Showing posts with label Upgrade. Show all posts
Showing posts with label Upgrade. Show all posts

Monday, May 13, 2013

[OpsMgr 2012] SP1 upgrade fails with error "Failed to set DW upgrade scenario"


When performing an upgrade to OpsMgr 2012 SP1, the upgrade process fails with the following error:
Failed to set DW upgrade scenario: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Cannot open database "OperationsManagerDW" requested by the login. The login failed.
In order to be able to relaunch the upgrade, verify that the correct Data Warehouse server name and SRS database instance name exist in the registry on the Management Server:
Data Warehouse server name:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup\DatawarehouseDBServerName
NOTE: This is a DWORD value and is the NetBIOS name or FQDN of the server.
SRS database instance name:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Reporting\SRSInstance
NOTE: The default SQL instance name is MSSQLSERVER but may be different in your environment if using a named instance.

Please read the original post on This page



This posting is provided "AS IS" with no warranties.

Posted by at 1:58:00 PM 0 comments Print Friendly and create PDF
Labels: , , , , , , ,

Tuesday, April 2, 2013

[OpsMgr 2012 SP1] Upgrading Operations Manager 2012 to SP1: The CDM Monitoring and Management Experience

 has written an interesting article on his experience upgrading Operations Manager 2012 to SP1 on the environment od Microsoft IT.


You can read the full article >>>>>>>>>> Here <<<<<<<<<<.

Here are some details of the environment :
  • 1 Management group
  • 6200 agents
  • 3 administration servers
  • 24 gateways
  • 2 administration servers with ACS
  • 2 administration servers with  web Console
  • 1 Cluster SQL (Operation DB)
  • 1 Cluster SQL (Data Warehouse, SSRS &Reporting)
    •

    This posting is provided "AS IS" with no warranties.

    Posted by at 12:59:00 PM 0 comments Print Friendly and create PDF
    Labels: , , , ,

    Wednesday, September 12, 2012

    [OpsMgr 2012] Thoughts on the Operations Manager 2012 Migration

    Thoughts on the operation manager 2012 migration or upgrade… I'll try to put here all what we need to check before launching a migration to the new OpsMgr 2012.

    What about supported configuration :
    -       How to manage Windows 2000 servers – no more supported in OpsMgr 2012 ?
    o    If you have money, you can try to keep a small infrastructure with a management group in OpsMgr2007R2. Waiting the replacement of all old 2000 servers.
    o    You can also decide to use the agentless monitoring but you will only have a limited monitoring… Better than nothing but this can scare applications owner.
    -       All SCOM 2007 R2 agent must have at least CU4, or later cumulative Update applied to be migrated in SCOM 2012 agent.
    o    If not, you ‘ll have to update your agents before the migration.
    -       Check your management servers configuration – all servers that have an OpsMgr Role must be Windows 2008 R2 or later
    -       Check the SQL version on servers that are used for Operations Manager DB and Data Warehouse – SQL version must be SQL Server 2008 SP2 or SQL Server 2008 R2 RTM/SP
    -       .Net Framework 3.5.1 role must be installed.
    -       SCOM 2012 Windows-Based Agent has some pre-requisite too :
    o    File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
    o    Operating Systems: Windows Server 2003 SP2, Windows 2008 Server, Windows Server 2008 SP2, Windows Server 2008 R2, Windows Server 2008 R2 SP1, Windows Server 2012, Windows XP Professional x64 Edition SP2, Windows XP Professional SP3, or Windows Vista SP2, or Windows 7, POSReady, Windows XP Embedded Standard, orWindows XP Embedded Enterprise, or Windows XP Embedded POSReady, Windows 7 Professional for Embedded Systems, orWindows 7 Ultimate for Embedded Systems.
    o    Processor Architectures: x64, x86, or IA64.
    o    Windows Installer version: at least Windows Installer 3.1.
    o    Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required for the Operations Manager agent.
    o    Windows PowerShell version: Windows PowerShell version 2.0, or Windows PowerShell version 3.0.
    Note
    Windows PowerShell is required for agents that will be monitored by a management pack that uses PowerShell scripts.


    You can also read more on supported configuration on this page Supported Configurations: System Center 2012 - Operations Manager and this other one Supported Configurations: System Center 2012 SP1 - Operations Manager.

    What about your management packs :
    -       In order to have an up-to-date inventory, check all installed management packs you have in your OpsMgr2007 R2 environment.
    o    You can also check for provided MP updates that could be usefull to install in the new OpsMgr 2012 environment.
    -       A needed task is now to check what Rules, Monitors, Tasks or Discoveries, also Management Packs that target the RMS :
    o    You can use a report or a SQL query, both provided by Jean-Sebastien Duchene. This will help you to identify MPs that store a monitoring that target the RMS.
    §  Next step is to activate the RMS Emulator for provided MPs that target the RMS (Microsoft Exchange Server 2010 Management Pack, Citrix EdgeSight Management Pack...)
    §  For your own developed MP, you can rewrite the MP to target any MS instead of RMS if possible. Tao Yang has created a post on a way to modify your PowerShell script to automatically connect the RMS in OpsMgr 2007 R2 and connect the first MS that respond in OpsMgr 2012.
    -       Next step is to identify what MP is using PowerShell – All Cmdlets has been renamed in SCOM 2012 by adding a prefix SCOM. You can find the System Center 2012 - Operations Manager Cmdlet Reference.
    §   Jean-Sebastion Duchene has worked on a SQL query to help us to identify what MP is using PowerShell.
    §  The next step will be to re-write your scripts with the new cmdlets !
    §  Load The OpsMgr 2007 Snap-in that are already installed with OpsMgr 2012. Here is post from Scott Moss that speak about that.

    /!\ Please do the same work for all your PowerShell script also. Don’t forget a task in your planning to identify all your scripts.

    What about your own reports :
    -       Please find this post from Peter Zerger this is quite old but give the OpsMgr 2012 Database Schemas & Operations Manager DW DB. It seems that some view like  RelationshipGenericView does not contain the same columns than in OpsMgr 2007 DB.


     
    To be continued ! :)

    This posting is provided "AS IS" with no warranties.

    Posted by at 11:01:00 AM 0 comments Print Friendly and create PDF
    Labels: , , , ,

    Thursday, July 12, 2012

    [OpsMgr 2012] Installing OpsMgr 2012 Agents with CU1 with a command Line

    I've just read this article from  Tommy Gunn : OpsMgr 2012: Installing OpsMgr 2012 Agents from the Command Line
    The script provided by Joe Thompson allow you to install the SCOM 2012 Agent and the CU1 with a single command line :
    msiexec /i MOMAgent.msi /qn /l*v %TEMP%\install.log PATCH="C:\MyPath\KB2674695-amd64-Agent.msp USE_SETTINGS_FROM_AD=0 USE_MANUALLY_SPECIFIED_SETTINGS=1 MANAGEMENT_GROUP=MYNEWMG MANAGEMENT_SERVER=SCOM2012.MYDomain.net SECURE_PORT=5723 ACTIONS_USE_COMPUTER_ACCOUNT=1"
      
     Be sure parameter are correct to launch the command line.
    Here is the script :
    1. ' OMINSTALL.VBS
    2. ' Version 1 (2012-06-27)
    3. ' Joe Thompson, EP Energy LLC
    4. ' OM 2012 vbs installer with CU1 agent patch and MGMT Group reconfig
    5.   
    6. Option Explicit
    7.   
    8. Dim sho, sCurPath, oReg, strKeyPath, strValueName, strComputer, strCmd, strVal, objMSConfig, intSleep, intRet
    9.   
    10. Set sho = Wscript.CreateObject("Wscript.Shell")
    11. sCurPath = CreateObject("Scripting.FileSystemObject").GetAbsolutePathName(".")
    12. strComputer = "."
    13. intSleep = 15000
    14. wscript.echo "Running installer..."
    15. strCmd = "msiexec /i MOMAgent.msi /qn /l*v %TEMP%\install.log PATCH=" & sCurPath & "\KB2674695-amd64-Agent.msp USE_SETTINGS_FROM_AD=0 USE_MANUALLY_SPECIFIED_SETTINGS=1 MANAGEMENT_GROUP=MYNEWMG MANAGEMENT_SERVER=SCOM2012.MYDomain.net SECURE_PORT=5723 ACTIONS_USE_COMPUTER_ACCOUNT=1"
    16. wscript.echo strCmd
    17. intRet = sho.run(strCmd,0,True)
    18.   
    19. ' Let things calm down
    20. wscript.echo "Sleeping..."
    21. WSCript.Sleep intSleep
    22.   
    23. ' Check registry for OM Mgmt Group info
    24. If intRet <> 0 Then
    25.                 wscript.Echo "Install error occurred.... "
    26.                 wscript.quit(intRet)
    27. Else
    28.                 On Error Resume Next
    29.                 wscript.echo "Checking registry for OM 2012 EPE Mgmt Group info..."
    30.                 strVal = sho.RegRead("HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Agent Management Groups\MYNEWMG\")
    31.                 If Err <> 0 Then    ' regkey doesn't exist
    32.                                 wscript.echo "Didn't find OM 2012 EPE Mgmt Group info, setting config..."
    33.                                 Set objMSConfig = CreateObject("AgentConfigManager.MgmtSvcCfg")
    34.                                 'Add a management group
    35.                                 Call objMSConfig.AddManagementGroup ("MYNEWMG", "SCOM2012.MYDomain.net",5723)
    36.                                 WSCript.Sleep intSleep
    37.                                 wscript.echo "Reloading agent Mgmt Group configuration..."
    38.                                 Call objMSConfig.ReloadConfiguration
    39.                 End If
    40. End If
    41.   
    42. wscript.quit(intRet)


    This posting is provided "AS IS" with no warranties.

    Posted by at 1:35:00 PM 0 comments Print Friendly and create PDF
    Labels: , , , , ,

    Wednesday, May 30, 2012

    [OpsMgr 2007R2][OpsMgr 2012] Upgrading from OpsMgr2007R2 to OpsMgr2012 - Process Flow Diagrams

    Updated: April 1, 2012

    Applies To: System Center 2012 - Operations Manager

    Before you upgrade to System Center 2012 – Operations Manager, you must first determine whether all servers in your System Center Operations Manager 2007 R2 management group meet the minimum supported configurations for System Center 2012 – Operations Manager. For more information, see Supported Configurations for System Center 2012 – Operations Manager. You can use a set of process flow diagrams to determine your upgrade path and visualize the process.


    The following table lists the process flow diagrams available, along with a description of when each upgrade path should be used.


    Condition
    		Process flow diagramChecklist
    When you have a single-server or distributed management group that already meets the minimum supported configuration requirements for System Center 2012 – Operations Manager.Single-Server and Distributed Upgrade (Simple) Process Flow Diagram
    Distributed Upgrade (Simple)
    When your single-server management group does not yet meet the minimum supported configuration requirements for System Center 2012 – Operations Manager, and requires new hardware.Single-Server Upgrade (Complex) Process Flow DiagramChecklist: Single-Server Upgrade (Complex)
    When your distributed management group has one or more servers that do not meet the minimum supported configuration requirements for System Center 2012 – Operations Manager, and might require new hardware.Distributed Upgrade (Complex) Process Flow Diagram
    		Checklist: Distributed Upgrade (Complex)

    Single-Server and Distributed Upgrade (Simple) Process Flow Diagram


    Single-Server Upgrade (Complex) Process Flow Diagram



    Distributed Upgrade (Complex) Process Flow Diagram



    Checklists

    Single-Server Upgrade (Simple)
     
    		TaskReferences
     Import the Upgrade Helper management pack.Import the Upgrade Helper Management Pack
     Review the Operations Manager 2007 R2 event logs.Review the Operations Manager 2007 R2 Event Logs
     Remove agents from Pending Management.Remove Agents from Pending Management
     Check for any active connected consoles to the root management server.Check the Operations Manager 2007 R2 RMS for Active Connected Consoles
     Back up the RMS encryption key (SecureStorageBackup.exe).Back Up the RMS Encryption Key
     Disable all notification subscriptions.Disable Notification Subscriptions
     Stop services or disable any connectors that are installed.Stop Services for Connectors
     Verify that your operational database has enough free space.Verify that the Operational Database Has More than 50 Percent of Free Space
     Verify that you have a supported SQL Server collation on all databases and instances of databases.Verify the SQL Server Collation
     Back up the databases.Back up the Operations Manager Databases
     Upgrade the manually installed agents.Upgrading Manually Installed Agents
     Run the management group upgrade on the root management server.How to Upgrade an Operations Manager 2007 R2 Single-Server Management Group
     Upgrade the push-installed agents.Upgrading Push-Installed Agents
     Re-enable the notification subscriptions.Re-enable the Notification Subscriptions.
     Restart or re-enable the service for any connectors that are installed.Restart the Connector Services
     Update overrides.Update Overrides
     Verify the success of the upgrade.Verify upgrade success


    Distributed Upgrade (Simple)
     
    		TaskReferences
     Import the Upgrade Helper management pack.Import the Upgrade Helper Management Pack
     Move agents that report to the RMS to a secondary management server.How to Move Agents to an Operations Manager 2007 R2 Secondary Management Server (Operations Manager Upgrade)
     Back up the encryption key.Back Up the Encryption Key
     Review the Operations Manager 2007 R2 event logs.Review the Operations Manager 2007 R2 Event Logs
     Remove agents from pending management.Remove Agents from Pending Management
     Verify that you have a supported SQL Server collation on all databases and instances of databases.Verify the SQL Collation
     Upgrade the manually installed agents.Upgrading Manually Installed Agents
     Upgrade the secondary management servers.How to Upgrade a Secondary Management Server from Operations Manager 2007 R2
     Upgrade gateways, if present.How to Upgrade a Gateway Server from Operations Manager 2007 R2
     Upgrade the push-installed agents.Upgrading Push-Installed Agents
     Check for any active, connected consoles to the root management server.Check the Operations Manager 2007 R2 RMS for Active, Connected Consoles
     Disable all notification subscriptions.Disable the Notification Subscriptions
     Stop services or disable any connectors that are installed.Stop the Services for Connectors
     Verify that your operational database has enough free space.Verify that the Operational Database Has More than 50 Percent of Free Space
     Back up the databases.Back Up the Operations Manager Databases
     Restore the encryption key on secondary management server.Restore the Encryption Key on the Secondary Management Server
     Run management group upgrade on the root management server.How to Upgrade a Management Group from an Operations Manager 2007 R2 RMS
     Upgrade or install the optional features, such as the web consoles and Reporting server.Upgrading or Installing Optional Features
     Re-enable notification subscriptions.Re-enable the Notification Subscriptions
     Restart or re-enable the service for any connectors that are installed.Restart the Connector Services
     Update overrides.Update Overrides
     Verify the success of the upgrade.Verify the Upgrade Success


    Single-Server Upgrade (Complex)
     
    		TaskReferences
     Add a secondary management server and install System Center Operations Manager 2007 R2.How to Add an Operations Manager 2007 R2 Secondary Management Server (Operations Manager Upgrade)
     Move agents that report to the root management (RMS) server to the secondary management server.How to Move Agents to an Operations Manager 2007 R2 Secondary Management Server (Operations Manager Upgrade)
     If SQL Server does not meet the supported configuration requirements, upgrade SQL Server.Upgrading SQL Server (Operations Manager Upgrade)
     Back up the encryption key.Back Up the Encryption Key
     Review the Operations Manager 2007 R2 event logs.Review the Operations Manager 2007 R2 Event Logs
     Remove agents from Pending Management.Remove Agents from Pending Management
     Verify that you have a supported SQL Server collation on all databases and instances of databases.Verify the SQL Collation
     Upgrade the manually installed agents.Upgrading Manually Installed Agents
     Upgrade the secondary management server.How to Upgrade a Secondary Management Server from Operations Manager 2007 R2
     Upgrade the push-installed agents.Upgrading Push-Installed Agents
     Check for any active connected consoles to the root management server.Check the Operations Manager 2007 R2 RMS for Active Connected Consoles
     Disable all notification subscriptions.Disable the Notification Subscriptions
     Stop services or disable any connectors that are installed.Stop the Services for Connectors
     Verify that your operational database has enough free space.Verify that the Operational Database Has More than 50 Percent of Free Space
     Back up the databases.Back Up the Operations Manager Databases
     Restore the encryption key on secondary management server.Restore the Encryption Key on the Secondary Management Server
     Run management group upgrade on the secondary management server.How to Upgrade a Management Group from an Operations Manager 2007 R2 Secondary Management Server
     Re-enable the notification subscriptions.Re-enable the Notification Subscriptions.
     Restart or re-enable the service for any connectors that are installed.Restart the Connector Services
     Uninstall the old root management server.Uninstall the Old RMS
     Update overrides.Update Overrides
     Verify the success of the upgrade.Verify the Upgrade Success

    Distributed Upgrade (Complex)

    Import the Upgrade Helper Management Pack
     
    		TaskReferences
     
    Import the Upgrade Helper Management Pack
    		Upgrade Helper Management Pack

    Replacing Secondary Management Servers
     
    		TaskReferences
     If operating system is 32-bit, add a secondary management server.How to Add an Operations Manager 2007 R2 Secondary Management Server (Operations Manager Upgrade)
     Move the Operations Manager 2007 R2 agents to a secondary management server, and remove the old secondary management server.How to Move Agents to an Operations Manager 2007 R2 Secondary Management Server (Operations Manager Upgrade)
     Ensure that the secondary management server meets the supported configuration requirements for System Center 2012 – Operations Manager.Supported Configurations for System Center 2012 - Operations Manager
    Replacing Gateways
     
    		TaskReferences
     If gateway server does not have a 64-bit operating system, build a new gateway server.How to Replace an Operations Manager 2007 R2 Gateway that Has an Unsupported Configuration (Operations Manager Upgrade)
     Remove the old gateway server.How to Remove an Operations Manager 2007 R2 Gateway (Operations Manager Upgrade)
     Ensure that the gateway server meets the supported configuration requirements for System Center 2012 – Operations Manager.Supported Configurations for System Center 2012 - Operations Manager
    Secondary Management Server Upgrade
     
    		TaskReferences
     If RMS does not meet supported configuration requirements for System Center 2012 – Operations Manager, move agents that report to root management server to the secondary management server.How to Move Agents to an Operations Manager 2007 R2 Secondary Management Server (Operations Manager Upgrade)
     If Microsoft SQL Server does not meet the supported configuration requirements, upgrade SQL Server.Upgrading SQL Server (Operations Manager Upgrade)
     Back up the encryption key.Back Up the Encryption Key
     Review the Operations Manager 2007 R2 event logs.Review the Operations Manager 2007 R2 Event Logs
     Check if any gateway servers report to an unsupported RMS.Check for Gateway Servers Reporting to the RMS
     Remove agents from Pending Management.Remove Agents from Pending Management
     Verify that you have a supported SQL Server collation on all databases and instances of databases.Verify the SQL Server Collation
     Upgrade the manually installed agents.Upgrading Manually Installed Agents
     Upgrade the secondary management servers.How to Upgrade a Secondary Management Server from Operations Manager 2007 R2
     Upgrade gateway servers, if present.How to Upgrade a Gateway Server from Operations Manager 2007 R2
     Upgrade the push-installed agents.Upgrading Push-Installed Agents
    Management Group Upgrade from RMS
     
    		TaskReferences
     Check for any active, connected consoles to the root management server.Check the Operations Manager 2007 R2 RMS for Active Connected Consoles
     Disable all notification subscriptions.Disable the Notification Subscriptions
     Stop services or disable any connectors that are installed.Stop the Services for Connectors
     Verify that your operational database has sufficient free space.Verify that the Operational Database has More than 50 Percent of Free Space
     Back up all databases.Back Up the Operations Manager Databases
     Run management group upgrade on the root management server.How to Upgrade a Management Group from an Operations Manager 2007 R2 RMS
     Upgrade optional features.Upgrading or Installing Optional Features
     Re-enable the notification subscriptions.Re-enable the Notification Subscriptions.
     Restart or re-enable the service for any connectors that are installed.Restart the Connector Services
     Update overrides.Update Overrides
     Verify the success of the upgrade.Verify the Upgrade Success

    Management Group Upgrade from Secondary Management Server
     
    		TaskReferences
     Check for any active, connected consoles to the root management server.Check the Operations Manager 2007 R2 RMS for Active, Connected Consoles
     Disable all notification subscriptions.Disable the Notification Subscriptions
     Stop services or disable any connectors that are installed.Stop the Services for Connectors
     Verify that your operational database has sufficient free space.Verify that the Operational Database has More than 50 Percent of Free Space
     Back up all databases.Back Up the Operations Manager Databases
     Restore the encryption key.Restore the Encryption Key on the Secondary Management Server
     Run the management group upgrade on the secondary management server.How to Upgrade a Management Group from an Operations Manager 2007 R2 Secondary Management Server
     If required, install the optional features, such as the consoles and Reporting.Upgrading or Installing Optional Features
     Re-enable the notification subscriptions.Re-enable the Notification Subscriptions.
     Restart or re-enable the service for any connectors that are installed.Restart the Connector Services
     Uninstall the old root management server.Uninstall the Old RMS
     Update overrides.Update Overrides
     Verify the success of the upgrade.Verify the Upgrade Success




    This posting is provided "AS IS" with no warranties.

    Posted by at 12:28:00 PM 0 comments Print Friendly and create PDF
    Labels: , , ,
    Subscribe to: Posts (Atom)