VMware's upgrade advisor still states that vCenter 4.0 & ESX 4.0. Does anyone know when a vSphere compatible version of View will release? Also, does anyone know:
If I upgrade to vSphere will my current View Manager continue to function connecting clients to VMs or would the upgrade render View inoperable?
I assume that upgrading to vSphere would cause Composer to be unable to create new pools, could anyone verify?
Any thoughts on what other negative impact upgrading to vSphere would have on a production View environment?
>VMware's upgrade advisor still states that vCenter 4.0 & ESX 4.0. Does anyone know when a vSphere compatible version of View will release? Also, does anyone know:
View 4.0 is in beta now, but VMware won't comment of future releases
If I upgrade to vSphere will my current View Manager continue to function connecting clients to VMs or would the upgrade render View inoperable?
I wouldn't upgrade until View4.0 is officially supported. If using linked clones it will not work.
I assume that upgrading to vSphere would cause Composer to be unable to create new pools, could anyone verify?
exactly.
Any thoughts on what other negative impact upgrading to vSphere would have on a production View environment?
My thoughts are until it is supported, wait. Whatever issues that may arise using View 3.x on a vSphere4 environment will come down to a non-supported enviornment.
>VMware's upgrade advisor still states that vCenter 4.0 & ESX 4.0. Does anyone know when a vSphere compatible version of View will release? Also, does anyone know:
View 4.0 is in beta now, but VMware won't comment of future releases
If I upgrade to vSphere will my current View Manager continue to function connecting clients to VMs or would the upgrade render View inoperable?
I wouldn't upgrade until View4.0 is officially supported. If using linked clones it will not work.
I assume that upgrading to vSphere would cause Composer to be unable to create new pools, could anyone verify?
exactly.
Any thoughts on what other negative impact upgrading to vSphere would have on a production View environment?
My thoughts are until it is supported, wait. Whatever issues that may arise using View 3.x on a vSphere4 environment will come down to a non-supported enviornment.