With the following workflow we can see an entire upgrade cycle of a baseline. With this, when is the second Wednesday of every month we will upgrade PRE to check if all updates applied to Hyper-V works fine. To start with this we synchronize SCVMM for download all new updates from Update Server and we will notify managers that we will upgrade all Hosts groups for PRE. Done that we will analyze what updates are necessary for our hosts and we will add to the Baseline. Next week we start to upgrade one single host, member of a cluster, in a Hosts Group starting a Maintenance Mode and Scanning and Remediating it. If some update or the hyper-v host has a problem we will check which the cause is and we will solve it. If it finish fine we do the same for the others hyper-v hosts in the same cluster, if it´s ok then we do a maintenance mode and a scan and remediate for every one of all hosts groups for PRE. When we finish for all hosts groups in PRE and all is ok we will start with PRO in the next week. If some update or host has a problem we will check which the cause is and we will solve it.

After upgrade SCVMM 2012 R2 CU3 to CU4 I have seen in the VMM console on the connector between SCVMM and OpsMgr 2012 R2 CU4 an incompatibility with the Management Pack version and the SCVMM version.

Management pack Microsoft.SystemCenter.VirtualMachineManager.PRO.Library version 3.2.7672.0 is incompatible with this version of Virtual Machine ManagerManagement pack Microsoft.SystemCenter.VirtualMachineManager.PRO.V2.Library version 3.2.7672.0 is incompatible with this version of Virtual Machine ManagerManagement pack Microsoft.SystemCenter.VirtualMachineManager.Pro.2008.Library version 3.2.7672.0 is incompatible with this version of Virtual Machine ManagerManagement pack Microsoft.SystemCenter.VirtualMachineManager.Library version 3.2.7672.0 is incompatible with this version of Virtual Machine ManagerManagement pack Microsoft.SystemCenter.VirtualMachineManager.2012.Discovery version 3.2.7672.0 is incompatible with this version of Virtual Machine ManagerManagement pack Microsoft.SystemCenter.VirtualMachineManager.2012.Monitoring version 3.2.7672.0 is incompatible with this version of Virtual Machine ManagerManagement pack Microsoft.SystemCenter.VirtualMachineManager.2012.Reports version 3.2.7672.0 is incompatible with this version of Virtual Machine ManagerManagement pack Microsoft.SystemCenter.VirtualMachineManager.PRO.V2.HyperV.HostPerformance version 3.2.7672.0 is incompatible with this version of Virtual Machine ManagerManagement pack Microsoft.SystemCenter.VirtualMachineManager.Pro.2012.Diagnostics version 3.2.7672.0 is incompatible with this version of Virtual Machine ManagerManagement pack Microsoft.SystemCenter.VirtualMachineManager.2012.Discovery version 3.2.7672.0 is incompatible with this version of Virtual Machine Manager

Seeking on internet I saw entries talking to change a key in the registry of the SCVMM server. In my case this key was correct and I didn´t it.

Yesterday I have been upgrading to CU4 for SCVMM 2012 R2 CU3 console and I found the following error when I open powershell from VMM Console:

Get-SCVMMServer : The type or name syntax of the registry key value IndigoTcpPort under Software\Microsoft\MicrosoftSystem Center Virtual Machine Manager Administrator Console\Settings is incorrect.Ensure that the type of value name is correct; the name is not empty, contains only valid characters and is less than255 characters.At line:1 char:409+ … $vmmserver_VAR=Get-SCVMMServer ServerNameXXXXXX -UserRoleName ‘Administrator’;+ ~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [], CarmineException + FullyQualifiedErrorId : Microsoft.VirtualManager.Utils.CarmineException

To solve the problem I have delete under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Administrator Console\Settings the key IndigoTcpPort (Reg_SZ) and I did a new one with the same name but to be reg_Dword and with a decimal value of 8100, this is:

Sometimes when I´m doing a deployment of various VM via scripting in my test lab and some thing fail for some reason as my smb file share are out of space or something like this the ip assigned to the machine is blocked… you have not the new virtual machine and you loose one ip from the pool.

The solution to that situation is the following:

First of all execute from PS Get-SCIPAddress

Second we seek the name of the virtual machine bad deployed and we copy the ip address.

Third we execute the following command with the ip address that we want to liberate $ip = get-scipaddress -IPAddress “100.64.35.122”

Fourth we execute the command $ip | revoke-scipaddress to recover the ip.

Also, is more easy to do from the GUI… then go to Fabric Pane/Logical Networks and there over the Pool where you are deploying vms do right click and push on Inactive Address. Select All and push Release. Easy no? 🙂

These months I´m on a project of Private Cloud and I´m working now doing offline images with DISM. A mate told me about this script and here I share with all because is very easy toconvert from WIM to VHDX 🙂