I first thought this an error or setup issue, but we have identified the following weird scenario:
8 Hosts in a cluster, all powered on, our floating linked clones work like a charme, closed desktops get redeployed and all is fine.
Once we enable DPM we start seeing issues with linked clone reprovisioning.
The error we see on the VMware View server is:
Provisioning error occured for Machine vdc-desk-012: Cloning failed for Machine
Next is an info that the desktop get's deleted
Once we poweron all hosts again and restart provisioning all is fine again.
Anyone else seeing the same behaviour, did I miss something?
So View is not "aware" of DPM and can choose any host to start provisioning on, I would recommend not to use DPM with View at the moment or if its required you need to script around it somehow.
// Linjo
Hi Linjo,
is that somewhere documented or only knowledge by test? Is there a KB article or something similar?
View is the ideal usecase for DPM, so I'm a bit confused if view has issues with DPM, especially as this customer had no issues with vSphere 4.1 and View 4.x?
Thanks
Yves
Just from my own experience, not sure if its documented somewhere. If you want the official answer you probably need to open an SR.
// Linjo