SCOM 2012 R2 Upgrade Plan Discussion

Dear Experts,
Currently I have a RMS and one MS Server with SCOM 2007 R2 in my Test Environment (Windows 2008 R2).
Now, The Upgradation plan is below and please correct me if I am wrong.
SCOM 2007 R2 CU4 --> SCOM 2012
SCOM 2012 --> SCOM 2012 SP1
SCOM 2012 SP1 --> SCOM 2012 R2.
So we need to purchase of three types of SCOM 2012 versions S/W or else we can simply download those versions from Microsoft ?
Please provide me the complete process of this Migration cycle.
Saravana Raja

Hi Saravana:
Upgrading to System Center 2012 – Operations Manager is supported from Operations Manager 2007 R2 CU4, or from the latest available CU. See
http://technet.microsoft.com/en-us/library/hh476934.aspx.
As for upgrading from SCOM 2012 to SCOM 2012 SP1 to SCOM 2012 R2, MVP Marnix Wolf is clear that you need to perform each upgrade step separately:
http://thoughtsonopsmgr.blogspot.com/2013/07/upgrade-paths-to-system-center-2012-r2.html. The "complete process" would consists of performing the upgrade for each version one after the other, again, just as you put in your plan.
You do not need to purchase any additional software, but you will need to download the 3 versions as you described from Microsoft volume license site or other media source.
John Joyner MVP-SC-CDM

Similar Messages

SCOM 2007 R2 to SCOM 2012 SP1 upgrade issues.

We have SCOM 2007 R2 on one of our development Environment.
The plan was to upgrade to SCOM 2012 R2 so we installed the SCOM 2007 R2 CU5.
We are having issues to upgrade now from SCOM 2007 R2 CU5 to SCOM 2012 SP1.
While upgrading we received the below message:
Unable to Proceed
Setup is unable to proceed with installation for the following reason:
At least one of the following application is installed on the computer.Due to incompatibility with system center 2012 - operations manager,these applications must be uninstalled.
-System Center 2012 - operations manager beta
-system center operations manager 2007
-system center operations manager 2007 sp1
--system center operations manager 2007 r2
-system center service manager agent
--system center essentials agent

Hi,
You cannot upgrade from SCOM2007R2 to SCOM2012SP1, you must upgrade to SCOM2012 and the upgrade to SCOM2012SP1
Cameron Fuller has a blog:
http://blogs.catapultsystems.com/cfuller/archive/2013/02/11/can-you-upgrade-from-opsmgr-2007-r2-to-opsmgr-2012-sp1-scom-sysctr.aspx
Upgrading System Center 2012 – Operations Manager to System Center 2012 SP1
http://technet.microsoft.com/en-us/library/jj899854.aspx
"The only supported upgrade path to System Center 2012 Service Pack 1 (SP1), Operations Manager is from System Center 2012 – Operations Manager. If you are upgrading from System Center Operations Manager 2007 R2, you must first upgrade to System Center 2012
– Operations Manager"
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Dashboards Problem after SCOM 2012 Inplace Upgrade- Missing Stored Procedures

