I logged a call with VMware Support. It turned out that this is a issue with vCenter Server 5.1, and has been fixed with 5.1.0.B . We will give ist a try, and hope that the upgrade runs smooth
↧
I logged a call with VMware Support. It turned out that this is a issue with vCenter Server 5.1, and has been fixed with 5.1.0.B . We will give ist a try, and hope that the upgrade runs smooth