none
Cannot delete agents on cluster nodes RRS feed

  • Question

  • Help!  We've decommissioned an Exchange cluster.  The physical nodes have been turned off and I'm now trying to delte them from SCOM.  When I try to delete the agents from "Agent Managed" view I get the message:

    "Agent is managing other devices and cannot be uninstalled.  Plese resolve this issue via Agentless Managed view in Administration prior to attempting uninstall again."

    If I try to delete the virtual nodes from the "Agenless Managed" view, nothing happens.  How do I delete these??
    Friday, July 24, 2009 7:15 PM

Answers

  • Hi Dean

    The official answer was given by Anders - that is an official KB Article that says it can't be done. And it is correct - from the GUI (supported) it can't be done.

    The hack that Marius mentions and I give the full url to above has worked for me but as ever, use at your own risk.

    A PSS call is always good for reassurance but they will just point you back at the official response:
    http://technet.microsoft.com/en-us/library/dd827187.aspx

    Trying to change "act as proxy" will have no effect. I am not defending the official answer but at the moment that is the way it is. Please feel free to add this to the connect site so that we can all get it fixed.

    It is important to follow a process to decommission servers with OpsMgr agents.

    Cheers

    Graham



    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
    • Proposed as answer by Dan Rogers Wednesday, October 14, 2009 4:11 PM
    • Marked as answer by Vineet Kulkarni Friday, October 23, 2009 9:14 PM
    Wednesday, October 14, 2009 6:26 AM
    Moderator

