SCOM 2012, Windows Server 2008 R2, test environment. 1) Previously there was enother management server (SCOM 2007 R2) in the AD domain. That server has died without being uninstalled properly. I've deployed SCOM 2012. Now SCOM agents on all managed servers report that they cannot contact the dead server in the dead management group. I've tried to clean registry on SCOM and managed servers, but to no luck. How could I remove traces of the old management group? 2) I cannot see the new management group in SCOM sonsole in Administration -> Conected Management Group pane. I also cannot add it using Add management group link (console throws some strange exception - "Discovery data generated by invalid connector...") Possibly the cause is cyrillic letters in group's name. What could be done? AFAIK a group's name cannot be changed after installation. Is SCOM redeploying the single way to correct it?

It appears you might have missed few steps in the clean up of SCOM 2007 infrastructure or/and in the setup of SCOM 2012 Did you uninstalled old SCOM 2007 agents before deploying SCOM 2012 agents?Are you using the same server name for SCOM 2012 as the old dead SCOM 2007 server?Did you uninstalled SCOM 2007 console and installed SCOM 2012. I suggest, it might be easier to uninstall (server/s and agents) and rebuild your SCOM 2012 from scratch.  Kind Regards Tim (Canberra)

Tim, 1) No I did not uninstalled old agents. 2) No. The servers' names are different. 3) Old server died along with SCOM console, so I did not uninstalled it. :) In fact I'm considering the full rebuild of SCOM infrasrtucture. However I'd like to exterminate all the traces of SCOM 2007 to prevent clients from future connection attempts. The question is where those SCOM traces could be found.

Regarding your 2) point in the origianl post: "I cannot see the new management group in SCOM console" SCOM management Group name is displayed in the SCOM Title bar. It won't show up in the connected Management Group Pane, this is used to link two or more SCOM management groups. To clean up SCOM 2007 after RMS is dead: 1) Uninstall SCOM 2007 agents on all servers. 2) Delete old SCOM 2007 databases. 3) Uninstall any SCOM console installed on any server, 4) Uninstall SCOM Reporting or Web Console or Management server roles (if they were installed on server other than RMS).        Kind Regards Tim (Canberra)

Hi Ideally the SCOM 2007 R2 agents would have been uninstalled from the SCOM 2007 R2 console - this information is still in every SCOM 2007 R2 agent and you will need to uninstall every agent. How many do you have? 1) Manually uninstalling each agent will be time consuming and tedious 2) Do you have something like Configuration Manager at your company so that you could create a collection based upon the existance of the SCOM agent and then look to leverage Configuration Manager to remove the SCOM agent 3) Command line: http://www.jonathancusson.com/2010/07/28/uninstall-scom-agent-the-easy-way/ http://technet.microsoft.com/en-us/library/bb381455#bkmk_TouninstalltheagentbyusingtheMOMAgentmsiagentsetupwizard There is a CleanMOM utility as well: http://blogs.technet.com/b/momteam/archive/2010/11/16/updated-momclean-reskit-tool-for-om2007r2.aspx Cheers GrahamRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Tim, Graham, Thank you a lot for information. In addition to the steps mentioned by you I'd add manual deletion of agent regustry keys (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0). Anyways I need to rebuild SCOM installation, because I tried to remove old internal connector from dead Service Manager service (manually running a stored procedure in database), and now SCOM console cannot open "Internal connectors" pane. This method was described as working for SCOM 2007, however in SCOM 2012 it seems to have fatal after-effects. Back to cleaning then...