Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 166
  • Last Modified:

How do I move 2008 R2 Cluster from VMM 2008 R2 over to Vmm 2012 R2?

We were formerly using 2008 R2 SCVMM and now must use 2012 R2 SCVMM.   Due to circumstances, the 2008R2 VMM is not longer accessible due to corrupt sid on SQL database as the result of active directory issues.  The 2008 VMM database was using a SQL 2005 express edition (32bit).  Managing this database has proven difficult. At this time we have been unable to access the 2005 database.

Our end goal is to begin managing (3) Hyper V Host in a cluster on our new 2012 VMM (r2).  However, when we try to add the cluster as a resource on the 2012 VMM Console, the host severs of the cluster remain in a "pending" status.

Any advise on how to cause the 2008 VMM to "release" the associate to the old VMM console (if that is the problem) so that they can be managed in the new 2012 VMM console?
Ken Stokes
Ken Stokes
  • 2
1 Solution
VishalnarseSystem Wintel Administrator L2Commented:

At a experience, I have been deploying a new System Center Virtual Machine Manager 2012 Sp1.

I was here and deployed their previous solution with VMM 2012 and BareMetal deploy of their hosts. They have been patching and updating the hosts with the integration of wsus in VMM. As I described in an earlier post my first intention was to upgrade the database but after some investigation and trials I decided to start fresh instead…

So with the new installation I wanted to add the old Hyper-V cluster and manage it from the VMM 2012 SP1 and also be able to do migration from the old bare metal deployed hosts and cluster to the new cluster.

After adding the 2008 r2 cluster I had two nodes that did not respond correctly and with the following error

Error 2912

I tried to restart the VMM-agent on the hosts and that did not help, also tried to reboot the servers, which did not help either.

On one node I also tried to uninstall the VMM agent on the host itself and then to get it back into VMM involved some VMM-database massage, and that did not help either.

So what did help?!

Rebuilding the performance counters as this KB2554336 describes

To rebuild all Performance counters including extensible and third-party counters, type the following commands at an Administrative command prompt. Press ENTER after each command.

Rebuilding the counters:
     cd c:\windows\system32
     lodctr /R
     cd c:\windows\sysWOW64
     lodctr /R

Resyncing the counters with Windows Management Instrumentation (WMI):

Stop and restart the Performance Logs and Alerts service.
Stop and restart the Windows Management Instrumentation service.

and then restart the VMM agent did solve the above issue and now the hosts reports nicely in VMM

The hosts had been reporting correctly in the old VMM 2012 so what caused the per counters to go bad, maybe the installation of the new VMM 2012 SP1 agent? If you have had the same issues, please let me know.
Ken StokesChief Information OfficerAuthor Commented:
We had to RESTART ALL the Host Servers, then the cluster moved over nice and easy.   The reason for this is after the 2012 Agents were installed on the Hyper V host servers, they simply needed a restart for the services to start properly.
They AGENTS never stated that a restart was necessary.   This also could have been a "side effect" of the 2008 agents that were previously installed on those Hyper V hosts.
Ken StokesChief Information OfficerAuthor Commented:
The posted solution, that I accepted as the solution, is the best answer.  There were no other answers even close to the real solution.

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now