SCOM 2012R2 Operations Manager Multi-tenancy

Hi
I am interested to hear people's deployment experiences with SCOM OpsMgr 2012 R2 in a multi-tenant / Service Provider environment.
I have an interest in setting up a Management Group that will receive alerts (etc.) from external SCOM 2012 agents located in another geographical location & domain - WITHOUT any AD domain trusts involved. I plan to host my new SCOM 2012 R2 deployment
in Azure.
I've looked at the IPD Guide for SCOM but this scenario is out-of-scope of that document. I have read other articles suggesting a 'Gateway Server' - but now I'm confused by the choices for my requirements. Any help / guidance appreciated. Does Microsoft
have any sample Architecture guides for this approach?
Thank you

Hi!
Usually you put the whole Management Group (Management Server, OPS-DB and DWH-DB) in a shared zone (Azure in your case). In each customers network you place a Gateway Server which is joined to the customers domain. For trusts you need certs for the Management
Servers and all Gateways from the same root CA. All agents in the customers domain will communicate with the GW, no need for certs as long as they are in the same domain or other domains that have domain level trusts to the domain where the GW is hosted..
HTH,
Patrick
Please remember to click “Mark as Answer” on the post that helped you.
Patrick Seidl (System Center and Private Cloud)
Website: http://www.syliance.com
Blog: http://www.systemcenterrocks.com

Similar Messages

  • SCOM 2012 Operations Manager Failed to start a process

    We have recently upgraded from SCOM 2007 to SCOM 2012. We are not getting a great deal of “Operations Manager Failed to start a process”. The process varies including:
    DiscoverSQL2008ASDiscovery.vbs
    DiscoverSQL2008DBEngineDiscovery.vbs
    DiscoverSQL2008ASDiscovery.vbs
    Microsoft.Windows.Server.NetwokAdapter.BandwidthUsed.ModuleType.vbs
    I have researched and researched. I know that you can try to run the scripts locally on the machine but it seems the scripts never make it to the machine. I go to the path in the error, no luck. I look in the other folders as I know that SCOM moves the scripts,
    and I even search the entire C drive but the scripts are not getting to the server. The folder is not even making it. For example:
    Command executed: "C:\Windows\system32\cscript.exe" /nologo "Microsoft.Windows.Server.NetwokAdapter.BandwidthUsed.ModuleType.vbs" SERVER true Working Directory: C:\Program Files\System Center Operations Manager\Agent\Health Service State\Monitoring
    Host Temporary Files 11606\1759\
    The script is not there and the folder \1759 is not there either.
    I have removed and reinstalled the client.
    Antivirus is fine, up to date and not blocking on any of the machines.
    I have stopped the “System Center Management service” and renamed the “Health Service State” folder and it recreates fine but not long after I get the warning in SCOM about “Operations Manager Failed to start a process”.
    I look in event viewer for Operations Manager on this particular one and I see a lot of:
    Performance data from the Health Service could not be collected since required registry keys could not be read, the error was 2L (The system cannot find the file specified.). Event ID 6001.
    I tried the fix of
    "lodctr MOMConnectorCounters.ini" and "lodctr HealthServiceCounters.ini" but I get “error
    encountered while updating text in registry. Status: 0”. Again I am using SCOM 2012.
    Do I need to look at each failed script or is there a overall issue because the scripts are not making it to the machines. Any ideas?

    I guess you might need to run "mofcomp sqlmgmproviderxpsp2up.mof".
    Thanks, S K Agrawal

  • Operations Manager 2012 r2 Multi-tenancy

    I'm searching the solution on Multi-tenancy on SCOM 2012 r2. Are there best practices for design and deployment for it? Thanks!!

    Are you looking for this or you can provide more info.
    http://blogs.technet.com/b/servicemanager/archive/2009/12/22/does-service-manager-support-multitenancy-managed-service-providers.aspx
    Juke Chou
    TechNet Community Support

  • MS System Center Operations Manager 2010 Download required for Upgrade from SCOM 2007 R2 (Select)

    We need the download of SCOM 2012 without Service Pack1.
    Upgrade from SCOM 2007 R2 (select license) fails while upgrade check with error: Logs shows "At least one of the following applications is installed on this computer. Due
    to incompatibility with System Center 2012 - Operations Manager, these applications must be uninstalled."
    Upgrade was started from dos elevated prompt with modified parameters like this:
    setup.exe /silent /upgrade
    /AcceptEndUserLicenseAgreement:1
    /UseLocalSystemDASAccount
    /DataReaderUser:<domain\user>
    /DataReaderPassword:<password>
    Research in internet and we found another person with same issue, which reports that direct upgrade from SCOM 2007 R2 to SCOM 2012 SP1 is not possible but if upgrade is done over
    SCOM 2012 to SCOM 2012 SP1 it succeeds.
    Unfortunately, we don't find any downloads for the first release of System Center 2012  e.g. Operations Manager.
    Everything shows Service Pack 1 or the newer R2.
    Who can help?

    Our “Recommended” rolling upgrade path looks like the following:
    SCOM 2007R2 CU4+ > SCOM 2012 RTM UR2+ >
    SCOM 2012 SP1 UR4+ > SCOM 2012 R2
    Also you can refer below link
    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
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical

  • Extending System Center Operations Manager Classes & Discovery SCOM 2007 R2

    I want to add some additional attributes to SCOM that are populated from information in another database.....for example.
    I have a CMDB that contains information about the support level for each server (i.e. gold, silver, bronze), i want to be able to display this information in the SCOM console.  This needs to cover both Windows and Unix/linux servers.
    I have played around with creating a custom MP and have created a new class, and custom script discovery using a vbscript to query the CMDB SQL database containing the info that i want....I have got to the point where i can see the new column in SCOM console
    but cannot get it to populate with any data.
    any help would be appreciated.
    thanks

    Hi,
    Here are some good articles about extending SCOM classes, please go through them:
    Extending System Center Operations Manager Classes & Discovery
    http://blogs.technet.com/b/stufox/archive/2008/07/23/extending-system-center-operations-manager-classes-discovery.aspx
    Extending Windows Computer Class using Visual Studio Authoring Extensions (VSAE)
    http://blogs.technet.com/b/emreguclu/archive/2012/11/07/extending-windows-computer-class-using-visual-studio-authoring-extensions-vsae.aspx
    http://blogs.msdn.com/b/steverac/archive/2011/09/16/extending-a-class-in-the-authoring-console.aspxRegards,
    Ya Li
    Regards, Yan Li

  • SCOM 2012R2 Network Vicinity View doesn't show agent managed PCs

    Hello,
    Network Vicinity View in my SCOM only shows other network devices+management server, but does not show any agent managed computers, why is that? Or is it supposed to be like that and i'm missing something here?
    Thank you

    Hi,
    Things to try in the vicinity view:
    Select a node or connection to view details for that node or connection in the
    Details view.
    Change the levels of connection to be displayed in the diagram by selecting a new value for
    Hops in the toolbar.
    To include agent computers in the view in addition to network devices, select the
    Show Computers check box.
    Select a node in the vicinity view. In the Tasks pane, click the option to launch the Network Node dashboard.
    To change the central device of the view, select a device, and then click
    Vicinity View.
    For more information, please review the link below:
    Viewing Network Devices and Data in Operations Manager
    https://technet.microsoft.com/en-us/library/hh212706.aspx?f=255&MSPPError=-2147217396#bkmk_networkvicinitydashboard
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • SCOM 2012 System Center Operations Manager has stopped working when adding Web Console.

    I am trying to ad the Web console to one of my Management Servers but at the point where it asks what website to use it fails with the "System Center Operations Manager Setup has Stopped working error.
    This is the included information.
    Problem Event Name: CLR20r3
      Problem Signature 01: setupchainerui.exe
      Problem Signature 02: 7.0.9538.0
      Problem Signature 03: 509042f2
      Problem Signature 04: System
      Problem Signature 05: 4.0.30319.18022
      Problem Signature 06: 506a7689
      Problem Signature 07: 1cf5
      Problem Signature 08: 72
      Problem Signature 09: System.UriFormatException
      OS Version: 6.2.9200.2.0.0.272.7
      Locale ID: 1033
      Additional Information 1: 79c6
      Additional Information 2: 79c63d7b6daeea05a42903612b7137d2
      Additional Information 3: 88ec
      Additional Information 4: 88ec54f8fa758d8069cdb2ad5cd91e2b
    The only error I get in the log file is this.
    Error: :Error:IsReportingValidToInstall failed SRS instance not provided 
    I don't understand why I would be getting an SRS error, our reports run fine.
    Thanks,
    Gary

    Hi Gary,
    Did you end up finding a solution to this issue? The GUI and silent/command line installer are failing for me in the same spot.
    App Log Errors:
    Application: SetupChainerUI.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: Microsoft.EnterpriseManagement.Common.ServiceNotRunningException
    Stack:
       at Microsoft.EnterpriseManagement.Common.Internal.ExceptionHandlers.HandleChannelExceptions(System.Exception)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](Microsoft.EnterpriseManagement.EnterpriseManagementConnectionSettings,
    Microsoft.EnterpriseManagement.Common.Internal.SdkChannelObject`1<Microsoft.EnterpriseManagement.Common.Internal.IDispatcherService>)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.ConstructEnterpriseManagementGroupInternal[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0,
    Culture=neutral, PublicKeyToken=b77a5c561934e089]](Microsoft.EnterpriseManagement.EnterpriseManagementConnectionSettings, Microsoft.EnterpriseManagement.DataAbstractionLayer.ClientDataAccessCore)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.RetrieveEnterpriseManagementGroupInternal[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0,
    Culture=neutral, PublicKeyToken=b77a5c561934e089]](Microsoft.EnterpriseManagement.EnterpriseManagementConnectionSettings, Microsoft.EnterpriseManagement.DataAbstractionLayer.ClientDataAccessCore)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Connect[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](Microsoft.EnterpriseManagement.EnterpriseManagementConnectionSettings,
    Microsoft.EnterpriseManagement.DataAbstractionLayer.ClientDataAccessCore)
       at Microsoft.EnterpriseManagement.ManagementGroup.InternalInitialize(Microsoft.EnterpriseManagement.EnterpriseManagementConnectionSettings, Microsoft.EnterpriseManagement.ManagementGroupInternal)
       at Microsoft.EnterpriseManagement.ManagementGroup.Connect(System.String)
       at Microsoft.SystemCenter.Essentials.SetupFramework.WebConsoleSite.GetValidationProperties(System.Object)
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
       at System.Threading.ThreadPoolWorkQueue.Dispatch()
    Faulting application name: SetupChainerUI.exe, version: 7.0.9538.0, time stamp: 0x509042f2
    Faulting module name: KERNELBASE.dll, version: 6.3.9600.16656, time stamp: 0x5318237f
    Exception code: 0xe0434352
    Fault offset: 0x00000000000043c8
    Faulting process id: 0x638
    Faulting application start time: 0x01cf9a697847d9c8
    Faulting application path: C:\Users\szb\AppData\Local\SCOM\SetupChainerUI.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: c52d5d75-065c-11e4-80c2-00155dcb0b37
    Faulting package full name:
    Faulting package-relative application ID:

  • Again - Active Directory Management Pack - AD MP - SCOM 2012R2 - AD 2012R2 - Action / RunAs Account permissions

    Hi,
    after reading many Posts and Blogs i came to the conclusion that it is still unclear to me what is needed to Monitor Active Directory successfully and what is the securest way configuring the RunAs or Action Account. I hope the experts here can make a clear
    Statement to answer the question for all time ;-)
    1. Action Account:
    Here is described what permissions and rights are needed to use a low-privileged account:
    https://technet.microsoft.com/en-us/library/hh212808.aspx
    Now you might say: that was asked and answered so many times..you are right, but the answer was from run as "local System" to "you Need local admin". So also the AD MP documentation still says you Need a local Admin account.
    here are other references which says you Need local admin rights:
    http://micloud.azurewebsites.net//2014/02/26/scom-agent-grayed-out-when-trying-to-monitor-domain-controllers/
    Even Kevin Holman says here
    https://social.technet.microsoft.com/Forums/systemcenter/en-US/2a0e5a2b-a3d9-42d4-8474-9f690007caa0/opsmgrlatency-cn-gets-auto-created-in-domain-not-configuration:
    "Basically - if your domain controllers are running as local system default agent action account, in most cases you will not need to ever set up any replication monitoring run-as accounts.... as local system on a DC has all the rights necessary. 
    (in most cases).
    "Simple questions: Is this really enought to Monitor every aspect of an ActiveDirectory Domain and Domain Controller using a low privilege account the the permissions in the article? Or is using local System better? Is there a difference when
    using SCOM2012R2 with the new Agent? Most documentation referes to SCOM2007(except the replication Monitoring where it is clear that other permissions are needed:
    http://blogs.technet.com/b/jimmyharper/archive/2009/05/20/configuring-or-disabling-replication-monitoring-in-the-active-directory-management-pack.aspx )

    The MP guide is not really clear about it. The only thing they are clear about is whenever you want to use client monitoring. In those situations low privileged will not work.
    For each of the client-side monitoring scripts to run successfully, the
    Action Account must be a member of the Administrators group on both the computer
    on which the client management pack is running and the domain controller that is being monitored. The
    Action Account must also be a member of the
    Operations Manager Administrators group, which is configured through the Operations console in so that all the scripts that are configured on the Root Management Server can run properly
    Both a local system and domain admin are a risk. If someone loads a malicious management pack that makes changes to the AD services you are screwed. The local system has unrestricted access to local resources including domain services.
    The only reason I don't want a domain admin account in SCOM is that you have an additional layer where the password potentially could be retrieved. That's not the case with a local system account. But the risks are the same.
    See: https://msdn.microsoft.com/en-us/library/ms677973%28v=vs.85%29.aspx
    But this not an answer to your question. :-)

  • SCVMM 2012R2 Management Pack for SCOM 2012R2?

    Per the requirements of the SCVMM 2012R2 Dashboard Management Pack:
    http://www.microsoft.com/en-us/download/details.aspx?id=43707
    It requires the following files:
    Microsoft System Center Virtual Machine Manager Library 3.2.7510.0
    Microsoft System Center Virtual Machine Manager 2012 R2 Discovery 3.2.7510.0
    Microsoft System Center Virtual Machine Manager 2012 R2 Monitoring 3.2.7510.0
    However I am unable to find this management pack anywhere. Can someone point me in the right direction?

    Ah, got it. I was confused by the vocabulary. Followed this document:
    http://technet.microsoft.com/en-US/library/hh882396.aspx
    thanks!

  • Migration from SCOM 2007R2 to SCOM 2012R2

       Hello to all. I have a SCOM 2007R2 environment with 3 servers:
       1- SRV #1 has RMS and WebConsole roles.
       2- SRV #2 has Gateway role.
       3- SRV #3 is Shared SQL Server with SCOM DB + Reporting roles.
       This deplyoment monitors ~600 and I´m planning to take it to SCOM 2012 R2.
       Question 1:
       I already read several articles but for me is not clear if I can just insert SCOM 2012 R2 Management Server and Gateway on a existing 2007R2 Management Group (of course that it already has a RMS), begin migrating agents to it
    and at the end  decomission SCOM 2007 R2 Servers. All articles that I read mention just two options:
    a) Side-by-Side migration (install SCOM 2012R2 on a NEW Management Group and begin agent migration to this NEW Management Group) and
    b) Upgrade (run in-place upgrade to SCOM 2012 R2 if current SCOM 2007R2 attend SCOM 2012 R2 requirements - if not, install new SCOM 2007R2 servers with supported requirements and run upgrade in-place). Considering this info.,
    is it possible to run SCOM 2007 R2 --> 2012 R2 migration as I previously mentioned?
       Question 2:
       Does SCOM 2007R2 agent reports to SCOM 2012R2 Management Servers?
       Question 3:
       Is it possible to run direct migration (not pass through SCOM 2012 - withouy R2) using the path SCOM 2007 R2 --> SCOM 2012 R2 path?
       Regards, EEOC.

    Hi,
    Q1:
    It is suggested to do side by side migration, and for upgrading from System Center Operations Manager 2007 R2, please refer to the below link:
    http://technet.microsoft.com/en-us/library/hh476934.aspx
    Q2:
    You can multi-home the clients to both SCOM 2007R2 & 2012, but 2007 agent can’t communicate with a SCOM2012 MS.
    Q3:
    If we use side by side migration, then we don't need to pass through SCOM 2012, but if we use in-place-upgrade, then we must follow the below path:
    SCOM 2007R2 CU4+ >
    SCOM 2012 RTM > SCOM 2012 SP1 > SCOM 2012 R2
    More details:
    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
    Regards,
    Yan Li
    Regards, Yan Li

  • OMServer.msi returns error 1603 when trying to upgrade first management server from Operations Manager 2012 SP1 to Operations Manager 2012 R2

    Hi All, looking for some assistance with the following issue.
    We are attempting to upgrade our Operations Manager 2012 SP1 environment to Operations Manager 2012 R2.
    We have completed all the pre-upgrade tasks detailed here
    http://technet.microsoft.com/en-us/library/dn249704.aspx
    We are then following the guidance detailed here regarding upgrading distributed management groups
    http://technet.microsoft.com/en-us/library/dn249721.aspx. The upgrade fails on the first management server with the following screen being displayed.
    OMServer.log file is as follows.
    === Verbose logging started: 22/01/2014 10:21:27 Build type: SHIP UNICODE 5.00.9200.00 Calling process: C:\Users\scomaction\AppData\Local\SCOM\Setup\SetupChainerUI.exe ===
    MSI (c) (78:34) [10:21:27:040]: Resetting cached policy values
    MSI (c) (78:34) [10:21:27:040]: Machine policy value 'Debug' is 0
    MSI (c) (78:34) [10:21:27:040]: ******* RunEngine:
    ******* Product: F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
    ******* Action:
    ******* CommandLine: **********
    MSI (c) (78:34) [10:21:27:040]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (78:34) [10:21:27:040]: Grabbed execution mutex.
    MSI (c) (78:34) [10:21:27:071]: Cloaking enabled.
    MSI (c) (78:34) [10:21:27:071]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (78:34) [10:21:27:071]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (D4:30) [10:21:27:082]: Running installation inside multi-package transaction F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
    MSI (s) (D4:30) [10:21:27:082]: Grabbed execution mutex.
    MSI (s) (D4:A0) [10:21:27:086]: Resetting cached policy values
    MSI (s) (D4:A0) [10:21:27:086]: Machine policy value 'Debug' is 0
    MSI (s) (D4:A0) [10:21:27:086]: ******* RunEngine:
    ******* Product: F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
    ******* Action:
    ******* CommandLine: **********
    MSI (s) (D4:A0) [10:21:27:175]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (D4:A0) [10:21:27:181]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
    MSI (s) (D4:A0) [10:21:27:190]: SRSetRestorePoint skipped for this transaction.
    MSI (s) (D4:A0) [10:21:27:192]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
    MSI (s) (D4:A0) [10:21:27:200]: File will have security applied from OpCode.
    MSI (s) (D4:A0) [10:21:27:234]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi' against software restriction policy
    MSI (s) (D4:A0) [10:21:27:234]: SOFTWARE RESTRICTION POLICY: F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi has a digital signature
    MSI (s) (D4:A0) [10:21:27:354]: SOFTWARE RESTRICTION POLICY: F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi is permitted to run at the 'unrestricted' authorization level.
    MSI (s) (D4:A0) [10:21:27:354]: MSCOREE not loaded loading copy from system32
    MSI (s) (D4:A0) [10:21:27:360]: End dialog not enabled
    MSI (s) (D4:A0) [10:21:27:360]: Original package ==> F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
    MSI (s) (D4:A0) [10:21:27:360]: Package we're running from ==> C:\Windows\Installer\4b8344.msi
    MSI (s) (D4:A0) [10:21:27:371]: APPCOMPAT: Compatibility mode property overrides found.
    MSI (s) (D4:A0) [10:21:27:372]: APPCOMPAT: looking for appcompat database entry with ProductCode '{C92727BE-BD12-4140-96A6-276BA4F60AC1}'.
    MSI (s) (D4:A0) [10:21:27:372]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (D4:A0) [10:21:27:378]: Machine policy value 'TransformsSecure' is 1
    MSI (s) (D4:A0) [10:21:27:379]: Machine policy value 'DisablePatch' is 0
    MSI (s) (D4:A0) [10:21:27:379]: Machine policy value 'AllowLockdownPatch' is 0
    MSI (s) (D4:A0) [10:21:27:379]: Machine policy value 'DisableLUAPatching' is 0
    MSI (s) (D4:A0) [10:21:27:379]: Machine policy value 'DisableFlyWeightPatching' is 0
    MSI (s) (D4:A0) [10:21:27:380]: APPCOMPAT: looking for appcompat database entry with ProductCode '{C92727BE-BD12-4140-96A6-276BA4F60AC1}'.
    MSI (s) (D4:A0) [10:21:27:380]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (D4:A0) [10:21:27:380]: Transforms are not secure.
    MSI (s) (D4:A0) [10:21:27:380]: Note: 1: 2205 2: 3: Control
    MSI (s) (D4:A0) [10:21:27:380]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'C:\Users\scomaction\AppData\Local\SCOM\Logs\OMServer.log'.
    MSI (s) (D4:A0) [10:21:27:380]: Command Line: OM_INSTALLDIR=F:\Program Files\Microsoft System Center 2012 R2\Operations Manager SEND_CEIP_REPORTS=0 MU_SETTING=0 ROOT_MANAGEMENT_SERVER_PORT=5723 SC_DB_SERVER=SCOM-XXX-AG SCDATABASENAME=OperationsManager DW_DB_SERVER=SCOM-XXX-AG DWDATABASENAME=OperationsManagerDW REBOOT=ReallySuppress CURRENTDIRECTORY=C:\Users\scomaction\AppData\Local\SCOM\Setup CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1 CLIENTPROCESSID=4472
    MSI (s) (D4:A0) [10:21:27:380]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{58EFE971-58C1-4DBD-A400-A7607A745475}'.
    MSI (s) (D4:A0) [10:21:27:380]: Product Code passed to Engine.Initialize: ''
    MSI (s) (D4:A0) [10:21:27:380]: Product Code from property table before transforms: '{C92727BE-BD12-4140-96A6-276BA4F60AC1}'
    MSI (s) (D4:A0) [10:21:27:380]: Product Code from property table after transforms: '{C92727BE-BD12-4140-96A6-276BA4F60AC1}'
    MSI (s) (D4:A0) [10:21:27:380]: Product not registered: beginning first-time install
    MSI (s) (D4:A0) [10:21:27:380]: Product {C92727BE-BD12-4140-96A6-276BA4F60AC1} is not managed.
    MSI (s) (D4:A0) [10:21:27:380]: MSI_LUA: Credential prompt not required, user is an admin
    MSI (s) (D4:A0) [10:21:27:381]: PROPERTY CHANGE: Adding ProductState property. Its value is '-1'.
    MSI (s) (D4:A0) [10:21:27:381]: Entering CMsiConfigurationManager::SetLastUsedSource.
    MSI (s) (D4:A0) [10:21:27:381]: User policy value 'SearchOrder' is 'nmu'
    MSI (s) (D4:A0) [10:21:27:381]: Adding new sources is allowed.
    MSI (s) (D4:A0) [10:21:27:381]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is '1'.
    MSI (s) (D4:A0) [10:21:27:381]: Package name extracted from package path: 'OMServer.msi'
    MSI (s) (D4:A0) [10:21:27:381]: Package to be registered: 'OMServer.msi'
    MSI (s) (D4:A0) [10:21:27:383]: Note: 1: 2262 2: AdminProperties 3: -2147287038
    MSI (s) (D4:A0) [10:21:27:383]: Machine policy value 'DisableMsi' is 1
    MSI (s) (D4:A0) [10:21:27:383]: Machine policy value 'AlwaysInstallElevated' is 0
    MSI (s) (D4:A0) [10:21:27:383]: User policy value 'AlwaysInstallElevated' is 0
    MSI (s) (D4:A0) [10:21:27:383]: Product installation will be elevated because user is admin and product is being installed per-machine.
    MSI (s) (D4:A0) [10:21:27:383]: Running product '{C92727BE-BD12-4140-96A6-276BA4F60AC1}' with elevated privileges: Product is assigned.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding OM_INSTALLDIR property. Its value is 'F:\Program Files\Microsoft System Center 2012 R2\Operations Manager'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding ROOT_MANAGEMENT_SERVER_PORT property. Its value is '5723'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Modifying SC_DB_SERVER property. Its current value is 'OperationsManager'. Its new value: 'SCOM-XXX-AG'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding DW_DB_SERVER property. Its value is 'SCOM-XXX-AG'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding DWDATABASENAME property. Its value is 'OperationsManagerDW'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding REBOOT property. Its value is 'ReallySuppress'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'C:\Users\scomaction\AppData\Local\SCOM\Setup'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding MSICLIENTUSESEXTERNALUI property. Its value is '1'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '4472'.
    MSI (s) (D4:A0) [10:21:27:383]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
    MSI (s) (D4:A0) [10:21:27:383]: RESTART MANAGER: Disabled by MSIRESTARTMANAGERCONTROL property; Windows Installer will use the built-in FilesInUse functionality.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding MsiSystemRebootPending property. Its value is '1'.
    MSI (s) (D4:A0) [10:21:27:383]: TRANSFORMS property is now:
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '300'.
    MSI (s) (D4:A0) [10:21:27:395]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming
    MSI (s) (D4:A0) [10:21:27:396]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\Favorites
    MSI (s) (D4:A0) [10:21:27:398]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Network Shortcuts
    MSI (s) (D4:A0) [10:21:27:399]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\Documents
    MSI (s) (D4:A0) [10:21:27:401]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
    MSI (s) (D4:A0) [10:21:27:402]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Recent
    MSI (s) (D4:A0) [10:21:27:404]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\SendTo
    MSI (s) (D4:A0) [10:21:27:405]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Templates
    MSI (s) (D4:A0) [10:21:27:405]: SHELL32::SHGetFolderPath returned: C:\ProgramData
    MSI (s) (D4:A0) [10:21:27:406]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Local
    MSI (s) (D4:A0) [10:21:27:408]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\Pictures
    MSI (s) (D4:A0) [10:21:27:411]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
    MSI (s) (D4:A0) [10:21:27:413]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
    MSI (s) (D4:A0) [10:21:27:414]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs
    MSI (s) (D4:A0) [10:21:27:415]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu
    MSI (s) (D4:A0) [10:21:27:417]: SHELL32::SHGetFolderPath returned: C:\Users\Public\Desktop
    MSI (s) (D4:A0) [10:21:27:420]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Administrative Tools
    MSI (s) (D4:A0) [10:21:27:421]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
    MSI (s) (D4:A0) [10:21:27:423]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
    MSI (s) (D4:A0) [10:21:27:424]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Start Menu
    MSI (s) (D4:A0) [10:21:27:426]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\Desktop
    MSI (s) (D4:A0) [10:21:27:427]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Templates
    MSI (s) (D4:A0) [10:21:27:428]: SHELL32::SHGetFolderPath returned: C:\Windows\Fonts
    MSI (s) (D4:A0) [10:21:27:428]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
    MSI (s) (D4:A0) [10:21:27:433]: MSI_LUA: Setting MsiRunningElevated property to 1 because the install is already running elevated.
    MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding MsiRunningElevated property. Its value is '1'.
    MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding Privileged property. Its value is '1'.
    MSI (s) (D4:A0) [10:21:27:434]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
    MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding USERNAME property. Its value is 'Windows User'.
    MSI (s) (D4:A0) [10:21:27:434]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
    MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:\Windows\Installer\4b8344.msi'.
    MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi'.
    MSI (s) (D4:A0) [10:21:27:434]: Machine policy value 'MsiDisableEmbeddedUI' is 0
    MSI (s) (D4:A0) [10:21:27:434]: EEUI - Disabling MsiEmbeddedUI due to existing external or embedded UI
    MSI (s) (D4:A0) [10:21:27:434]: EEUI - Disabling MsiEmbeddedUI for service because it's not a quiet/basic install
    MSI (s) (D4:A0) [10:21:27:434]: Note: 1: 2205 2: 3: PatchPackage
    MSI (s) (D4:A0) [10:21:27:434]: Machine policy value 'DisableRollback' is 0
    MSI (s) (D4:A0) [10:21:27:434]: User policy value 'DisableRollback' is 0
    MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding UILevel property. Its value is '2'.
    === Logging started: 22/01/2014 10:21:27 ===
    MSI (s) (D4:A0) [10:21:27:435]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
    MSI (s) (D4:A0) [10:21:27:436]: APPCOMPAT: [DetectVersionLaunchCondition] Launch condition already passes.
    MSI (s) (D4:A0) [10:21:27:438]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
    MSI (s) (D4:A0) [10:21:27:438]: Doing action: INSTALL
    Action start 10:21:27: INSTALL.
    MSI (s) (D4:A0) [10:21:27:444]: Running ExecuteSequence
    MSI (s) (D4:A0) [10:21:27:444]: Doing action: SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76
    MSI (s) (D4:A0) [10:21:27:447]: PROPERTY CHANGE: Adding SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76 property. Its value is 'C:\Windows\SysWOW64\'.
    Action start 10:21:27: SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76.
    MSI (s) (D4:A0) [10:21:27:448]: Doing action: System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76
    Action ended 10:21:27: SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76. Return value 1.
    MSI (s) (D4:A0) [10:21:27:450]: PROPERTY CHANGE: Adding System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76 property. Its value is 'C:\Windows\system32\'.
    Action start 10:21:27: System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76.
    MSI (s) (D4:A0) [10:21:27:450]: Doing action: WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6
    Action ended 10:21:27: System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76. Return value 1.
    MSI (s) (D4:A0) [10:21:27:452]: PROPERTY CHANGE: Adding WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6 property. Its value is 'C:\Windows\'.
    Action start 10:21:27: WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6.
    MSI (s) (D4:A0) [10:21:27:453]: Doing action: System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522
    Action ended 10:21:27: WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6. Return value 1.
    MSI (s) (D4:A0) [10:21:27:455]: PROPERTY CHANGE: Adding System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522 property. Its value is 'C:\Windows\system32\'.
    Action start 10:21:27: System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522.
    MSI (s) (D4:A0) [10:21:27:456]: Doing action: WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C
    Action ended 10:21:27: System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522. Return value 1.
    MSI (s) (D4:A0) [10:21:27:458]: PROPERTY CHANGE: Adding WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C property. Its value is 'C:\Windows\'.
    Action start 10:21:27: WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C.
    MSI (s) (D4:A0) [10:21:27:458]: Doing action: SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C
    Action ended 10:21:27: WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C. Return value 1.
    MSI (s) (D4:A0) [10:21:27:461]: PROPERTY CHANGE: Adding SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C property. Its value is 'C:\Windows\SysWOW64\'.
    Action start 10:21:27: SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C.
    MSI (s) (D4:A0) [10:21:27:461]: Doing action: WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7
    Action ended 10:21:27: SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C. Return value 1.
    MSI (s) (D4:A0) [10:21:27:463]: PROPERTY CHANGE: Adding WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7 property. Its value is 'C:\Windows\'.
    Action start 10:21:27: WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7.
    MSI (s) (D4:A0) [10:21:27:463]: Doing action: System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7
    Action ended 10:21:27: WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7. Return value 1.
    MSI (s) (D4:A0) [10:21:27:466]: PROPERTY CHANGE: Adding System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7 property. Its value is 'C:\Windows\system32\'.
    Action start 10:21:27: System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7.
    MSI (s) (D4:A0) [10:21:27:467]: Doing action: WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8
    Action ended 10:21:27: System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7. Return value 1.
    MSI (s) (D4:A0) [10:21:27:468]: PROPERTY CHANGE: Adding WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8 property. Its value is 'C:\Windows\'.
    Action start 10:21:27: WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8.
    MSI (s) (D4:A0) [10:21:27:469]: Doing action: WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9
    Action ended 10:21:27: WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8. Return value 1.
    MSI (s) (D4:A0) [10:21:27:471]: PROPERTY CHANGE: Adding WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 property. Its value is 'C:\Windows\'.
    Action start 10:21:27: WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9.
    MSI (s) (D4:A0) [10:21:27:472]: Doing action: WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE
    Action ended 10:21:27: WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9. Return value 1.
    MSI (s) (D4:A0) [10:21:27:474]: PROPERTY CHANGE: Adding WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE property. Its value is 'C:\Windows\'.
    Action start 10:21:27: WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE.
    MSI (s) (D4:A0) [10:21:27:475]: Doing action: ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0
    Action ended 10:21:27: WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE. Return value 1.
    MSI (s) (D4:A0) [10:21:27:477]: PROPERTY CHANGE: Adding ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0 property. Its value is 'C:\ProgramData\Microsoft\Windows\Start Menu\Programs\'.
    Action start 10:21:27: ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0.
    MSI (s) (D4:A0) [10:21:27:477]: Doing action: FindRelatedProducts
    Action ended 10:21:27: ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0. Return value 1.
    Action start 10:21:27: FindRelatedProducts.
    MSI (s) (D4:A0) [10:21:27:481]: PROPERTY CHANGE: Adding CORECOMPONENTPRESENT_AGENT property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'.
    MSI (s) (D4:A0) [10:21:27:483]: Skipping action: _StopCoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
    MSI (s) (D4:A0) [10:21:27:483]: Skipping action: _KillOMProcesses.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
    MSI (s) (D4:A0) [10:21:27:483]: Skipping action: _SearchOpsMgrShellPath.CFE2C791_D05A_4240_90ED_DEB20161DFB0 (condition is false)
    MSI (s) (D4:A0) [10:21:27:483]: Doing action: _SetMonadFilePath.CFE2C791_D05A_4240_90ED_DEB20161DFB0
    Action ended 10:21:27: FindRelatedProducts. Return value 1.
    MSI (s) (D4:08) [10:21:27:501]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI847C.tmp, Entrypoint: SetMonadFilePath
    MSI (s) (D4:B0) [10:21:27:502]: Generating random cookie.
    MSI (s) (D4:B0) [10:21:27:505]: Created Custom Action Server with PID 4964 (0x1364).
    MSI (s) (D4:34) [10:21:27:527]: Running as a service.
    MSI (s) (D4:34) [10:21:27:529]: Hello, I'm your 64bit Impersonated custom action server.
    Action start 10:21:27: _SetMonadFilePath.CFE2C791_D05A_4240_90ED_DEB20161DFB0.
    MSI (s) (D4!DC) [10:21:27:638]: PROPERTY CHANGE: Modifying MONAD_SHELL_PATH property. Its current value is 'Error: Value Never Set. Check the CACore:SetMonadFilePath CA'. Its new value: 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe'.
    GetRegistyStringValue: Registy key value found.. C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
    MSI (s) (D4:A0) [10:21:27:640]: Doing action: _Set_CORECOMPONENTPRESENT
    Action ended 10:21:27: _SetMonadFilePath.CFE2C791_D05A_4240_90ED_DEB20161DFB0. Return value 1.
    MSI (s) (D4:A0) [10:21:27:643]: PROPERTY CHANGE: Adding CORECOMPONENTPRESENT property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'.
    Action start 10:21:27: _Set_CORECOMPONENTPRESENT.
    MSI (s) (D4:A0) [10:21:27:644]: Skipping action: _AbortDowngradeProductAttempt (condition is false)
    MSI (s) (D4:A0) [10:21:27:644]: Doing action: _AbortIncompatibleComponents
    Action ended 10:21:27: _Set_CORECOMPONENTPRESENT. Return value 1.
    Action start 10:21:27: _AbortIncompatibleComponents.
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5044 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 1580 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5512 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 4268 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5024 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 6064 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 3396 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 2704 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5568 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5940 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 1968 could not be cancelled. Error: 1168
    MSI (s) (D4:A0) [10:21:27:652]: 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.
    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.
    Action ended 10:21:27: _AbortIncompatibleComponents. Return value 3.
    Action ended 10:21:27: INSTALL. Return value 3.
    Property(S): DiskPrompt = Please Insert Disk 1
    Property(S): UpgradeCode = {17058653-A628-4C03-8F80-5E2B179ECD55}
    Property(S): SCDATABASENAME = OperationsManager
    Property(S): SC_DB_SERVER = SCOM-XXX-AG
    Property(S): SDK_PASSWORD.540EA3C0_A5E9_41EA_A585_822C09EA2650 = **********
    Property(S): CORECOMPONENTPRESENT = {8B21425D-02F3-4B80-88CE-8F79B320D330}
    Property(S): OM_INSTALLDIR = F:\Program Files\Microsoft System Center 2012 R2\Operations Manager
    Property(S): ProgramFiles64Folder = C:\Program Files\
    Property(S): Privileged = 1
    Property(S): ARPSYSTEMCOMPONENT = 1
    Property(S): DONOTSKIPDELETESERVICES = 0
    Property(S): DONOTSKIPINSTALLSERVICES = 0
    Property(S): OM_COMMON_PRODUCT_REGISTRY_PATH = SOFTWARE\Microsoft\System Center Operations Manager
    Property(S): OM_COMMON_PRODUCT_RELEASE_REGISTRY_KEY = 12
    Property(S): OM_COMMON_PRODUCT_DEFAULT_INSTALL_DIR = System Center Operations Manager
    Property(S): NetFxVersion = v2.0.50727
    Property(S): IS_OM_SERVER = 1
    Property(S): InstallAPMAgent = 1
    Property(S): INSTALLLEVEL = 100
    Property(S): ALLUSERS = 1
    Property(S): ARPNOREPAIR = 0
    Property(S): ARPURLINFOABOUT = http://www.microsoft.com/mom
    Property(S): ARPURLUPDATEINFO = http://www.microsoft.com/mom
    Property(S): ARPHELPLINK = http://support.microsoft.com
    Property(S): MSIRESTARTMANAGERCONTROL = Disable
    Property(S): SQL_PORT = 1433
    Property(S): DbSizeGood = 1
    Property(S): DbFileOptionsGood = 1
    Property(S): DbFilesSpaceGood = 1
    Property(S): DbNameGood = 1
    Property(S): SqlServicesStarted = 1
    Property(S): _SetSDKServiceAccount.540EA3C0_A5E9_41EA_A585_822C09EA2650 = **********
    Property(S): _SetConfigServiceAccount.540EA3C0_A5E9_41EA_A585_822C09EA2650 = **********
    Property(S): DialogWizardTitle = System Center 2012 R2 Operations Manager Setup
    Property(S): MinimumOSMsg = This product must be installed on Windows Server 2008 R2 or higher.
    Property(S): MOMSDKPortDesc = Operations Manager SDK.
    Property(S): MOMConnectorPortDesc = Operations Manager Connector Framework.
    Property(S): MOMAEMPortDesc = Operations Manager Application Error Monitoring.
    Property(S): MOMSQMPortDesc = Operations Manager Customer Experience Improvement Program.
    Property(S): MOMHSPortDesc = System Center Management Health Service
    Property(S): SCOMV3SP1ProgramName = System Center 2012 R2 Operations Manager
    Property(S): FWRulePingRequestName = Operations Manager Ping Request (Echo Request - ICMPv4 OUT)
    Property(S): FWRulePingRequestDesc = Operations Manager network monitoring ping request
    Property(S): FWRulePingResponseName = Operations Manager Ping Response (Echo Response - ICMPv4 IN)
    Property(S): FWRulePingResponseDesc = Operations Manager network monitoring ping response
    Property(S): FWRuleSnmpRequestName = Operations Manager SNMP Request
    Property(S): FWRuleSnmpRequestDesc = Operations Manager network monitoring SNMP request
    Property(S): FWRuleSnmpResponseName = Operations Manager SNMP Response
    Property(S): FWRuleSnmpResponseDesc = Operations Manager network monitoring SNMP response
    Property(S): FWRuleSnmpTrapListenerName = Operations Manager SNMP Trap Listener
    Property(S): FWRuleSnmpTrapListenerDesc = Operations Manager network monitoring SNMP trap listener
    Property(S): Manufacturer = Microsoft Corporation
    Property(S): ProductCode = {C92727BE-BD12-4140-96A6-276BA4F60AC1}
    Property(S): ProductLanguage = 1033
    Property(S): ProductName = System Center Operations Manager 2012 Server
    Property(S): ProductVersion = 7.1.10226.0
    Property(S): SecureCustomProperties = ACTIONSPASSWORD;CORECOMPONENTPRESENT_AGENT;CORECOMPONENTPRESENT_GW;CORECOMPONENTPRESENT_RC;CORECOMPONENTPRESENT_SCE;CORECOMPONENTPRESENT_SMB2;CORECOMPONENTPRESENT_SMRTM;IS_AVICODE_AGENT_INSTALLED;IS_MOMASPAGENT_INSTALLED;MOM_DB_SERVER;MOMDATABASENAME_OLD;OM_NEWER_PRODUCT_FOUND;SDK_PASSWORD.540EA3C0_A5E9_41EA_A585_822C09EA2650;SQL_PORT
    Property(S): MsiHiddenProperties = _SetConfigServiceAccount.540EA3C0_A5E9_41EA_A585_822C09EA2650;_SetSDKServiceAccount.540EA3C0_A5E9_41EA_A585_822C09EA2650;ACTIONSPASSWORD;SDK_PASSWORD.540EA3C0_A5E9_41EA_A585_822C09EA2650
    Property(S): WixPdbPath = d:\btvsts\20867\private\product\setup\wix\msi\server\om\obj\amd64\OMServer.wixpdb
    Property(S): CORECOMPONENTPRESENT_AGENT = {8B21425D-02F3-4B80-88CE-8F79B320D330}
    Property(S): ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0 = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
    Property(S): MONAD_SHELL_PATH = C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
    Property(S): EnableEV.CFE2C791_D05A_4240_90ED_DEB20161DFB0 = 1
    Property(S): AddInstallPath.CFE2C791_D05A_4240_90ED_DEB20161DFB0 = add
    Property(S): RemoveInstallPath.CFE2C791_D05A_4240_90ED_DEB20161DFB0 = remove
    Property(S): WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE = C:\Windows\
    Property(S): VersionNT = 602
    Property(S): DW_DB_SERVER = SCOM-XXX-AG
    Property(S): DWDATABASENAME = OperationsManagerDW
    Property(S): OMDATABASENAME = OperationsManger
    Property(S): MaximumDataAgeMinutes = 10080
    Property(S): MaximumQueueSizeKB = 102400
    Property(S): MOMSDKPort.1451A536_2C9B_42F2_A37A_C9C6460E7EEA = 5724
    Property(S): MOMConnectorPort.1451A536_2C9B_42F2_A37A_C9C6460E7EEA = 51905
    Property(S): MOMAEMPort.1451A536_2C9B_42F2_A37A_C9C6460E7EEA = 51906
    Property(S): MOMSQMPort.1451A536_2C9B_42F2_A37A_C9C6460E7EEA = 51907
    Property(S): SDK_SERVICE_TYPE = 4
    Property(S): ROOT_MANAGEMENT_SERVER_PORT = 5723
    Property(S): SERVER_MANAGEMENT_GROUP_TYPE.C6F00077_9737_419B_A8B6_B309BA6F8FC8 = 1
    Property(S): MaximumForwardedVirtualQueuePercentage = 8
    Property(S): QueueSendDataSinglePriority = 0
    Property(S): ADMIN_ROLE_GROUP.C6F00077_9737_419B_A8B6_B309BA6F8FC8 = Administrators
    Property(S): USE_MANUALLY_SPECIFIED_SETTINGS = 1
    Property(S): WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 = C:\Windows\
    Property(S): CommonFiles64Folder = C:\Program Files\Common Files\
    Property(S): CAN_REGISTER_FOR_MU = 0
    Property(S): MU_SETTING = 0
    Property(S): IS_ROOT_HEALTH_SERVICE = 0
    Property(S): IS_MOM_SERVER = 0
    Property(S): IS_MOM_GATEWAY = 0
    Property(S): WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8 = C:\Windows\
    Property(S): WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7 = C:\Windows\
    Property(S): System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7 = C:\Windows\system32\
    Property(S): DirectoryTable100_amd64.1C11561A_11CB_36A7_8A47_D7A042055FA7 = DirectoryTable
    Property(S): WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C = C:\Windows\
    Property(S): SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C = C:\Windows\SysWOW64\
    Property(S): DirectoryTable100_x86.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C = DirectoryTable
    Property(S): SEND_CEIP_REPORTS = 0
    Property(S): System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522 = C:\Windows\system32\
    Property(S): ACS_AGENT_ACCOUNT.A7850EAF_DD6F_4ED6_9581_E958CBD8A522 =
    Property(S): WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6 = C:\Windows\
    Property(S): SC_COMMON_REGISTRY_PATH = SOFTWARE\Microsoft\System Center\2010\Common
    Property(S): DISCOVERY_DATA_AUTHORIZATION_ENABLED = 0
    Property(S): IcmpProtocol.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 1
    Property(S): IcmpRequestType.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 8:*
    Property(S): IcmpResponseType.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 0:*
    Property(S): SnmpProtocol.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 17
    Property(S): SnmpPort.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 161
    Property(S): SnmpTrapPort.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 162
    Property(S): DirectionIn.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 0
    Property(S): DirectionOut.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 1
    Property(S): SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76 = C:\Windows\SysWOW64\
    Property(S): System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76 = C:\Windows\system32\
    Property(S): ADVISOR_UPLOADFREQUENCY_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #1
    Property(S): ADVISOR_UPLOADDAY_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #-1
    Property(S): ADVISOR_UPLOADTIMEHOUR_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #-1
    Property(S): ADVISOR_UPLOADTIMEMIN_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #-1
    Property(S): ADVISOR_MAXCACHESIZE_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #1024
    Property(S): ADVISOR_MAXMAILBOXSIZE_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #1024
    Property(S): ADVISOR_ARCHIVEPERIOD_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #5
    Property(S): ADVISOR_LOGLEVEL_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #3
    Property(S): ADVISOR_NEEDMPINITIALIZE_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #1
    Property(S): ADVISOR_LYNC_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #0
    Property(S): ADVISOR_SHAREPOINT_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #0
    Property(S): MsiLogFileLocation = C:\Users\scomaction\AppData\Local\SCOM\Logs\OMServer.log
    Property(S): PackageCode = {58EFE971-58C1-4DBD-A400-A7607A745475}
    Property(S): ProductState = -1
    Property(S): PackagecodeChanging = 1
    Property(S): REBOOT = ReallySuppress
    Property(S): CURRENTDIRECTORY = C:\Users\scomaction\AppData\Local\SCOM\Setup
    Property(S): CLIENTUILEVEL = 3
    Property(S): MSICLIENTUSESEXTERNALUI = 1
    Property(S): CLIENTPROCESSID = 4472
    Property(S): MsiSystemRebootPending = 1
    Property(S): VersionDatabase = 300
    Property(S): VersionMsi = 5.00
    Property(S): VersionNT64 = 602
    Property(S): WindowsBuild = 9200
    Property(S): ServicePackLevel = 0
    Property(S): ServicePackLevelMinor = 0
    Property(S): MsiNTProductType = 3
    Property(S): WindowsFolder = C:\Windows\
    Property(S): WindowsVolume = C:\
    Property(S): System64Folder = C:\Windows\system32\
    Property(S): SystemFolder = C:\Windows\SysWOW64\
    Property(S): RemoteAdminTS = 1
    Property(S): TempFolder = C:\Users\SCOMAC~1\AppData\Local\Temp\
    Property(S): ProgramFilesFolder = C:\Program Files (x86)\
    Property(S): CommonFilesFolder = C:\Program Files (x86)\Common Files\
    Property(S): AppDataFolder = C:\Users\scomaction\AppData\Roaming\
    Property(S): FavoritesFolder = C:\Users\scomaction\Favorites\
    Property(S): NetHoodFolder = C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Network Shortcuts\
    Property(S): PersonalFolder = C:\Users\scomaction\Documents\
    Property(S): PrintHoodFolder = C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Printer Shortcuts\
    Property(S): RecentFolder = C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Recent\
    Property(S): SendToFolder = C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\SendTo\
    Property(S): TemplateFolder = C:\ProgramData\Microsoft\Windows\Templates\
    Property(S): CommonAppDataFolder = C:\ProgramData\
    Property(S): LocalAppDataFolder = C:\Users\scomaction\AppData\Local\
    Property(S): MyPicturesFolder = C:\Users\scomaction\Pictures\
    Property(S): AdminToolsFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\
    Property(S): StartupFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\
    Property(S): ProgramMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
    Property(S): StartMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\
    Property(S): DesktopFolder = C:\Users\Public\Desktop\
    Property(S): FontsFolder = C:\Windows\Fonts\
    Property(S): GPTSupport = 1
    Property(S): OLEAdvtSupport = 1
    Property(S): ShellAdvtSupport = 1
    Property(S): MsiAMD64 = 6
    Property(S): Msix64 = 6
    Property(S): Intel = 6
    Property(S): PhysicalMemory = 8192
    Property(S): VirtualMemory = 7854
    Property(S): AdminUser = 1
    Property(S): MsiTrueAdminUser = 1
    Property(S): LogonUser = scomaction
    Property(S): UserSID = S-1-5-21-607126847-70518424-489426498-210484
    Property(S): UserLanguageID = 2057
    Property(S): ComputerName = SCOMMS1-VM
    Property(S): SystemLanguageID = 2057
    Property(S): ScreenX = 1024
    Property(S): ScreenY = 768
    Property(S): CaptionHeight = 23
    Property(S): BorderTop = 1
    Property(S): BorderSide = 1
    Property(S): TextHeight = 16
    Property(S): TextInternalLeading = 3
    Property(S): ColorBits = 32
    Property(S): TTCSupport = 1
    Property(S): Time = 10:21:27
    Property(S): Date = 22/01/2014
    Property(S): MsiNetAssemblySupport = 4.0.30319.17929
    Property(S): MsiWin32AssemblySupport = 6.2.9200.16384
    Property(S): RedirectedDllSupport = 2
    Property(S): MsiRunningElevated = 1
    Property(S): USERNAME = Windows User
    Property(S): DATABASE = C:\Windows\Installer\4b8344.msi
    Property(S): OriginalDatabase = F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
    Property(S): UILevel = 2
    Property(S): ACTION = INSTALL
    MSI (s) (D4:A0) [10:21:27:697]: Note: 1: 1708
    MSI (s) (D4:A0) [10:21:27:698]: Product: System Center Operations Manager 2012 Server -- Installation operation failed.
    MSI (s) (D4:A0) [10:21:27:698]: Windows Installer installed the product. Product Name: System Center Operations Manager 2012 Server. Product Version: 7.1.10226.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
    MSI (s) (D4:A0) [10:21:27:744]: Deferring clean up of packages/files, if any exist
    MSI (s) (D4:A0) [10:21:27:744]: MainEngineThread is returning 1603
    MSI (s) (D4:30) [10:21:27:744]: No System Restore sequence number for this installation.
    === Logging stopped: 22/01/2014 10:21:27 ===
    MSI (s) (D4:30) [10:21:27:746]: User policy value 'DisableRollback' is 0
    MSI (s) (D4:30) [10:21:27:746]: Machine policy value 'DisableRollback' is 0
    MSI (s) (D4:30) [10:21:27:746]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (D4:30) [10:21:27:746]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (D4:30) [10:21:27:746]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (D4:30) [10:21:27:746]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
    MSI (s) (D4:30) [10:21:27:747]: Destroying RemoteAPI object.
    MSI (s) (D4:B0) [10:21:27:747]: Custom Action Manager thread ending.
    MSI (c) (78:34) [10:21:27:748]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
    MSI (c) (78:34) [10:21:27:749]: MainEngineThread is returning 1603
    === Verbose logging stopped: 22/01/2014 10:21:27 ===
    Any assistance anyone can provide will be greatly appreciated.

    Verify from permission of user that you use it in upgrade, make sure that scom machine and user that you use it in upgrade in sysadmin group in database of operationsManager and OperationsManagerDW
    Also Verify from Prerequisites of Upgrade SCOM 2012 sp1 as below link
    http://technet.microsoft.com/en-us/library/jj656654.aspx
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"

  • Operations Manager 2007 R2 Failed RMS Promotion

    Forum,
    I am moving our RMS to a 64-bit computer in preparation to upgrade to Operations Manager 2012. I have followed the directions found in the How to Promote a Root Management Server and it seemed successful. After reviewing the event logs, I have found repeating
    21042 and 29106 events. There appears be a problem with my Secure Storage Key. I have tried creating a new key but that doesn't help. I have tried reinstalling my RMS server but I always end up at the same place. The agents are getting the 20070 error and
    are unable to communicate with the server. Is there a way to rebuild the secure storage key?
    RMS OS - Windows 2012R2
    RMS - Ops Manager 2007R2 CU7
    21042 Event
    Operations Manager has discarded 1 items in management group LCC, which came from $$ROOT$$.  These items have been discarded because no valid route exists at this time.  This can happen when new devices are added to the topology but the complete
    topology has not been distributed yet.  The discarded items will be regenerated.
    29106 Event
    The request to synchronize state for OpsMgr Health Service identified by "00745302-047f-944b-0542-544eb4314c22" failed due to the following exception "System.Security.Cryptography.CryptographicException: Error occurred during a cryptographic
    operation.
    Server stack trace:
       at Microsoft.EnterpriseManagement.Mom.Internal.AesNativeTransform.DepadBlock(Byte[] block, Int32 offset, Int32 count)
       at Microsoft.EnterpriseManagement.Mom.Internal.AesNativeTransform.TransformFinalBlock(Byte[] inputBuffer, Int32 inputOffset, Int32 inputCount)
       at Microsoft.EnterpriseManagement.Security.SecureStorageManager.Decrypt(Byte[] value)
       at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.CredentialDocumentHelper.CreateCredentialSectionsForGivenCredentialType(XmlWriter& writer, Result dbRow)
       at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.CredentialDocumentHelper.InsertCredentialInfo(XmlWriter& writer, ReadOnlyCollection`1 requestedGuids, List`1 dbList, TypeOfCredentialDocumentElement elementType)
       at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.CredentialDocumentHelper.GenerateCredentialAndCredentialReferenceDocument()
       at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.RootConnectorMethods.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1
    modifiedSecureStorageReferences, ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
       at Microsoft.EnterpriseManagement.Mom.Sdk.Service.SDKReceiver.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1 modifiedSecureStorageReferences,
    ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
       at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
    Exception rethrown at [0]:
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.EnterpriseManagement.Mom.Internal.ISdkService.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1 modifiedSecureStorageReferences,
    ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
       at Microsoft.Mom.ConfigService.Networking.ConnectionFactory.Connection.Sender.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1
    modifiedSecureStorageReferences, ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
       at Microsoft.Mom.ConfigService.Networking.ConnectionFactory.Connection.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1 modifiedSecureStorageReferences,
    ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
       at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ResponseWriter.SecureDataWriter.Write(StateSyncResponseMessage response)
       at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ResponseWriter.WriteState(StateSyncResponseMessage response)
       at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ResponseWriter.Write(StateSyncResponseMessage response)
       at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ResponseWriter.Write(StateContext stateContext, ConfigurationItems configurationItems, StateSyncResponseMessage response, IConnection connection)
       at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.CreateResponse(Managers managers)
       at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.Managers.Synchronize(OnDoSynchronizedWork onDoSynchronizedWork)
       at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.Execute(Managers managers)
       at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.Run(Guid source, String cookie, Managers managers, IConfigurationDataAccessor dataAccessor, Stream stream, IConnection connection)".
    Agent Event Error 20070
    The OpsMgr Connector connected to RMS ServerName, but the connection was closed immediately after authentication occurred.  The most likely cause of this error is that the agent is not authorized to communicate with the server, or the server
    has not received configuration.  Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect.
    Thanks,
    Warren

    Hi Warren,
    May be it helps you:
    http://blogs.technet.com/b/kevinholman/archive/2009/11/10/29106-event-on-rms-index-was-out-of-range-wait-what.aspx
    http://scug.be/christopher/2012/08/31/scom-2007-r2-configuration-not-loaded/
    http://anandthearchitect.com/2009/12/02/scom-2007-r2-%E2%80%93-rms-server-not-seeing-the-agents-or-agents-are-not-talking-to-the-server/
    Natalya

  • SCOM 2012R2 - Alerts Not Generating, Must Restart SCOM to Resolve

    Hi TechNet,
    I am having an issue with my SCOM 2012R2 where the system goes into a state where alerts are not generated.  We start to see events like the one below leading up to the point where this happens. This is resolved by restarting our SCOM MS. Is there another
    solution besides having to restart our SCOM MS every day?
    A Bind Data Source in Management Group has posted items to the workflow, but has not received a response in 36720 seconds.  This indicates a performance or functional problem with the workflow.
    Workflow Id : Microsoft.SystemCenter.CollectPerformanceData
    Instance    : SCOM01.xxxxx.LOCAL
    Instance Id : {1189BAF9-AFDC-ADA0-196D-D749A369A350}
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
    <Provider Name="HealthService" />
    <EventID Qualifiers="32768">2115</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-02-02T11:28:11.000000000Z" />
    <EventRecordID>2683831</EventRecordID>
    <Channel>Operations Manager</Channel>
    <Computer>SCOM01.xxxxx.LOCAL</Computer>
    <Security />
    </System>
    - <EventData>
    <Data>Concerto Systems Management</Data>
    <Data>Microsoft.SystemCenter.CollectAlerts</Data>
    <Data>SCOM01.xxxxx.LOCAL</Data>
    <Data>{1189BAF9-AFDC-ADA0-196D-D749A369A350}</Data>
    <Data>37320</Data>
    </EventData>
    </Event>

    Hi,
    Please refer to the Kevin's reply in the thread below:
    https://social.technet.microsoft.com/forums/systemcenter/en-US/f88bf528-d896-495f-ada2-abfda37e634e/a-bind-data-source-in-management-group-xyx-has-posted-items-to-the-workflow-but-has-not-received-a
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • SCOM 2012R2 – Issues with Chained Gateways

    We recently migrated from our SCOM 2012 SP1 to 2012R2.  In both versions of SCOM, we have set up designated chained gateway servers, whose sole purpose is to communicate between untrusted forests and the RMS.  It goes as follows:  Untrusted
    Forest (AD Server) -> Chained SCOM Gateway -> RMS.  For example, ACLOUD -> SCOMGW01 -> SCOM01 
    We recently added new site and duplicated the gateway installation process from our current site to our new site.  From the example above, rather than reporting upstream to the chained site gateway (SCOMGW01), ACLOUD
    attempts to reach RMS server directly (SCOM01), which it has no route to resulting to the error event below:
    “The OpsMgr Connector could not connect to [RMS Server]:5723.  The error code is 10061L (No connection could be made because the target machine actively refused it).”

    That was a great post, thanks!  Unfortunately, because we are using 2012 R2 and no longer 2012, I saw some noticeable differences in the cmdlets.  All else equal, I think this is the part of our script that is the issue.  Because this exact
    same part worked with our 2012 configurations.  Do you see anything here that may be the problem, or anything new/replaced for 2012 R2?
    $CAName = "CA01.xxxxx.LOCAL\xxxxx-ROOTCA"
    $SCOMApprovalToolPath = "C:\Program Files\Microsoft System Center 2012 R2\Operations               Manager\Server\Microsoft.EnterpriseManagement.GatewayApprovalTool.exe"
    $SCOMGatewayInstallFilesPath = "C:\SCOMGatewayInstallationFiles"
    $SCOMDefaultManagementServer = "SCOMGW01.xxxxx.LOCAL"
    $SCOMFailoverServer = ”SCOMGW02.xxxxx.LOCAL”
    Our management server (RMS) is SCOM01.xxxxx.local (xxxxx changed, of course) with SCOM02.xxxxx.local as the failover MS.  SCOMGW01 & SCOMGW02 are our chained gateways.

  • Team Foundation Server 2010 and System Center 2012 SP1 Operations Manager WorkItem Synchronization fail

    Hello,
    We are currently implementing a Devops solution with SCOM 2012 SP1 and TFS 2010 SP1 and we would like to synchronize APM alerts with TFS and the Operational Issue WorkItem. However we are not
    able to sync anything.
    Here is our environments :
    Products :
    SCOM
    System Center Operations Manager 2012 SP1
    French
    OS: Windows 2012 SP1 Std x64
    French
    DB: SCOM SQL Server 2012 SP1 x64
    Management Pack
    MP Operations Manager TFS Work Item Synchronisation 7.0.9538.0
    MP Alert Attachement 7.0.9538.0 (We have also try the version in the VM DEVOPSALL : 7.0.9538.1005)
    TFS
    Team Foundation Server 2010 SP1
    French 10.0.40219.1
    OS: Windows 2008 R2 SP1 Std x64
    French
    DB: TFS SQL Server 2008 x64
    TFS 2012 Object Model Installer (We have also try the version 2010)
    Here is our configuration :
    TFS Platform                                                                                                                              
    This a French platform with a project based on the Process Template SCRUM 1.0 alone in a Team Project collection. The Operational Issue import completed successfully. It’s possible to manipulate
    Operational Issue for all of its states from TFS.
    SCOM Platform
    We followed the documentation at :
    http://technet.microsoft.com/en-us/library/jj883936.aspx
    to configure SCOM Alert Attachment and Operation Manager Tfs Work Item Synchronization. Everything seems to be ok. All configurations succeed. We did not configure Intellitrace collector.
    The problem occurs when we are trying to push an APM alert to TFS. When we assigned an alert to the Engineering nothing is synchronized in TFS. There is no error in the event viewer on the TFS
    server. But, on the SCOM server we get 2 exceptions raised by  Microsoft.EnterpriseManagement.Modules.Apm.TfsWISync.OMModules. We provide you the log of the SCOM Server in this mail.
    Detailed exceptions :
    Exception message are in French. In English it could be : OEF expected. The followed elements are not closed : Source, Link.
    Microsoft.SystemCenter.TfsWISync.SyncAttachments.Rule
    TFS Work Item Synchronisation ServerName
    {EC924637-2725-7C94-8F37-013B657F4530}
    Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.OMModules.ReadOpenAlertsModule
    System.Xml.XmlException: Fin de fichier inattendue. Les éléments suivants ne sont pas fermés : Source, Link. Ligne 1, position 65537.
       à System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
       à System.Xml.XmlTextReaderImpl.ParseElementContent()
       à System.Xml.XmlReader.ReadString()
       à System.Xml.XmlReader.ReadElementString(String name)
       à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.Common.DataItems.Links.DeserializeInternal(XmlReader reader)
       à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.Common.DataItems.Links.Deserialize(String mappings)
       à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.OMModules.ReadOpenAlertsModule.InitializeConfiguration(XmlReader reader)
       à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.OMModules.ReadOpenAlertsModule..ctor(ModuleHost`1 moduleHost, XmlReader configurationReader, Byte[] previousState)
    Microsoft.SystemCenter.TfsWISync.SyncWorkItems.Rule
    TFS Work Item Synchronisation ServerName
    {EC924637-2725-7C94-8F37-013B657F4530}
    Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.OMModules.ReadAlertsSyncModule
    System.Xml.XmlException: Fin de fichier inattendue. Les éléments suivants ne sont pas fermés : Source, Link. Ligne 1, position 65537.
       à System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
       à System.Xml.XmlTextReaderImpl.ParseElementContent()
       à System.Xml.XmlReader.ReadString()
       à System.Xml.XmlReader.ReadElementString(String name)
       à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.Common.DataItems.Links.DeserializeInternal(XmlReader reader)
       à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.Common.DataItems.Links.Deserialize(String mappings)
       à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.OMModules.ReadAlertsSyncModule.InitializeConfiguration(XmlReader reader)
       à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.OMModules.ReadAlertsSyncModule..ctor(ModuleHost`1 moduleHost, XmlReader configurationReader, Byte[] previousState)
    According to you, is there a possible incompatibility of the synchronization system with French environments?
    Thanks for your  help.
    Gregory OTT => http://twitter.com/gregory_ott
    ALM Engineer at Tekigo => www.tekigo.com

    Hi,
    To monitor the complete TFS infrastructure, you need additional monitoring packs that alert you about a wide range of problems with TFS components. When you import the TFS Work Item Synchronization management pack, it is a best practice to
    also import and configure these monitoring packs, you can double check these:
    Monitoring Integration between Operations Manager and TFS in System Center 2012 SP1
    http://technet.microsoft.com/en-us/library/jj899893.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.

Maybe you are looking for