{"id":474,"date":"2013-04-15T15:21:02","date_gmt":"2013-04-15T19:21:02","guid":{"rendered":"http:\/\/rajdude.com\/blog\/?p=474"},"modified":"2013-06-10T13:39:38","modified_gmt":"2013-06-10T17:39:38","slug":"getting-started-with-scvmm-2012","status":"publish","type":"post","link":"https:\/\/rajdude.com\/blog\/getting-started-with-scvmm-2012\/","title":{"rendered":"Getting Started with SCVMM 2012"},"content":{"rendered":"

After I installed SCVMM<\/a> I wanted to get up and running quickly. At that time I wrote this document. However after using VMM for a few months I fouund what I did wrong. I re-installed VMM and now I have updated this document to reflect the changed.<\/p>\n

Here are the updated steps:<\/p>\n

    \n
  1. Start SC VMM manager on the VMM server (At least once start the VMM manager on the VMM server, later on you can install and use it from your own Workstation.)\n
  2. Authenticate to the localhost using the admin account (I was already logged on using an admin account so I chose the option \u2013 \u201cUse current\u2026)\n
  3. On the lower left corner, click on \u201cSettings\u201d.\n
  4. On the left side, expand \u201csecurity\u201d and click on the \u201cRun As Accounts\u201d.\n
  5. On the ribbon at the top, click on \u201cCreate Run As Account\u201d button.\n
  6. Create a new account called \u201cHost Admin\u201d and give it the credentials of the AD account we created earlier \u2013 \u201cSCVMM Admin\u201d. More info about why this account is needed is here.<\/a>\n
  7. Now that you  have a run as account in VMM, you will use it to add Hyper-V hosts to VMM.\n
  8. Click on \u201cFabric\u201d on the lower left side.\n
  9. Click on the big green plus sign called \u201cAdd Resources\u201d on the top left corner and choose \u201cHyper-V hosts and Clusters\u201d.<\/li>\n<\/ol>\n

    Note: The next screen has some very interesting options. The last one is very, very interesting:<\/p>\n

    \"VMM1\"<\/a><\/p>\n

      \n
    1. At this point, I will just choose the first option and go with it.\n
    2. On the next page, choose \u201cUse and existing Run As Account\u201d and click \u201cBrowse\u201d.\n
    3. Choose the \u201cHost admin\u201d account and click OK\n
    4. On the next page I specified an AD query to search for all my hyper-v hosts. I just used a wildcard because all my hyper-v hosts are named similarly.\n
    5. It found all my 4 Hyper-V hosts including the Hyper-V cluster I had setup separately.\n
    6. I selected all hosts and the cluster and clicked \u201cnext\u201d.\n
    7. On the next screen I checked the checkbox \u201cReassociate this host\u2026\u201d because I  had been using these hosts with another VMM server earlier.\n
    8. I added two VM placement paths<\/li>\n
        \n
      1. C:\\ClusterStorage\\Volume2 (for a CSV on SAN)\n
      2. D:\\Hyper-V (for local disk array on the HV nodes)<\/li>\n<\/ol>\n
      3. On the next screen I turned on the incoming\/outgoing live migrations.\n
      4. Since my servers are already configured to  use Kerberos, I checked that radio button.\n
      5. I set the Cluster heartbeat network to be used for live migrations \u2013 10.10.10.0\/24\n
      6. Click next and it shows a confirmation page of what it is going to do next.\n
      7. Click finish and it shows the jobs page.\n
      8. I got a few failures\u2026all of them were saying that the hosts have an unsupported version of VMM agent. I uninstalled the old VMM agent software on the host servers and tried the operation again.\n
      9. I went to \u201cVMs and Services\u201d on the left side and noticed that my cluster was there but the nodes under were in a pending state. I removed the cluster from VMM and tried re-adding the hosts and clusters and described above.\n
      10. At this point the add succeeded.\n
      11. Sweet!<\/li>\n<\/ol>\n

        Notes from the install I did earlier:<\/strong><\/p>\n

          \n
        1. It takes a minute or two for the jobs to finish. I think it installs an agent on each hyper-v host.\n
        2. I got a warning for each machine, telling me that a restart is required because \u201cthe server needs to complete claiming of multi-path I\/O devices\u201d. I did that later.\n
        3. I closed the jobs window and now I see all three hyper-v hosts and my VMM server in the managed computers list.\n
        4. Click on \u201cVMs and Services\u201d and I see all my Hosts and the VMs running on those hosts.\n
        5. The console provides a lot of options for managing these VMs and hosts from within one application. Sweet!<\/li>\n<\/ol>\n

          More, detailed information on Administering SCVMM 2012 is here.<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

          After I installed SCVMM I wanted to get up and running quickly. At that time I wrote this document. However after using VMM for a few months I fouund what I did wrong. I re-installed VMM and now I have updated this document to reflect the changed. Here are the updated steps: Start SC VMM manager on the VMM server (At least once start the VMM manager on the VMM server, later on you can install and use it from your own Workstation.) Authenticate to the localhost using the admin account (I was already logged on using an admin account so I chose the option \u2013 \u201cUse current\u2026) On the lower left corner, click on \u201cSettings\u201d. On the left side, expand \u201csecurity\u201d and click on the \u201cRun As Accounts\u201d. On the ribbon at the top, click on \u201cCreate Run As Account\u201d button. Create a new account called \u201cHost Admin\u201d and give it the credentials of the AD account we created earlier \u2013 \u201cSCVMM Admin\u201d. More info about why this account is needed is here. Now that you  have a run as account in VMM, you will use it to add Hyper-V hosts to VMM. Click on \u201cFabric\u201d on the lower left side. Click on the big green plus sign called \u201cAdd Resources\u201d on the top left corner and choose \u201cHyper-V hosts and Clusters\u201d. Note: The next screen has some very interesting options. The last one is very, very interesting: At this point, I will just choose the first option and go with it. On the next page, choose \u201cUse and existing Run As Account\u201d and click \u201cBrowse\u201d. Choose the \u201cHost admin\u201d account and click OK On the next page I specified an AD query to search for all my hyper-v hosts. I just used a wildcard because all my hyper-v hosts are named similarly. It found all my 4 Hyper-V hosts including the Hyper-V cluster I had setup separately. I selected all hosts and the cluster and clicked \u201cnext\u201d. On the next screen I checked the checkbox \u201cReassociate this host\u2026\u201d because I  had been using these hosts with another VMM server earlier. I added two VM placement paths C:\\ClusterStorage\\Volume2 (for a CSV on SAN) D:\\Hyper-V (for local disk array on the HV nodes) On the next screen I turned on the incoming\/outgoing live migrations. Since my servers are already configured to  use Kerberos, I checked that radio button. I set the Cluster heartbeat network to be used for live migrations \u2013 10.10.10.0\/24 Click next and it shows a confirmation page of what it is going to do next. Click finish and it shows the jobs page. I got a few failures\u2026all of them were saying that the hosts have an unsupported version of VMM agent. I uninstalled the old VMM agent software on the host servers and tried the operation again. I went to \u201cVMs and Services\u201d on the left side and noticed that my cluster was there but the nodes under were in a pending state. I removed the cluster from VMM and tried re-adding the hosts and clusters and described above. At this point the add succeeded. Sweet! Notes from the install I did earlier: It takes a minute or two for the jobs to finish. I think it installs an agent on each hyper-v host. I got a warning for each machine, telling me that a restart is required because \u201cthe server needs to complete claiming of multi-path I\/O devices\u201d. I did that later. I closed the jobs window and now I see all three hyper-v hosts and my VMM server in the managed computers list. Click on \u201cVMs and Services\u201d and I see all my Hosts and the VMs running on those hosts. The console provides a lot of options for managing these VMs and hosts from within one application. Sweet! More, detailed information on Administering SCVMM 2012 is here.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[73],"class_list":["post-474","post","type-post","status-publish","format-standard","hentry","category-itsys","tag-scvmm-2012"],"_links":{"self":[{"href":"https:\/\/rajdude.com\/blog\/wp-json\/wp\/v2\/posts\/474","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rajdude.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rajdude.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rajdude.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rajdude.com\/blog\/wp-json\/wp\/v2\/comments?post=474"}],"version-history":[{"count":2,"href":"https:\/\/rajdude.com\/blog\/wp-json\/wp\/v2\/posts\/474\/revisions"}],"predecessor-version":[{"id":547,"href":"https:\/\/rajdude.com\/blog\/wp-json\/wp\/v2\/posts\/474\/revisions\/547"}],"wp:attachment":[{"href":"https:\/\/rajdude.com\/blog\/wp-json\/wp\/v2\/media?parent=474"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rajdude.com\/blog\/wp-json\/wp\/v2\/categories?post=474"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rajdude.com\/blog\/wp-json\/wp\/v2\/tags?post=474"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}