Archive

Archive for the ‘SCVMM’ Category

vCenter 5.5 integration in SC VMM 2012 R2

June 10th, 2014 No comments

I have for a Server Lifecycle project been investigating the possibility to add a vCenter 5.5 to a System Center VMM 2012 R2 environment as we are going to use WAP, SMA, SPF and VMM.

Based on the documentation on Microsoft Technet site the support ends with vSphere 5.1. Now this customer already runs vSphere 5.5  and I wanted to quickly check if it was possible at all to connect a vCenter 5.5 to VMM 2012 R2 and manage some basic tasks on VM´s.

Screen Shot 2014-06-09 at 13.02.08

And as you can see I managed to add the vCenter Server and after adding a ESXi host the view in VMM looks like this

Screen Shot 2014-06-09 at 16.41.09

Checking it in PowerShell, I can see that it looks and reports in the same manner as the 5.1 vCenter that I have registered

Screen Shot 2014-06-09 at 21.21.58

And after some VM massage I can see that basic tasks as starting, stopping and also taking snapshots works as intented through the vCenter 5.5.

Screen Shot 2014-06-09 at 22.34.27

Of course new features introduced in vCenter 5.5 and ESXi 5.5 for the VM´s will not work and there might be other things that also can have issues, I will continue to explore and if I find anything that seems to be a showstopper I will do a followup blog post.

Categories: SCVMM, SysCtr, Virtualization, VMware Tags:

Regional Settings on your VMM 2012 R2 VM Templates

April 14th, 2014 No comments

When you created VM templates out-of-the-box in System Center Virtual Machine Manager they get the en-US regional settings for all rolled-out VM´s and that in Sweden is not always standard for the IT departments and the IT techi-guy has to configure that manually afterward. This can be altered with either PowerShell or with an unattend.xml file.

If there happens to be some templates that you have not configured with the right regional settings and keyboard layout I have a small PowerShell script that will configure this for all templates in the VMM library.

Screen Shot 2014-04-14 at 18.53.39

Check out this KB2709539 article for more information and also your specific regional codes for your country :-)

Categories: SCVMM, Virtualization Tags:

Automated PowerShell to keep your template vhd(x) IC updated

March 31st, 2014 No comments

For the Veeam Seminar I did some digging in how to check and also apply updated integrational components on virtual disks in the System Center VMM library and found Ben´s script which I altered to fit my goal. This is quite convenient based on that you can schedule it and always have updated IC´s on those VHDX in the library.

I check and get the current IC´s from one Hyper-V host and thus based on that if it has been updated I also get that update instead of using a copied IC version locally in the VMM server. The script runs on the VMM server and that is why I use the Mount-DiskImage cmdlet instead of the Mount-VHD as that does not work on a non-hyper-V enabled windows server.

Screen Shot 2014-03-30 at 10.42.33

 

 

 

Veeam webinar 19/3: Automate daunting virtualization tasks with SMA

March 5th, 2014 No comments

On wednesday the 19th of March I will together with Veeam have a web seminar with the topic:

Screen Shot 2014-03-05 at 21.54.12

Automate daunting virtualization tasks  with SMA

Now that you have set up your virtualization environment, you’ll want to automate it. In this webinar, you will learn how to do this with Service Management Automation(SMA) and how to integrate automated tasks into the Hyper-V virtualization environment. You will use different runbooks to automate some boring but necessary tasks that IT admins have to do.

This webinar will show you how to:

  • Automate patching of virtualization hosts
  • Expand virtual hard disks based on usage
  • Automatically update integrational components on VMs
  • Automatically update virtual hard disk templates
  • Clean old snapshots that have been forgotten
  • And more…

If you want to register and be part of this crazy one hour with the Swedish Chef you can do it on the following link

And guess what, It comes in a swedish version also! Check out in the following link and if you understand Swedish, register here!

Why are my Hyper-V hosts in VMM reporting “Needs Attention”?

February 27th, 2014 No comments

If you are kind of new to System Center VMM console and wondering why after a while your hosts responds “Needs Attention” and checking the host properties and seeing that everything looks green in the status, then continue and read this post!

Screen Shot 2014-02-27 at 10.18.10

Screen Shot 2014-02-27 at 12.31.28

You can just extend the console by right-click the hosts bar and add the column with “Agent Version Status” and then you can see the reason for host status,

Screen Shot 2014-02-27 at 10.23.49

The reason for this “Upgrade Avail” is that the VMM server has been updated with some new patches/updates that came with Windows Update and now you need to update your hosts to have the new agent to properly talk to the VMM Server.