Dears,<o:p></o:p>
After finishing SCOM 2012 in place Upgrade I face a problem on Performance and Service level dashboards, the Upgrade has been finished successfully as shown below
But after I start Dashboards configuration I receive below errors
After troubleshooting I see an error in Event viewer beside the errors on Snapshots above said that
Fault Detail is equal to could not find stored procedure
so I compared Stored Procedures under SCOM data warehouse database with another SCOM 2012 installation (different customer) and i see a lot of Missing Stored Procedures
(all Stored Procedures start with 'SDK.Microsoft_SystemCenter_Visualization are missing)
Here i am stuck, I don’t know what I can do, I have some ideas but i don't know if its will work.<o:p></o:p>
My ideas are:<o:p></o:p>
1. Repair SCOM 2012 Installation (does the repair option will repair the databases)
2. Re import Default SCOM Management packs like (Microsoft.SystemCenter.Visualization.Library.mpb) (does MP contains Stored procedures in the Database)<o:p></o:p>
3. Install Rollup Update (may during installation it will create missing Stored Procedures)
4. Move Stored Procedures from other SCOM server installation
Please advise its strange issue
Appreciate Your help
Note:<o:p></o:p>
Everything is work correctly regarding Raising alerts , generate reports , servers state , reset and recalculate health state, installing and ininstalling agents and others.

Hi,
Could you post the error message in forum directly? This snapshot it too fuzzy to know what the exactly meaning is.
Alex Zhao
TechNet Community Support

SCOM 2012 R2 Upgrade - Reporting goes to install mode instead of Upgrade

Hi
I have upgraded all scom managent servers succesfully, but when I try to run setup.exe on the SQL server it doesn't detect the existing SCOM 2012 SP1 Reporting installation and instead of Upgrade mode it goes into Install mode. Have anyone seen this
before?
Torboro

Hi Torboro,
Just a quick reviewal of the below settings.
Can you once check and see if SCOM 2012 / 2012 R2 wizard / program is showing in Add / remove programs
of the reporting server.
If yes can you select uninstall / repair option and give next it will show the installed components
and see if you get the reporting option there as per my screen shot below plz?
Gautam.75801

SCOM 2007 R2 to SCOM 2012 Migration\Upgrade

What are the different ways to migrate\Upgrade from scom 2007 r2 to scom 2012 r2 ?

This link lists multiple upgrade paths.
Is this what your looking for?
http://technet.microsoft.com/en-us/library/hh476934.aspx
Cheers,
Martin
Blog:
http://sustaslog.wordpress.com
LinkedIn:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

SCOM 2012 SP1 Upgrade

Hello,
I have a SCOM 2007 R2 CU7 server that I upgraded to SCOM 2012. I am running Windows Server 2008 R2 SP1 and SQL Server 2008 R2 SP2. I tried twice to upgrade it to SCOM 2012 SP1 and it failed both times. In the OpsMgrSetupWizard.log file,
I see this error:
: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Incorrect syntax near 'MERGE'. You may need to set the compatibility level of the current database to a higher value to enable this feature.
See help for the SET COMPATIBILITY_LEVEL option of ALTER DATABASE.
Incorrect syntax near the keyword 'AND'.
Incorrect syntax near the keyword 'THEN'.
[10:58:04]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
[10:58:04]: Error: :RunStandardScripts failed with the following exception: : Threw Exception.Type: System.Reflection.TargetInvocationException, Exception Error Code: 0x80131604, Exception.Message: Exception has been thrown by the target of an invocation.
[10:58:04]: Error: :StackTrace:   at System.RuntimeMethodHandle._InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
   at System.RuntimeMethodHandle.InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at Microsoft.EnterpriseManagement.SetupFramework.ActionEngine.Action.Run(String displayStringNamespace, ProgressData progressData, Func`2 progressDelegate)
   at Microsoft.EnterpriseManagement.SetupFramework.ActionEngine.InstallStep.Run(String displayStringNamespace, ProgressData progressData, Func`2 progressDelegate)
[10:58:04]: Error: :Inner Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131604, Exception.Message: Incorrect syntax near 'MERGE'. You may need to set the compatibility level of the current database to a higher value
to enable this feature. See help for the SET COMPATIBILITY_LEVEL option of ALTER DATABASE.
Incorrect syntax near the keyword 'AND'.
Incorrect syntax near the keyword 'THEN'.
After both failed upgrades, I had to re-install SCOM 2007. How can I get the upgrade to complete? The prerequisites have been installed.

So try to change the SQL database Compatibility Level to SQL 2008 (100):
1. Open SQL Server Management Studio
2. Connect to the SQL server hosting the Operations Manager Databases
3. Expand Databases, Right Click on OperationsManager and click properties
4. Click Options, Change the Compatibility level: drop down to SQL Server 2008 (100), Click OK
5. Right Click on OperationsManagerDW and click properties, Click Options
6. Change the Compatibility level: drop down to SQL Server 2008 (100), Click OK
Niki Han
TechNet Community Support

SCOM 2012 SP1 Upgrade - RMS fine but can't upgrade reporting or web console

Hi,
We've just upgraded our RMS to SCOM 2012 SP1 and everything went smoothly as per the documentation. However when I next try to upgrade the Reporting or Web Consoles (located on separate servers) to SP1 I am presented with a message saying:
"The management server to which this component reports has not been upgraded".
At that point we cannot proceed past the prerequisite checker.
I am totally confident that the SP1 upgrade went through on the RMS and all file versions are at SP1.
Can anyone help please?
Thanks,
Tim

Hi Retee,
I was not able to find a fix for this but I did find a workaround.
1. I copied the installation files from the SCOM 2012 SP1 DVD/ISO to a folder, SCOM_2012_INSTALL on the reporting server.
2. Browsed to the following folder ..\SCOM_2012_INSTALL\setup\AMD64\ and commented out the following section of the IntermilestoneUpgradePrereqs.xml file:

3. Ran ..\SCOM_2012_INSTALL\setup.exe and the upgrade was successful.
Our SCOM infrastructure has now been at 2012 R2 for a couple of months and I have not seen any issues caused by commenting out this section. But as always, use at your own risk.
Hope this helps.
Thanks,
Iain

Windows 2012 upgrade plan to R2 hosted with SCOM 2012 SP1

Dear Experts,
Currently we are hosting SCOM 2012 SP1 on Windows 2012 Operating System and the Server team plan to upgrade Windows server OS 2012 to Windows OS 2012 R2.
So, Is there any Potential road blocks and things to take care for SCOM 2012 SP1 if we want to upgrade the Windows 2012 R2 OS.
Thanks,
Saravana
Saravana Raja

Hi,
I have seen this a couple of times without any issues.
Just make sure you backup all SCOM related (databases if local, management packs etc).
www.coretech.dk - blog.coretech.dk

SCOM 2012 R2 agent upgrade fails crippling agents

Running into a large amount of SCOM agents that are failing the upgrade from 2012 SP1 to R2 and would appreciate any feedback from my SCOM community colleagues. Warning this issue is not for the faint of heart.
Plan:
I am in the process of upgrading 1900 manually installed SCOM 2012 SP1 agents to R2. I am using SCCM to deliver the upgrade using the standard sanctioned upgrade parameters.
Momagent.msi /qn /l*v %SystemDrive%\SCOM2012AgentUpgrade.log AcceptEndUserLicenseAgreement=1
Problem:
I have run into a problem where on a larger group of systems, 165 servers, where the upgrade fails and leaves the agent in a crippled state. At this point the agent cannot be removed cleanly via add remove, nor can a straight install of the agent
be done. What is required is a manual removal of registry keys and then a clean install of the agent can be performed to remediate. This is no problem and I am able to do this. (Note: all other methods of agent removal did not work ie:
Cleanmom.exe utility or add remove)
Task:
Seeing that we need to do agent upgrades in the future it would be great to know why this happened so we can plan for this in the future.
Notes:
Seems like a random sample of servers (2003/2008) with different applications running on them so that doesn't help in narrowing things down.
Looking at the MSI log, I see a common issue among systems that had this problem.
******* Product: {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
           ******* Action:
           ******* CommandLine: **********
MSI (s) (7C:7C) [08:08:43:668]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (7C:7C) [08:08:43:668]: User policy value 'DisableMedia' is 0
MSI (s) (7C:7C) [08:08:43:668]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Looking for sourcelist for product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Adding {387306D9-78CE-4E0E-B952-28A50CC8B3EE}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Now checking product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media is enabled for product.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Trying source C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 2203 2: C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\MOMAgent.msi 3: -2147287037
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing net source list.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing media source list.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Processing URL source list.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Failed to resolve source
MSI (s) (7C:8C) [08:08:44:744]: Note: 1: 1714 2: Microsoft Monitoring Agent 3: 1612
CustomAction returned actual error code 1612 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (7C:8C) [08:08:44:744]: Product: Microsoft Monitoring Agent -- Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
Action ended 8:08:44: RemoveExistingProducts. Return value 3.
Action ended 8:08:44: INSTALL. Return value 3.
Ok so the obvious is that the installer is looking for original source installation files and not able to find them. What is surprising to me however is that the product references a 32 bit scom agent guid
387306D9-78CE-4E0E-B952-28A50CC8B3EE, however this is a 64 bit machine. Our build process dictates that a 64 bit machine only receive a 64 bit SCOM agent.
Doing a search on this product guid I realized I skipped some other references at the top of the MSI log that might offer some more explanation...
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_OM12_SP1_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Modifying OM_OM12_SP1_AGENT_FOUND property. Its current value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'. Its new value: '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _StopCoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _KillOMProcesses.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_OM_AGENT_FOUND
Action ended 8:08:11: FindRelatedProducts. Return value 1.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
Action start 8:08:11: _Set_OM_AGENT_FOUND.
MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_MOMV3_AGENT_FOUND
Action ended 8:08:11: _Set_OM_AGENT_FOUND. Return value 1.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding MOMV3_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
Action start 8:08:11: _Set_MOMV3_AGENT_FOUND.
Well that is interesting, seems to me that in the first line the MSI installer reads the OM_OM12_SP1_AGENT_FOUND property and identifies this with a 64 bit agent guid (8B21425D-02F3-4B80-88CE-8F79B320D330), but then appends
the 32 bit guid at the end (387306D9-78CE-4E0E-B952-28A50CC8B3EE). This is the point of my confusion and my suspicion as the cause of the problem I am having.
Concluding thoughts:
Why does the installer seems to first recognizes a 64 bit agent, but then later changes it's property to include a 32 bit agent guid.  Could a 32 bit agent have got on this 64 bit server based on the details of this log? Would this
cause my agents to fail the upgrade? I think so, but looking to bounce this over to another fellow SCOM colleague who may have wrestled with this before.
Thanks in advance if you took the time to read this and think about it. Extra points if you have any extra thoughts!
Keith

Hi,
Have you used Requirement to limit the platform when you deploy application with SCCM.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Upgrade from SCOM 2007 R2 to SCOM 2012 R2 on a single server

we are planning to Upgrade from SCOM 2007 R2 to SCOM 2012 R2 on a single server.We are planning to do in place upgrade.

If you looking for a guide, check : http://blogs.4ward.it/how-to-upgrade-to-scom-2012-from-scom-2007-inplace-upgrade/
MS documentation for the upgrade is located at: http://technet.microsoft.com/en-us/library/hh476934.aspx
thx
Pranav

Upgrading SCOM 2012 SP1 agent to SCOM 2012 R2

Hello All
We have created a new SCOM 2012 R2 environment and now planning to upgrade our agents which are in SCOM 2012 SP1 environment . We want to keep the agents dual homed for some time . I would like to know if there is any kind of automation/script that someone
has already made to upgrade SCOM agent from SP1 to R2 ,and at the same time have it dual homed (pointing to 2 MG)

You may try
1) upgrade the SCOM agent by
msiexec /i MOMAgent.msi /qn /l*v D:\logs\AgentUpgrade.log AcceptEndUserLicenseAgreement=1
2) Add additional management group y using following vb script
Option Explicit
Dim objMSConfig
Set objMSConfig = CreateObject("AgentConfigManager.MgmtSvcCfg")
‘Add a management group
Call objMSConfig.AddManagementGroup ("MyManagementGroupToAdd", "company.sm.net",5723)
For detail, pls. refer to
http://technet.microsoft.com/en-us/library/jj899848.aspx
http://msdn.microsoft.com/en-us/library/hh329017.aspx
Roger

