I recently decommissioned a Windows Server 2008 Hyper-V cluster. It was monitored by OpsMgr 2007 R2. When we shutdown the last cluster node I tried to remove both its agent object and the agentless managed cluster object from OpsMgr administration. I couldn’t. The cluster just refused to disappear. The server agent would delete because there was a remaining dependency – the cluster object which relied on it as a proxy.
It had a red state (ruining my otherwise all green status view) and, more annoyingly, many of the migrated resources (VM’s) still seemed to be linked to the old cluster despite being moved to the new cluster.
I searched and found lots of similar queries. The official line from MS is that there is no supported way to do this deletion. There is a hack but the instructions didn’t work for me – I couldn’t find the key piece of info – plus it is unsupported.
So I uninstalled the agent manually. No joy. I waited. No joy. I rebuilt the server and added it to our Windows Server 2008 R2 Hyper-V cluster. No joy. I installed the OpsMgr agent and enabled the proxy setting.
That was yesterday. This morning I logged in and the old cluster object is gone. Vamoose! I guess OpsMgr figured out that the server was now in a new cluster and everything was good.
This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.
No related posts.