That can of course be done with PowerShell if you have quite some hosts…  You can of course also get the list of which hosts that need an update,

Screen Shot 2014-02-27 at 10.41.28

And then with the following command also update the hosts that need to

Screen Shot 2014-02-27 at 10.53.23

If you are wondering why I am filtering on Agent-Version -ne “0.0″ is because in this environment there are several VMware hosts and they do not have a VMM agent but is recognised as managed hosts and appear when getting the “managed computers”

Good luck :-)

Categories: Hyper-V, Powershell, SCVMM, SysCtr, Virtualization Tags:

SCVMM 2012 R2 and deploying VM´s with altered name on vhdx

January 20th, 2014 2 comments

I observed a question on the technet forums regarding if it was possible to change name of the virtual hard disk when deploying a virtual machine or template from System Center Virtual Machine Manager, and the answer is yes.

Having a few hundred VM´s and all of them having the same name of the vhdx as the template might not look so good.

So how to solve this then, first of is when deploying new VM´s you should change the name and that can only be done in the VMM GUI when deploying to a host and not to a cloud. Notice that I create the VM from the template in the library view of the console.

Screen Shot 2014-01-20 at 12.20.07

When using this way the console automatically fills in the guest os name. When creating a VM from a template in the VM´s and Services view that has to be filled in manually.

Screen Shot 2014-01-20 at 12.22.27

So how to get the name of the VM also on the vhdx that holds the VM´s operating system, as I described above, you have to select deploy to a host and not a cloud (of course, when the VM has been created it can be updated with a cloud)

Screen Shot 2014-01-20 at 12.24.29

Then when you come to the configure settings view in the wizard, the option to change the vhdx name appears,

Screen Shot 2014-01-20 at 12.32.54

Surely you find that having vhdx that has the same name as the VM instead of the generic library vhdx name of win2012-std.vhdx more suitable?

In the next post I will show you how to change the names of the disks on already deployed VM´s.

 

Categories: Hyper-V, SCVMM, Virtualization Tags:

VMM Configuration Analyzer for 2012 R2

January 17th, 2014 No comments

In the upgrading of a VMM 2012 Sp1 to R2 I wanted to test and run the Configuration Analyzer. When clicking on the link from the VMM R2 GA media you should be observant that it points you to the wrong place though, as you can see on the following screendump there is a link on the splash screen.

Screen Shot 2014-01-17 at 09.59.27

And when pressing that link you will arrive at the following site, which is wrong! So do not start downloading the stuff from this as these files are for the VMM 2012.

Screen Shot 2014-01-17 at 11.04.08

The right site is at the following link:  http://www.microsoft.com/en-us/download/details.aspx?id=41555 and looks like this, do also notice that it is an analyzer for the whole System Center suite so you can do analyzing of all your different SysCtr servers.

Screen Shot 2014-01-17 at 11.05.18

You can also at this technet site read more about how it works and what prerequisites you have to install first.

Categories: SCVMM, Virtualization Tags:

SCVMM VM property dialog crash console with missing vhd(x)

January 14th, 2014 No comments

Today I was at a customer and they had an interesting error in their virtualization environment with Hyper-V 2012 and SC VMM 2012 Sp1 (yes I know, it is not R2 but we are working on it). One of their Hyper-V hosts had a hardware memory failure which lead to the host crashing and the VM´s restarting on other hosts..

during this the VM´s that was on that host got an error in the VMM db, looking and handling the VM´s from Hyper-V manager or failover cluster manager was no problem. Every time we tried to refresh the VM´s showed the following error and the job did not succeed.

Screen Shot 2014-01-14 at 14.36.51

And when we tried to look at the properties on the VM from VMM the console just died, and that happened every time..

Screen Shot 2014-01-14 at 14.28.50

So how could we find the VM´s that was suffering from this, well PowerShell could be used and with the following we could get the amount of VM´s and also easily get a list of the VM´s names.

Screen Shot 2014-01-14 at 13.26.15

So how could we fix this then,

There is a cmdlet in VMM with a parameter that can be used,  Remove-SCVirtualMachine -Force , this will remove the VM but not the virtual hard disk as it cannot find it..

Screen Shot 2014-01-14 at 16.20.21

