Results for category "RollUP"

Update Rollup 3 for System Center 2012 Service Pack 1 Released

As mentioned on the last post, We have Rollup 3 for System Center 2012 SP1.

http://support.microsoft.com/kb/2836751

 

Lot many issues got fixed specific to SCVMM. Here is the list of issues which got fixed with this rollup.

 

Issue 1

You receive an invalid prefix length error and cannot set migration subnets if the prefix length is not between 4 and 30 characters for IPv4 or between 64 and 126 characters for IPv6.

Issue 2

Migration subnets for cluster and cluster nodes must be read-only.

Issue 3

Virtual Machine Manager (VMM) cannot take any action on Recovery Virtual Machine (VM) post-failover without reverse replication.

Issue 4

In some cases, a virtual machine on an SMB file share that is registered by using a NetBIOS name on a cluster will be in an unsupported cluster configuration state in VMM. This problem may occur even though the virtual machine is healthy and running. Additionally, the virtual machine status cannot be updated after that.

Issue 5

The virtual machine refresher does not correctly update the state of the virtual machine even after an unsupported cluster configuration issue is corrected.

Issue 6

In a bare-metal setup, the VMM service crashes when an out-of-range IP address is specified.

Issue 7

Every time DRA Initialize occurs in the VMM service, a database corruption exception is received.

Issue 8

You receive an “Unable to connect to the VMM DB” exception when you try to publish host and virtual machine network data to the SQL Server Reporting Service.

Issue 9

When you try import a Linux template from VMware in Virtual Machine Manager 2012 Service Pack 1, you receive error 22723.

Issue 10

The Get-SCVirtualMachine cmdlet does not return virtual machines by their IDs when the virtual machines contain clustered pass-through disks.

Issue 11

A user cannot set the domain name in Service Setting.

Issue 12

The VMM service crashes intermittently.

Issue 13

The VMM ID registry subkey value is set to a null value after Update Rollup 1 is applied.

Issue 14

This update fixes some UI text issues in the Virtual Machine Manager 2012 Service Pack 1 console for Disaster Recovery and for the HRM Azure Service.

Issue 15

This update fixes some reports that are not working with SQL Server 2012.

Issue 16

If a virtual machine has a static IP address, Test Failover does not set the IP address on the test virtual machine.

Issue 17

Virtual machine snapshot operations might fail if multiple snapshots are restored at the same time and have the same name.

Issue 18

The VMM server might crash when you create a virtual machine template from a virtual machine that has a previous failed task checkpoint data.

Issue 19

Logical unit numbers (LUNs) for EMC storage cannot be assigned to a cluster in VMM.

Issue 20

The VMM service crashes if a VMWare cluster or host is added by using a local root or administrator account.

Issue 21

Some log information is recorded multiple times in the guest log file.

Issue 22

This update fixes some performance issues in a bare-metal installation.

Issue 23

The placement of the Network Load Balancing (NLB) clusters in a network environment does not work for NLB load balancer and nested host groups.

Issue 24

The VMM service may stop while VMWare vSphere 4.1 is updated.

Issue 25

If Test Failover is initiated while VMM is restarting, the recovery side of VMM crashes.

 

SCVMM 2012 Sp1 – Building a priviate cloud

I am very excited to let you all know that I am trying out a private cloud with SCVMM 2012 Sp1. Its almost three weeks I am playing around SCVMM 2012 Sp1. Still trying to understand the concepts and features. In the initial phase, I was in the assumption that configuration is something which I can do easily. Unfortunately, Fabric configuration made me into panic mode having sequence of issues. At-last, I landed safely by fixing all issues.

Another important note is on Roll-up 1. As you are aware, System Center 2012 Sp1 got a new Roll-up1 which got released on Jan 9th 2013. This rollup is intented to fix the below issues. I am yet to apply this roll-up, but scheduled for this weekend.

 

Virtual Machine Manager (KB2792925 – Console; KB2792926 – VMM Server)

Issue 1

When a logical unit number (LUN) is unmasked on an iSCSI array, the VMM service may crash.

Issue 2

When a node is put in maintenance mode, virtual machines in the cluster change to a status of “Unsupported Cluster Configuration.”

Issue 3

When an add-in that uses multiple DLL files is imported into the VMM console, the add-in is not imported. Additionally, you receive the following error message:

Add-in cannot be installed

Issue 4

When an add-in is imported into the VMM console on a server that is running Windows Server 2008 R2, the add-in is not imported.

Issue 5

When an add-in is imported into the VMM console, the console may crash.

Cheers !

Shaba