Question on upgrading to SCOM 2012 R2 form SCOM 2012 SP1

Hello!
I planned upgrade to SCOM 2012 R2 form SCOM 2012 SP1.
Should I install any or last update rollup package to my SCOM 2012 SP1, before upgrading to SCOM 2012 R2 ?

It is highly recommend that you has install most updated CU before upgrade SCOM 2012 sp1 1 to SCOm 2012 R2 but it is not necessary. You should view NEPA PFE Team blog that demostrate how to upgrade SCOM 2012 SP1 with CU4 to SCOM 2012 R2.
http://blogs.technet.com/b/nepapfe/archive/2013/11/26/upgrading-scom-2012-sp1-to-scom-2012-r2.aspx
Roger

Issue upgrading SCOM 2012 SP1 to SCOM 2012 R2

I have been having a really fun time trying to get my test SCOM 2012 SP1 environment upgraded to SCOM 2012 R2. I initially had an issue with the DB server not accepting connections to SMB which was causing the upgrade to fail stating database permission
issues (that was a fun one to troubleshoot). Once I figured out that problem I am now getting an error in the OpsMgrSetupWizard log that is stating the following:
[14:46:47]: Always:
:LaunchMsiSetup: Complete: 2 seconds
[14:46:47]: Error:
:LaunchMsiSetup: Failed, return code: 1612
[14:46:47]: Error:
:Error:Failed to uninstall previous MOM product on this machine, cannot proceed with upgrade
[14:46:47]: Error:
:Error:Failed to uninstall Operations Manager Agent on this machine. This is fatal error, we cannot proceed with upgrade
[14:46:50]: Error:
:LaunchMSI: MSI E:\Setup\AMD64\Server\OMServer.msi returned error 1603
[14:46:50]: Error:
:ProcessInstalls: Install Item Management Server failed to install. We did not launch the post process delegate.
In the application log I am getting the following error:
"Product: System Center Operations Manager 2012 Server -- The Operations Manager management server cannot be installed on a computer on which the Operations Manager agent, Operations Manager gateway, System Center Essentials, or System Center Service
Manager is already installed. These must be uninstalled to proceed."
I have verified that I don't have any of these installed and have even gone so far as to remove my Config man agent and System Center Endpoint Protection just in case it was getting confused with System Center Essentials.
I am at a loss as to what to try next. Any suggestions?