But because we want to keep the VM we will do a bit of a workaround

  1. Stop the vm in VMM  by Stop-SCVirtualMachine own01  (even if the vhd(x) is not seen by VMM it will shut down the actual VM)
  2. Remove the VM from the cluster in Failover cluster manager or with powershell (this will only remove the cluster instance but not the actual VM)
  3. Start the VM in Hyper-V manager or with PowerShell  Get-VM own01 -ComputerName HV01 | Start-VM
  4. Remove the VM from the VMM with Powershell using the -force  Get-SCVirtualMachine own01 | Remove-SCVirtualMachine -Force (as I have removed the VM from the cluster VMM cannot find it and delete the vm´s xml file etc)
  5. Add the running VM to the cluster again with hyper-V PowerShell and failover cluster powershell using Get-VM own01 -ComputerName HV01 | Add-VMToCluster (Get-Cluster HVCL30)
  6. refresh VM´s in VMM and see that now the own01 vm can open properties

The reason I start the VM after removing it from the failover cluster is that VMM should think it is in stopped state, because that makes it easier to remove! And as in Hyper-V 2012 I can add a running VM to a cluster I do not have to keep the VM shut down during the whole process but just to get it into the right state in VMM :-)

Not the easiest way but hey who had said that VMM was self-healing :-P And yes we are in the process of upgrading to R2 and hopefully this error will not reemerge in that version….

 

Creating Hyper-V 12 R2 Cluster from Windows Server 12/VMM

January 10th, 2014 1 comment

I got a question about an error that occured when creating a Hyper-V 2012 R2 cluster from VMM 2012 R2 and the errorlog stated the following:

“Error (25325) The cluster creation failed because of the following error: An error occurred while performing the operation.. “

In the troubleshooting I found that the VMM 2012 R2 was running on a Windows Server 2012 Standard (which is fully supported). But as VMM uses the failover cluster cmdlets from the OS where installed it fails creating the R2 cluster as it is not supported to manage Windows 2012 R2 from a Windows 2012.

looking at the technet article regarding Server Manager it has a good table about support:

Screen Shot 2014-01-10 at 13.53.35

 

I have done some upgrades from VMM 2012 SP1 to 2012 R2 and have always in that process changed the operating system first to the latest version so this issue has not appeared for me before.

Testing to create a Hyper-V 2012 R2 cluster from a windows 2012 failover cluster manager gives the following error :

Screen Shot 2014-01-10 at 14.12.35

Categories: Hyper-V, SCVMM, Virtualization, Win2012 Tags:

Make running VM highly available in VMM 2012 R2

December 20th, 2013 No comments

So I was helping a customer to migrate a VMware VM to their Hyper-V environment that is managed with System Center VMM, As I described in an earlier post I had some things that I did not like in the built-in v2v conversion that is part of the VMM.

In this migration I used Double-Take Move and this is a really nice software from Vision Solutions that allows you to migrate a running VM and will only get a few minutes downtime during the failover :-). The great thing is that the VM is replicated to the hyper-v host directly and you get a synthetic NIC and also a VHDx virtual disk.

There are though some small things that need to be considered and Double-Take does not do the whole part when used separately, when using it with Vision Solutions system center integration toolkit we can automate these things too, but for migrating just a few VM´s that is a bit of overkill. So what do we need to take care of,

  • DT does not set VLAN on the nic for the migrated VM, that can be done during the replication in VMM when the newly provisioned VM appears there and set the right vm network and bandwidth etc.
  • DT does not make the VM highly available during the migration, it can be deployed on the Clusterstorage volume though.
  • DT does not remove VMware tools during the migration so that has to be cleaned up after.
  • DT does not update/install the Hyper-V integration components.

So now to the main focus for this article, when the VM has been migrated to Hyper-V, how do I configure it to be highly available? When looking in the properties of the VM on VMM that option is greyed out

Screen Shot 2013-12-20 at 12.56.41

And trying to add it through the PowerShell cmdlets in VMM gives the following error message:

Screen Shot 2013-12-20 at 14.50.46

So the way to do it is with the Hyper-V and failover cluster cmdlets instead:

Screen Shot 2013-12-20 at 14.58.34

And then when refreshing the VM in VMM you can see that it is now highly available :-)

Screen Shot 2013-12-20 at 14.21.48

The workaround option that is available in VMM to be able to make the VM highly available is to do a Live Storage migration to another CSV Volume/SMB share and in the wizard check the box for making it highly available but that involves file copying and goes painfully slower than the Add-VMToCluster on the running VM that already resides on a shared storage volume.

Screen Shot 2013-12-20 at 15.36.05

And this also (at least in my test environment) creates a copy cluster resource that has to be cleaned up manually cause the real one is running..

Screen Shot 2013-12-20 at 15.53.40

Categories: Hyper-V, SCVMM, Virtualization, Win2012 Tags: