Scom 2007 and scom 2012 agent multi home

is there version limit for the agent multihom for scom 2007 and scom 2012?
In technet i found it for SCOM upgrade it mentioned need scom 2007 CU4 and above, how about for multihome approach for SCOM agent?
Besides that, instead of agent upgrade, could we perform agent uninstallation scom 2007 and reinstall scom 2012?
Thanks for your advice.

Hi Cylim,
You can upgrade your agents to SCOM 2012 only from SCOM 2007 R2 CU4. Please look at these helpful links:
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
http://blogs.catapultsystems.com/cfuller/archive/2012/05/31/quicktricks-multi-homing-an-agent-to-opsmgr-2012-scom-sysctr.aspx
http://blogs.catapultsystems.com/cfuller/archive/2014/04/02/multihomed-migrations-in-operations-manager-lessons-from-the-field.aspx
As Scott mentioned, you can uninstall SCOM 2007 agent and install SCOM 2012 agent on one or a few servers, and see if they report properly to both management groups SCOM 2007 and SCOM 2012:
http://dynamicdatacenter.wordpress.com/2012/10/15/om-2012-agent-report-to-scom-2007-not-r2-scom-2012/
Natalya

Similar Messages

  • Difference between Scom 2007 and Scom 2012 Gateway server setup.

    Hi All,
    Greetings!!
    I would like to know the differences for gateway server setup in Scom 2007 and 2012 versions..
    Are there any changes in the data collection or in the configuration? and also the prerequisites for it.
    Please let me know these info..
    Regards,
    Gokul

    There is no great different in settng up gateway server in SCOM 2007 R2 and SCOM 2012. As summary, it requires
    1.Request certificates.
    2. Import those certificates into the target computers by using the MOMCertImport.exe tool.
    3. Distribute the Microsoft.EnterpriseManagement.GatewayApprovalTool.exe to the management server.
    4. Run the Microsoft.EnterpriseManagement.GatewayApprovalTool.exe tool to initiate communication between the management server and the gateway
    5. Install the gateway server.
    However, the prerequisites has different between SCOM 2007 R2 and SCOM 2012
    SCOM 2007 R2 gateway server support folloiwng OS
    Windows Server 2003 Standard Edition with Service Pack 1 (SP1)
    Windows Server 2003 Standard Edition with Service Pack 2 (SP2)
    Windows Server 2003 Standard x64 Edition with SP1 or SP2
    Windows Server 2003 Enterprise Edition with SP1
    Windows Server 2003 Enterprise Edition with SP2
    Windows Server 2003 Enterprise x64 Edition with SP1 or SP2
    Windows Server 2003 R2 Standard Edition with SP1 or SP2
    Windows Server 2003 R2 Standard x64 Edition with SP1 or SP2
    Windows Server 2003 R2 Enterprise Edition with SP1 or SP2
    Windows Server 2003 R2 Enterprise x64 Edition with SP1 or SP2
    Windows Server 2008 Standard 32-Bit with SP1 or SP2
    The 64-bit edition of Windows Server 2008 Standard with SP1 or SP2
    Windows Server 2008 Enterprise 32-Bit with SP1 or SP2
    The 64-bit edition of Windows Server 2008 Enterprise with SP1 or SP2
    Windows Server 2008 Datacenter 32-Bit with SP1 or SP2
    The 64-bit edition of Windows Server 2008 Datacenter with SP1 or SP2
    Windows Server 2008 R2
    Windows Server 2008 R2 with SP1
    SCOM 2007 R2 gateway server
    CPU :2.8 GHz or faster
    Memory: 2 GB of RAM or more
    available Space: 20 GB of available hard disk space
    NET Framework 2.0
    Microsoft Core XML Services (MSXML) 6.0
    SCOM 2012 Gateway server
    Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
    Server Operating System: must be Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 Core Installation or Windows Server® 2012 R2.
    Processor Architecture: must be x64.
    Windows PowerShell version: Windows PowerShell version 2.0, or Windows PowerShell version 3.0.
    Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required for the management server.
    .NET Framework 4 is required if the Gateway server manages UNIX/Linux agents or network devices.
    Roger

  • Update agent from SCoM 2007 to SCOM 2012

    Expets,
    We have SCOM 2007 R2 CU7on 1 server.
    we installed another single SCOM 2012 r2 on another server.
    when i push the agent from the SCOM 2012 to machine still monitored by SCOM 2007, the machine appear in pending management under device management under  setting
    tab
    but when i remove the SCOM 2007 manualy, there is no problem and the installing of SCOM 2012 agent done successfully
    any way to make SCOM 2012 agent automatically without remove SCOM 2007 agent ?
    Ahmad Samir | MCSE 2003 | MCTS: Exchange 2010, MCTS: Lync 2010. MCTS: SCOM 2007

    Hi,
    If SCOM 2012 and SCOM 2007 R2 belong to the same management group, then you are trying to make your agents multi-homing, and if so, just discovery them and push agent to them should work.
    Here is a similar thread, please go through it:
    http://social.technet.microsoft.com/Forums/en-US/c6d15d7f-1779-47ea-a437-bc6ab00e2f64/upgrading-scom-2007-r2-to-scom-2012?forum=operationsmanagergeneral
    And we may need to logon to one agent and check its event viwer for operation manager log for more details.
    Regards,
    Yan Li
    Regards, Yan Li

  • Group member migration from sCOM 2007 to SCOM 20012

    Hi Team,
    Could you please help us to migrate all the static and dynamic members in the SCOM 2007 group ( these group created manually ) to SCOM 2012.

    More info:
    OpsMgr Groups
    Group members via PowerShell
    Create OpsMgr Groups in PowerShell from Excel File
    OpsMgr: Listing all OpsMgr groups for which a computer is a member
    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.

  • OM 2007 and 2012 Integrated Console

    Customer have both OM 2007 R2 and 2012 R2 environment, but they don’t want two different consoles.
    We plan to customize a console to collect data from 2007 and 2012, thus customer could only check single console on daily operation.
    However, we don’t have table schema for OM 2007 and 2012, the only way to do this is through SDK?
    Or any other suggestions could meet their requirements? Thanks.

    Hi,
    Based on my research, there is a possibility to install both consoles on the same desktop / laptop machine following this post:http://scug.be/dieter/2012/07/25/scom-install-both-scom2007r2-and-scom2012-console/
    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
    Very handy if you need to monitor both scom 2007 and scom2012 environments.
    Regards,
    Yan Li
    Regards, Yan Li

  • 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

  • SCOM 2012 R2 agent with SCOM 2007 R2?

    Server: SCOM 2007 R2 (now); eventual upgrade to SCOM 2012 R2
    OS to monitor: Windows Server 2012
    I understand SCOM 2012 agents can be installed on Windows Server 2012 and report back to SCOM 2007 R2 MGs.
    I haven't been able to find documentation for or against whether SCOM 2012 R2 agents can be installed on Windows Server 2012 and can report back to SCOM 2007 R2 MGs...  Is this supported?
    I can't find anything on any specific CU level that might be required on SCOM 2007 R2 to support this.

    Hi,
    I have not found any document talking about this. The only thing I can find is SCCM 2012 r2 agent can talk with SCCM 2012 SP1.
    Juke Chou
    TechNet Community Support

  • SCVMM and SCOM 2012 Integration Issues

    Hello, I have integrated SCOM 2012 RTM and SCVMM 2012 RTM and am having lots of issues that were not present with 2007/2008 family integration.  For starters, my SCOM environment manages multiple untrusted domains, etc.  When enabling VMM integration
    I now get hundreds of alerts about "Unable to verify Run As Account", stating that is cannot login as the VMM service account for all clients that don't live in same domain as SCVMM server.  For starters why do my physical servers, and all VMs need
    to be distributed with this account?  The alert is also expected logically, because this is impossible to distribute a Run As account to every agent in a multi-domain untrusted environment.  Also according to this configuration, the Virtual
    Machine Manager Connection Account created in SCOM is set to less secure (distributed to all agents), which is why the alert is coming up; additionally less secure setting is typically bad practice.  Why does SCVMM do this by default?  Can it be
    changed?  What are options here?  It seems to me only the SCOM management server should need this Run As account, not every agent?  Thoughts on this?  Thanks!

    I'm running SCVMM 2012 R2 and OpsMgr 2012 R2.  I have the integration setup and have had the same issue with the RunAs account logging on to workgroup computers.
    I tried changing the account distribution to More secure and only targeting my two management servers and the VMM server.  I also changed the profile so that it targeted only the Windows Computer object for the same three servers.  I came in this
    morning and I do not have the "Run As Account Could Not Log On" message anymore on the workgroup computer, but now I have an alert "VMM Agent Not Monitored By Operations Manager" for the VMM server.  I look at the Health Explorer and see that the agent
    is reachable but its not being monitored.
    I tried changing the RunAs profile back to "All Targeted Objects" but monitoring still didn't restart.  Then I tried restarting the OpsMgr agent and then the VMM agent, but still the status did not change.  Now, I have just set the account back
    to Less secure and have again received the warning from the workgroup computer about not being able to log on.  I'll wait a little longer to see if the VMM server begins to be managed.
    Any experience with this?

  • SCOM 2012 Agent - Best Practices with Base Images

    I've read through the
    SCOM 2012 agent installation methods technet article, as well as how to
    install the SCOM 2012 agent via command line, but don't see any best practices in regards to how to include the SCOM 2012 agent in a base workstation image. My understanding is that the SCOM agent's unique identifier is created at the time of client installation,
    is this correct? I need to ensure that this is a supported configuration before I can recommend it. 
    If it is supported, and it does work the way I think it does, I'm trying to find out a way to strip out the unique information so that a new client GUID will be created after the machine is sysprepped, similar to how the SCCM client should be stripped of
    unique data when preparing a base image. 
    Has anyone successfully included a SCOM 2012 (or 2007 for that matter) agent in their base image?
    Thanks, 
    Joe

    Hi
    It is fine to build the agent into a base image but you then need to have a way to assign the agent to a management group. SCOM does this via AD Integration:
    http://technet.microsoft.com/en-us/library/cc950514.aspx
    http://blogs.msdn.com/b/steverac/archive/2008/03/20/opsmgr-ad-integration-how-it-works.aspx
    http://blogs.technet.com/b/jonathanalmquist/archive/2010/06/14/ad-integration-considerations.aspx
    http://thoughtsonopsmgr.blogspot.co.uk/2010/07/active-directory-ad-integration-when-to.html
    http://technet.microsoft.com/en-us/library/hh212922.aspx
    http://blogs.technet.com/b/momteam/archive/2008/01/02/understanding-how-active-directory-integration-feature-works-in-opsmgr-2007.aspx
    You have to be careful in environments with multiple forests if no trust exists.
    http://blogs.technet.com/b/smsandmom/archive/2008/05/21/opsmgr-2007-how-to-enable-ad-integration-for-an-untrusted-domain.aspx
    http://rburri.wordpress.com/2008/12/03/untrusted-ad-integration-suppress-misleading-runas-alerts/
    You might also want to consider group policy or SCCM as methods for installing agents.
    Cheers
    Graham
    Regards Graham New System Center 2012 Blog! -
    http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at
    http://systemcentersolutions.wordpress.com/

  • Does the SCOM 2012 agent "look back" in the logs before the service was started?

    Does the SCOM 2012 agent "look back" in the logs before the service was started?<o:p></o:p>
    We raised this question to our Microsoft rep back when we migrated to SCOM 2007. We wanted to know if SCOM would alert on errors generated before the Heath Service started. For example, errors
    logged before the service is started on reboot (which is when some critical errors are logged). We also wondered what happens when the service is restarted...would errors during the same window be missed?
    If I remember correctly the MS response was that the agent looks back on startup/restart based on a timestamp of some kind. We did some testing that seemed to confirm this information. I've
    recently encountered several instances of errors generated while the service was stopped (primarily during boot up) where SCOM failed to alert on the error.
    Can anyone confirm how the SCOM 2012 agent deals with errors generated before the service starts on boot and during service restarts?

    I would suspect it's with watermarks as it has been in the past.  What you should look into is if these alerts you were expecting are event based, and if there are rules set to alert for these conditions.  If so, and you don't get an alert,
    then you can bring that up with your msft rep.  However, they should be caught.
    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.
    There is a watermark. If the agent has been down for a significant period of time, the watermark may not apply, as the log would have rolled - but the entire log will still be processed regardless of what has already been discarded in the log. This may cause
    some problems if a monitor picks up an unhealthy state, and the healthy state log entry has already been flushed. In this case, you need to reset health on that particular monitor, or just flush the cache on the agent to start anew.
    Jonathan Almquist | SCOMskills, LLC (http://scomskills.com)

  • 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.

  • 'High' Priority and 'critical' severity alerts from all MP's in SCOM 2007 R2

    Hi All
    Can anyone help me with the script to get all alert details from monitors and rules which are set to "high" priority and "critical" severity in SCOM 2007.
    Regards
    Madhavi

    You can below script to show all agent which isn't health
    $ReportOutput += "<h2>Agents where Health State is not Green</h2>"
    $ReportOutput += Get-Agent |
    where {$_.HealthState -ne "Success"} |
    select Name,HealthState | ConvertTo-HTML
    -fragment$ReportOutput += "<h2>Agents where the Monitoring Class is not available</h2>"
    $AgentMonitoringClass = get-monitoringclass
    -name "Microsoft.SystemCenter.Agent"
    $ReportOutput+= Get-MonitoringObject-monitoringclass:$AgentMonitoringClass|
    where{$_.IsAvailable -eq$false} |
    selectDisplayName | ConvertTo-HTML-fragment
    Also you can refer below links
    http://www.definit.co.uk/2012/01/scom-2007-r2-daily-health-check-script/
    http://www.blackops.ca/cms/blog/?p=155
    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

  • Can overrides from SCOM 2007 R2 be used in a new SCOM 2012 R2 installation?

    Hi All,
    I'm wondering if we can "easily" use our overrides/configuration from our current SCOM 2007 R2 implementation and use them in a new SCOM
    2012 R2 environment that we plan on standing up.  We are using SCOM to monitor approx. 400 servers (physical and virtual).
    We have been using 2007 R2 for a few years and we'd like to start using 2012 R2.  Instead of using the update path (2007 R2 to 2012
    to 2012 SP1 to 2012 R2), we are planning on setting up a new 2012 R2 environment and configuring our servers to start reporting to 2012 R2 (after it has been configured in such a way as to "mimic" our 2007 R2 environment).
    Ideally, we'd like to avoid going through the upgrade path.  (We'll leave our 2007 R2 environment running so that we can still access "historical
    data" until the new 2012 R2 environment has had a chance to build up its own "historical data".)
    So ... I was thinking we could export our overrides from 2007 R2 and import them into 2012 R2, but I'd like to verify that this approach makes
    sense.  We haven't done extensive customizations to 2007 R2 in terms of Distributed Applications or Management Pack Objects (although we have made some changes - which I guess we could manually configure in 2012 R2 to offer the same "experience").
    The following are some of the Management Packs that we are using in 2007 R2:
    Microsoft Windows Active Directory
    Active Directory Certificate Services
    EMC Storage Monitoring
    IBM Hardware
    Microsoft Exchange Server 2010
    McAfee
    Microsoft Forefront Server Protection 2010
    Microsoft Office SharePoint Server 2007
    Microsoft SQL Server
    Microsoft Windows DNS Server
    Microsoft Windows WINS
    Microsoft Windows Hyper-V
    Microsoft Windows Internet Information Services
     Microsoft Windows Server
    Microsoft Windows DHCP
    NetBackup Operations Manager
    Office Communications Server
    OpsLogix (BlackBerry)
    Service Level Dashboard for OpsMgr 2007 R2
    SolarWinds Orion
    Schedule Maintenance Mode
    Team Foundation Server 2010
    Virtual Machine Manager
    Microsoft Windows Cluster
    Operations Manager 2007 R2
    I appreciate all feedback and the sharing of you expertise.
    Thanks, Joe.

    As long as the base pack works and you wish to retain the customisation then you should be ok, there’s a good article
    here which explains how to perform the migration and some of implication/things to check.
    There will be complications if you’ve stored anything in the default mp but this is explained in the above article.

  • Stopping scom 2007 & 2012

    How to completely stop Stopping scom 2007 & 2012.
    thanks 
    Mike
    Regards, Mike ||Persistent Work Triumphs||

    Hi,
    it seems, putting RMS and MS in maintenance mode is not the best choice, old article from Cameron Fuller (2011, so this should mean: SCOM 2007):
    http://www.systemcentercentral.com/so-i-accidentally-put-my-rms-into-maintenance-mode-what-do-i-do-now/
    New article on SCOM 2012:
    http://windowspowered.wordpress.com/2011/09/09/management-server-maintenance-mode-in-scom-2012/
    Excerpt: "The only thing you need to do, is make sure you never put more then 50% of your Management Servers into Maintenance Mode, because this makes your Resource Pool unusable."
    HTH, Holger (alias Marvin)
    Holger alias InternetSmurf, Munich, Germany

  • Deploying SCOM 2012 Agents to untrusted Forests/Domain

    Can we deploy SCOM 2012 agents to untrusted forest/domain? I don't want to use SCCM 2012 for installing agents via package deployment. Pls suggest.
    Regards,
    Ravi

    Yes, You can deploy SCOM Agent to untrusted domain manually and using Certificate.
    For deployment scom Agent, you can refer below links
    http://www.toolzz.com/?p=279
    http://jimmoldenhauer.blogspot.com/2012/11/scom-2012-deploying-agents-to-untrusted.html
    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 | Twitter:
    Mai Ali

Maybe you are looking for