Hi,
Check if you have the following registry. If so, please back it up first, then delete for a test.
HKEY_CLASSES_ROOT\Installer\UpgradeCodes\C96403E8AD6025B4F9E1FE9C574E34AE
Also, please uninstall MOM product and Operations Manager Agent manually to check the result.
Upgrading System Center 2012 SP1 - Operations Manager to System Center 2012 R2
http://technet.microsoft.com/en-us/library/dn249707.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Upgrade to R2 from SCOM 2012 SP 1 UR 4 - Final configuration failed to install

I was upgrading our test SCOM 2012 SP1 UR 4 sever to R2 and ran into the following issue:
Setup cannot be completed… Final configuration failed to install.
Everything else upgraded fine.
There was no rollback performed…. The log states “Skipping rollback for install item Final Configuration as it was not successfully installed”
Looking in OpsManagerSetupWizard.log in the section for Final Configuration I see the following:
[16:00:43]:           Always: :!***** Installing: POSTINSTALL ***
[16:00:43]:           Info:      :SetProgressScreen: StartMinorStep.
[16:00:43]:           Warn:    :ApplyUpdates: Unable to load QFE file.
[16:00:43]:           Always: :Doing Preinstall task for POSTINSTALL
[16:00:43]:           Warn:    :CheckAndLoadUpdateFiles: Unable to load QFE file.
[16:00:43]:           Always: :Doing Install task for POSTINSTALL
[16:00:44]:           Debug: :DoInstallTask: Found Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.PostInstall;PostInstallProcessor as type and method.
[16:00:44]:           Info:      :Type: Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.PostInstall Method: PostInstallProcessor
[16:00:44]:           Info:      :SetProgressScreen: Init Exe Install progress.
[16:00:44]:           Info:      :AddUninstallChangeEntry: Cleaning out existing files at the ARP file cache location D:\Program Files\System Center 2012\Operations
Manager\Setup
[16:00:44]:           Error:     :InstallActionProcessor.DoInstallTask: method PostInstallProcessor threw exception. We will return installSuccessful = false.:
Threw Exception.Type: System.Reflection.TargetInvocationException, Exception Error Code: 0x80131604, Exception.Message: Exception has been thrown by the target of an invocation.
[16:00:44]:           Error:     :StackTrace:   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Microsoft.SystemCenter.Essentials.SetupFramework.InstallActionProcessor.DoInstallTask(InstallItemsInstallDataItem itemToInstall)
[16:00:44]:           Error:     :Inner Exception.Type: System.UnauthorizedAccessException, Exception Error Code: 0x80131604, Exception.Message: Access to the path 'EULA_EN_EVAL.RTF'
is denied.
[16:00:44]:           Error:     :InnerException.StackTrace:   at System.IO.Directory.DeleteHelper(String fullPath, String userPath, Boolean recursive, Boolean
throwOnTopLevelDirectoryNotFound)
   at System.IO.Directory.Delete(String fullPath, String userPath, Boolean recursive, Boolean checkHost)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupHelpers.ARPFileCache()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupHelpers.AddUninstallChangeEntry()
   at Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.PostInstall.PostInstallProcessor(Func`3 setProgressScreen)
[16:00:44]:           Error:     :ProcessInstalls: Install Item Final Configuration failed to install. We did not launch the post process delegate.
[16:00:44]:           Always: :SetErrorType: Setting VitalFailure. currentInstallItem: Final Configuration
[16:00:44]:           Info:      :SetProgressScreen: FinishMinorStep.
[16:00:44]:           Always: :****************************************************************
[16:00:44]:           Always: :****Starting*RollBack*******************************************
[16:00:44]:           Always: :****************************************************************
[16:00:44]:           Info:      :SetProgressScreen: StartMinorStep.
[16:00:44]:           Always: :ProcessRollback: Skipping rollback for install item Final Configuration as it was not successfully installed.
[16:00:44]:           Always: :****************************************************************
[16:00:44]:           Always: :****Ended*RollBack**********************************************
[16:00:44]:           Always: :****************************************************************
[16:00:44]:           Always: :Entering Page: FinishPage
The log states “Access to the path 'EULA_EN_EVAL.RTF' is denied.” I was able to find this file in D:\Program Files\System Center 2012\Operations Manager\SetupTemp\EN, but when viewing its contents I see it
was from the SP 1 upgrade as it starts off with “MICROSOFT EVALUATION SOFTWARE LICENSE TERMS MICROSOFT SYSTEM CENTER 2012 STANDARD SERVICE PACK 1.” Based on everything else referenced in the log file previously, it seems like it was trying to locate
this file in D:\Program Files\System Center 2012\Operations Manager\Setup. Also, I applied the product key after installing SP1 previously, so it was not running with an evaluation license.
Running Get-SCOMManagementGroup | ft skuforlicense, version, timeofexpiration –a
gives me:
SkuForLicense Version     TimeOfExpiration
       Retail 7.1.10226.0 12/31/9999 11:59:59 PM
The version (7.1.10226.0) is that of SCOM 2012 R2 (as I noted before, there was no rollback.) Everything seems to be functioning fine (Console, Web Console, Reporting Services.)
Is there a way to get it to re-run only the Final Configuration steps (which will probably fail again as the EULA file does not exist where it expects it)? I am not sure if there were supposed to be any further
configuration steps that did not get completed, so i dont know how stable SCOM is now. Should I re-run the R2 installer? Or is it OK as is? The only info online about a SCOM Install where the final configuration failed to install dealt with
an error upgrading the SCOM Console, which is not relevant to my situation. This is my test SCOM environment, running on a VM. I could revert to the pre-upgrade snapshot and see if another upgrade attempt completes successfully, but if that does
work I am concerned that something like this may happen in my prod environment, which is not running on a VM, so has no ability to revert to a snapshot.

Hi,
Please refer to the following links:
Do I need a specific Cumulative Update Release (UR) in order to upgrade to SCOM 2012 or 2012 SP1 or 2012 R2?
http://blogs.technet.com/b/kevinholman/archive/2014/01/20/do-i-need-a-specific-cumulative-update-release-ur-in-order-to-upgrade-to-scom-2012-or-2012-sp1-or-2012-r2.aspx
Upgrading Operations Manager from 2012 SP1 to 2012 R2 step by step
http://www.systemcentercentral.com/upgrading-operations-manager-from-2012-sp1-to-2012-r2-step-by-step-upgrading-to-2012-r2-series/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+systemcenterforum+%28System+Center+Central+Rollup%29
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Problem upgrading from SCOM 2012 SP1 to R2 (near impossible to uninstall SCOM agent from Management Server)

I'm trying to upgrade our SCOM 2012 SP1 environment to R2, but I have a heck of a problem getting there.
We currently have an test installation with SCOM 2012 SP1 with Management Server and Console on a single 2012 Standard server. The database are located on a remote server. The R2 setup stopped mid way through the setup, because the SCOM 2012 SP1 agent is
installed. And I could NOT remove it my any normal means. I've tried "misexec.exe /x productcode", the setup, powershell uninstall and so on. Nothing works, because the management server installation is blocking the uninstall. The uninstall says
I have to remove the management installation first. And that's not gonna happen.
I had to follow this guide to finally getting through the setup: http://www.opsman.co.za/forcibly-removing-a-scom-agent-that-cannot-be-uninstalled-by-normal-means/
In addition to searching for the agent msi install key in registry, and deleting everything. After I did this, the setup is working, and the SCOM management server, console and DB are up to date. However, the Microsoft Monitoring Agent are STILL there in
Control Panel. And this can NOT be the most healthy way of getting through the setup.
I'm about to upgrade to R2 in our production environment with 3 management servers, and I would hate to go through this sketchy process there as well. Just for the record, I have no idea why the agents are installed on our management servers.
Any of you have tips as to how I can get rid of the agents more gracefully?

Hi
Thanks for the replay guys!
None of those links touch my problem I'm afraid. I have followed the Upgrade guides you pointed to, step by step. But the setup does not Complete. There's problems during the actual software Upgrade of the management servers (3'rd step in the Upgrade page).
I've dived into the Application logs and installation logs, and as far as I can tell, it stops because it has trouble upgrading while the server has the 2012 SP1 Agent installed. I do not remember the actual error text right now, but I can get it in a few
days.
Anyhow, the setup DID move on once I removed most of the registry information of the agent installation. So. that leaves me to the conclusion that the agent IS in fact stopping the setup. Either the agent are malfunctioning, or the setup do not expect the
agent to be present on the management servers. I suspect the latter to be the the most plausible. At least until Yan Li told me this was normal.
So, I'm not sure what to think. I'm pretty much forced to remove this agents, as this is the only thing allowing me to continue the setup. At least untill I'm told otherwise. But I hate to do it this way. It's so dirty. The registry is pretty much cleaned,
but there's still Application files present, and the agent is still in the Control panel and can be started. It's not something I would like to do in our prodution environment.

SCOM 2012 R2 Upgrade Plan Discussion

Similar Messages

Maybe you are looking for