We currently have SCOM 2007 R2 RTM implemented in our domian (With 1 RMS , 1 Managemnet Group , remote OpsMgrDB and DW ) . Is there any way we can Build another Managemnet group in the same domain (preferably SCOM 2007 R2 CU4 One ( Differnet managemnet group name , 1 RMS , Remote SQL for BD and DW) and then Slowly over time migrate all our agents from one old Managemnet group to the new Ones. I checked there is some concept called Multruihomed , where in an agent can simultaneously talk to 2 Managemnet Groups. Any Advise for the transition.. We will be planning it in phases .. and just have around 200 Agents ..

Hi Yes - there is no problem doing this. You can either multi-home the agents so that they communicate with both management groups during the transition or you could uninstall the agent from the old MG and then install from new MG if you don't need the agents reporting to both management groups. What you might find with muli-homing is that when you push the agent from the new managemetn group it is slow to go monitored: http://nocentdocent.wordpress.com/2009/10/09/discoveries-multihoming-and-cookdown/ Once all agents have been migrated (and you have removed them) from the old management group, you can then decommission the old SCOM RMS \ databases. Cheers GrahamView OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

We do this here; some of our agents are in our DEV and production SCOM MG's (same domain) They work just fine. On larger boxes, (SQL servers with lots of DBs/instances), the agent can get a bit bogged down, but overall, it works fine."Fear disturbs your concentration"

We do this here; some of our agents are in our DEV and production SCOM MG's (same domain) They work just fine. On larger boxes, (SQL servers with lots of DBs/instances), the agent can get a bit bogged down, but overall, it works fine."Fear disturbs your concentration"

Hi, The following thread also discussed a similar issue, please check it: http://social.technet.microsoft.com/Forums/en-IE/operationsmanagergeneral/thread/2c2b2fe3-b4da-4be4-a037-9d0648aac954Please 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.

Yep, works very well. The agent just runs two sets of rules/monitors and reports each back to the respective management server. Of course it is best to do this a limited amount of time (days and week rather than months/years) because you are running two sets of workflows and thats a waste of resources. But for migration it works perfect. Just push out the agents from the new mgmt group and start tuning your management packs. When decommisioning the old mgmt group please remember to use the uninstall task fro the old mgmt group (this will not remove the agents as they are multihomed), it will remove the mgmt group entry from the config of the agent. Otherwise you might find yourself runnig commands to remove the old mgmt group reference from all agents. Enjoy!!Bob Cornelissen - BICTT (My BICTT Blog)

Would it Matter if the new Management RMS (that is the one we will migrate to eventually) be Running SCOM 2007 R2 CU4. Our current Managemnet Group is running SCOM 2007 R2 RTM. So can we have 2 different version agents one RTM and other CU4 as multihomed.