All replies

  • Are you running R2? I found this http://technet.microsoft.com/en-us/library/dd827187.aspx 

    You cannot uninstall or delete an agent from a node in a cluster

    When you try to uninstall or delete an agent from a node in cluster, the following error message is displayed:

    Agent is managing other devices and cannot be uninstalled. Please resolve this issue via Agentless managed view in Administration prior to attempting uninstall again.

    Notice that the agent can be uninstalled from the node that is agentlessly managing the virtual servers. However, the agent cannot be uninstalled from the node that is managing the virtual servers.

    Workaround: None at this time.


    Anders Bengtsson | Microsoft MVP - Operations Manager | http://www.contoso.se
    • Marked as answer by Rob KuehfusModerator Sunday, July 26, 2009 10:53 PM
    • Unmarked as answer by Bubslg Monday, October 5, 2009 9:20 PM
    Friday, July 24, 2009 7:54 PM
    Moderator
  • Yeah, I think I saw that as well.  THere's got to be a way to get rid of them?????  I don't like having dead agents sitting sround in my console :(.
    Friday, July 24, 2009 8:20 PM
  • You might want to check http://ops-mgr.spaces.live.com/blog/cns!3D3B8489FCAA9B51!163.entry or http://www.techlog.org/archive/2008/07/29/stale_computer_objects_in_oper , I am not sure if there is any supported way of doing this as "Workaround: None at this time" is noted in  http://technet.microsoft.com/en-us/library/dd827187.aspx.
    Sunday, July 26, 2009 3:02 PM
  • I think the one at techlog is when you delete a agent under the administrator workspace, but the computer is still under the monitoring workspace. You can mark it as deleted in the database, but editing directly in the database is not supported I belive.
    Anders Bengtsson | Microsoft MVP - Operations Manager | http://www.contoso.se
    Sunday, July 26, 2009 3:23 PM
    Moderator
  • only way to get rid of it is thru direct access to DB which will nullify your warranty. If you can create similar cluster environment again, then proper steps are:

    How to decommission a cluster monitored by System Center Operations Manager 2007

    Introduction

    This article describes the steps necessary to stop monitoring a cluster that will be decommissioned and is currently being monitored with System Center Operations Manager 2007.

    More Information

    In order to remove monitoring of the cluster, perform the following steps

    1.       Remove the Operations Manager agent from all nodes of the cluster being decommissioned

    2.       Ensure that all the cluster nodes (including the virtual cluster nodes) are no longer visible in the Operations Manager console by checking the Agent Managed  and Agentless Managed views under the Administration section of the Operations Manager console.

    3.       Proceed with decommissioning the cluster

     

    Applies to

    Microsoft System Center Operations Manager 2007 RTM, SP1 and R2 editions

     
    now one of the guys here did this, but again, this is not supported

    Used this article http://ops-mgr.spaces.live.com/blog/cns!3D3B8489FCAA9B51!163.entry and only did step 3

     

    UPDATE dbo.[BasemanagedEntity]

    SET IsDeleted = 1

    where BaseManagedEntityID=’<# from event log here>’  

     

     


    Marius Sutara
    My MSDN blog

    This posting is provided "AS IS" with no warranties, and confers no rights. Use of attachments are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
    Monday, July 27, 2009 9:19 PM
    Moderator
  • Hello,

    "Remove the Operations Manager agent from all nodes of the cluster being decommissioned"
    Is it through Add/remove Program or by another method?

    Thanks,
    Dom

    Altiris Support / System Center Configuration Manager Support
    Tuesday, September 22, 2009 10:11 PM
  • I have the same question as Felyjos.  If you're unable to uninstall an cluster node agent from the console, http://technet.microsoft.com/en-us/library/dd827187.aspx, how are you supposed to validate step 2 in Marius' post? 

    2. Ensure that all the cluster nodes (including the virtual cluster nodes) are no longer visible in the Operations Manager console by checking the Agent Managed  and Agentless Managed views under the Administration section of the Operations Manager console.

    Uninstalling an agent from add/remove programs will not remove it from the SCOM console, correct?
    Wednesday, September 23, 2009 3:39 PM
  • Bubslg, it seems multiple answers have been unmarked. Any update on if or how you  resolved this?
    Pete Zerger, MVP-OpsMgr and SCE | http://www.systemcentercentral.com
    Monday, October 12, 2009 5:45 PM
    Moderator
  • If the cluster has decommissioned (as was stated in the original post) then the 2 correct answers are:

    a) Anders - it can't be done (well, at least not in a supported way)

    b) Marius - using the blog link supplied (which isn't supported but does work - I have had to do it on a customer site where they decommissioned the cluster without following the proper process). Close your eyes, clench your buttocks and pray ... works everytime (at your own risk) ;-)
    http://ops-mgr.spaces.live.com/blog/cns!3D3B8489FCAA9B51!163.entry

    Cheers

    Graham
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
    Monday, October 12, 2009 5:54 PM
    Moderator
  • Most of the proposed answers don't answer the original question "How do I get rid of previously decommisioned cluster nodes from SCOM?".  The only proposed answer that might actually be an answer is the one mentioning hacking the DB.  I haven't been able to confirm that one yet, haven't had time.  I want to run this problem through PSS and see what the "Official" answer is.

    Dean
    Tuesday, October 13, 2009 9:46 PM
  • i have not seen the error that you mention but what if you uncheck the "act as a proxy" option before deleting the agent?

    Best Regards,



    MCSE + Security, TS Exchange 2007, TS SCOM 2007
    Wednesday, October 14, 2009 4:10 AM
  • Hi Dean

    The official answer was given by Anders - that is an official KB Article that says it can't be done. And it is correct - from the GUI (supported) it can't be done.

    The hack that Marius mentions and I give the full url to above has worked for me but as ever, use at your own risk.

    A PSS call is always good for reassurance but they will just point you back at the official response:
    http://technet.microsoft.com/en-us/library/dd827187.aspx

    Trying to change "act as proxy" will have no effect. I am not defending the official answer but at the moment that is the way it is. Please feel free to add this to the connect site so that we can all get it fixed.

    It is important to follow a process to decommission servers with OpsMgr agents.

    Cheers

    Graham



    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
    • Proposed as answer by Dan Rogers Wednesday, October 14, 2009 4:11 PM
    • Marked as answer by Vineet Kulkarni Friday, October 23, 2009 9:14 PM
    Wednesday, October 14, 2009 6:26 AM
    Moderator
  • Yes, add-remove programs.
    Microsoft Corporation
    Wednesday, October 14, 2009 4:10 PM
  • Hi Bubslg and hi all, I tried to summarize cluster issues in this post http://nocentdocent.wordpress.com/2009/10/18/r2-and-cluster-monitoring-time-is-running-out/ I set a possible solution, even if it is unsupported, for your issue as well.

    - Daniele, Microsoft MVP OpsMgr This posting is provided "AS IS" with no warranties, and confers no rights. http://nocentdocent.wordpress.com http://www.progel.it
    Sunday, October 18, 2009 5:30 PM
    Moderator
  • I faced the same issue on Clustered Mailbox Servers & resolved it by:

    1- Uninstalling the agents manually from all nodes

    2- deleting the managment packs (all dependent as well)

    3- I went to Agentless Managed, and deleted the cluster resource

    4- I went to agent managed & then i successfully deleted the agents

    Wednesday, February 9, 2011 6:26 AM
  • Well, here we are 5 years later and still no real resolution to this problem, even with 2 major revisions of the software!!  What's going on M$??  I still cannot properly remove SCOM agents from cluster nodes in a clean and supported fashion in SCOM 2012!  Please Micro$oft FIX THIS PROBLEM!!!!!!
    Tuesday, March 18, 2014 5:01 PM
  • Well, here we are 5 years later and still no real resolution to this problem, even with 2 major revisions of the software!!  What's going on M$??  I still cannot properly remove SCOM agents from cluster nodes in a clean and supported fashion in SCOM 2012!  Please Micro$oft FIX THIS PROBLEM!!!!!!
    Same here. Same issue over and over. My clients server guys love it when this happens year over year.

    Brody Kilpatrick

    Friday, January 9, 2015 4:52 PM
  • Hi There,

    Correct but alternate not recommended option is to Delete it directly from the Ops DB By using the below query

    UPDATE dbo.[BasemanagedEntity]

    SET IsDeleted = 1

    where Fullname like '%SCOM Agent FQDN%


    Gautam.75801

    Saturday, January 10, 2015 4:41 PM
  • Yup.  there are all manner of "unsupported" workarounds available.  the issue here is M$ STILL have no documented procedure that THEY will support for doing this.
    Thursday, March 5, 2015 5:56 PM
  • One gotta love the fact this bug is 8 years old, acknowledged since OpsMgr 2007 and not yet resolved :-) Brilliant. 

    Thursday, June 8, 2017 9:06 AM